F-Line to Dudley
Senior Member
- Joined
- Nov 2, 2010
- Messages
- 9,196
- Reaction score
- 9,002
Telling Metro-North to fuck right off, Amtrak's in charge of dispatching now.
No, I'm serious. The only thing preventing Amtrak trains from running faster than they are today along significant stretches of the New Haven Line (significant enough to shave 20 minutes off the trip) is the fact that Metro-North simplifies dispatching complexity by forcing all trains to run at the same speed on Metro-North track (which naturally means "the same speed as the slowest train.")
No, you're not serious.
Metro North is a lot of things, and stubborn is one of them. But there is not much they can do about their dispatching. The New Haven Line is already functioning as 3 lines in one: a Stamford-west local making all stops, a Stamford-east local making all stops, and a GCT-NHV limited going the whole distance in fewer stops. 3 full-blast schedules all at once. Plus all the co-mingled Danbury, Waterbury, and SLE trains that spend a limited part of the trip on the line. At peak load all 4 tracks including the express ones are chock full of commuter trains going all directions at more or less the same baseline speed. The signal blocks are incredibly tight. There is already higher density of crossovers than nearly any other stretch of track in the country. There flat-out are not a lot of passing opportunities to be had.
Could it be better? Yes. They haven't exactly been the most cooperative outfit in the world at optimizing dispatching performance. Are there opportunities on the off-peak for better passing opps when the tracks are less-crowded that could gain Amtrak a lot more all-day slots? Yes. And they need to be pushed towards that.
But no...this is not a problem you're going to fix by barging into the control room and telling them there's a new sheriff in town. At peak load it is not possible to juggle that many simultaneous movements in a way that's going to give somebody a clear path to blast by at 125 MPH. The track-switching dance ends up inducing too many micro-delays as limiteds cut in front of locals and back again. The ripple effect ends up degrading every schedule all the same. So they don't try to squeeze blood from stone...they impose the speed limit to keep it orderly.
And no, the brute force method of telling them it's Amtrak's way or the highway does no better here when MNRR is far and away the predominant user of the line in total trains, ridership, and $$$ poured into it. This is the single most operating-profitable segment of the entire NEC. It's a peculiar at-best and insane at-worst argument to tell the primary breadwinner (who, lest we forget, owns the tracks) to take a seat and give up schedule slots it's selling out standing-room-only. Especially when considering what ridership they're likely to be pulling into Penn when East Side Access opens up some terminal capacity for commuter trains. It's not ideal, but it makes practical sense. They don't restrict speeds because they want to be dicks to their partners...they restrict them because they can't do their own jobs running an on-time railroad if every peak-hour trip has to be gamed out with 99 different passing scenarios. MNRR's on-time performance is just about the gold standard for North American commuter rail, so it's tough to find fault with them for that choice.
Amtrak will gladly concede this point if they can make up for the savings they don't get here with savings achieved elsewhere. Which is why they're putting the bucks into more 150 MPH territory in NJ and DE now and stamping out capacity crimps on either side of MNRR. Those are easier-won gains than what they'd achieve trying to design a magic bullet signaling/dispatching that speeds up a stuffed New Haven Line. The only real legit beef they've got is that MNRR needs to treat on- and well off-peak hours differently and give Amtrak more passing leeway when the express tracks are less crowded. That is not too much to ask.
FWIW...there is no way around this problem unless they can build the highly improbable Westchester-Danbury-Waterbury-Hartford inland bypass. The also-improbable LIRR + under-Sound tunnel hits exactly the same commuter rail congestion for almost exactly the same distance...and LIRR is not in MNRR's league when it comes to on-time dispatching. Given the odds of any of the alternatives working out, I'd learn to love the New Haven Line as it is and not waste too much time lamenting what the laws of physics won't let it be.