Remember this thread is “Crazy” transit pitches. As long as there’s a legitimate purpose for it - that’s the only requirement (or am I misunderstanding?)
The thought behind my proposal is - at some point extending HRT lines up CR lines can be a bit redundant. Just electrify and increase headways if that’s the case.
My plan reaches areas that would likely consider it a hassle to reach mass transit. Chestnut/Western is a dense area that’s on the other side of Lynn and intersects with a couple bus lines. You’d like see it pull a great deal of commuters from the East Peabody
Vinnin Square would be a phenomenal location as it would surely attract a ton of work day commuting from Marblehead who has no rail transit.
Salem State speaks for itself and the area surrounding the edge of Downtown Salem is a no brainer.
Especially if you extend the Blue line South to Charles and to Kenmore... then anyone coming from the North Shore to a Sox game would likely be taking the T
Western Ave. has the 424 and 450 direct out of Central Square. Chestnut has the 436. Ridership is not exactly awesome on those, per the 2014 Blue Book's stats for all 169 Yellow Line routes. The 450 ranks 73rd on the system with 1785 weekday boardings, the 436 ranks 125th with 823 boardings, and the part-timer 424 ranks 151st with 258 boardings. That's not only pretty poor, it's several orders of magnitude below anything that has the properties to support rapid transit. It's also two entirely different directional corridors you're attempting to mash into one uni-corridor, so the demand ends up
splitting those very low source ridership stats to a point where the likely stops almost can't escape being some of the biggest loss leaders for low ridership on the entire rapid transit system, regardless of frequencies. The corner of Western + Chestnut isn't a known diverging node or 'square' of any consequence that's any destination unto itself nor a linchpin for major transfers. It's just an intersection. If it were a 'square'-level gravity well, it would already be leaving its fingerprint on the riderships for these routes. Lots of big dense-looking thoroughfares intersect...not all of them end up creating a sum-greater-than-parts gravity well out of the resulting node. The intersection is one that very clearly does not, in spite of how convenient it *might* look on Google Maps. The on-the-ground evidence is completely lacking, and shows no signs of translating into transit shares. These are the very tells that any transpo study looks for to pop out when one is trying to quantify what makes a potential map corridor a real ride-generating capital-C Corridor.
Now...the frequencies are admittedly not real good on all of these Lynn routes. Frequencies are a problem with
all of the 4xx-series buses because of the equipment-cycle drain caused by thru-routing all of them to Wonderland then nearly all of them to Downtown through the congested tunnels. Of course, one of the biggest resulting booms from bringing BLX to Lynn at all is that it ends the bus cycling anemia and simplifies route turn to *just* Lynn Terminal...meaning an enormous amount of equipment availability comes available to reinvest directly into better frequencies. Something on the order of 40% more cycles with the same equipment sprayed all throughout the 4xx routes and targeted map expansion therein. So you could grow the ridership on each of those routes handsomely if enough bus equipment came available to pulse 10 min. frequencies on Western and 15 on Chestnut. With the convergence of those routes not being a particularly unique destination unto itself and just a single-point crossroads, does the baseline frequency improvement not do plenty to improve transit accessibility throughout Lynn??? Yes...it will, just by them being better buses. The evidence is still sorely lacking that there's any latent rapid transit corridor there. This is sort of why all BLX studies to-date just stub out at Central Sq. and don't bother with Swampscott & Salem until a later extension. Yes...the pan- North Shore demand will probably at some point crest enough that you eventually need real Blue Line frequencies into Downtown Salem. But the bus network reboot just from getting the transfer implanted at Central Square is an enormous amount of uncapped growth unto itself for how much it increases Yellow Line frequencies across the North Shore. Eyes-on-the-prize as far as the installment plans go.
------------------------------
Finally...when it comes to Salem: look at what parallels the Eastern ROW in walking distance: the afforementioned 450, and the 456 up the rest of MA 107 to Salem...plus the 455/459 to Salem via Swampscott + Salem State U. and the 4 Marblehead routes. Station siting at the ex-B&M East Lynn stop on Eastern Ave. would be a large secondary node unto itself, as would Swampscott Station, just by looping the buses around the station block. On the systemwide spider map the whole area from Riverworks to Swampscott is so thickly paralleled by multitude of bus routes that it *very* strongly resembles the GLX corridor in Somerville for potential multimodal network effects. Enormously shorter bus trips to the endpoints, enormously better-frequency buses in general across the network, way better loading profiles in the areas of route overlap, and new routing possibilities galore. All because every potential stop on the Eastern ROW (including even a relative throwaway like a Swampscott-Salem State spacer @ Essex St. by the cemetery) is a thickly-served new transfer node to multiple diverging routes. Much like the GLX corridor it's ripe for densification. Unfortunately the existing Purple Line mode isn't well set up for extremely dense Fairmount-like stop spacing. Travel times to the Newburyport and Rockport endpoints carry a lot of riders, and need to stay snugly within an hour. Even with EMU's, speed increases, and overall tightened ops Transit Matters is having trouble explaining in its Implementation Plan how its recs for 3 infills (Everett, Revere, and South Salem...in addition to full-timeing Riverworks) are ever going to fit inside a same-or-better end-to-end schedule. They probably all can't...at least not the Everett + Revere ones. That leaves pretty much South Salem/SSU as the consensus "must-have" by everyone who's been studying the North Shore over the last 25+ years. East Lynn's close spacing is definitely a bridge too far on even the electrified CR mode for all that needs to be kept in-balance right out to the Rockburyport endpoints, and even the worlds-better acceleration profile of EMU equipment is still an order of magnitude clunkier for dense stop spacing than literally any HRT/LRT rapid transit vehicle on the planet.
These are the same sets of conditions that GLX studied to-death on the Lowell Line corridor. In every case a Purple Line shuttle rated worse than side-by-sideing rapid transit when the Alternatives were studied. And in every case the optics arguments "why not tunnel under _____ street to avoid ROW duplication" (which was indeed studied for GLX to attempt to uni-branch Union + Medford into one mainline) paled in comparison to splitting the difference on-ROW with a mode way better task-oriented to serving the stop density. The Central Sq.-Swampscott corridor is a shoe-fit analogue to that. Shockingly good fit, in fact. BLX-Salem probably would've been given a comprehensive study long ago were it not for the fact that Wonderland-Lynn has been an unfinished mandate going on 6 decades. If/when an actual study lassoes all the data streams into an Alternatives rec...it's going to bullseye the expandable Eastern ROW hands-down over anything/everything off of it. And rely on leveraging stations at East Lynn, Swampscott, a trans-Swampscott spacer in the Essex vicinity, Salem State U. to amplify the density effects to the converging/diverging bus routes. We know this because we already fed the very similar at broad-based level GLX corridor into the same amount of study rigor, and it wasn't even a contest what shape the final recs ended up taking.