Search results for: boston regional rail

Boston Regional Rail

At TransitMatters, we have finally released our regional rail paper, recommending improvements to the MBTA that regular readers of this blog are probably familiar with. Alert readers might even want to probe which parts were written by me and which by others; the main document underwent several edits but some stylistic differences might persist, and the appendices were mostly written individually. We are suggesting the following two-step process:

1. Modernize the system based on best industry practices. This includes full electrification and fleet replacement with electric multiple units (and not electric locomotives), high platforms at all stations, and high frequency all day, every half hour on every branch interlining to support a train every 10-15 minutes on urban trunk lines. In some areas, such as Revere, there should also be infill stops. The capital cost, excluding fleet replacement, should be on the order of $2-3 billion, but the first priority, the Providence Line, is maybe $100 million excluding rolling stock, mostly going to high platforms.

2. Build the North-South Rail Link, with four tracks connecting the South Station and North Station systems. This takes longer than electrification, so planning should start immediately, with the intention of opening somewhat after the entire system is wired. The capital cost should be $4-6 billion, per a study that we’re referencing in our report.

In my mind, regional rail serves three main markets:

1. Local trips on trunk lines, connecting to urban neighborhoods and subway transfer points. The main benefit of regional rail is that it provides an express subway at very high frequency, just as I use the RER to get to Western Paris faster than I would on the Metro. In Boston, areas that would benefit include Forest Hills, Allston and Brighton, Hyde Park, Dorchester and Mattapan along the Fairmount Line, Chelsea, Revere, and Porter Square. Residents of these neighborhoods are likely to travel to other neighborhoods and not just to Downtown Boston.

2. Suburban trips, which are dominated by peak commutes; I complained here that US commuter rail demand is peaky, with 67-69% of suburban trips on the LIRR and Metro-North and 80% on the MBTA occurring in the morning peak compared with around 47% on Transilien, but this is in large part about land use and not just frequency. We’re calling for replacing park-and-rides with town center stations in the report, but absent extensive transit-oriented development, suburban trips are likely to remain peaky and CBD-bound. This is the only market North American commuter rail serves, and its users are territorial about what they view as their trains. However, electrification would speed up these trips materially (the Sharon-South Station trip time would go from 35 to 23 minutes), and the North-South Rail Link would offer North Side suburbs access to the CBD, which is too far from North Station.

3. Intercity trips, which are not peaky except insofar as some people commute. Those tend to dominate off-peak ridership today: per a CTPS study from 2012, about half of the Providence Line’s off-peak ridership originates in Providence itself, which also accords with my observations taking the line on weekends. These trips gain less from high frequency, but need a consistent frequency all day, every day, at worst every 30 minutes, ideally every 15 or 20. Regional rail modernization also speeds these trips the most.

Bear in mind that even though the report just came out, the actual writing was for the most part done in November. This means that the technical aspects of scheduling reflect my thinking in November and not now. At the time, I hadn’t thought about peak-to-base ratios systematically, so my sample schedule for the Providence Line has a train every 15 minutes on each branch (Providence and Stoughton) at the peak and a train every 30 minutes off-peak. I had been assuming a peak-to-base ratio of 2 would be appropriate, by comparison with schedules in Tokyo and on the RER here in Paris. I knew that the ratio was lower in some other places I think highly of, including London and the German-speaking world, but my assumption had been that demand would be so peaky that the maximum acceptable peak-to-base ratio was the correct one.

I’ve argued before that the peak-to-reverse-peak ratio must be 1 or as close to it as practical, in order to avoid parking trains in city center midday. The capacity problems at South Station, which averages a train arrival per platform track per 35 minutes at the peak even though the system is capable of 10-minute turnaround times, come from trains going from the platform tracks to the layover yard during the peak, crossing the station throat at-grade and delaying peak arrivals.

But recently, I started thinking more carefully about operating costs, and wrote this post about peak-to-base ratios. I no longer think peak-to-base frequency ratios higher than 1 are supportable. The marginal labor cost of midday service when there’s a prominent peak is very low, since the railroad would be replacing split shifts with regular shifts, and this encourages running the same frequency during rush hour and midday, if not during the evening and on weekends. And as I explain in the linked post, the cost of rolling stock purchase and maintenance encourages running trains as often as possible. Only energy costs scale linearly with service-km, and those are low: at New England’s current electricity rates, it costs $180 to run a 320-ton 8-car EMU between Providence and Boston each way, and at current fares, inducing 16 extra passengers from the extra frequency is enough to make this pay.

In the report, we talk about American commuter rail operating costs, mostly because that’s what’s available. SEPTA’s are $311/car-hour, whereas those of the LIRR, Metro-North, New Jersey Transit, Metra, and the MBTA are $500-600/car-hour. Per car-km, SEPTA costs about $9 to operate. But a system built around cost minimization, with a peak-to-base ratio of 1 (thus, relatively empty off-peak trains), can get this down to about $2/car-km, or about $180/car-hour.

The reason I think the MBTA could run modern regional rail for $2/car-km, where the RER costs $6/car-km and the Singapore MRT $4-5/car-km, is that the schedule is faster. The costs of rolling stock and labor are based on time rather than distance, and the regional rail system we’re proposing has aggressive schedules, averaging 90 km/h between Boston and Providence. Even energy costs can be contained, since a fast schedule implies relatively few stops. For the same reason it’s easier to make a profit on high-speed rail averaging 200 km/h than on low-speed rail, it’s easier to make a profit on a 90 km/h train at the boundary between regional and intercity scale than on a 40 km/h local train.

In general, I believe that transit planning has to be opportunistic: no city is perfect, so it’s always necessary to find workarounds for some local misfeatures, or ways to turn them into positives. In Boston, the misfeature is very low suburban density, making intense regional service modeled after the RER less useful. The opportunity lies in retooling lines that serve low-density suburbs as intercity lines, connecting Boston with Worcester, Providence, Lowell, Nashua, and Hyannis. With the exception of Worcester, which is on a curvy line, these cities can be connected to Boston at an average speed of 90 km/h or so: the stop spacing is so sparse, and the lines are so straight, that long stretches of 160 km/h are feasible.

But none of this can happen under the present-day operating paradigm. The opportunity I’m describing relies on postwar travel patterns and to some extent even on 21st-century ones (namely, university travel between Providence and Cambridge), which requires reforming frequencies, rolling stock, and infrastructure decisions to incorporate best industry practices that emerged from the 1970s onward. The MBTA can offer a fast, affordable, frequent regional transportation system from as far north as Manchester to as far south as Providence, but for this it needs to implement the regional rail improvements we’re proposing.

The Limits of Regional Rail

I recently found myself involved in a discussion about Boston regional rail that involved a proposal to do more thorough regional rail-subway integration. Normally, S-Bahn systems mix some aspects of longer-range regional rail and some aspects of urban metro systems. They provide metro-like service in the urban core – for example, Berliners use the the three trunk lines of the S-Bahn as if they were U-Bahn lines. But, unlike proper metros, they branch in the suburbs and tend to have lower frequency and lower quality of infrastructure. However, there is a limit to this integration, coming from timetabling.

The characteristics of metro-like S-Bahn

When I call some S-Bahns, or some S-Bahn trunks, “metro-like,” what I mean is how users perceive them, and not how planners do. A metro line is one that users get on without concern for the timetable. It may run on a clockface schedule, for example on a 5-minute takt in Berlin, but passengers don’t try to time themselves to get on a specific train, and if the train is 1-2 minutes behind schedule then nobody really minds. This user behavior usually comes from high frequency. However, in New York, despite extensive branching and 10-minute frequencies, I classify the subway as fully metro-like because the trains are not dispatched as a scheduled railroad and even if they were, passengers don’t ever think in terms of “my Queens-bound N train arrives at :06 every 10 minutes.”

S-Bahn lines have trunks like this, but also branches that work like regional rail. The regional rail pattern in the sense of RegionalBahn is one in which passengers definitely look at timetables and try to make them, and connecting public transit lines are planned to make timed transfers. On lines branded as RegionalBahn service comes every half hour or every hour, and usually S-Bahn tails are every 15-30 minutes (occasionally 10), but the printed schedule is paramount either way; when I rode the RER B to IHES in the last three months of 2016, I memorized the 15-minute takt and timed myself to it.

The key aspect of S-Bahns is combining these two patterns. But this leads to a key observation: they have to interline a number of different service patterns, which requires planning infrastructure and service to permit both. They can’t run on pure headway management in the core, because the branches must be scheduled. But they have to use a timetabling system that permits high core frequency nonetheless.

Finally, observe that I am not discussing the type of equipment used. A subway train that extends far into the suburbs may qualify as regional rail – the Metropolitan line in London qualifies as an example on account of its highly branched service pattern in Metro-land. In the other direction, a train built to mainline standards that runs consistent service pattern with little to no branching at a range typical of metros is not, for the purpose of this issue, regional rail – examples include the Yamanote and Keihin-Tohoku Lines in Tokyo, which run identical trains to those that run deeper into suburbia but have literally no (Yamanote) or almost no (Keihin-Tohoku) variation in service patterns.

The limit of interlining

A large degree of interlining tends to reduce timetable reliability. Trains have to make junctions at specific times. This is compounded by a number of different factors:

1. Trunk throughput

The busier the trunk is, the harder it is to keep everything consistent. If you run 15 trains per half-hour, that’s 15 opportunities for a 2-minute delay to mess the order in which trains arrive, which has implications further down. If you run 4 trains per half-hour, that’s 4 opportunities, and a 2-minute delay is easily recoverable anyway.

2. Trunk length

Longer and more complex trunks introduce their own problems. If many passengers treat trains as interchangeable and don’t care what order they arrive in, then this may not be good for timekeeping – a slight delay on a branch may lead to grossly uneven headways on the trunk, which compound on busy metro lines for similar reasons as on buses. Berlin’s Stadtbahn has 14 stations from Ostkreuz to Westkreuz counting both, and this may make the branches with their 20-minute frequencies a little too difficult to fit together – evidently, peak throughput is 18 trains per hour, hardly the cutting edge. The RER A has 7 trunk stations from Vincennes to La Défense inclusive, and around 27 peak trains per hour.

3. Branch infrastructure quality

In the limit, the branches have to have excellent infrastructure quality, to be resilient to 1-2 minute delays. Timed meets on a mostly single-trunk line, routine on 15-minute branches like some lines in suburban Zurich and Tokyo, become dicey on lines that feed very busy trunks. Tokyo does this on the Yokosuka Line, which is far from the busiest (it peaks around 20 trains per hour) and Zurich on the right bank of Lake Zurich, which feeds into an S-Bahn trunk with 4 stations inclusive from Stadelhofen to Oerlikon. The busiest S-Bahn lines tend to have all-doubled outer ends.

4. One vs. two ends

If the line is single-ended, then inbound trains can just run metro-style in city center without regard for the printed schedule, use the terminal for schedule recovery, and then go outbound on schedule. Non-through-running lines are by definition single-ended, and this includes what I believe is Tokyo’s busiest regional rail line, the Chuo Rapid Line. But even some through-running lines are de facto single-ended if demand is highly asymmetric, like the Stadtbahn, which has far more demand from the east than from the west, so that one branch even turns at Westkreuz. Double-ended lines do not have this opportunity for recovery, so it’s more important to stay on schedule, especially if the end is not just busy but also has extensive branching itself.

We Ran a Conference About Rail Modernization

The Modernizing Rail (Un)Conference happened last Sunday. We’re still gathering all the materials, but here are video uploads, including the keynote by Michael Schabas.

We will also have slides as given by presenters who used them. But for now, here are the slides used by the keynote. You may notice that the recording does not begin on the first slide; we missed Schabas’s introduction and some remarks on his background, detailing his 40 years of experience designing public transit systems in a number of countries, mainly Britain and Canada but also elsewhere in the developed world.

My session on construction costs was slide-free (and was not recorded), since I mostly just showed people around our under-construction cost dataset and answered a lot of questions. Some of those questions were annoying, by which I mean they questioned my thinking or brought up a point I haven’t considered before. I am not talking too much about it partly because I was mostly (mostly) repeating things I’ve said here, and the full database should be out later this summer, with all the mistakes I’ve made in currency conversion rates and in not updating for cost overruns fixed.

After my breakout, I was uncertain between which of two sessions to attend – one on HSR-legacy rail compatibility by María Álvarez, and one on equity issues in rail planning, by Grecia White and Ben She. I ended up going to the latter, which featured interesting discussions of inclusion of low-income people and minorities, both as riders (that is, serving people who are not middle-class whites better on regional rail) and as workers (that is, diversifying planning and engineering departments).

It went well in that there was no monopolization of discussion by people who have more a comment than a question, or any open racism or sexism; but it was somewhat frustrating in that while there was a lot of productive discussion of racial equality in rail planning, there was very little of gender equality even though we did intend to talk about both; Grecia was specifically interested in discussing these, for example women’s perceptions of public safety. This is in line with conference demographics – the organizing team and the breakout presenters were each one-third people of color, in line with US demographics; but the organizing team had 2/18 active women and the presenters 3/15. TransitMatters is similar in that regard – racial diversity is comparable to that of the Boston region, and the proportion of regulars who are queer is enormous, but there are very few women.

