Crazy Transit Pitches

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.
 
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.

And I'm going to point out that he asked what the best way to shave 20 minutes off the trip time was, not an hour or more.

If you increase the average moving speed of Amtrak's trains through the 55.7 miles of track shared with Metro-North by just 20 MPH, the total travel time comes down by 14 minutes. Every Acela is scheduled to dwell for at least 2 minutes in New Haven, and the other 4 minutes can be found lurking in over-cautious schedule padding or over-conservative rounding errors. There's 20 minutes off the trip time, with absolutely zero investment into electronics, steel or concrete.

You're right in that a change of dispatching management is not going to work miracles, it's not going to take an hour off of the trip - but it can be better. I'm pretty confident in my estimation that it can be about 20 MPH average moving speed better.

EDIT: And by the way - even if it can't be 20 MPH average moving speed better, improving the average moving speed by just 10 MPH shaves off 8 minutes, with tighter padding and/or dwell times easily getting that to 10~12 minutes. You'd have to invest elsewhere in the corridor (I'd suggest starting with 165 MPH operation between Warwick and Kingston, and doing something about the curves between Kingston and Westerly to get trains up to 100 MPH through there instead of 90 MPH - but I'm selfish that way) to get the rest of the way to 20 minutes, but it's still a significant portion of the time savings owing to better dispatching practice.
 
Last edited:
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.

Sigh , what don't you understand. The Congestion on the LIRR is on the 2 tracked Main line , FRA/Amtrak plan would use the lightly used Hempstead Branch and abandoned Central Branch ROW thus bypassing the congested area of the network. The Harold Interchange upgrade will eliminate even more congestion along with the Jamaica Interchange upgrade. The rest of the single tracked Main line is being double tracked , so all you have to do is grade separated 17 crossings and build a sound tunnel which can be made into a regional and freight rail tunnel package which would make it easier to sell to Long Islanders and Connecticut people alike. Add in a Eurotunnel car shuttle for a bonus.
 
Idea for improving CR service on Newburyport/Rockport line, as well as warming up riders for a Danvers/Peabody branch and the Blue Line extension.

Phase 1:
Create more local short turns at Beverly, which also hit new stops at the proposed Blue Line stops running alongside the CR line (West Lynn, South Salem) This would be great for DMU service, but it isn't a neccesity.

Build double track up to the tunnel at Salem to allow for train meets.

Phase 2

Run the new local service out to Peabody and Danvers, which are both in need of service and provide great potential for 128 park and ride, as well as reverse commuting to downtown Peabody and the Northshore Mall. This line would hit all the previously implemented local stops.

Phase 3

Extend the Blue Line out to Lynn, and beef up the local trains to 20-30 minute headways. The "local" CR trains could alternate between ending at Danvers and Beverly, allowing for demand at the end to remain strong. A stop at Sullivan Square allowing for transfer to the Orange Line would be huge.


Basically you'd end up with a train (preferably DMU) going:

North Station
Sullivan Square
Chelsea (Hopefully beefed up to a legitimate stop with easier/better bus connections)
Lynn
West Lynn
Swampscott
South Salem
Salem

and then either

Peabody and Danvers (North Shore Mall/128), or Beverly Depot


Seems like a pretty solid schedule that would easily beef up service on the more populous parts of the line, as well as provide an easy outlet for Danvers/Peabody service, as well as being a better feeder for the Blue Line to Lynn. Would be nice to see DMU service to someday.
 
All pretty reasonable, and would make for a well used "Indigo Line" type service. But I'm not sure double tracking Salem Station is enough. You might need to remove that pinch in the tunnel, and that's a whole big fiasco to get done today.

Also, Sullivan Square (for the Orange Line) would need to be shifted west and then you need to triple track the commuter rail there, plus add platforms. It's doable, of course. But is it worth the bustitutions and expenses for it instead of just transfering at North Station?
 
Idea for improving CR service on Newburyport/Rockport line, as well as warming up riders for a Danvers/Peabody branch and the Blue Line extension.

Phase 1:
Create more local short turns at Beverly, which also hit new stops at the proposed Blue Line stops running alongside the CR line (West Lynn, South Salem) This would be great for DMU service, but it isn't a neccesity.

Build double track up to the tunnel at Salem to allow for train meets.

