August Monthly Performance Report

Amtrak Unlimited Discussion Forum

Help Support Amtrak Unlimited Discussion Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Status
Not open for further replies.
No disruptions and pretty good OTP for the Zephyr for years, and lots more foot traffic to Denver Union Station -- this IMO explains why the Zephyr is way up.

The LSL is finally bouncing back from the Norfolk Southern Autorouter disaster in winter 2014-2015. This tells you how long it takes ridership to come back after something like that. The problem ended in Spring 2015; the ridership came back in Fall 2016. So about 18 months, I guess.

Worth noting the next time a class I delays Amtrak repeatedly. They should be socked with penalties for lost revenue for *18 months*.

(Futurology follows:)

I'm not expecting a future bounce-back in ridership from future high oil prices, since I think substitution will keep oil prices low-ish. But oil prices won't get much cheaper than this, ever, because producers can't afford to produce more cheaply As gas cars are replaced by electric cars, it will get cheaper to drive, but it won't get cheaper to fly. We all know that in the short-haul market it isn't really the price of driving which causes people to switch to trains -- it's congestion and the *unpleasantness* of driving -- and that won't change. The rail advantage over airplanes in the short-haul market due to the overhead (airport time) and unpleasantness of short air travel will remain. In the long-haul rural market, we may see some weakness due to an increase in road trips, but "sleep while you travel" will still be a selling point, as will the avoidance of driving through urban congestion. Accordingly, I think the ridership/revenue of these coming months is a decent representation of future ridership/revenue for several years *without service improvements* such as reliability and speed. (Some service improvements are already under construction.) The exceptions are long-haul rural daytime and "3 am station stop" service, which I expect to get weaker ridership, but these are not particularly strong Amtrak markets already.
 
Last edited by a moderator:
With only one month left in the fiscal year, I reran my projections which attempt to back out the overhead (based on the latest data we have on the overhead, which is years old) to get the profit/loss based on *direct costs*. (To do this a month early, I used variances between last year and this and just assumed September would have the same numbers as last year, which is as good as I can do until the September report comes out.) To be clear about this, if a train is profitable based on *direct costs*, then cancelling the service would mean Amtrak loses more money every year. These trains contribute to Amtrak's bottom line. They just don't contribute enough to cover very much overhead.

My estimates do not account for any possible overhead reallocation which occured due to the Silver Star having its dining car removed. If it had its overhead costs reduced, then that means that *the Silver Star is actually doing significantly worse than my estimates*. If that overhead was allocated elsewhere, then I*other trains are actually doing better than my estimates*.

Furthermore, if Amtrak has massively reduced overhead in the last few years (which would be a good thing), then all the trains are individually doing worse than I am estimating. If Amtrak has substantially increased overhead, on the other hand (...which is more likely due to inflation), all the trains are doing better than I think.

My current estimates, and they remain estimates, are that:

-- The Auto Train is generating about $38 million / year to help cover overhead

-- The Silver Star and Silver Meteor are each generating about $15 million/year

-- The Palmetto is generating about $13 million/year

-- The Crescent seems to have gone into the black, generating about $3 or $4 million/year. (Interestingly, this matches with a projection I made last year for when it would become profitable based on simple averaging of trends since 2012.)

-- The Lake Shore Limited is still generating about $2 or $3 million/year

-- The Coast Starlight seems to have gone into the black, generating about $1 or $2 million/year. (Interestingly, this matches with a projection I made last year for when it would become profitable based on simple averaging of trends since 2012.)

-- The Empire Builder is probably fluctuating a bit short of breakeven. My raw model says $1-2 million in the red, but I know its costs increased because BNSF is getting its OTP payments again which it wasn't before, so it's probably $3 to $6 million in the red. (My projection based on trends says it should be in the black in in 2017.)

-- The Capitol Limited is still in the red by $4 to 5 million. I believe the Cap generates substantial income on other trains through connecting traffic, so in fact it probably would cause Amtrak to lose more money if it were cancelled.