Finally, I hosted a session on how to set up a transport association, a.k.a. Verkehrsverbund. Christof Spieler did the most talking, and German attendees explained a lot about the difference between a transport association and agency amalgamation. But for the most part that session felt like an ersatz conclusion to the entire conference; it technically lasted an hour, but once the hour had lapsed, people from other sessions came to the room and the conversation continued naturally, talking a bit about different transit planning issues in Germany and a bit about applicability to rail reform in the Northeastern US.

Some Notes About Northeast Corridor High-Speed Rail

I want to follow up on what I wrote about speed zones a week ago. The starting point is that I have a version 0 map on Google Earth, which is far from the best CAD system out there, one that realizes the following timetable:

Boston 0:00
Providence 0:23
New Haven 1:00
New York 1:40
Newark 1:51
Philadelphia 2:24
Wilmington 2:37
Baltimore 3:03
Washington 3:19

This is inclusive of schedule contingency, set at 7% on segments with heavy track sharing with regional rail, like New York-New Haven, and 4% on segment with little to no track haring, like New Haven-Providence. The purpose of this post is to go over some delicate future-proofing that this may entail, especially given that the cost of doing so is much lower than the agency officials and thinktank planners who make glossy proposals think it should.

What does this entail?

The infrastructure required for this line to be operational is obtrusive, but for the most part not particularly complex. I talked years ago about the I-95 route between New Haven and southern Rhode Island, the longest stretch of new track, 120 km long. It has some challenging river crossings, especially that of the Quinnipiac in New Haven, but a freeway bridge along the same alignment opened in 2015 at a cost of $500 million, and that’s a 10-lane bridge 55 meters wide, not a 2-track rail bridge 10 meters wide. Without any tunnels on the route, New Haven-Kingston should cost no more than about $3-3.5 billion in 2020 terms.

Elsewhere, there are small curve easements, even on generally straight portions like in New Jersey and South County, Rhode Island, both of which have curves that if you zoom in close enough and play with the Google Earth circle tool you’ll see are much tighter than 4 km in radius. For the most part this just means building the required structure, and then connecting the tracks to the new rather than old curve in a night’s heavy work; more complex movements of track have been done in Japan on commuter railroads, in a more constrained environment.

There’s a fair amount of taking required. The most difficult segment is New Rochelle-New Haven, with the most takings in Darien and the only tunneling in Bridgeport; the only other new tunnel required is in Baltimore, where it should follow the old Great Circle Tunnel proposal’s scope, not the four-track double-stack mechanically ventilated bundle the project turned into. The Baltimore tunnel was estimated at $750 million in 2008, maybe $1 billion today, and that’s high for a tunnel without stations – it’s almost as high per kilometer as Second Avenue Subway without stations. Bridgeport requires about 4 km of tunnel with a short water crossing, so figure $1-1.5 billion today even taking the underwater penalty and the insane unit costs of the New York region as a given.

A few other smaller deviations from the mainline are worth doing at-grade or elevated: a cutoff in Maryland near the Delaware border in the middle of what could be prime 360 km/h territory, a cutoff in Port Chester and Greenwich bypassing the worst curve on the Northeast Corridor outside major cities, the aforementioned takings-heavy segment through Darien continuing along I-95 in Norwalk and Westport, a short bypass of curves around Fairfield Station. These should cost a few hundred million dollars each, though the Darien-Westport bypass, about 15 km long, could go over $1 billion.

Finally, the variable-tension catenary south of New York needs to be replaced with constant-tension catenary. A small portion of the line, between New Brunswick and Trenton, is being so replaced at elevated cost. I don’t know why the cost is so high – constant-tension catenary is standard around the world and costs $1.5-2.5 million per km in countries other than the US, Canada, and the UK. The Northeast Corridor is four-track and my other examples are two-track, but then my other examples also include transformers and not just wires; in New Zealand, the cost of wires alone was around $800,000 per km. Even taking inflation and four tracks into account, this should be maybe $700 million between New York and Washington, working overnight to avoid disturbing daytime traffic.

The overall cost should be around $15 billion, with rolling stock and overheads. Higher costs reflect unnecessary scope, such as extra regional rail capacity in New York, four-tracking the entire Providence Line instead of building strategic overtakes and scheduling trains intelligently, the aforementioned four-track version of the Baltimore tunnel, etc.

The implications of cheap high-speed rail

I wrote about high-speed rail ridership in the context of Metcalfe’s law, making the point that once one line exists, extensions are very high-value as a short construction segment generates longer and more profitable trips. The cost estimate I gave for the Northeast Corridor is $13 billion, the difference with $15 billion being rolling stock, which in that post I bundled into operating costs. With that estimate, the line profits $1.7 billion a year, a 13% financial return. This incentivizes building more lines to take advantage of network effects: New Haven-Springfield, Philadelphia-Pittsburgh, Washington-Virginia-North Carolina-Atlanta, New York-Upstate.

The problem: building extensions does require the infrastructure on the Northeast Corridor that I don’t think should be in the initial scope. Boston-Washington is good for around a 16-car train every 15 minutes all day, which is very intense by global standards but can still fit in the existing infrastructure where it is two-track. Even 10-minute service can sometimes fit on two tracks, for example having some high-speed trains stop at Trenton to cannibalize commuter rail traffic – but not always. Boston-Providence every 10 minutes requires extensive four-tracking, at least from Attleboro to beyond Sharon in addition to an overtake from Route 128 to Readville, the latter needed also for 15-minute service.

More fundamentally, once high-speed rail traffic grows beyond about 6 trains per hour, the value of a dedicated path through New York grows. This is not a cheap path – it means another Hudson tunnel, and a connection east to bypass the curves of the Hell Gate Bridge, which means 8 km of tunnel east and northeast of Penn Station and another 2 km above-ground around Randall’s Island, in addition to 5 km from Penn Station west across the river. The upshot is that this connection saves trains 3 minutes, and by freeing trains completely from regional rail traffic with four-tracking in the Bronx, it also permits using the lower 4% schedule pad, saving another 1 minute in the process.

If the United States is willing to spend close to $100 billion high-speed rail on the Northeast Corridor – it isn’t, but something like $40-50 billion may actually pass some congressional stimulus – then it should spend $15 billion and then use the other $85 billion for other stuff. This include high-speed tie-ins as detailed above, as well as low-speed regional lines in the Northeast: new Hudson tunnels for regional traffic, the North-South Rail Link, RegionalBahn-grade links around Providence and other secondary cities, completion of electrification everywhere a Northeastern passenger train runs

Incremental investment

I hate the term “incremental” when it comes to infrastructure, not because it’s inherently bad, but because do-nothing politicians (e.g. just about every American elected official) use it as an excuse to implement quarter-measures, spending money without having to show anything for it.

So for the purpose of this post, “incremental” means “start with $15 billion to get Boston-Washington down to 3:20 and only later spend the rest.” It doesn’t mean “spend $2 billion on replacing a bridge that doesn’t really need replacement.”

With that in mind, the capacity increases required to get from bare Northeast Corridor high-speed rail to a more expansive system can all be done later. The overtakes on Baltimore-Washington would get filled in to form four continuous tracks all the way, the ones on Boston-Providence would be extended as outlined above, the bypasses on New York-New Haven would get linked to new tracks in the existing right-of-way where needed, the four-track narrows between Newark and Elizabeth would be expanded to six in an already existing right-of-way. Elizabeth Station has four tracks but the only building in the way of expanding it to six is a parking garage that needs to be removed anyway to ease the S-curve to the south of the platforms.

However, one capacity increase is difficult to retrofit: new tracks through New York. The most natural way to organize Penn Station is as a three-line system, with Line 1 carrying the existing Hudson tunnel and the southern East River tunnels, including high-speed traffic; Line 2 using new tunnels and a Grand Central link; and Line 3 using a realigned Empire Connection and the northern East River tunnels. The station is already centered on 32nd Street extending a block each way; existing tunnels going east go under 33rd and 32nd, and all plans for new tunnels continuing east to Grand Central or across the East River go under 31st.

But if it’s a 3-line system and high-speed trains need dedicated tracks, then regional trains don’t get to use the Hell Gate Line. (They don’t today, but the state is spending very large sums of money on changing this.) Given the expansion in regional service from the kind of spending that would justify so much extra intercity rail, a 4-line system may be needed. This is feasible, but not if Penn Station is remodeled for 3 lines; finding new space for a fourth tunnel is problematic to say the least.


The point of integrated timetable planning is to figure out what timetable one want to run in the future and then building the requisite infrastructure. Thus, in the 1990s Switzerland built the tunnels and extra tracks for the connections planned in Bahn 2000, and right now it’s doing the same for the next generation. This can work incrementally, but only if one knows all the phases in advance. If timetable plans radically change, for example because the politicians make big changes overruling the civil service to remind the public that they exist, then this system does not work.

If the United States remains uninterested in high-speed rail, then it’s fine to go ahead with a bare-bones $15 billion system. It’s good, it would generate good profits for Amtrak, it would also help somewhat with regional-intercity rail connectivity. Much of the rest of the system can be grafted on top without big changes.

But then it comes to Penn Station. It’s frustrating, because anything that brings it into focus attracts architects and architecture critics who think function should follow form. But it’s really important to make decisions soon, get to work demolishing the above-ground structures starting when the Madison Square Garden lease runs out, and move the tracks in the now-exposed stations as needed based on the design timetable.

As with everything else, it’s possible not to do it – to do one design and then change to another – but it costs extra, to the tune of multiple billions in unnecessary station reconstruction. If the point is to build high-speed rail cost-effectively, spending the same budget on more infrastructure instead of on a few gold-plated items, then this is not acceptable. Prior planning of how much service is intended is critical if costs are to stay down.

Speed Zones on Railroads

I refined my train performance calculator to automatically compute trip times from speed zones. Open it in Python 3 IDLE and play with the functions for speed zones – so far it can’t input stations, only speed zones on running track, with stations assumed at the beginning and end of the line.

I’ve applied this to a Northeast Corridor alignment between New York and Boston. The technical trip times based on the code and the alignment I drew are 0:36:21 New York-New Haven, 0:34:17 New Haven-Providence, 0:20:40 Providence-Boston; with 1-minute dwell times, this is 1:33 New York-Boston, rising to maybe 1:40 with schedule contingency. This is noticeably longer than I got in previous attempts to draw alignments, where I had around 1:28 without pad or 1:35 with; the difference is mainly in New York State, where I am less aggressive about rebuilding entire curves than I was before.

I’m not uploading this alignment yet because I want to fiddle with some 10 meter-scale questions. The most difficult part of this is between New Rochelle and New Haven. Demolitions of high-price residential properties are unavoidable, especially in Darien, where there is no alternative to carving a new right-of-way through Noroton Heights.

The importance of speeding up the slowest segments

The above trip times are computed based on the assumption that trains depart Penn Station at 60 km/h as they go through the interlocking, and then speed up to 160 km/h across the East River, using the aerodynamic noses designed for 360 km/h to achieve medium speed through tunnels with very little free air. This require redoing the switches at the interlocking; this is fine, switches in the United States are literally 19th-century technology, and upgrading them to Germany’s 1925 technology would create extra speed on the slowest segment.

Another important place to speed up is Shell Interlocking. The current version of the alignment shaves it completely, demolishing some low-rise commercial property in the process, to allow for 220 km/h speeds through the city. Grade separation is obligatory – the interlocking today is at-grade, which imposes unreasonable dependency between northbound and southbound schedules on a busy commuter railroad (about 20 Metro-North trains per hour in the peak direction).

In general, bypasses west of New Haven prioritize the slowest segments of the Northeast Corridor: the curves around the New York/Connecticut state line, Darien, Bridgeport. East of New Haven the entire line should be bypassed until Kingston, even the somewhat less curvy segment between East Haven and Old Saybrook, just because it’s a relatively easy segment where the railroad can mostly twin with I-95 and not have any complex viaducts.

The maximum speed is set at 360 km/h, but even though trains can cruise at such speed on two segments totaling 130 km, the difference in trip time with 300 km/h is only about 3 minutes. Similarly, in southwestern Connecticut, the maximum speed on parts of the line, mostly bypasses, is 250 km/h, and if trains could run at 280 km/h on those segments, which isn’t even always possible given curvature, it would save just 1 minute. The big savings come from turning a 10 miles per hour interlocking into a modern 60 km/h (or, ideally, 90+ km/h) one, eliminating the blanket 120 km/h speed limit between the NY/CT state line and New Haven, and speeding up throats around intermediate stations.

Curve easements

Bypasses are easier to draw than curve modifications. Curves on the Northeast Corridor don’t always have consistent radii – for example, the curves flanking Pawtucket look like they have radius 600 meters, but no, they have a few radii of which the tightest are about 400 meters, constraining speed further. Modifying such curves mostly within right-of-way should be a priority.

Going outside the right-of-way is also plausible, at a few locations. The area just west of Green’s Farms is a good candidate; so is Boston Switch, a tight curve somewhat northeast of Pawtucket whose inside is mostly water. A few more speculative places could get some noticeable trip time improvements, especially in the Bronx, but the benefit-cost ratio is unlikely to be good.