Salem tunnel can't be double-tracked. It's too narrow. What you CAN do, and which they ruefully aren't doing with that over-budget car sink under construction in Salem, is double-tracking the platform. There is room to immediately double the second the tracks emerge from the portal. The station is much more a capacity choke point than the tunnel. It means only one train can occupy the entire stretch between Swampscott and Beverly with the single at high-use/high-dwell Salem making train meets nearly impossible to stage. The tunnel itself takes 2 minutes to clear. It essentially has to be 12 minutes of spacing on opposite-direction meets because the middle station of that stretch is single. Double-up the platform and everything except those 2 minutes in the tunnel are free for passing...smaller than the dwell time at the station. Pausing at the platform for a train to hit the tunnel is imperceptible on the schedule, and they could pack headways way denser.

Even better...if they build South Salem/Salem State U station at the south portal like the North Shore Transit Improvements study strongly recommends both ends of the tunnel have an on-platform dwell time control for staging meets through the tunnel with zero schedule drag. I firmly believe if they fix the single-platform constriction the line is fully equipped to handle all the headways they can possibly throw at it for Peabody, Portsmouth, and increased Rockport service. Assuming the other constrictions like the grade crossings and the sorry state of the movable bridges are taken care of.

Phase 2

Run the new local service out to Peabody and Danvers, which are both in need of service and provide great potential for 128 park and ride, as well as reverse commuting to downtown Peabody and the Northshore Mall. This line would hit all the previously implemented local stops.
Absolutely. Probably gonna have to wait for more money before they can build the new infrastructure to North Shore/Lahey Clinic, but if they wanted to spiff up the mainline today and just funnel the short-turns to a Peabody Sq. stub in the interim it wouldn't cost very much at all to rehab and signal such a short stretch of the active branch + build the separate Peabody platform at Salem station. It would help the bus connectivity immensely, which is why the phasing is attractive and probably would deliver the ridership.