-- The CONO is still in the red by $3 to $4 million

-- The Cardinal is still in the red by $3 to 4 million. (Same projection as used for Crescent and Coast Starlight says it's in the black in 2018, updated says 2020, but if it were daily it would be profitable today.)

-- The SWC is still in the red by $6 to $7 million. (Same projection as used for Crescent and Coast Starlight says it would be in the black this year, but I was wrong. Updating the projection gives 2020.)

-- The Texas Eagle is still in the red by $6 to $7 million. (Same projection as used for Crescent and Coast Starlight says it's in the black in 2019, updated projection says 2021.)

-- The CZ is in the red by $8 to $9 million. (Same projection as used for Crescent and Coast Starlight says it's in the black in 2018.)

-- The Sunset is in the red by $11 to $12 million. (Same projection as used for Crescent and Coast Starlight says it's in the black in 2021, but if daily, by 2019.)

The key takeaway from this is how much better every one of these trains is doing financially than they were in 2012.

Other conclusions I take from this:

-- As I've said before, nearly all of Amtrak's operating subsidy goes to overhead. More trains == more gross profit to cover the overhead.

-- The Viewliner dining and sleeping cars, *if they ever deploy*, will mostly cut the running costs and add to the revenue of trains which are already profitable before overhead.

-- The entirety of the "subsidy for running particular trains" on the long-distance network (as opposed to "subsidy needed to have a train system at all") goes to the four Western Transcons, the Texas Eagle, the CONO, the Cardinal, and the Capitol Limited (which is almost certainly generating enough revenue on connecting trains to cover its subsidy).

-- The EB, CZ, and SWC should be profitable before overhead around 2018 just based on trends.

-- The Cardinal would be profitable before overhead right now -- about $4 to $5 million in the black -- if it ran daily. (This assumes costs multiply by 1.5 and revenues multiply by 7/3.) If CSX decided to charge an extra $4 million/year for the "privilege" of running daily, it would *still* be worth it to run daily. The increased profits of $5 - 6 million / year are certainly enough to make a rational pitch for an RRIF loan to build $30 million in improvements if that's what it takes to run daily.

-- A daily Sunset Limited should be profitable before overhead around 2019.

-- This would mean the only long-distance trains with subsidies for direct costs would be the Texas Eagle, CONO, and Capitol Limited -- and the Capitol Limited is generating connecting traffic sufficient to cover iits subsidy.

At this point the political pitch to Congress has to be "Basically all the trains make money, just not enough to cover overhead. Cutting service will cost you more money; adding service will cost you less money. We're just asking you to cover our overhead costs." I think this pitch should be hammered hard, because it makes it very hard for them to yammer about "money-losing trains". Congress is not subsidizing the operation of the trains. They're subsidizing the ticketing system and the cost of mainting stations and the central dispatching offices and the cost of catching up on deferred maintenance by the former private railroads. They're subsidizing the equivalent of the airports, the air traffic control system, the road maintenance crews, the highway patrol.
 
And I took a look at the delay charts!

-----

On slow orders:

Most of the Class Is are doing pretty well on slow orders now. UP and CP are outstanding. CN and BNSF are worse. CSX is middle of the pack!

CSX is still not good enough, as CSX slow orders remain the top cause of delays on Carolinian and Virginia Regionals, but it's improvement.

I am surprised that CSX is starting to behave itself better, particularly with slow orders (which used to be their big issue).

BNSF is within striking distance of actually meeting the PRIIA delay requirements, but it's allowed slow orders to accumulate on several routes.

CN remains bad all around.

Amtrak slow orders are the cause of major delays on the trains running through Schenectady. Hopefully the double-tracking will open soon!

The Wolverine is delayed by slow orders in Michigan track, undoubtedly due to construction, which will hopefully complete soon.

The Silver Star and Silver Meteor and Auto Train are being delayed on SunRail by slow orders and signals, probably more construction.

Metro-North has slow orders on its part of the NEC. Construction?

The Vermonter continues to have slow orders in Massachusetts on the MaDOT section (seriously, didn't they finish construction?).

The Vermonter is also having slow order delays on NECR. Not cool.

NM RailRunner is having a problem with slow orders as well, probably due to a funding shortage.

----------------

On freight train (and other train) interference:

CP is the standout, with near-perfect dispatching (under 100 minutes / 10K train miles)

BNSF is pretty good, not far behind CP (around 200 minutes per 10K train miles)

The other class Is are still not acceptable but getting better.

UP is worse than BNSF (around 300-400 minutes per 10K train-miles)

CSX is a little worse than UP (around 300-400)

CN is worse than that (500-600 minutes)

and NS is worst of all (550-650 minutes), although this is down from last year. They have not recovered from their Autorouter disaster.

They all do seem to be trying to do better. The performance of BNSF is about what I'd expect, and UP is in line with previous years, but CP's *exceptional* performance is unexpected.

Freight train interference on CSX is still the major cause of delays on Auto Train, Empire Corridor, and Palmetto.

CN is bad all around with both slow orders and freight train interference on every route and clearly hasn't changed its behavior.

NS ihas one major problem: they need to figure out how to stop causing freight train interference on the Chicago corridor. You'd think they'd just pay for South of the Lake out of pocket to get Amtrak out of their hair! If the contracts were set up right ("We clear out a high-speed two track right of way for passengers, give it to you, and you don't run passengers on our tracks in this area again") it would be money well spent. (I think to avoid crossing traffic they'd have to put the high speed tracks on the east side of the ROW and move Park Manor Yard operations to their new Englewood yard.) Apart from that area NS is doing OK, but that's a mess.

UP is having freight train interference on the Sunset Limited and Texas Eagle routes. I'm guessing they won't want daily service until they build more double track (does anyone know how much of those routes is still single track?). On most of their other owned routes the major delays are *passenger* train interference, which means the states need to beuild the double and triple track.

The Silver Star and Silver Meteor are being delayed on TriRail by freights (!) Huh?

Metro North continues to run commuter trains ahead of interity trains on the Empire Corridor, which is not very excusable given the number of tracks available. The second largest problem there is RTE, which if I remember correctly, means that there's a communication problem between Amtrak and Metro-North where Amtrak engineers and conductors are not getting the Metro-North paperwork promptly. THIS should be fixable and it's worth making a substantial effort to fix it.

(RTE and signals are also causing delays on trains on NS out of Chicago on the Chicago Line. Surely they'd love to fund South of the Lake and get this entirely out of their hair?)

Commuter train interference is more understandble on the MBTA, Metra, and Metrolink/Sounder, where they still have a lot of single track.
 
The Wolverine is delayed by slow orders in Michigan track, undoubtedly due to construction, which will hopefully complete soon.

NS ihas one major problem: they need to figure out how to stop causing freight train interference on the Chicago corridor. You'd think they'd just pay for South of the Lake out of pocket to get Amtrak out of their hair! If the contracts were set up right ("We clear out a high-speed two track right of way for passengers, give it to you, and you don't run passengers on our tracks in this area again") it would be money well spent. (I think to avoid crossing traffic they'd have to put the high speed tracks on the east side of the ROW and move Park Manor Yard operations to their new Englewood yard.) Apart from that area NS is doing OK, but that's a mess.

RTE and signals are also causing delays on trains on NS out of Chicago on the Chicago Line. Surely they'd love to fund South of the Lake and get this entirely out of their hair.
If NS want to get rid of most of this problem. South of the Lake passenger tracks would do it.

I would be totally amazed if NS would build a two track main on there own dime. However I am pretty sure Michigan would be interested in buying the track work when it's done. Just not sure there enough of a benefit for NS to get the trains out of there hair, and if they do nothing at some point a government will get it done.
 
If I were actually at NS I'd set up a deal where:

(1) NS pays for and assists in the completion of the EIS and all that stuff

(2) NS pays to clear out the right-of-way (relocates utilities with easements, relocates its own tracks where needed, etc.), including room for future catenary

(3) NS donates the right-of-way and the disused bridges

(4) The states and Amtrak pay for and build the actual tracks (and catenary, eventually), and most importantly bridges.

(5) The states and Amtrak agree not to run passenger trains on the NS tracks after moving (with penalties payable if they do)

(6) The right-of-way reverts to NS if Amtrak doesn't manage to build the new tracks and move its trains onto them in some specific number of years.

This gives Amtrak and the states a kick in the pants to get the construction done promptly, because if it doesn't get done promptly the land reverts. While paying only a small fraction out of pocket (the utility relocation) and donating land which wasn't making them any money and was actually costing them money in taxes (it has value but it's essentially speculative). The reason I would do the utility relocation out of pocket is that it can drag on forever and it has a very long lead time, and NS is in the best position to get it started ASAP.

My assumption here is that as NS I want the passenger trains out of the way in this segment as soon as I can, though without paying too much.
 
Last edited by a moderator:
Some belated comments on the ridership stats in the August monthly report. In the Ticket Revenue and Ridership section for the state supported corridors, it notes:

State Supported ridership was 7% below budget but 2% above last year.

The budget projections for the state corridor were rather over optimistic if ridership was up 2% but still fell 7% short of the budget. Was someone thinking that one or more of the corridor major upgrade projects was going to finally be completed by August 2016?

Summary stats from the August 2016 monthly report by category for the month and first 11 months of the fiscal year compared to prior years.

Ridership and Revenue summary for the month of August compared to 2015:

System: ridership +2.3%, revenue: +3.1%

Acela: ridership -1.0%, revenue: +8.8%

NE Regional: ridership +3.5%, revenue +3.7%

State supported corridors: ridership +1.9%, revenue -0.8%

LD trains: ridership +3.7%, revenue +1.5%

Ridership and Revenue summary for the YTD from October to August:

System: ridership +1.0%, revenue: -0.7%

Acela: ridership 0.1%, revenue: +0.6%

NE Regional: ridership +2.2%, revenue -0.3%

State supported corridors: ridership -0.2%, revenue -0.0%

LD trains: ridership +3.6%, revenue -1.3%

Despite weaknesses and drops in ridership on a number of state corridors due to track work disruptions, ridership for the first 11 months of the FY is ahead of FY2015. If September ridership held up, system ridership should easily break 31 million for FY2016. We might see Amtrak posting a news release in the next week or so touting the FY2016 ridership numbers.

In the Chief Mechanical Officer report, under the Car Wreck Program for Bear, the plan had 2 planned YTD, but Actuals are 5 for the YTD and in the comments Currently working last Amfleet wreck for a total of 6 cars being returned to service for the fiscal year. So there has been a push to repair wrecked Amfleet cars to get them back into service.
 
Unless there is going to be a full build out of true high speed rail and 60 passenger trains a day i don't see a need for the south of the lake project. I would rather see that money used for buying trainsets and adding actual trains. Lets not forget the point of infrastructure spending. There has been way too much spending without adding amtrak frequecies or new destinations as it is.

Perhaps the plain statistics are a little misleading but i haven't seen anything more than relatively minor delays on the NS since the autorouter fiasco except for maybe an odd day.

Remember the Lake shore is on Csx until cleveland and the michigan trains leave at porter. With the indiana gateway project nearing completion there is plenty of capacity for more passenger trains on this line. I would guess you could probably fit at least 5 to 10 more Amtraks a day with current infrastructure on this line as long as they were scheduled properly. The BNSF and UP in Chicago do ok with full Metra schedules which the NS does not have to deal with. Don't let the freights pull the wool over everyones eyes and say they are busier than they really are. Why do you think the CP looks good dispatching? It's because they don't have all that much for traffic across wisconsin! Easiy could fit 5 daily roundtrip amtraks chicago to st paul tomorrow with current infrastructure. But the freight companies management has people that don't know better think that they are at capacity when they are not anywhere close.
 
Unless there is going to be a full build out of true high speed rail and 60 passenger trains a day i don't see a need for the south of the lake project.
It seems like you must never have ridden on the Lake Shore Limited, Capitol Limited, or any of the Michigan trains. Bluntly.

WE NEED IT. This is THE major source of delays on all of these trains. Ridership will always be suppressed if the trains don't run on time. They will not run on time unless they get their own tracks. Your "relatively minor delays" can still be an hour. If the trains actually ran on time, ridership would blow through the roof, and there would be the demand for even more trains! :)

The reason there is not enough capacity for passenger trains on this line segment even with Indiana Gateway and Englewood Flyover, is because there are more and more and more and more and more freights running on the line -- NS is doubling the size of their freight yard in Englewood (Chicago), you know. In this area, at least through the final approach from the Calumet River to Chicago, passenger trains need tracks which do not have ANY freight trains on them.

BNSF's passenger route in Chicago has three tracks all the way to Aurora, and half the BNSF freight is on the other route, the Chillicothe Line. UP's passenger route from the west, UP-West in Chicago has three tracks much of the way, and due to delays they've been making it more and more of the way. UP's passenger route from the south in Chicago (via Springfield) is being double-tracked at a cost of billions, even while half the UP freight from that direction is on their alternate line from the south.

NS, by contrast, has *one* route into Chicago (no viable alternate line to get to its major yards), with *two* tracks. It needs to have separate passenger tracks. Conveniently, these used to exist and they're just lying fallow along most of the route, so it'll be way way cheaper than the St. Louis - Chicago upgrades.
 
Last edited by a moderator:
This poster does believe that south of the lake is eventually needed but --------- To save costs maybe add one HrSR passenger track to the ROW next to NS's line. That will require the several out of service bridges to be refurbished. Passing would be on the present freight tracks. If NS runs freight on the tracks they must make whole any damage done to the passenger track. AEI and WILD detectors can monitor all traffic on the passenger tracks.

IMO that is much less expensive and if the anticipated traffic at the higher numbers occur then a second track parallel to the passenger track and eventually south of the lake. Then sell to NS parallel tracks.
 
Last edited by a moderator:
This poster does believe that south of the lake is eventually needed but --------- To save costs maybe add one HrSR passenger track to the ROW next to NS's line. That will require the several out of service bridges to be refurbished. Passing would be on the present freight tracks. If NS runs freight on the tracks they must make whole any damage done to the passenger track. AEI and WILD detectors can monitor all traffic on the passenger tracks.

IMO that is much less expensive and if the anticipated traffic at the higher numbers occur then a second track parallel to the passenger track and eventually south of the lake. Then sell to NS parallel tracks.
Why not do a single track with passing sidings every 8-10 miles?
 
Why not do a single track with passing sidings every 8-10 miles?

That is probably a good second step after connecting to the original NS. However with the cost of installing CPs making the passing sidings every few miles might not be that much more costly. Would need as many CPs to NS tracks. Also the sidings can be HrSR capable which NS would not be.

The only problem of following the current ROW is the amount of sub grade work needed to guarantee a low number of times track has to be surfaced. Sub grade work will probably require the use of sheet piling next to NS track to maintain NS's track from sinking.
 
Last edited by a moderator:
The vast majority of the work is subgrade. Bluntly, once you've prepped the ROW, might as well drop double track. And keeping it separate from NS just makes life easier for everyone...
 
Status
Not open for further replies.
Back
Top