Bush consulting on takings

In some situations, there’s a choice of which route to take – for example, which side of I-95 to go on east of New Haven (my alignment mostly stays on the north side). Some right-of-way deviations from I-95 offer additional choice about what to demolish in the way.

In that case, it’s useful to look for less valuable commercial properties, and try to avoid extensive residential takings if it’s possible (and often it isn’t). This leads to some bush consulting estimates of how valuable a strip mall or hotel or bank branch is. It’s especially valuable when there are many options, because then it’s harder for one holdout to demand unreasonable compensation or make political threats – the railroad can go around them and pay slightly more for an easier takings process.

How fast should trains run?

Swiss planners run trains as fast as necessary, not as fast as possible. This plan does the opposite, first in order to establish a baseline for what can be done on a significant but not insane budget, and second because the expected frequency is high enough that hourly knots are not really feasible.

At most, some local high-speed trains could be designated as knot trains, reaching major stations on the hour or half-hour for regional train connections to inland cities. For example, such a local train could do New York-Boston in 2 hours rather than 1:40, with such additional stops as New Rochelle, Stamford, New London (at I-95, slightly north of the current stop), and Route 128 or Back Bay.

But for the most part, the regional rail connections are minor. New York and Boston are both huge cities, so a train that connects them in 1:40 is mostly an end-to-end train, beefed up by onward connections to Philadelphia, Baltimore, and Washington. Intermediate stops at New Haven and Providence supply some ridership too, much more so than any outlying regional connections like Danbury and Westerly, first because those outlying regional connections are much smaller towns and second much of the trip to those towns is at low speed so the trip time is not as convenient as on an all-high-speed route.

This does not mean Swiss planning maxims can be abandoned. Internal traffic in New England, or in Pennsylvania and South Jersey, or other such regions outside the immediate suburbs of big cities, must hew to these principles. Even big-city regional trains often have tails where half-hourly frequency is all that is justified. However, the high-speed line between Boston and New York (and Washington) specifically should run fast and rely on trips between the big cities to fill trains.

How much does it cost?

My estimate remains unchanged – maybe $7 billion in infrastructure costs, closer to $9-10 billion with rolling stock. Only one tunnel is included, under Bridgeport; everywhere else I’ve made an effort to use viaducts and commercial takings to avoid tunneling to limit costs. The 120 km of greenfield track between New Haven and Kingston include three major viaducts, crossing the Quinnipiac, Connecticut, and Thames; otherwise there are barely any environmentally or topographically sensitive areas and not many areas with delicate balance of eminent domain versus civil infrastructure.

I repeat, in case it is somehow unclear: for $7 billion in infrastructure investment, maybe $8 billion in year-of-expenditure dollars deflated to the early 2020s rather than early 2010s, trains could connect New York and Boston in 1:40. A similar project producing similar trip times between New York and Washington should cost less, my guess is around $3 billion, consisting mostly of resurrecting the old two-track B&P replacement in lieu of the current scope creep hell, building a few at-grade bypasses in Delaware and Maryland, and replacing the variable-tension catenary with constant-tension catenary.

None of this has to be expensive. Other parts of the world profitably build high-speed rail between cities of which the largest is about the size of Boston or Philadelphia rather than the smallest; Sweden is seriously thinking about high-speed trains between cities all of which combined still have fewer people than metropolitan Boston. Better things are possible, on a budget, and not just in theory – it’s demonstrated every few years when a new high-speed rail line opens in a medium-size European or Asian country.

Metcalfe’s Law for High-Speed Rail

I wrote a Twitter thread about high-speed rail in the United States that I’d like to expand to a full post, because it illustrates a key network design principle. It comes from Metcalfe’s law: the value of a network is proportional to the square of the number of nodes. The upshot is that once you start a high-speed rail network, the benefits to extending it in every direction are large even if the subsequent cities connected are not nearly so large as on the initial segment. Conversely, isolated networks from the initial segments are of lower value.

The implication for the United States is that, first of all, it should invest in high-speed rail on the entire Northeast Corridor from Boston to Washington, aiming for 3-3.5 hour end-to-end trip times. And as the Corridor is completed, the priority should be extensions in all directions: south to Atlanta, north to Springfield and (by legacy rail) Portland, west to Pittsburgh and Cleveland, northwest to Upstate New York and Toronto.

The model

To quantify the benefits, I’m going to look purely at railroad finances: construction costs go out, annual profits go in. Intercity high-speed rail pretty much universally turns an operating profit, the question is just how it compares with interest on capital construction. For this, in turn, we need to estimate ridership. Here is an illustrative photo of the sophistication of the model I am using:

In the picture: someone who gets on the train without letting you get off first. Credit: William O’Connor.

The theoretical model for ridership is called a gravity model: ridership between two cities of populations Pop_A and Pop_B at distance d is proportional to


However, two complications arise. First of all, there are some diseconomies of scale: the trip time from the train station to one’s ultimate destination is likely to be much higher if the city is as huge as Tokyo or New York than if it is smaller. Empirically, this can be resolved by raising the populations of both cities to an exponent slightly less than 1; on the data I have, which is Japanese (east and west of Tokyo), Spanish (Madrid-Barcelona, Madrid-Seville), and French (see post here – all its sources link-rotted), the best exponent looks like 0.8.

And second, at short distance, the gravity model fails for two reasons: first, access time dominates so in-vehicle time is less important, and second, passengers drive more and take fast trains less. In fact, on the data I’m most certain of the quality of – that from Japan – ridership seems insensitive to distance up to and beyond the distance of Tokyo-Osaka, which is 515 km by Shinkansen. Tokyo-Hiroshima, 821 km and 3:55 by Shinkansen, underperforms Tokyo-Osaka by a factor of about 1.6 if the model is \mbox{Pop}_{A}^{0.8}\cdot\mbox{Pop}_{B}^{0.8} if we lump in air with rail traffic; of course, air travel time is incredibly insensitive to distance over this range, so it may not be fair to do so. French data taken about 3 hours out of Paris overperforms the mid-distance Shinkansen, although that’s partly an artifact of lower fares on the TGV.

To square this circle, I’m going to make the following assumption: the model is,

\mbox{Pop}_{A}^{0.8}\cdot\mbox{Pop}_{B}^{0.8}/\min\{500 \mbox{ km}, d\}^{2}.

If the populations of the two metro areas so connected are in millions then the best constant for the model is 75,000: that is, take out the number the formula spits, multiply by 500^{2} = 250,000 to get rid of the denominator at low d, multiply by 0.3, and make that your annual number of passengers in millions.

Finally, operating costs are set at $0.05/seat-km or $0.07/passenger-km, which is somewhat lower than on the TGV but realistic given how overstaffed and peaky the TGV is. This is inclusive of the capital costs of rolling stock, but not of fixed infrastructure. Fares are set at $0.135/passenger-km, a figure chosen to make New York-Boston and New York-Washington exactly $49 each, but on trips longer than 770 km, the fares rise more slowly so that profit is capped at $50/trip. Of note, Shinkansen fares are about $0.23/p-km on average, so training data on Shinkansen fares for a network that’s supposed to charge lower fares yields conservative ridership estimates; I try to be conservative since my model is, as the picture may indicate, not the most reliable.

The model on the Northeast Corridor

The Northeast Corridor connects four metropolitan areas: Boston (8 million people), New York (22), Philadelphia (7), Washington (10). All populations cover combined statistical areas, just as the metropolitan area definitions in Japan are expansive and include faraway exurbs. In the Northeast, the CSAs lump together some independent metro areas, such as Baltimore-Washington, but the largest of the subsidiary metro areas, including Baltimore, Providence, New Haven, and Trenton, are along the Northeast Corridor and would get their own stations.

The distances are 360 km Boston-New York, 140 km New York-Philadelphia, 220 km Philadelphia-Washington. I am not going to take into account subsidiary stations in passenger-km calculations, for simplicity’s sake. Splitting Baltimore apart from Washington would actually raise ridership by a little, first because the 0.8 exponent means that combining metro areas reduces ridership, and second because Boston-bound ridership is higher if we assume the destination is a little bit closer.

The highest-ridership city pair is New York-Washington. Per the formula above, we get

0.3\cdot 22^{0.8}\cdot 10^{0.8} = 22.44 \mbox{mio. pax/year.}

By the same formula, New York-Boston is 18.77 million, New York-Philadelphia is 16.87 million, Washington-Philadelphia is 8.98 million, and Boston-Philadelphia is 7.51 million. All of these are within the 500 km limit in which we assume distance doesn’t matter. Finally, Boston-Washington is

75,000\cdot 10^{0.8}\cdot 8^{0.8}/720^{2} = 4.82 \mbox{mio. pax/year.}

Overall, this is 79.4 million annual passengers, excluding shorter-distance commuter travel like New York-New Haven. Taking distance traveled into account, this is 26.4 billion annual p-km, generating $1.7 billion of operating profit. What I think it should cost to generate this service is investments that, with good value engineering that has been missing from all plans in the last 12 or so years, should cost in the low teens, say $13 billion. If costs can be held to $13 billion, or just less than $20 million per kilometer for a line of which about two-thirds of the physical infrastructure is good enough, then the financial return on investment is 13%. Not bad.

Of note, traffic density is fairly symmetric at the two ends. At the southern end, between Philadelphia and Washington, total traffic density is 36.24 million passengers per year; at the northern end, between New York and Boston, it is 31.1 million. So there should be some extra trains just for New York-Philadelphia, where the expected traffic density is 51.64 million – perhaps ones diverting west to inland Pennsylvania, perhaps interregional trains making an extra stop or two running 5-10 minutes slower than the trains to Washington – but otherwise trains should run on the entire corridor from Boston to Washington.

Also of note, I don’t expect much peakiness on the line – probably none outside the New York-Philadelphia segment. Short-distance lines, including New York-New Haven and New York-Philadelphia, have a rush hour peak in travel. But longer-range intercity lines generate weekend leisure travel and same-day business travel, both of which tend to peak outside the regular rush hour; TGV traffic, heavily weighted toward longer-range city pairs, peaks on Friday and Sunday, with weaker weekday ridership to balance it out. The Northeast Corridor thus benefits from mixing cities at various ranges, with the various peaks mostly canceling each other out. It’s plausible to get away with running service at a regular interval of every 15 minutes all day, with extra trains on New York-Philadelphia.

The Northeast Corridor and Metcalfe’s law

Two examples of Metcalfe’s law in action can be found on the corridor, one for an expansion and one for a contraction.

The contraction would be to ignore Boston and just focus on New York-Washington. The traffic density is higher there, for one. Moreover, no extensive civil infrastructure is required, only some small fixes in Maryland and New Jersey, a rebuild of the catenary, and rebuilds of the station throat interlockings. However, this is less prudent than it seems, because Boston doesn’t just generate traffic on New York-Boston, but also on New York-Washington, on trains bound from points south of New York to Boston.

If we exclude Boston, we have just three city pairs on what is left: New York-Washington, New York-Philadelphia, Washington-Philadelphia. They total 48.3 million passengers per year and 12.4 billion p-km – in other words, slightly less than half the p-km of the entire line including Boston. What’s more, there’s an extra fudge factor, not modeled in my ridership screen, coming from peakiness: a shorter line is one with a more prominent rush hour peak, as the longer trips on Boston-Washington are not included, and this ends up requiring more rush hour-only equipment and increases operating expenses per p-km.

The expansion is, in this section, one that is almost part of the Northeast Corridor today: New Haven-Springfield. The line is unelectrified today despite substantial investment by Connecticut, which like other American states is allergic to rail electrification for reasons that are beyond me. Speeds today are low, even though the right-of-way is straight. However, investment in bypasses and in speedups on the highest-quality legacy segment is possible, and would connect Hartford and Springfield to New York and points south.

The Hartford-Springfield region has 2 million people, and Springfield is 100 km from New Haven and 210 from New York. We apply our usual model and get New York-Springfield ridership of 6.19 million, Philadelphia-Springfield ridership of 2.48 million, and Washington-Springfield ridership of 3.3 million. In passenger-kilometers, these three city pairs amount to 1.3 billion, 620 million, and 1.55 billion respectively, for a total of 3.47 billion, which I will round to 3.5 billion to avoid giving the impression that the model is reliable to 3 significant figures (or even 2, to be honest).

So we have 3.5 billion additional p-km for just 100 km of new construction, or 35 million p-km per km of construction. Note that the expected density on New Haven-Springfield based on the model is just 12 million passengers – the remaining p-km are on the core Northeast Corridor, as passengers from New York and points south travel on a portion of the corridor to get up to the branch to Springfield. So even though the expected traffic is very light, the impact on revenue per kilometer of construction is comparable to that of the base corridor. If costs can be held to $2 billion, which is low-end for an entirely greenfield line but reasonable for service that would partly run on the existing legacy line, then the return on investment is $0.065*3.5/$2 = 11%, almost as high as on the base Northeast Corridor.

Further extensions

Portland (0.7)

To the north, it is valuable to run upgraded legacy trains between Boston and Portland, with a short connection to high-speed trains at South Station. Estimating ridership and revenue there is dicier, because the trains are slower and the data is trained on high-speed trains. We assume 190 km of revenue, as is the current length of the line. But costs and the ridership-suppressing effect of distance are charged at 350 km, roughly scaled for time.