Note: The Danvers branch is gone now. Trail has claimed it. So the twin branches or either/or branches originally scoped out in the study are no longer an option. It can only be Peabody/128 @ North Shore Mall, since that stretch of abandoned ROW is not trailed and has no plans to be trailed (no 95/1 crossing to connect to the trail on the other side, so it's moot). It's also a power line ROW so securing the easement isn't something a trail lobby could do by its lonesome.

Phase 3

Extend the Blue Line out to Lynn, and beef up the local trains to 20-30 minute headways. The "local" CR trains could alternate between ending at Danvers and Beverly, allowing for demand at the end to remain strong. A stop at Sullivan Square allowing for transfer to the Orange Line would be huge.
No on Sullivan. That's the highly constrained stretch of track shared by both Haverhill/Reading and all of the Eastern Route. A stop there destroys the capacity on both mainlines. And would even if you swapped the OL express track for an extra CR track. You don't need it either because Orange @ North Station is only 2 stops away. Have to concede that one as a permanent infrastructure constriction.


Basically you'd end up with a train (preferably DMU) going:

North Station
Sullivan Square
Chelsea (Hopefully beefed up to a legitimate stop with easier/better bus connections)
Lynn
West Lynn
Swampscott
South Salem
Salem

and then either

Peabody and Danvers (North Shore Mall/128), or Beverly Depot


Seems like a pretty solid schedule that would easily beef up service on the more populous parts of the line, as well as provide an easy outlet for Danvers/Peabody service, as well as being a better feeder for the Blue Line to Lynn. Would be nice to see DMU service to someday.
DMU's are not a good idea for the Eastern Route, and it's because of that Eastern + Western Route concurrency in Somerville. The need to load-balance through there means that DMU schedule density to Beverly or Peabody and need to maintain at-minimum current headways to Reading means Newburyport and Rockport will pay a headway penalty. It's the only way to make the traffic work through Somerville, and it flunks the do-no-harm test. Today Eastern Route trains must be granted priority through the junction in train meets because stopping and waiting for a Western Route train to pass does more schedule harm to Newburyport/Rockport than it does for Haverhill/Reading. The Western Route train is always the one asked to wait. DMU's push the conflicting movements to a point where even prioritized movements are not enough to prevent Newburyport/Rockport from getting kneecapped.

However...you CAN implement DMU's on the Western Route onlywithout creating similar strain provided all Haverhill thru trains get booted back to the Lowell Line and Reading reverts back to its pre-1979 status as a short-turn only line. Reading short-turn is near enough distance that Eastern Route getting 100% priority at meets in Somerville and the Reading DMU's having to pause every time at Mystic Jct. does no harm to any line's schedules. So you also have to consider...if picking northside DMU applications, where is it going to have biggest return on investment at most negligible strain on operations? That's Western Route...slam-dunk. I wouldn't even think twice about it given that it would substantially improve Reading ridership while still allowing every regular-CR growth slot the Eastern Route would need (if the crossings + decaying bridges + Salem squeeze were fixed yadda yadda. . .).

So have to concede this one as well. There is far more to gain by upping Newburyport/Rockport at regular CR frequencies and full 6-8 car bi-level consists to swallow up the ridership growth out to 495 than there is flooding the zone with DMU dinkys inside 128. Lines with that many current and potential branches just don't work well unless the branch schedules rule the mainline schedule. That's not a bad thing, because 3 potential branches at CR schedules is itself a substantial increase in mainline frequencies. All-day/clock-facing is the only thing you can't really have with branch schedules ruling...but it's still a train every few minutes at Salem and Beverly the hours of the day it counts most. This could work if they got the CR system Charlie'd and altered the fare structure Beverly-inbound to something a little more flat-fee and rapid transit-like. I'd suggest the same for the Lowell Line out to Anderson, as that's in a similar boat needing to let its future growth be ruled by 495-and-beyond CR schedules and not clock-facing DMU's...but where the sheer density of the potential CR schedule saturates the biggest inside-128 stops all the same.


The ONLY solution that's going to satiate demand for true rapid transit inside 128 on the North Shore is...true rapid transit. Lynn is too big a bus terminal too constrained by traffic to thru-route the entire North Shore's bus routes to Wonderland and downtown-via-Route 1. Letting the terminal act as a real transfer node to Blue suddenly makes every bus out there work vastly better and frees up the capacity to substantially expand the bus network and schedule density in Lynn, Saugus, Revere, Salem, Peabody, Marblehead, etc. That's why Blue's ridership projections are so freaking high out there. It makes the dense bus connections work right for the first time in history. DMU's don't because the bus capacity is still kneecapped by the traffic problems of thru-routing to Wonderland and beyond.

And as for Salem...Blue past Lynn is cheaper than getting Blue to Lynn. And produces similar ridership. They need to get their house in order and get to Lynn pronto, but the second Salem leg starts looking awfully inevitable +20 years after Lynn.
 
Last edited:
All good points, never thought about the impact that DMUs would have on scheduling conflicts with the Western Route.

Note: The Danvers branch is gone now. Trail has claimed it. So the twin branches or either/or branches originally scoped out in the study are no longer an option. It can only be Peabody/128 @ North Shore Mall, since that stretch of abandoned ROW is not trailed and has no plans to be trailed (no 95/1 crossing to connect to the trail on the other side, so it's moot). It's also a power line ROW so securing the easement isn't something a trail lobby could do by its lonesome.

Yeah the North Shore Mall route was always the only one with serious viability, there's no reason to bring the tracks to downtown Danvers or to the Endicott Plaza when 128 and 2 major employers and transit destinations are right next door.

DMUs definitely seem out, I guess I'm just hoping for this to make a comeback https://www.youtube.com/watch?v=5V1ig5FWS4w
 
Also, trying to take a bus to the Blue line at Wonderland is awful right now, especially from Danvers. Just getting to Salem takes at least 45 minutes, so I can imagine a whole lot more people would take the bus if it meant getting off at the Northshore Mall or even Peabody CR stop, as it would be a much quicker and relatively painfree trip into Boston.

Then they could scrap the current termination of the 465 bus, and instead run service just to North Shore or Peabody instead. If they want to get really crazy, they could bring back the old bus which ran towards the intersection of Route 1/95 and 62, over by tons of low income housing, North Shore Community College, and the good sized strip mall. Assuming it would be a roughly 10 minute ride to downtown Danvers from the CC, and then a 20-25 minute ride to the malls it should see at least as much use as the current 465 bus, if not more.
 
I amended the Southern New England Map , added Providence - Hartford and Hartford - Worcester - Boston. High Speed Rail would go via Worcester along with Regional Services. Providence would carry limited High Speed Rail and Regional Rail Services.

https://maps.google.com/maps/ms?msid=215312482559953359515.00049110c2f416653cba3&msa=0&ll=41.996243,-71.553955&spn=2.75552,6.696167

Providence Link High Speed Rail Service
Boston South Station
Boston Back Bay
Providence
Hartford Union Station
New Haven Union Station
Stamford
New York Penn Station
Newark Penn Station
Philadelphia 30th Street Station
Wilmington
Baltimore Penn Station
Washington Union Station


Providence Regional Rail Service
Boston South Station
Boston Back Bay
Route 128
Providence
Danielson
Storrs
Manchester

Hartford Union Station
Berlin
Meriden
Wallingford
New Haven Union Station
Bridgeport
Stamford
New Rochelle
Fordham
Harlem 125th Street
Grand Central Terminal


Worcester High Speed Rail Service
Boston South Station
Boston Back Bay
Metrowest
Hartford Union Station
New Haven Union Station
Ronkonkoma
Jamaica
New York Penn Station
Newark Penn Station
Philadelphia-Market East
Philadelphia- Intl Airport
Baltimore - Charles Center

Washington DC Union Station


Worcester Regional Rail Service
Boston South Station
Boston Back Bay
Framingham
Metrowest
Worcester Union Station
Palmer
Springfield Union Station
Windsor Locks
Hartford Union Station
Berlin
Meriden
Wallingford
New Haven Union Station
Rocky Point
Ronkonkoma
Farmingdale
Garden City
Jamaica
New York Penn Station
Newark Penn Station
Newark Int Airport Station
Trenton
Cornwall Heights
North Philadelphia
Philadelphia-30th Street

 
Worcester Regional Rail Service
Boston South Station
Boston Back Bay
Framingham
Metrowest
Worcester Union Station
Palmer
Springfield Union Station
Windsor Locks
Hartford Union Station
Berlin
Meriden
Wallingford
New Haven Union Station
Rocky Point
Ronkonkoma
Farmingdale
Garden City
Jamaica
New York Penn Station
Newark Penn Station
Newark Int Airport Station
Trenton
Cornwall Heights
North Philadelphia
Philadelphia-30th Street


Where is "Metrowest"? Westborough? Southborough? By the Pike and I-495 Interchange?
 
How do you get all your lines onto one "page" for Google Maps? I have one with perhaps fewer miles of lines and yet it's on two pages.
 
The problem with the Hartford - Providence routing you've drawn is that it requires either a ridiculous amount of property takes in western Providence OR a ridiculously long tunnel underneath western Providence for what is essentially no point.

If you drag the line down and across the Washington Secondary instead, you eliminate the need for a nasty and/or expensive "solution" for getting through western Providence (and, as an added bonus, you don't have to deal with the Scituate Reservoir), you "lose" service to Danielson but pick up Planfield and Willimantic (Storrs still gets served either way), and you have a much easier time going back and adding light rail (or extra tracks for commuter rail) to an existing HSR line through there than you do in reactivating the line JUST for light rail.
 
Magic , I honestly don't know.

Again, I always post the KML source link, which you can copy by right-clicking on the KML download button when you're editing. It puts the whole map on one, un-editable page.
 
Again, I always post the KML source link, which you can copy by right-clicking on the KML download button when you're editing. It puts the whole map on one, un-editable page.

Does it do that correctly now? Because last year I was trying to do a map in Maps that was doing the annoying page-splitting behavior, totally clean-roomed in it Earth to see if a fresh KML export/import into Maps would fix the issue...and the import was page-splitting it all the same. I figured it was a bug in Maps, because sometimes I can have really overstuffed maps that fit all on one page and sometimes stuff only a small fraction as busy gets split. It's very random behavior to this day, but would be great if they finally got the KML import glitches fixed as a workaround.
 
Does it do that correctly now? Because last year I was trying to do a map in Maps that was doing the annoying page-splitting behavior, totally clean-roomed in it Earth to see if a fresh KML export/import into Maps would fix the issue...and the import was page-splitting it all the same. I figured it was a bug in Maps, because sometimes I can have really overstuffed maps that fit all on one page and sometimes stuff only a small fraction as busy gets split. It's very random behavior to this day, but would be great if they finally got the KML import glitches fixed as a workaround.

Mine page splits while I'm editing, but when I want to showcase my maps posting the kml file link always seems to work.
 

Back
Top