Jeff Smith wrote:I'm wondering if some of these service changes (at least concerning Amtrak) will survive this summer's work. What I mean is, will Amtrak find that some of these changes forced on them by emergency repair work actually add to operating efficiency? I.e. will ending some Keystones at 30th St or Newark, turning LD trains at DC, etc., actually improve operations?
Some of the employees have wondered that as well, but consider some of the changes being made. It may be easy to cut a few regional and NJT commuter trains in the summer when there are a lot of people on vacation. However, some of this won't translate into a year round proposal.
WAS can barely handle what they are about to do with 19. They don't have the space or the S&I slots to turn multiple trains. One of the biggest things with 19/20 is where to put the passengers and hasn't been totally resolved. 10 or your top 15 city pairs for the Crescent involve stations north or WAS. Additionally, there is quite a bit of connecting traffic from Albany line. One of the issues is asking passengers to take a train to GCT, shuttle to Penn, take another train to WAS and transfer once again. When you put people through that, it will lead to a loss of revenue. Just think of the sleeping car loss of revenue for those that make the trip. The hope is the extra equipment can capture spill revenue.
The same goes for the Keystones and Albany service. The regional train barely have enough room for their passengers. Taking on Keystone passengers will be problematic in the long term. Additionally, both services are state supported. As may are fond of saying, one seats rides are always the best option where they exist. While I can see a couple of regional trains falling (the ones they are cutting are the usual suspects...the ones that always fall during a disruption), I don't see a future altering the service patterns for a long period of time, particularly when a lot of the business travel returns in full force.