With this in mind, ridership on Boston-Portland is 1.19 million, ridership on New York-Portland is 1.33 million, ridership on Philadelphia-Portland is 0.37 million, and ridership on Washington-Portland is 0.31 million. In total, this is about 1.5 billion p-km, of which 45 million, all from Washington, are beyond the 770 km at which fares are $0.135/km and are charged at the lower rate of $0.07/km. Altogether it’s around $200 million a year in revenue. Costs are around $140 million, including extra costs for service south of Boston. Operating profits are fairly low, but Boston-Portland legacy trains don’t cost per km nearly as much as high-speed rail; electrification and some track work can be done for maybe $600 million, for an ROI of 10%.

Of course, this ROI does not exist without high-speed rail the Northeast Corridor and without the separately-charged North-South Rail Link for local and regional trains. Like other tails, Boston-Portland is valuable once the mainline preexists – it isn’t so great on its own.

The South

The route from Washington to Atlanta has a sequence of cities roughly following the I-85 corridor. They are small and sprawly, but are still valuable to connect thanks to Metcalfe’s law. These include Richmond (1, and 180 km from Washington), Raleigh (2, and 240 km from Richmond), the Piedmont Triad (1.6, 120 km), Charlotte (2.6, 150 km), Greenville (1.4, 160 km), and finally Atlanta (7, 230 km).

The line is long, 50% longer than the Northeast Corridor. With quite sprawly cities in North Carolina and few good rights-of-way, takings and viaducts are needed and would raise construction costs, to perhaps $30 billion. Moreover, there is probably an intercity rail ridership penalty because these cities do not have public transportation; the model does not incorporate such a penalty, which should be regarded as a risk with investments made appropriately. And yet, each city in sequence generates ridership on the line to its north, creating decent ROI if we assume the model applies literally.

Take Richmond. It’s a small city, generating 1.89 million annual riders to Washington, 1.42 million to Philadelphia, 3.05 million to New York, 0.49 million to Boston. But this is 2.9 billion p-km for just 180 km of new construction, and nearly all of these p-km are chargeable at the full rate, giving us a total of $190 million in annual operating profit. If construction can be kept to $5 billion, this is just short of 4% ROI, which is not amazing but is decent for how small Richmond is compared with the cities to its north.

This calculation cascades farther south. We have the following table of ridership levels, in millions of annual passengers as always:

City N\City S Richmond Triangle Triad Charlotte Greenville Atlanta
Boston 0.49 0.66 0.36 0.43 0.21 0.58
New York 3.05 3.14 1.6 1.73 0.79 2.03
Philadelphia 1.42 1.87 0.9 0.92 0.41 1.13
Washington 1.89 3.3 2.36 2.13 0.86 1.92
Richmond 0.64 0.44 0.62 0.22 0.44
Triangle 0.76 1.12 0.68 1.42
Triad 0.94 0.57 1.78
Charlotte 0.84 3.06
Greenville 1.9

This leads to the following operating profits, in millions of dollars per year:

City N\City S Richmond Triangle Triad Charlotte Greenville Atlanta
Boston 24.5 33 18 21.5 10.5 29
New York 107.06 157 80 86.5 39.5 101.5
Philadelphia 36.92 77.79 44.46 46 16.5 56.5
Washington 22.11 90.09 82.84 95.53 43 96
Richmond 9.98 10.3 20.55 9.58 88
Triangle 5.93 19.66 19.01 60.92
Triad 9.17 11.49 62.48
Charlotte 8.74 77.57
Greenville 19.76

This totals to $1.8 billion a year, or an ROI of 6%. This is not a safe number – a hefty share of the figure comes from city pairs that trains would connect in 3.5+ hours, like New York-Charlotte, Washington-Atlanta, and even the 5.5-hour New York-Atlanta, in which range the model has essentially two data points (Tokyo-Hiroshima, Paris-Nice). Another noticeable share comes from intra-South connections, in which neither city in the pair has a strong center or a public transport network to connect the station with destinations.

But thankfully, because this line can build itself up by accretion of extensions, starting with Washington-Raleigh and seeing how ridership holds up would not create a white elephant, just missed benefits if the model is in fact correct.

Harrisburg (0.7), Pittsburgh (2.5), and Cleveland (3)

The Keystone corridor is an interesting example of a branch that gets stronger if it is longer. The reason for this is that Harrisburg is pretty small, and Harrisburg-Pittsburgh requires painful tunneling across the Appalachians. Philadelphia-Harrisburg is 170 km and can probably be done for $4 billion; Harrisburg-Pittsburgh is 280 km and, as a pure guess, requires around 40 kilometers of tunnel, let’s say $14 billion. Pittsburgh-Cleveland is 200 km and may require some tunneling near the Pittsburgh end to bypass suburban sprawl without good rights-of-way, but not too much – figure it for $6 billion.

For the benefits, we make a table similar to that for the South, but smaller. Of note, Washington-Harrisburg is 390 km and about 1:45, and costs accordingly to operate, but can only charge for 220 km, or $30, barely more than breakeven rate, because the straight line distance is short and high fares may not be competitive with driving on I-83. The straight line distance is even shorter than 220, about 190 via Baltimore, but Washington-Philadelphia is 220. Trains from Washington are assumed to earn the usual marginal profit west of Harrisburg, $0.065/km up to a maximum of $50, which is not reached even in Cleveland.

Finally, note that Cleveland has a big difference between the population of the core metro area (2 million) and the combined one (3.5), like Boston and Washington. Here we don’t take the bigger population but split the difference, since the biggest subsidiary regions in the combined area, Akron and Canton, could plausibly be on the line – and if they’re not then the line can serve Youngstown (0.7), and then 2^{0.8} + 0.7^{0.8} \approx 3^{0.8}. Note, finally, that Boston-Cleveland is faster via Albany and Buffalo, so the line through Pittsburgh is not considered even if it is built first.

City E\City W Harrisburg Pittsburgh Cleveland
Boston 0.66 0.91
New York 2.67 5.32 3.43
Philadelphia 1.07 2.96 2.03
Washington 1.42 2.19 1.51
Harrisburg 0.47 0.54
Pittsburgh 1.5

And as before, using the special malus for the roundabout Washington-Harrisburg route, we have the following operating revenues in millions of annual dollars:

City E\City W Harrisburg Pittsburgh Cleveland
Boston 28.74 45.5
New York 53.8 204.02 171.5
Philadelphia 11.82 86.58 85.77
Washington 3.41 45.11 50.74
Harrisburg 8.55 16.85
Pittsburgh 19.5

Note that the relatively easy to build segment to Harrisburg only generates $98 million in operating profit on $4 billion in construction costs, just less 2.5% ROI – Harrisburg is almost as big as Richmond, but it’s a branch and not a direct extension. Then Pittsburgh generates $390 million on $14 billion, or 2.8%. But Cleveland, easier to build to and bigger than Pittsburgh, manages to generate $344 million on $6 billion, finally a respectable ROI of 6%.

The northern cross

What may be caled the northern cross or the Albany cross – that is, a cruciform system consisting of lines from Albany to New York, Boston, Montreal, and Toronto – is an interesting case of a system where Metcalfe’s law again applies and encourages going big rather than small.

To apply the model, we make a crucial assumption: the same formula calibrated to domestic travel works internationally. Eurostar severely underperforms it – it has 10 million annual riders, of whom around 7-8 million go between London and Paris, where the formula predicts 18 million. Eurostar fares are very high, and has mandatory security theater and a slow boarding process that breaks down at peak travel time, and this may be enough to explain the low ridership. But then again, domestic TGVs overperform the model.

We also make a secondary assumption: fares charged are for actual distance traveled, even though the New York-Toronto routing isn’t the most direct.

We start with the New York-Toronto leg by itself. It connects New York to Albany (1.2, 220 km), Utica (0.3, 140 km from Albany), Syracuse (0.8, 80 km), Rochester (1.1, 120), Buffalo (1.2, 110), and Toronto (8, 160 km). Toronto’s metro population ranges between 6 million and 9 million depending on definition, and the high-end figure of 8 million is justifiable by the fact that Niagara Falls and Hamilton are on the line.

City S\City N Albany Utica Syracuse Rochester Buffalo Toronto
Washington 1.63 0.35 0.62 0.6 0.52 1.76
Philadelphia 1.65 0.54 0.88 0.78 0.63 2
New York 4.12 1.36 2.67 3.06 2.29 6.81
Albany 0.13 0.26 0.37 0.4 1.23
Utica 0.09 0.12 0.13 0.6
Syracuse 0.24 0.26 1.19
Rochester 0.37 1.71
Buffalo 1.83

And in operating profit:

City S\City N Albany Utica Syracuse Rochester Buffalo Toronto
Washington 61.45 16.38 31 30 26 88
Philadelphia 38.61 17.55 33.18 35.49 31.5 100
New York 58.92 31.84 76.36 109.4 99.73 340.5
Albany 1.18 3.72 8.18 11.7 48.77
Utica 0.47 2.03 3.13 18.33
Syracuse 1.87 3.89 30.17
Rochester 2.65 30.01
Buffalo 19.03

New York-Albany should cost maybe $5 billion to build and generates $160 million a year in operating profit, just 3.2%. But Albany-Buffalo, for around $11 billion extra, generates $580 million, about 5.2%. And then Buffalo-Toronto, assuming no international penalty, should cost on the order of $3 billion (much of the line in the Toronto suburbs automatically follows from the ongoing electrification project) and generate $670 milion. So the last segment, Buffalo-Toronto, returns around 20% if New York-Buffalo preexists; even if there’s a serious international malus, the ROI is very high. Everything combined is around 7%.

None of this is robust. The model handwaves the forced transfer at Penn Station – through-service from points south to Albany and points north would be excellent given expected traffic levels, but the approaches to both Albany and Philadelphia point west. The model also assumes New York-Toronto fares are in line with rail distance, even though the route is 50% longer by rail than by air. Finally, it assumes no international penalty. A 7% ROI is robust to any one of these assumptions failing, but if all fail, the route drops in profitability.

Or, rather, the base route does. Just as completing Buffalo-Toronto makes New York-Buffalo seem far stronger, so do the two additional legs of the northern cross strengthen the initial Empire Corridor. Here’s the Boston-Albany leg, at 260 km, with Springfield at kp 135, recalling that Hartford and Springfield count as one region of 2 million:

City W\City E Boston Springfield
Springfield 2.76
Albany 1.83 0.6
Utica 0.6 0.2
Syracuse 1.32 0.44
Rochester 1.19 0.56
Buffalo 0.91 0.46
Toronto 2.76 1.28

And in revenue:

City W\City E Boston Springfield
Springfield 24.22
Albany 30.93 4.88
Utica 15.6 3.45
Syracuse 41.18 9.87
Rochester 46.41 16.93
Buffalo 45.5 17.19
Toronto 138 61.15

$450 million a year, of which nearly half comes out of connecting Toronto to Massachusetts and Hartford, is not a lot, but then constructing 260 km of high-speed rail is not that expensive either; my best guess is around $7 billion, with some tunnels between Springfield and the summit to the west but also some approaches at both ends that would already exist. This is 6.4% ROI, which is better than New York-Toronto gets without the assistance of Philadelphia and Washington even though that route connects to a bigger city and requires less tunneling.

The final leg of the northern cross is to Montreal (4, 370 km from Albany), and is the most speculative. If the model has an international malus, it may well apply here, crossing not just a national border but also a linguistic one. It may apply with no or limited penalty, if the underperformance of Eurostar can be ascribed entirely to fares; but if it applies and is serious, then there is less cushion for mistakes than there is for trains to Toronto. The only intermediate city is Burlington (0.2, kp 220 from Albany), which exists largely for state-level completeness. Note also that Buffalo-Montreal is faster via Toronto and is thus omitted, while Buffalo-Burlington would have third-order impact.

City ESW\City N Burlington Montreal
Washington 0.2 1.59
Philadelphia 0.29 2.02
New York 0.98 7.74
Albany 0.1 1.05
Boston 0.44 3.02
Springfield 0.14 1.58
Utica 0.03 0.33
Syracuse 0.06 0.49
Rochester 0.07 0.5
Burlington 0.25

And in operating revenue:

City ESW\City N Burlington Montreal
Washington 10 31.8
Philadelphia 10.93 95.85
New York 28.03 296.83
Albany 1.43 25.25
Boston 13.73 123.67
Springfield 3.14 50.84
Utica 0.7 10.94
Syracuse 1.72 18.79
Rochester 2.55 23.08
Burlington 2.44

This is $750 million a yeer, of which Burlington furnishes about 10%, and New York-Montreal about 40%. This isn’t bad ROI – about $10 billion is a reasonable construction cost – but since 90% of it is about Montreal, any serious international or interlinguistic penalty leads to a big drop in profitability. Worse, if traffic drops, there may be a frequency-ridership spiral – I am writing timetables assuming half-hourly frequency, which is just enough for the model’s projected 18 million passengers per year, but if ridership is off by a factor of more than 2, then hourly frequencies start taking a bite out of the nearer markets and trains start running less full.

Lines that do not touch the Northeast Corridor

In the previous sections, I’ve argued in favor of building out a high-speed rail network out of the Northeast Corridor, on the grounds that extensions would be profitable toward Pittsburgh-Cleveland, Montreal, Buffalo-Toronto, and Atlanta. What about other lines?

The answer is that lines that do not feed into the Northeast somehow are a lot weaker. California can get decent ridership out of Los Angeles-San Francisco and thence extensions to Sacramento and San Diego are pretty strong, but the traffic density per the model is both well below California HSR Authority projections and well below the Northeast Corridor.

And it gets worse in parts of the country without a Los Angeles-size city anchoring everything. Texas is currently building a Dallas (8)-Houston (7) high-speed line, using private money by Texas Central, a railroad owned by JR Central using Shinkansen technology. The model predicts 7.5 million annual riders between the two regions, and the system’s public ridership projections for the near term are pretty close. Moreover, construction costs are pretty high, $15 billion for 380 km, despite the flat terrain. If the operating costs and fares are what I’m projecting, the financial ROI is 1.2%.

What’s more, Texas can expect ridership to underperform any model trained on European or Japanese cities. Tokyo has the world’s largest central business district, and maintains high density of destinations at a distance of several kilometers from Tokyo Station as well, and 20-something rapid transit lines depending on how one counts feed this center. Paris is smaller but has a strong center and urban rail connections. The provincial cities in both countries are lower-density and have higher car ownership, but that’s still okay, because people from those cities are not driving into the capital. By the same token, trains to New York should not underperform a model trained on Japan, Spain, or France. But Texas is completely different, with very weak centers, no public transportation to speak of, and no walkable cores near the train stations. The penalty for poor public transport connections is likely to be serious.

The situation in the Midwest is more hopeful than in Texas, but still dicey. Chicago just isn’t that big. Yes, it’s about the same size as Paris, but the cities ringing it don’t form neat lines the way Lyon and Marseille are on the same line out of Paris, just with a short spur rather than through-service.

The funniest thing about the Midwest is that high-speed rail construction there may be justifiable as an accretion of western extensions from the Northeast and Keystone Corridors. Cleveland-Detroit (5) is 280 km long, and would put Detroit 1,070 km and slightly more than 4 hours away from New York. The distance penalty is hefty, but 2.81 million annual users is still a lot over such distance, and the $140 million in operating profits get to around 2.5% ROI on construction costs in flat Midwestern land, without taking any other connections into consideration: Chicago-Cleveland, Chicago-Detroit, Philadelphia-Detroit, Pittsburgh-Detroit, New York-Toledo, Washington-Detroit.

Even New York-Chicago is a fairly solid line per the model: it’s 1,340 km and slightly longer than 5 hours, but there is still a lot of travel volume between the two cities, mostly by air. The model says 3.12 annual high-speed rail riders, somewhat fewer than the current O&D flight volume (4.68 million annualized from 2018 Q2), which is believable by comparison with Paris-Nice’s mode share (70% air, 30% rail, ignoring all other modes). The required mode share is still more favorable to rail, but the airports in New York and Chicago have more congestion and more delays than in Nice, turning what is a little more than an hour in the air into a three-hour flight schedule.

In contrast, just starting from Chicago-Cleveland (550 km)/Detroit (470 km), without any other connections (and without Pittsburgh-Cleveland), would not be financially great. Ignoring Toledo, the three cities generate 13 million annual riders, 6 billion annual p-km, and $400 million in annual operating income, for a system that would take perhaps $13 billion to construct, perhaps slightly more.

What this means for high-speed rail construction

Metcalfe’s law implies that high-speed rail networks get stronger as they add more nodes, even if those nodes are somewhat weaker than the initial ones. But it gives guideines for how to build such networks more broadly:

  • Don’t cheap out by only building a short segment.
  • Once the initial segment is in place, invest in extending it and building branches off it as soon as possible, in preference to building unconnected segments elsewhere.
  • A relatively empty tail may still be financially successful if it fills a trunk line.
  • Unless all your cities are on one line, try to build a mesh of lines to allow many origin-destination pairs.
  • You’ll always run into a frontier of marginal lines, so value-engineer infrastructure as much as possible to push that frontier forward.
  • Be wary of lines for which the analysis involves extrapolation, for example if neither city has a strong center or usable public transport.

High-speed rail is cheap to run when there’s enough scale to fill trains – high speeds ensure that labor and equipment cost per seat-km are fairly low. This means that self-sustaining profits are viable, and once they’re in place, they can generate further borrowing capacity for rapid expansion.

The limit is not the sky. Beyond a certain point, no realistic value engineering can make lines financially viable. Sometimes the cities are just too small or too far apart. But a realistic limit for the United States is still most likely much farther than anyone proposing immediate investment plans thinks: the Northeast Corridor can generate good returns if investment there is ever done competently, and branches and extensions to smaller and less dense cities are still more viable than they look at first glance.

New England High- and Low-Speed Rail

After drawing a map of an integrated timed transfer intercity rail network for the state of New York, people asked me to do other parts of the United States. Here is New England, with trains running every 30 minutes between major cities:

New England is a much friendlier environment for intercity rail growth than Upstate New York, but planning there is much more delicate. The map thus has unavoidable omissions and judgment calls, unlike the New York map, which straightforwardly follows the rule of depicting intercity lines but not suburban lines like the Long Island network. I ask that people not flame me about why I included X but not Y without reading the following explanations.

The tension between S-Bahn and ITT planning

The S-Bahn concept involves interlining suburban rail lines through city center to provide a high-frequency urban trunk line. For example, trains from a number of East Berlin neighborhoods and Brandenburg suburbs interline to form the Stadtbahn: in the suburbs, they run every 10 or 20 minutes, but within the Ring, they combine to form a diameter running regularly every 3:20 minutes.

The integrated transfer timetable concept instead involves connecting different nodes at regular intervals, typically half an hour or an hour, such that trains arrive at every node just before a common time and leave just after, to allow people to transfer. In a number of major Swiss cities, intercity trains arrive a few minutes before the hour every 30 minutes and depart a few minutes after, so that people can connect in a short amount of time.

S-Bahn and ITT planning are both crucial tools for good rail service, but they conflict in major cities. The ITT requires all trains to arrive in a city around the same time, and depart a few minutes later. This forces trains from different cities to have different approach tracks; if they share a trunk, they can still arrive spaced 2-3 minutes apart, but this lengthens the transfer window. The idea of an S-Bahn trunk involves trains serving the trunk evenly, which is not how one runs an ITT.

Normally, this is no problem – ITTs are for intercity trains, S-Bahns are for local service. But this becomes a problem if a city is so big that its S-Bahn network grows to encompass nearby city centers. In New York, the city is so big that its shadow reaches as far as Eastern Long Island, New Haven, Poughkeepsie, and Trenton. Boston is smaller but still casts shadows as far as southern New Hampshire and Cape Cod.

This is why I don’t depict anything on Long Island on my map: it has to be treated as the extension of an S-Bahn system, and cannot be the priority for any intercity ITT. This is also true of Danbury and Waterbury: both are excellent outer ends for an electrified half-hourly regional rail system, but setting up the timed transfers with the New Haven Line (which should be running every 10 minutes) and with high-speed rail (which has no reason to stop at the branch points with either Danbury or Waterbury) is infeasible. In Boston I do depict some lines – see below on the complications of the North-South Rail Link.

The issue of NSRL

The North-South Rail Link is a proposed north-south regional rail tunnel connecting Boston’s North and South Stations. Current plans call for a four-track tunnel extending across the river just north of North Station, about 4.5 km of route; it should cost $4 billion including stations, but Massachusetts is so intent on not building it lies that the cost is $12 billion in 2018 dollars.

In common American fashion, NSRL plans are vague about how service is to run through the tunnel. There are some promises of running intercity trains in addition to regional ones; Amtrak has expressed some interest in running trains through from the Northeast Corridor up to the northern suburbs and thence to Maine. However, we are not engaging in bad American planning for the purposes of this post, but in good Central European planning, and thus we must talk about what trains should run and design the tunnel appropriately.

The rub is that Boston’s location makes NSRL great for local traffic and terrible for intercity traffic. When it comes to local traffic, Boston is right in the middle of its metropolitan region, just offset to the east because of the coast. The populations of the North Side and South Side suburbs are fairly close, as are their commuter volumes into Boston. Current commuter rail ridership is about twice as high on the South Side, but that’s because South Station’s location is more central than North Station’s. NSRL really is a perfect S-Bahn trunk tunnel.

But when it comes to intercity traffic, Boston is in the northeast corner of the United States. There are no major cities north of Boston – the largest such city, Portland, is a metro area of 600,000. In contrast, going south, New York should not be much more than an hour and a half away by high-speed rail. Thus, high-speed rail has no business running through north of Boston – the demand mismatch south and north is too high.

Since NSRL is greatly useful for regional traffic but not intercity traffic, the physical infrastructure should be based on S-Bahn and not ITT principles, even though the regional network connects cities quite far away. For one, the tunnel should require all trains to make all stops (South Station, Aquarium, North Station) for maximum local connectivity. High-speed trains can keep feeding South Station on the surface, while all other traffic uses the tunnel.

But on the North Side, feeding North Station on the surface is not a good idea for intercity trains. The station is still awkwardly just outside city center. It also offers no opportunity to transfer to intercity trains to the most important city of all, New York.

The only resolution is to treat trains to Portland and New Hampshire as regional trains that just go farther than normal. The Nashua-Manchester-Concord corridor is already as economically linked to Boston as Providence and Worcester, and there are plans for commuter rail service there already, which were delayed due to political opposition to spending money on trains from New Hampshire Republicans after their 2010 election victory. Portland is more speculative, but electric trains could connect it with Boston in around an hour and a half to two hours. These trains would be making suburban stops north of Boston that an intercity train shouldn’t normally make, but it’s fine, the Lowell Line has wide stop spacing and the intermediate stops are pretty important post-industrial cities. At Portland, passengers can make a timed connection to trains to Bangor, on the same schedule but with shorter trainsets as the demand north of Portland is much weaker.

On the map, I also depict Boston-Cape Cod trains, which like Boston-Concord trains are really suburban trains but going farther. Potentially, the branch to Cape Cod – the Middleborough branch of the Old Colony Lines – could even run through with the Lowell Line, either the branch to Concord or the Wildcat Branch to Haverhill and Portland. Moreover, the sequencing of the branches should aim to give short connections to Boston-Albany high-speed trains as far as reasonable.

The issue of the Northeast Corridor

The Northeast Corridor wrecks the ITT plan in two ways, one substantial and one graphical.

The snag is that there should be service on legacy track running at a maximum speed of 160-200 km/h in addition to high-speed service on high-speed tracks. There may be some track sharing between New York and New Haven to reduce construction costs, using timed overtakes instead of full track segregation, but east of New Haven the high-speed trains should run on a new line near I-95 to bypass the Shore Line’s curves, and the Shore Line should be running electric regional trains to connect to the intermediate cities.

The graphical problem is that the distance between where the legacy route is and where the high-speed tracks should be is short, especially west of New Haven, and depicting a red line and a blue line together on the map is not easy. I will eventually post something at much higher resolution than 1 pixel = 500 meters. This also affects long-distance regional lines that I’d like to depict on the map but connect only to legacy trains on the Northeast Corridor, that is the Danbury and Waterbury Branches.

For planning purposes, figure that both run every half hour all day, are electric, run through to and beyond New York as branches of the New Haven Line, and are timed to have reasonable connections to high-speed trains to Albany and points north in New York. Figure the same for trains between New Haven and Providence, with some additional runs in the Providence suburbs giving 15-minute urban frequencies to such destinations as Olneyville and Cranston.

The substantial issue is that the Northeast Corridor is far too high-demand for a half-hourly ITT. Intercity trains run between New York and Boston better than hourly today, and that’s taking twice as long as a TGV and charging 2.5-4 times as much. My unspoken assumption when planning how everything should fit together is that there should be a 400-meter long train every 15 minutes on the corridor past New Haven, spaced evenly around Boston to overtake regional trains to Providence at consistent locations. Potentially, there should be more local trains taking around 1:50 and more express trains taking around 1:35, and then all timed transfers should be to the local trains.

On the New Haven Line, too, regional rail demand is much more than a train every half hour. Trains run mostly every half hour today, with management that is flagrantly indifferent to off-peak service, and trip times that are about 50% longer than they should be. Nonetheless, best practice is to set up timed transfers such that various branches all connect to the same train, so that passengers can connect between different branches. This mostly affects Waterbury; it’s useful to ensure that Waterbury trains arrive at Bridgeport with a short transfer to a train toward New Haven that offers a quick connection to trains to points north and east.

Planning HSR around timed connections

Not counting lines that are in the Boston sphere, or the lines around Albany, which I discussed two weeks ago, there are three lines proposed for timed connection to high-speed rail: New London-Norwich, Providence-Worcester-Fitchburg, Springfield-Greenfield.

All three are regional lines, not intercity lines. They are not optimized for intercity speed, but instead make a number of local urban and suburban stops. This is especially true of Springfield-Northampton-Greenfield, a line that Sandy Johnston and I have been talking about since 2014. A Springfield-Greenfield line with 1-2 intermediate stops might be able to do a one-way trip in around 39 minutes, at which point a 45-minute operator schedule may be feasible with a very tight turnaround regime – but there’s enough urban demand along the southern half of the route that adding stops to make it about 50 minutes with a one-hour operator schedule is better.

The Providence-Worcester line is likewise slower than it could be if it were just about Providence and Worcester. The reason is that high-speed rail compresses distances along its route. Providence-Boston by high-speed rail is about 22 minutes nonstop, including schedule contingency. Boston-Worcester is about the same – slower near Boston because of scheduling difficulties along the Turnpike and the inner Worcester Line, faster near the outer end because Worcester has no chance of getting a city center station but rather gets a highway station. Now, passengers have a range of transfer penalties, and to those who are averse to connections and have a high personal penalty, the trip between the two cities is more attractive directly than via Boston. But there are enough passengers who’d make the trip via Boston that the relative importance of intermediate points grows: Pawtucket, Woonsocket, Uxbridge, Millbury. In that situation, the importance of frequency grows (half-hourly is a must, not hourly) and that of raw speed diminishes.

The onward connection to Fitchburg is about three things. First, connecting Providence with Fitchburg. Second, connecting Worcester with Fitchburg. And third, connecting Fitchburg with the high-speed line. This makes investments into higher speed more valuable, since Fitchburg’s importance is high compared with that of points between Worcester and Fitchburg. The transfer between the line and high-speed rail should be timed in the direction of Fitchburg-to-Albany first of all, and Providence-to-Albany second of all, as the connections from the endpoints to Boston are slower than direct commuter trains.

The presence of this connection also forces the Worcester station to be at the intersection with the line to Providence. Without this connection, it may be better to site the station slightly to the west, at 290 rather than 146, as the area already has Auburn Mall.

Finally, the New London-Norwich line is a pure last-mile connector from the New London train station, which is forced to be right underneath the I-95 bridge over the river, to destinations to the north. The northern anchor is Norwich opposite the historic center, but the main destination is probably the Mohegan Sun casino complex. Already there are many buses connecting passengers from New York to the casino. The one-way trip time should be on the order of 21-22 minutes, but with a turnaround it’s a 30-minute schedule, and the extension south to the historic center of New London is for completeness; with a timed connection, trains could get between Penn Station and Norwich in around 1:20 counting connection time, and between Penn Station and Mohegan Sun in maybe 5 minutes less.

What about Vermont?

Vermont’s situation is awkward. Burlington is too far north and too small to justify a connection to high-speed rail by itself. A low-speed connection might work, but the line from Burlington south points toward Rutland and not New York, and connecting it onward requires reversing direction. If Vermont had twice its actual population this might be viable, but it doesn’t.

But Vermont is right between New York and Montreal. I generally don’t show New York-Montreal high-speed rail on my maps. It’s a viable line, but people in both cities severely overrate it, especially compared with New York-Toronto; I have to remind readers this whenever I write about international high-speed trains. In the event such a line does open, Burlington is the only plausible location for a Vermont stop – everything else is too small, even towns that historically did have rail service, like Middlebury. Rutland could get a line running partly on high-speed track and partly on legacy track taking it down to Glens Falls or Saratoga Springs to transfer to onward destinations, or maybe Albany if trains run 2-3 minutes apart in pairs every 30 minutes.

Current plans for Vermont try to connect it directly to Boston via New Hampshire, and that is wrong. The Vermonter route is mountainous from Greenfield to Burlington; trains will never be competitive with driving there. Another route under occasional study going into Boston from the north was even included on a 2009 wishlist of high-speed rail routes, under the traditional American definition of high-speed rail as “train that is faster than a sports bicycle.” That route, crossing mountains in both New Hampshire and Vermont, is even worse. The north-south orientation of the mountains in both states forces east-west routes to either stick to the lowlands or consolidate to strong enough routes that high-speed rail tunnels are worthwhile.

How much does this cost?

As always, I am going to completely omit the Northeast Corridor from this cost analysis; an analysis of that will happen later, and suffice is to say, the benefit-cost ratio if there’s even semi-decent cost control is extremely high.

With that in mind, the central pieces of this program are high-speed lines from Boston to Albany and from New Haven to Springfield, in a T system. The 99 km New Haven-Springfield line, timetabled at 45 minutes including turnaround and maybe 36 minutes in motion, is on the slow side for high-speed rail, as it is short and has a crucial intermediate station in Hartford. It does not need any tunnels or complex viaducts, and property takings are nonzero but light; the cost should not be higher than about $2-2.5 billion, utilizing legacy track for much of the way.

The Boston-Albany line is much costlier. It’s 260 km, and crosses the aforementioned north-south mountains in Western Massachusetts. Tunnels are unavoidable, including a few kilometers of digging required just west of Springfield to avoid a slowdown on suburban curves. At the Boston end, tunneling may also be unavoidable next to the Turnpike. The alternative is sharing a two-track narrows with the MBTA Worcester Line in Newton; it’s possible if the trains run no more than every 15 minutes, which is a reasonable short-term imposition but may be too onerous in the longer term if better service builds up more demand for commuter rail frequency in Newton. My best guess is that without Newton, the line needs around 20 km of tunnel and can piggyback on 35 km of existing lines at both ends, for a total cost in the $6-8 billion range. This figure is sensitive to whether my 20 km estimate is correct, but not too sensitive – at 40 it grows to maybe $9 billion, at 0 it shrinks to $4.5 billion.

Estimating the costs of the blue lines on the map is harder. All of them are, by the standard of high-speed rail, very cheap per kilometer. A track renewal machine on a one-third-in-tunnel German high-speed line can do track rebuilding for about a million euros per single-track-kilometer. All of these lines would also need to be electrified from scratch, for $1.5-3 million per kilometer. Stations would need to be built, for a few million apiece. My first-order estimate is $1 billion for the three blue connector lines and about the same for Boston-Portland-Bangor; the Hyannis and Concord lines would go in a regional rail basket. The NSRL tunnel should be $4 billion or not much more, and not what Massachusetts wants voters to believe it is to justify its decision not to build it.

The reason for the relatively limited map (e.g. no Montreal service) is that these lines are not such slam dunks that they’re worth it at any price. Cost control is paramount, subject to the bare minimum of good service (e.g. electrification and level boarding). For what I think a fair cost is, those lines are still good, providing fast connectivity across New England from most places to most other places. Moreover, the locations of the major nodes, like Worcester and Springfield, allow timing bus interchanges as well, providing further connections to various suburbs and city neighborhoods.

The red high-speed lines are flashy, but the blue ones are important too. That’s the key takeaway from planning in Switzerland, Austria, and the Netherlands, all of which have high rail usage without great geography for intercity rail. Trains should be planned coherently as a network, with all parts designed in tandem to maximize connectivity. This isn’t just about going between Boston and Springfield or Boston and Albany or New Haven and Springfield, but also the long tail of weaker markets using timed connections, like New Haven-Amherst, Brockton-Worcester, Dover-Providence, Stamford-Mohegan Sun, and so on. A robust rail network based on ITT design principles could make all of these and many more connections at reasonable cost and speed.

Empire State High- and Low-Speed Rail

If Swiss planners were hired to design an intercity rail network for New York State, they might propose something that looks like this:

The trip times depicted on the map are a few minutes longer than intended, especially next to a terminus station like Niagara Falls, Watertown, and Ithaca. The depicted times are inclusive of turnaround time: the 45-minute Buffalo-Niagara Falls line is intended to take around 35 minutes in actual service, with 10-minute turnarounds.

Swiss planning is based on hourly and half-hourly timetables repeating all day on a clockface pattern: if a train leaves your station at 8:24 am, a train will leave your station at xx:24 all day, and if the line runs every half hour then also at xx:54. Moreover, at major nodes, trains are timetabled to arrive a few minutes before the hour and depart a few minutes after, letting passengers connect between different trains with minimal wait. To minimize transfer time and turn time, trains run as fast as necessary – that is, the state invests in higher-speed lines to ensure connections between major cities take a few minutes less than an hour. The Bahn 2000 program set up connections between Zurich, Basel, and Bern taking just less than an hour, with a few further connections elsewhere taking just less than an integer number of half-hours; the Bahn 2030 program aims to do the same with more cities all over the country.

The above map is an adaptation of the concept to New York State. I hope the explanation of how to adapt Switzerland to New York will be of interest to rail advocates elsewhere – the differences between the two geographies matter elsewhere, for example in Germany, France, or Sweden, or for that matter in California or New England.

High-speed rail

There is no high-speed rail in Switzerland, unless one counts the mixed passenger and freight rail tunnels through the Alps, which allow 250 km/h passenger trains. The Bahn 2030 planning calls for a 2-hour trip time between Zurich and Lugano, a distance of about 170 km, even with heavy tunneling under all significant mountains; with so much tunneling, 1.5-hour trips are easy and even 1-hour trips are feasible with a bypass around Zug. Clearly, even when higher speeds are allowed, Swiss planning sticks to low- and medium-speed rail, targeting an average speed of about 120 km/h.

This works for Switzerland, a small country in which even Geneva is only 2:45 from Zurich. In New York, it does not. At the speed of upgraded legacy rail, comparable to the Northeast Corridor, the links on the above map along the high-speed spine would take 2 hours each rather than an hour. New York-Buffalo trains would take 6 hours, too long for most travelers, and New York-Rochester would take 5 hours, which is marginal at best. Trains doing New York-Albany in 2 hours could get fairly popular, but even that is long enough that cutting it to just less than an hour is feasible.


Trains are to run every half hour, with the exception of urban lines, namely Buffalo-Niagara Falls, Albany-Troy-Mechanicsville, and Utica-Rome, which run every 15 minutes. The reason for the half-hourly frequency is that all lines need it for either capacity or ridership. The lines either run to New York, which is so big it can easily fill a train every half hour and perhaps even every 15 minutes, or are quite short, so that running only every hour reduces ridership and it’s better to run shorter trains every 30 minutes.

With half-hourly timetables, a stub-end line can take an integer number of quarter-hours and not just half-hours. For example, Syracuse and Albany should have a pulse at :00 and :30 every hour. This in turn means that trains from Albany to Glens Falls can take 1:15, departing Albany just after :00 and :30, arriving at Glens Falls just before :15 and :45, turning back toward Albany just after :15 and :45, and then returning to Albany just before :00 and :30.

The only worry with quarter-hour trip times is that every cycle must sum up to an integer number of half-hours, not quarter-hours. Otherwise, some connections are broken, offset by 15 minutes. Thankfully, the only cycle on this map is New York-Albany-Syracuse-Binghamton-New York, which takes 7 hours.

Syracuse regional rail

Syracuse is depicted as having the most expansive regional rail network in the state, despite being the smallest of Upstate New York’s four major metropolitan areas. The reason is that the goal of the planned network is to provide intercity rather than local service. Rochester has some useful urban lines, for example to Freeport or northwest to the lakefront, but they are so short that they should run every 10 or 15 minutes and not every half hour. However, Rochester has no significant independent towns within an hour or so by rail, and thus there are no timed connections there. In contrast, Syracuse is located right between Watertown, Oswego, Auburn, and Cortland with its connection onward to Ithaca.

The Syracuse system is intended to be fully on the RegionalBahn side of the S-Bahn vs. RegionalBahn divide. The shared segment between Syracuse and the split between the lines to Oswego and Watertown is not meant to overlay to run frequent urban service. Instead, trains should tailgate, followed by a gap of nearly half an hour. Syracuse-bound trains may well call at Liverpool at :20 and :22, arriving at Syracuse at :25 and :27 to exchange passengers with other trains and then continue south, one of Oswego and Watertown paired with Cortland and Binghamton and the other terminating. If north-south S-Bahn service is desired, trains should be slotted in between the intercity trains.

New lines

The map depicts greenfield alignments for the high-speed line except on the approaches to New York and Toronto, and legacy alignments for the low-speed lines.

As in Switzerland, the low-speed lines do not necessarily slavishly adhere to legacy alignments. However, the deviations are not the same. Switzerland uses bypasses and tunnels to speed lines up. In New York, the main mechanisms to speed up lines are electrification, track renewal, and higher superelevation. Tunnels are too expensive for the population density of Upstate New York. I can see some bypasses, potentially getting Syracuse-Cortland and Cortland-Binghamton down to 30 minutes each, but none of the Upstate cities off the high-speed line is big enough to justify major civil works.

The one depicted bypass on a blue-colored line is the use of the Boonton Branch in New Jersey to offer an express bypass around the Morristown Line with its dense station spacing. This requires some additional tracks on busy urban regional lines as well as a short tunnel in Paterson, but New York is big enough that investing in faster service to Dover, Delaware Water Gap, and Scranton is worth it.

Upstate, the important deviations involve restoring old tracks, including between Cortland and Ithaca and within some town centers. Corning and Glens Falls both have disused rail alignments serving their centers better than the existing freight lines. But most importantly, Syracuse has an underused freeway running east-west through its center, which I am assuming replaced with a rail line. This is not a new idea – Syracuse is already removing a branch of the freeway, which should be used for a rail connection toward Binghamton, and even the mainline is a vestige of when midcentury planners thought Upstate cities would keep growing. The current Syracuse station is at an inconvenient location, making rail realignment a good use of the right-of-way.

Onward connections

New York State is much more integrated with its neighbors than Switzerland – it’s all the same country. There is extensive interstate travel, and rail planning must accommodate this. Forget the Deutschlandtakt – an Americatakt would be the most complex rail plan in a developed country out of sheer size. Thankfully, the connections depicted on the New York State plan accommodate interstate travel fairly well.

Going east, there are connections to Vermont, Massachusetts, and Connecticut. Albany-Boston can be done in around an hour, which makes for a half-hour takt connection between Albany and Springfield and 45 minutes minus turnaround between Springfield and Boston. Springfield-New Haven is 30 minutes by high-speed rail or 45 minutes by fast legacy rail, both with a stop at Hartford and few to no others; Springfield can then get its own small regional rail line toward Northampton (with some urban overlays for an S-Bahn) and Greenfield. Vermont can get a slow line to Rutland, and/or a fast line to Burlington continuing to Montreal; thence New York-Montreal and Boston-Toronto trains can be timed to connect at Albany, with New York-Toronto trains slotted in between, timed to connect only to the more frequent urban lines like Buffalo-Niagara Falls.

Going south, New York is separated from Pennsylvania by the northern reach of the Appalachians, called the Southern Tier in New York and the Northern Tier in Pennsylvania. This area had many coal mines in the 19th century and as a result has many legacy rail lines, but they are curvy and connect villages. But Scranton is a significant city on a nice line with Allentown and Philadelphia; unfortunately, the Philadelphia-Allentown line stretches via Reading and the Allentown-Scranton line is hilly and curvy, justifying some greenfield construction with some tunneling near the northern end.

Finally, going west, the I-90 route serves Erie and the Midwest. But this is a plausible high-speed rail connection toward Chicago, and so no low-speed interface is needed within the state. Erie could get a line to Youngstown and Pittsburgh, but it would be slower than connecting between high-speed trains in Cleveland; the largest city between Erie and Youngstown is Meadsville, population 13,000.


The cost of the high-speed spine is considerable, but if New York can keep it to the level of France (around $25 million/km), or even Germany (around $35 million/km), the benefits should exceed the costs. New York is huge, and even though nothing in Upstate New York is, the combined populations of Syracuse, Rochester, and Buffalo would add up to a big French or German city. And then there is Toronto at the other end, anchoring everything.

The low-speed lines should be quite cheap. Track renewal in Germany is around $1 million per single-track kilometer; at the frequency envisioned, all the low-speed lines can stay single-track with passing segments. Electrification is maybe $1.5 million per kilometer in Israel, despite a lawsuit that delayed the project by three years.

Is this feasible?

Technically, all of this is feasible. Good transit advocates in the Northeastern United States should push elected officials at the federal and state levels to quickly plan such a system and aim to begin construction early this decade. Bahn 2000 was supposed to take the 1990s to be built, but was delayed to 2004; this is a bigger program but can still happen by 2030 or so.

The trip times, frequencies, and coverage chosen for the map are deliberately conservative. It’s possible to squeeze higher speed at places, and add more branches to smaller towns, like Rochester-Niagara Falls or Buffalo-Jamestown. Bahn 2000 is followed up with Bahn 2030 or Bahn 2035, and likewise rail improvements can accrete in the United States. But as a starter system, this is a solid network connecting all large and nearly all small cities in New York State to one another with maximum convenience and minimum hassle. I hope state planners take heed and plan to invest soon.

The Different Travel Markets for Regional Rail

At a meeting with other TransitMatters people, I had to explain various distinctions in what is called in American parlance regional rail or commuter rail. A few months ago I wrote about the distinction between S-Bahn and RegionalBahn, but made it clear that this distinction was about two different things: S-Bahns are shorter-distance and more urban than RegionalBahns, but they’re also more about service in a contiguous built-up area whereas RegionalBahns have the characteristics of interregional service. In this post I’d like to explore the different travel markets for regional rail not as a single spectrum between urban and long-range service, but rather as two distinct factors, one about urbanity or distance and one about whether the line connects independent centers (“interregional”) or a monocentric urban blob (“intraregional”).

This distinction represents a two-dimensional spectrum, but for simplicity, let’s start with a 2*2 table, so ubiquitous from the world of consulting:

Connection \ Range Short Long
Intraregional Urban rail, S-Bahn Big-city suburban rail
Interregional Polycentric regional rail RegionalBahn

The notions of mono- and polycentricity are relative. Downtown Providence, Newark, and San Jose all have around 60,000 jobs in 5 km^2. But Caltrain and the Providence Line are both firmly in the RegionalBahn category, the other end being Downtown San Francisco or Boston, 70-80 km away with 300,000-400,000 jobs in 5-6 km^2. Newark, in an essentially contiguous urban area with New York, 16 km from Midtown and its 1.2 million jobs in 6 km^2, is relatively weaker and does not fit into the interregional category; a New York-Newark line is an S-Bahn.

Size matters

On the 2*2 table, the appellations “big-city” and “polycentric” are necessary. This is because longer-range rail lines are likelier to get out of the city and its immediate suburbs and connect to independent urban centers. Exceptions mostly concern the size of the primary urban cluster. If it is large, like New York, it can cast a shadow for tens of kilometers in each direction: commuter volumes are high from deep into Long Island, as far up the Northeast Corridor as Westport, as far up the Hudson as northern Westchester, and so on. In Paris, I wouldn’t be comfortable describing any of the RER and Transilien lines as RegionalBahn. In London, the closest independent cities of reasonable size are Cambridge, Brighton, Oxford, and Portsmouth, the first two about 80 km away and the last two about 100.

Tokyo, about as big as New York and London combined, casts an even longer shadow. In my post on S-Bahns and RegionalBahns I called some of its outer regional rail branches RegionalBahn, giving the examples like the Chuo Line past Tachikawa. But even that line is not really interregional in any meaningful way. It stays within the Tokyo prefecture as far as Takao, 53 km from Tokyo Station, and commuter service continues until Otsuki at kp 88, but everything along the line is bedroom communities for Tokyo or outright rural. The branching and short-turns at Tachikawa mean that the Chuo Line through Tachikawa is a long S-Bahn, and past Tachikawa is really a suburban commuter line too long to be an S-Bahn but too monocentric and peaky to be Regionalbahn (the peak-to-base frequency ratio is about 2:1, whereas German RegionalBahn is more commonly 1:1).

At the other end, we can have regional rail that is short-range but connects two distinct centers. This occurs when relatively small cities are in proximity to each other. In a modern first-world economy, these cities would form a polycentric region, like the Rhine-Ruhr or Randstad. Smaller regions with these characteristics include the Research Triangle, where relatively equal-size Raleigh and Durham are 40 rail kilometers apart, and Nord, where Lille is 30-50 km from cities like Douai and Valenciennes. This may even occur in a region with a strong primary center, if the secondary center is strong enough, as is the case for Winterthur, 28 km from Zurich, which has Switzerland’s fourth highest rail ridership.

Size is measured in kilometers, not people. Stockholm is a medium-size city region, but Stockholm-Uppsala is firmly within RegionalBahn territory, as the two cities are 66 km apart. Randstad’s major cities are all closer to each other – Amsterdam-Rotterdam is about 60 km – and that’s a region of 8 million, not 3 million like Stockholm and the remainder of Uppland and Södermanland.

The issue of frequency

The importance of the 2*2 table is that distance and urban contiguity have opposite effects on frequency: high frequency is more important on short lines than on long lines, and matching off-peak frequency to peak frequency is more important on interregional than intraregional lines.

Jarrett Walker likes to say that frequency is freedom, but what frequency counts as freedom depends on how long passengers are expected to travel on the line. Frequency matters insofar as it affects door-to-door travel time including wait time, so it really ought to be measured as a fraction of in-vehicle travel time rather than as an absolute number. An urban bus with an average passenger trip time of 15 minutes should run every 5 minutes or not much longer; if it runs every half hour, it might as well not exist, unless it exists for timed connections to longer-range destinations. But an intercity rail line where major cities are 2 hours apart can easily run every half hour or even every hour.

The effect of regional contiguity is more subtle. The issue here is that an intraregional line is likely to be used mostly by commuters at the less dense end. The effect of distance can obscure this, but within a large urban area, a 45-minute train will be full of commuters traveling to the primary city in the morning and back to the suburbs in the afternoon or evening; the same train between two distinct cities, like Boston and Providence, will not have so many commuters. In contrast, the same 45-minute trip will get much more reverse-commute travel and slightly more non-commute travel if it connects two distinct cities, because the secondary city is likelier to have destinations that attract travelers.

In no case are the extreme peak-to-base ratios of American commuter lines justifiable. Lines with tidal commuter flows can run 2:1 peak-to-base ratios, as is common in Tokyo, but much larger ratios waste capacity. The marginal cost of service between the morning and afternoon peaks is so low until it matches peak service that having less midday than peak service at all is only justifiable in very peaky environments. The 45-minute suburbs of New York, Tokyo, and other huge cities can all live with a 2:1 ratio, but other lines should have lower ratios, and interregional lines should have a 1:1 ratio.

The implication is that just as peak-to-base ratios going as high as 2:1 are acceptable for long-range intraregional lines, short-range interregional lines must run a constant, high frequency all day. I would groan at the thought of even half-hourly frequency on a 40-km interregional line; the worst I’m comfortable with is 15-20 minutes all day. Of note, such lines are necessarily pretty fast, since by assumption they make few intermediate stops to speed up travel between the two main cities – if there are significant cities in the middle then the lines connect even shorter-range cities and should be even more frequent.

Urban, suburban, intercity

Individual lines may have the characteristics of multiple variants of regional rail. They pass through urban neighborhoods on their way to outlying areas, which may be suburbs or independent cities; they may also pass through multiple kinds of independent areas.

In practice, in big cities this leads to three tiers on the same line: urban at the inner end, suburban at the middle end, interregional at the outer end. Inversions, in which there are independent cities and then suburbs, are possible but extremely rare – I can’t think of any in Paris, London, or New York, and arguably only three in Tokyo (Chiba, Saitama, Yokohama); fundamentally, if there are suburbs of the primary city beyond your municipality, then your municipality is likely to itself be popular as a suburb of the primary city.

That regional lines have these three tiers of demand type does not mean that every single regional line does. Some lines don’t reach any significant independent city. Some don’t usefully serve close-in urban areas – for example, the Providence Line barely serves anything urban, since the stop spacing is wide in order to speed up travel to high-demand suburbs and to Providence and the closest-in urban neighborhoods have Orange Line subway service. In rare cases, the suburban tier may be skipped, because there just isn’t much tidal suburban commuter ridership; in Boston, the Newburyport Line is an example, since its inner area has unbroken working-class urban development almost all the way to Salem, and then there’s almost nothing between Salem and Newburyport.

This does not mean that suburbs are always in between urban areas and independent cities – this is just a specific feature of large metropolitan areas. In smaller ones, the middle tier between urban and long-range interregional service is occupied by short-range interregional service rather than suburban commuter rail. Skipping the suburban tier, which is rare enough in large cities that in the cities I think about most often the only example I can come up with is the Newburyport Line, is thus completely normal in smaller cities.


There are common best practices for commuter rail: electrification, level boarding, frequent clockface schedules, timed transfers, fare integration, proof of payment fare collection.

However, high frequency means different things on lines of different characteristics. An interregional line should be running consistent all-day frequency, and if it is long enough could make do with half-hourly trains with timed connections to suburban buses; an urban line should be running every few minutes as if it were a metro line. Regional rail lines with characteristics off the main diagonal of the S-Bahn to RegionalBahn spectrum have different needs – suburban lines can have high peak frequency to reduce road congestion, although they should still have useful off-peak frequency; short-range interregional lines should run every 10-20 minutes all day.

The distinctions between intraregional and interregional lines and between short- and long-range lines may also affect other aspects of planning: station spacing, connections to local surface transit, connections at the city center end, through-running, etc. Even when the best industry practices are the same in all cases, the relative importance of different aspects may change, which changes what is worth spending the most money on.

Since an individual line can serve multiple markets on its way from city center to a faraway outlying terminal, it may be useful to set up a timetable that works for all of these markets and their differing needs. For example, urban lines need higher frequency than suburban and interregional ones, so a regional line with significant urban service should either branch or run short-turn trains to beef up short-range frequency. If there is a suburban area in the middle with demand for high peak frequency but also a secondary city at the outer end, it may be useful to give the entire line high all-day frequency, overserving the line off-peak just because the cost of service is low.

Ultimately, regional rail is about using mainline rail to fulfill multiple functions; understanding how these functions works is critical for good public transportation.

How Fast New York Regional Rail Could Be Part 3

In the third and last installment of my series posting sample commuter rail schedules for New York (part 1, part 2), let’s look at trains in New Jersey. This is going to be a longer post, covering six different lines, namely all New Jersey Transit lines that can go to Penn Station, including one that currently does not (Raritan Valley) but could using dual-mode locomotives.

As on Metro-North and the LIRR, very large improvements can be made over current schedules, generally reducing trip times by 30-43%, without straightening a single curve. However, electrification is required, as is entirely new rolling stock, as the electric locomotives used by NJ Transit are ill-fit for a fast schedule with many stops. Moreover, all low platforms must be raised to provide level boarding and some must be lengthened to avoid overuse of selective door opening, which may require a few new grade separations on the North Jersey Coast Line. As a first-order estimate, 50-something trainsets are required, each with 8-12 cars. This is not quite free, but the cost is low single-digit billions: about $1.5 billion for trains, maybe $400 million for 160 km of electrification, and around $700 million for what I believe is 70 low- or short-platform stations.

The timetables

Here is a spreadsheet detailing speed zones for all New Jersey Transit lines passing through Newark. In support of previous posts, here are other similar spreadsheets:

  • New Haven Line (express schedule, add stop penalties as appropriate for locals) – the spreadsheet is about a minute too fast, missing some slowdowns in the terminal, and the version in my post (part 1) corrects for that
  • Harlem Line
  • Hudson Line locals and expresses
  • LIRR Main Line (including Port Jefferson, not covered in my posts)

Line by line schedules

The New Jersey Transit timetables are less consistent than the east-of-Hudson ones; I attempted to look at local midday off-peak outbound trains whenever possible.

Northeast Corridor

Station Current time Future time
New York 0:00 0:00
Secaucus 0:09 0:06
Newark Penn 0:18 0:10
Newark South Street 0:12
Newark Airport 0:24 0:15
North Elizabeth 0:27 0:17
Elizabeth 0:30 0:19
Linden 0:35 0:23
Rahway 0:39 0:25
Metropark 0:45 0:29
Metuchen 0:49 0:32
Edison 0:54 0:36
New Brunswick 0:59 0:39
Jersey Avenue 1:03 0:41
Monmouth Junction 0:47
Princeton Junction 1:16 0:53
Hamilton 1:23 0:58
Trenton 1:35 1:01

This fastest rush hour express trains do the trip in 1:12-1:13, and Amtrak’s Regionals range between 0:55 and 1:04, with trains making all nominal Amtrak stops (including rarely-served New Brunswick and Princeton Junction) taking 1:15.

North Jersey Coast Line


Station Current time Future time
New York 0:00 0:00
Secaucus 0:09 0:06
Newark Penn 0:19 0:10
Newark South Street 0:12
Newark Airport 0:24 0:15
North Elizabeth 0:17
Elizabeth 0:29 0:19
Linden 0:35 0:23
Rahway 0:39 0:25
Avenel 0:45 0:29
Woodbridge 0:48 0:31
Perth Amboy 0:55 0:34
South Amboy 1:00 0:37
Aberdeen 1:08 0:42
Hazlet 1:12 0:45
Middletown 1:19 0:49
Red Bank 1:25 0:53
Little Silver 1:29 0:56
Monmouth Park 0:59
Long Branch 1:39-1:42 1:01
Elberon 1:46 1:04
Allenhurst 1:50 1:07
Asbury Park 1:54 1:09
Bradley Beach 1:57 1:11
Belmar 2:01 1:14
Spring Lake 2:05 1:16
Manasquan 2:09 1:19
Point Pleasant Beach 2:15 1:22
Bay Head 2:24 1:23


In electric territory, that is up to Long Branch, my schedule cuts 38% from the trip time, but in diesel territory the impact of electrification nearly halves the trip time, cutting 48%.

Raritan Valley Line

Station Current time Future time
New York (0:00) 0:00
Secaucus (0:09) 0:06
Newark Penn (0:18) 0:10
Newark South Street 0:12
Union 0:27 0:17
Roselle Park 0:30 0:19
Cranford 0:35 0:22
Garwood 0:38 0:24
Westfield 0:41 0:25
Fanwood 0:46 0:28
Netherfields 0:49 0:30
Plainfield 0:53 0:32
Dunellen 0:58 0:35
Bound Brook 1:03 0:39
Bridgewater 1:06 0:41
Somerville 1:12 0:44
Raritan 1:15 0:47
North Branch 1:21 0:50
Whitehouse 1:28 0:54
Lebanon 1:34 0:58
Annandale 1:39 1:01
High Bridge 1:52 1:04


The Raritan Valley Line does not run through to Manhattan but rather terminates at Newark Penn because of capacity constraints on the mainline, so the New York-Newark trip times are imputed from Northeast Corridor trains. So really the trip time difference is 1:34 versus 0:54, a reduction of 42% in the trip time thanks to electrification.

Morristown Line

Station Current time Future time
New York 0:00 0:00
Secaucus 0:10 0:06
Newark Broad Street 0:19 0:11
Newark 1st Street 0:13
East Orange 0:15
Brick Church 0:25 0:17
Orange 0:28 0:19
Highland Avenue 0:21
Mountain 0:23
South Orange 0:33 0:25
Maplewood 0:38 0:27
Millburn 0:42 0:29
Short Hills 0:45 0:31
Summit 0:49-0:50 0:34
Chatham 0:55 0:39
Madison 0:59 0:41
Convent 1:03 0:44
Morristown 1:07 0:47
Morris Plains 1:11 0:50
Mount Tabor 1:18 0:54
Denville 1:21 0:56
Dover 1:32 1:00
Mount Arlington 1:40 1:06
Lake Hopatcong 1:45 1:09
Netcong 1:53 1:12
Mount Olive 1:58 1:15
Hackettstown 2:14 1:22


This timetable is cobbled from two different train runs, as electric wires only run as far out as Dover, so trains from New York only go as far as Dover, and trains to Hackettstown serve Hoboken instead. Observe the 35% reduction in trip time in electric territory despite making a few more stops, and the 48% reduction in trip time in diesel territory.

Gladstone Branch

Station Current time Future time
New York (0:00) 0:00
Secaucus (0:10) 0:06
Newark Broad Street (0:19) 0:11
Newark 1st Street 0:13
East Orange 0:24 0:15
Brick Church 0:26 0:17
Orange 0:29 0:19
Highland Avenue 0:31 0:21
Mountain 0:33 0:23
South Orange 0:36 0:25
Maplewood 0:39 0:27
Millburn 0:42 0:29
Short Hills 0:45 0:31
Summit 0:50 0:34
New Providence 0:55 0:37
Murray Hill 0:58 0:40
Berkeley Heights 1:02 0:43
Gillette 1:05 0:46
Stirling 1:08 0:48
Millington 1:11 0:50
Lyons 1:14 0:53
Basking Ridge 1:17 0:56
Bernardsville 1:20 0:57
Far Hills 1:26 1:02
Peapack 1:30 1:06
Gladstone 1:37 1:08


As the line is entirely electrified, the time saving is only 30%. Note that Gladstone Branch trains do not run through to Penn Station except at rush hour, so I’m imputing New York-Newark Broad trip times using the Morristown Line.

Montclair-Boonton Line

Station Current time Future time
New York (0:00) 0:00
Secaucus (0:09) 0:06
Newark Broad Street (0:20) 0:11
Newark 1st Street 0:13
Newark Park Street 0:15
Watsessing Avenue 0:26 0:18
Bloomfield 0:28 0:19
Glen Ridge 0:31 0:21
Bay Street 0:34 0:23
Walnut Street 0:37 0:24
Watchung Avenue 0:40 0:26
Upper Montclair 0:43 0:28
Mountain Avenue 0:45 0:30
Montclair Heights 0:47 0:31
Montclair State U 0:50 0:33
Little Falls 0:56 0:37
Wayne-Route 23 1:00 0:40
Mountain View-Wayne 1:02 0:43
Lincoln Park 1:07 0:46
Towaco 1:11 0:49
Boonton 1:18 0:53
Mountain Lakes 1:22 0:56
Denville 1:27 0:59
Dover 1:34 1:04


Beyond Dover, a handful of evening trains continue to Hackettstown. Interestingly, the saving from electrification is only 32% – and the train I drew the current schedule from is a Hoboken diesel train. Electric trains run from New York to Montclair State University, but are for some reason actually slightly slower today than the Hoboken diesels on the shared Newark-MSU segment. I suspect that like the LIRR, NJ Transit does not timetable electric trains to be any faster than diesels on shared segments even though their performance is better.


There are specific patterns to where my schedule outperforms the existing one by the largest margin and where it does so by the smallest margin.

Terminal zone

Between New York and Newark, I am proposing that trains take 10-11 minutes, down from 18-20 today, cutting 45% from the trip time. This comes from several factors. The first is avoiding unnecessary slowdowns in terminal zones: Penn Station should be good for about 50 km/h, ideally even more if there are consistent enough platform assignments that the turnouts can be upgraded to be faster; Newark should not impose any speed limit whatsoever beyond that of right-of-way geometry.

The second is increasing superelevation and cant deficiency. The worst curve is the turn from Harrison to Newark; its radius is just shy of 500 meters, good for around 110 km/h at normal cant and cant deficiency (150 mm each), or even 120 km/h if the cant is raised to 200 mm in support of higher-speed intercity service. But the current speed limit is a blanket 45 mph, even on Amtrak, whose cant deficiency is fine. The Newark approach is then even slower, 35 mph, for no reason. It’s telling that on my schedule, the Secaucus-Newark speedup is even greater than the New York-Secaucus speedup, despite the Penn Station interlocking morass.

The third is reducing schedule padding. The schedules appear extremely padded for what NJ Transit thinks is a capacity problem but is not really a problem in the midday off-peak period. Between 9 am and noon, 18 trains depart Penn Station going west, 10 on the Northeast Corridor and North Jersey Coast and 8 on the Morris and Essex Lines and the Montclair Line.

Unelectrified lines

On lines without electrification, the time savings from electrification are considerable, with the exception of the Boonton Line. This is especially notable on the tails of the North Jersey Coast and Morristown Lines, both of which allow for 48% reductions in trip time, nearly doubling the average speed.

This is related to the issue of low platforms. These tails have low platforms, whereas the inner segment of the Raritan Valley Line (up to Westfield), which already has mostly high platforms, does not exhibit the same potential speed doubling. Outer segments may also not be well-maintained, leading to non-geometric speed limits. Between Long Branch and Bay Head the tracks are fairly straight, but the existing speed limits are very low, at most 60 mph with most segments limited to 40 or even 25 or less.

Upgraded lines

In contrast with the enormous slowdowns between New York and Newark and on unelectrified tails, the workhorse inner segments (including the entire Northeast Corridor Line) radiating out of Newark are only about 1.5 times as slow as they can be, rather than twice as slow. The Gladstone Branch, which runs EMUs rather than electric locomotive-hauled trains, manages to be only about 1.37 times as slow, in large part courtesy of low platforms.

Of course, 1.5 times as slow is still pretty bad. This is because no line on NJ Transit is truly modern, that is running all EMUs serving high platforms. But the electric lines manage to be less bad than the diesel lines, and the suburbs less bad than the New York-Newark segment with its excessive timetable padding and terminal zone slowdowns.

How to get there from here

NJ Transit has a problem: perhaps unaware of the new FRA regulations, it just ordered bilevel EMUs compliant with the old rather than new regulations. If it can cancel the order, it should do so, and instead procure standard European EMUs stretched to the larger clearances of the American (or Nordic) railway network.

Simultaneously, it should complete electrification of the entire Penn Station-feeding system, including the Raritan Valley Line even though right now it does not run through to New York. This includes some outer branches with low traffic, not enough to justify electrification on their own; that is fine, since the 31 km of wire between Dover and Hackettstown, 25 km between Long Branch and Bay Head, 27 between Raritan (where semi-frequent service ends) and High Bridge, and 30 between MSU and Denville permit a uniform or mostly uniform fleet with no diesel under catenary. EMUs are far more reliable than anything that runs on diesel, and if NJ Transit retires diesels and only runs EMUs on the most congested segment of the network, it will be able to get away with far less schedule padding.

In Boston, at Transit Matters we’ve likewise recommended full systemwide electrification, but with priority to lines that connect to already-electric infrastructure, that is the Stoughton branch of the Providence Line, the Fairmount Line (which is short enough to use Northeast Corridor substations), and subsequently the entire South Station-feeding system. By the same token, it is more important to electrify the outer edges of the Morristown and North Jersey Coast Lines and the entire Raritan Valley Line than to electrify the Erie lines not analyzed in this post, since the Erie lines’ infrastructure points exclusively toward Hoboken and not New York.

In addition to electrification, NJ Transit must replace all low platforms with high platforms. This should generally be doable with ramp access rather than elevators to save money, in which case a double-track station should be doable for about $10 million, if Boston and Philadelphia costs are any indication. In addition to speeding up general boarding, high platforms permit wheelchair users to board trains without the aid of an attendant or conductor.

All of this costs money – the infrastructure should cost somewhat more than $1 billion, and new rolling stock should cost about $1.5 billion at European costs, or somewhat more if there’s an American premium for canceling the in-progress contract for inferior equipment. But none of this costs a lot of money. New Jersey is ready to sink $2.75 billion of state money as part of an $11 billion Gateway tunnel that would do nothing for capacity (since it four-tracks the tunnel but not the surface segments to Newark); it should be ready to spend about the amount of money on a program that is certain to cut 25-50% off of people’s travel time and perhaps halve operating costs.