Category: High-Speed Rail

More on the Deutschlandtakt

The Deutschlandtakt plans are out now. They cover investment through 2040, but even beforehand, there’s a plan for something like a national integrated timetable by 2030, with trains connecting the major cities every 30 minutes rather than hourly. But there are still oddities that are worth discussing, especially in the context of what Germans think trains are capable of and what is achieved elsewhere.

The key is the new investment plans. The longer-term plans aren’t too different from what I’ve called for. But somehow the speeds are lower. Specifically, Hamburg-Hanover is planned to be a combination of legacy rail (“ABS”) and newly-built high-speed rail (“NBS”), dubbed the Alpha-E project, with trains connecting the two cities in 63 minutes.

The point of an integrated takt timetable is that trains should connect major nodes (“knots”) in just less than an integer number of half-hours for hourly service, or quarter-hours for half-hourly service. Trains connect Zurich and Basel in 53 minutes and each of these two cities with Bern in 56 minutes, so that passengers can change trains on the hour and have short connections to onward destinations like Biel, St. Gallen, and Lausanne. To that effect, Switzerland spent a lot of money on tunnels toward Bern, to cut the trip time from somewhat more than an hour to just less than an hour. So the benefits of cutting trip times from 63 minutes to just less than an hour are considerable.

What’s more, it is not hard to do Hamburg-Hanover in less than an hour. Right now the railway is 181 km long, but the planned Alpha-E route is shorter – an alignment via the A 7 Autobahn would be around 145 km long. The Tokaido Shinkansen’s Hikari and Nozomi trains run nonstop between Nagoya and Kyoto, a distance of 134 km, in 34 minutes. Kodama trains make two additional stops, with long dwell times as there are timed overtakes there, and take 51 minutes. Shinkansen trains have better performance characteristics than ICE trains, but the difference in the 270-300 km/h range is around 25 seconds per stop, and the Tokaido Shinkansen is limited to 270 km/h whereas an Alpha-E NBS would do 300. So doing Hamburg-Hanover in less than 40 minutes is eminently possible.

Of course, major cities have slow approaches sometime… but Hamburg is not a bigger city than Kyoto or Nagoya. It’s about comparable in size to Kyoto, both city proper and metro area, and much smaller than Nagoya. Hanover is a lot smaller, comparable to cities served by Hikari but not Nozomi, like Shizuoka and Hamamatsu. Hamburg-Hanover has 12 km between Hamburg and Harburg where trains would be restricted to 140 km/h, and around 6 in Hanover where trains would be restricted to 130 km/h; in between they’d go full speed, which at the performance characteristics of the next-generation Velaro would be a little more than 35 minutes without schedule padding and maybe 38 minutes with. This fits well into a 45-minute slot in the takt, permitting both Hanover and Hamburg to act as knots.

Moreover, if for some reason a full NBS is not desirable – for example, if NIMBY lawsuits keep delaying the project – then it’s possible to built a partial NBS to fit into an hourly time slot, trains taking around 53 minutes. The cost per minute saved in this context is fairly consistent, as this is a flat area and the legacy line is of similar quality throughout the route; if for some reason the cost per minute saved is too high, e.g. if nuisance lawsuits raise construction costs above what they should be on such a route, which is around 15-20 million euros per kilometer, then going down only to 53 minutes is fine as it makes the hourly takt work well.

And yet, it’s not done. The biggest cities are not planned to have regular half-hourly knots, because there’s too much traffic there. But Hanover is in fact a perfect place for a knot, with trains going east to Berlin, west to the Rhine-Ruhr, north to Hamburg, and south to Frankfurt and the cities of Bavaria. Hamburg is at the northern margin of the country, with trains going mostly south to Hanover, but having some timed connection with trains continuing north to Kiel and eventually Copenhagen is not a bad idea.

For some reason, German rail activists, including presumably the ones who pushed the Deutschlandtakt from the bottom up while the ministry of transport was run by pro-car conservatives, are just too conservative about the capabilities of trains. I’ve seen one of the D-Takt groups, I forget which one, criticize plans to build an NBS between Hanover and Bielefeld, a segment on which the existing line is fairly slow, on the grounds that it could never fit into a knot system. It is not possible to do the roughly 100 km between Hanover and Bielefeld (actually closer to 95 km) in less than half an hour to fit a knot, they say – average speeds higher than 200 km/h are only found on very long nonstop stretches of high-speed rail, as in France, they insist. Shinkansen trains achieve such speeds over such segments every day, and even with the slightly lower performance characteristics of the next-generation Velaro, Hanover-Bielefeld in 24 technical minutes and 26 minutes with 7% pad (and the Shinkansen only has 4% pad) is feasible.

I genuinely don’t know why there is such conservatism among German rail planners and advocates. It could be that Europeans don’t like learning from Asia, just as Americans don’t like learning from Europe. There are examples of faster trains than in Germany within Europe, but maybe German advocates discount French and Spanish examples because of genuine problems with French and Spanish rail operations, leading them to also make excuses like “the trains run nonstop for 500 km and that’s why they’re fast” to avoid adopting the things where France and Spain are genuinely superior to Germany.

Nothing about the integrated timed transfer schedule idea impedes high speeds. On the contrary, in some cases, like Hanover-Hamburg but also the planned Frankfurt-Stuttgart line (already in place south of Mannheim), high speeds are necessary to make the desired knots. Moreover, where distances between cities are long compared with desired frequency, as on Berlin-Hanover, it’s possible to build 300 km/h lines and cut entire half hours or even full hours from trip times. Germany could innovate in this and build such a network for an amount of money well within the limits of the corona recovery package, which includes €50 billion for climate mitigation.

But either way, Germany is about to make mistakes of underinvestment because it’s not quite willing to see where the frontier of rail transport technology is. This is not the American amateur hour, it’s not the sort of situation where I can spend a few hours with maps and come up with better timetables myself, but even so, the plans here are far too timid for Germany’s medium- and long-term transportation needs.

The D-Takt is a step forward, don’t get me wrong. None of the investments I’m seeing is bad. But it’s a small, hesitant step forward rather than a firm, bold walk toward direction of intercity rail modernization. A country that expects intercity rail ridership to double, putting Germany’s per capita intercity rail ridership in the vicinity of Japan’s, should have something similar to the Shinkansen network, with a connected network of NBS links between the major cities averaging 200-250 km/h and not 120-160 km/h.

Resist the Urge to Start Small

Remember the Ohio Hub? Back in 2009-10, Ohio was planning on running five low-speed trains per day between Cleveland and Cincinnati and branded this exercise as high-speed rail called the Ohio Hub. The Republican victory in the gubernatorial election put it out of its misery (as unfortunately happened to the far better Florida project), but the idea of little facts-on-the-ground kinds of rail investment persists among American advocates who don’t understand how rail operations work. Now that there’s serious talk of infrastructure funding in the United States as part of a stimulus package, I’d like to explain, to prevent the debacles of the late 2000s from happening again.

The central conceit is that public transportation is not cars. It’s a different, more complex system. The road network has fewer moving parts – one just builds roads based on traffic projections. Public transportation has schedules, transfers, and equipment, all of which must be planned in coordination. “This junction gets congested, let’s build a bypass” works for road advocacy, but fails for rail, because maybe speeding up the trains by a few minutes doesn’t really help get to any timed connections and is therefore of limited value to the system.

Rail works when everything is planned together. This makes little additions not too valuable: a small speedup may not be useful if connecting lines stay the same, infrastructure investment may have limited effect on trip times if the rolling stock doesn’t change, etc.

The upshot is that it’s very easy to find 80/20 problems: 80% of the money gets you 20% of the benefits. In addition to examples of lack of coordination between infrastructure, the timetable, and rolling stock, there are issues with insufficient frequency. When frequency is low relative to trip time, the long-term elasticity of ridership with respect to service is more than 1 – that is, running more service makes the trains and buses fuller, as better service encourages more ridership. Thus, service with insufficient frequency will fail, trains and buses getting too little ridership to justify additional investment, whereas if initial frequency were higher from the start then it would succeed.

The Ohio Hub was one such example: five roundtrips a day, starter service. It makes sense to someone who thinks like a manager or a general-purpose activist: start small and build from there. But to someone who thinks like a public transportation planner, it’s a disaster. Already 10 years ago, Max Wyss in comments was warning that such service would fail – the original Intercity brand in Germany succeeded by running trains every two hours, with hourly service on stronger city pairs, often with timed transfers at junctions.

Regional rail projects suffer from a similar urge to start small. Peak-only service will invariably fail – the operating costs will be too high for ridership even if almost all seats fill. This covers just about every American effort at starting up new commuter rail service.

More fundamentally, the issue is that nobody likes failure. Insufficient, poorly-optimized service creates facts on the ground, but these facts don’t lead to any effort toward better service if people perceive what has been built to be a failure. If a handful of trains per day that average 70 km/h are called high-speed rail, then it doesn’t lead passengers to want high-speed rail; it leads them to avoid the train and conclude that high-speed rail is slower than driving on the freeway.

The passengers on such service may not be a great constituency for better service, either. If the train is very slow, then the riders will be the sort of people who are okay with slow trains. Older American railfans are filled with nostalgia for traditional railroading and openly say that slower is better. Such people are not going to advocate for modern high-speed rail, nor for learning from successful Asian and European examples.

Another group of people who ride trains and often advocate against better service is peak commuters on trains serving high-income suburbs. They are used to an adversarial relationship with the state; to them, the state taxes them to give money to poorer people, and they instead prefer hyper-local forms of government providing segregated schools and policing. Representatives of such riders engage in agency turf warfare, such as when state senators from Long Island opposed Metro-North’s Penn Station Access because it would use train slots into Penn Station that the LIRR believes are its property. On social media, people sporadically yell at me when I propose fare integration, on grounds that boil down to viewing any urban riders who would be attracted to lower fares as interlopers.

There’s an ultimate proof-of-pudding issue here. Americans have to a good approximation never seen a working public transportation system. At best, they’ve seen a megacity where people use the trains even though they are dirty and expensive to run because there is no alternative and construction was done 100 years ago when costs were lower. There is no coordinated planning; Americans do not demand it because only a handful of people know what it is, who are often young and have often lived abroad for an extended period of time, both of which make one less likely to be listened to in politics.

The result is that the sort of bottom-up activism people are used to is not useful in this context. In Germany it’s different – enough people have seen what works in Austria, Switzerland, and the Netherlands and know what to call for. But in the United States, it won’t work – the knowledge base of how to build reliable, interconnected public transportation exists but is too thinly spread and is the domain of people who do not have much political prestige.

It’s critical to then get things right from the start. Do not assume future activism will fix things. Half-measures are much more likely to lead to disillusionment than to any serious efforts to improve things to turn them into full measures. If the choice is between a high chance of bad service and low chance of good service, don’t settle for bad service and make a gamble for good service; bad public transportation is a waste of money and the general public will correctly perceive it as such.

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.

Future-proofing

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.

Holidays by Train

What does leisure travel look like in a world where driving and flying are prohibitively expensive, and rail travel is more abundant and convenient?

It does not look exactly like today’s travel patterns except by train. Where people choose to travel is influenced by cultural expectations that are themselves influenced by available technology, prices, and marketing. Companies and outfits providing transportation also market the destinations for it, whether it’s a private railway selling real estate in the suburbs on its commuter lines, an airline advertising the resort cities it flies to, or a highway authority promoting leisure drives and auto-oriented development. The transition may annoy people who have gotten used to a set of destinations that are not reachable by sustainable transportation, but as the tourism economy reorients itself to be greener, new forms of leisure travel can replace old ones.

Historic and current examples

Railroads were the first mode of mechanized transportation, and heavily marketed the destinations one could reach by riding them. The involvement of some railroads in suburban development, such as Japanese private railroads or the original Metropolitan Railway, is fairly well-known to the rail advocacy community. Lesser-known but equally important is rail-based tourism. Banff and Jasper owe their existence to transcontinental railways, Lake Louise was founded as a montane resort on top of the Canadian Pacific Railway, Glacier National Park opened thanks to its location next to the (American) Great Northern. Even Niagara Falls, for all its unique natural beauty, benefited from heavy marketing by the New York Central, which offered the fastest route there from New York.

Other than Niagara Falls, the North American examples of rail-based tourism are all in remote areas, where people no longer travel by train. Some may drive, but most fly over them. The American system of national parks, supplemented by some state parks like the Adirondacks and Catskills, has thus reoriented itself around long-distance leisure travel by car. This includes popular spots like Yellowstone, Bryce, Grand Canyon, and Yosemite in the United States, Schwarzwald in Germany, or the tradition of summer homes in outlying areas in Sweden or the American East Coast.

The airline industry has changed travel patterns in its own way. Planes are fast, and require no linear infrastructure, so they are especially suited for getting to places that are not easy to reach by ground transportation. Mass air travel has created a tourism boom in Hawaii, the Maldives, southern Spain, the Caribbean, any number of Alpine ski resorts, Bali, all of Thailand. Much of this involves direct marketing by the airlines telling people in cold countries that they could enjoy the Mediterranean or Indian Ocean sun. Even the peak season of travel shifted – English vacation travel to the Riviera goes back to the early Industrial Revolution, but when it was by rail and ferry the peak season was winter, whereas it has more recently shifted to the summer.

The politics of vacation travel

In some cases, states and other political actors may promote particular vacation sites with an agenda in mind. Nationalists enjoy promoting national unity through getting people to visit all corners of the country, and if this helps create a homogeneous commercial national culture, then all the better. This was part of the intention of the Nazi program for Autobahn construction and Volkswagen sales, but it’s also very common in democratic states that aim to use highways for nation-building, like midcentury America.

If there’s disputed land, then nationalists may promote vacation travel there in order to instill patriotic feelings toward it among the population. Israel has turned some demolished Arab villages into national forests, and promoted tourism to marginal parts of the country; settler forces are likewise promoting vacation travel to the settlements, cognizant of the fact that the median Israeli doesn’t have strong feelings toward the land in the Territories and wouldn’t mind handing them over in exchange for a peace agreement.

Politics may also dictate promoting certain historic sites, if they are prominent in the national narrative. In the Jewish community, two such trips are prominent, in opposite directions: the first is the organized Israeli high school trips to Poland to see the extermination camps and the ghettos, perpetuating the memory of the Holocaust in the public; the second is Birthright trips for Jews from elsewhere to visit Israel and perhaps find it charming enough to develop Zionist feelings toward it.

So what does this mean?

I bring up the politics and economic history of leisure travel, because a conscious reorientation of vacation travel around a green political agenda is not so different from what’s happened in the last few generations. The big change is that the green agenda starts from how people should travel and works out potential destinations and travel patterns from there, whereas nationalist agendas start from where people should travel and are not as commonly integrated with economic changes in how people can travel.

The point, then, is to figure out what kinds of vacation travel are available by train. Let’s say the map that I put forth in this post is actually built, and in contrast, taxes on jet fuel as well as petrol rise by multiple euros per liter in order to effect a rapid green transition. Where can people go on vacation and where can’t they?

Intercity leisure travel

By far the easiest category of leisure travel to maintain in a decarbonized world is between cities within reasonable high-speed rail range. Tens of millions of people already visit Paris and London every year, for business as well as for tourism. This can continue and intensify, especially if the green transition also includes building more housing in big high-income cities, creating more room for hotels.

High-speed rail lives on thick markets, the opposite of air travel. Once the basic infrastructure is there, scaling it up to very high passenger volumes on a corridor is not difficult; the Shinkansen’s capacity is not much less than 20,000 passengers per hour in each direction. Many people wish to travel to Paris for various reasons, so the TGV makes such travel easier, and thus even more people travel to and from the capital. A bigger and more efficient high-speed rail network permits more such trips, even on corridors that are currently underfull, like the LGV Est network going toward much of Germany or the LGV Sud-Europe Atlantique network eventually connecting to much of Spain.

Germany does not have a Paris, but it does have several sizable cities with tourist attractions. A tightly integrated German high-speed rail network permits many people in Germany and surrounding countries to visit the museums of Berlin, go to Carnival in Cologne, attend Oktoberfest in Munich, see the architecture of Hamburg, or do whatever it is people do in Frankfurt. The international connections likewise stand to facilitate German travel to neighboring countries and their urban attractions: Paris, Amsterdam, Basel, Vienna, Prague.

Intercity travel and smaller cities

Big cities are the most obvious centers of modern rail-based tourism. What else is there? For one, small cities and towns that one encounters on the way on corridors designed to connect the biggest cities. Would Erfurt justify a high-speed line on its own? No. But it has an ICE line, built at great expense, so now it is a plausible place for travel within Germany. The same can be said about cities that are not on any plausible line but could easily connect to one via a regional rail transfer. When I fished for suggestions on Twitter I got a combination of cities on top of a fast rail link to Berlin, like Leipzig and Nuremberg, and ones that would require transferring, like Münster and Heidelberg.

Even auto-oriented vacation sites can have specific portions that are rail-accessible, if they happen to lie near or between large cities. In North America the best example is Niagara Falls, conveniently located on the most plausible high-speed rail route between New York and Toronto. In Germany, South Baden is normally auto-oriented, but Freiburg is big enough to have intercity rail, and as investment in the railroad increases, it will be easier for people from Frankfurt, Munich, and the Rhine-Ruhr to visit.

Farther south, some Swiss ski resorts have decent enough rail connections that people could get there without too much inconvenience. If the German high-speed rail network expands with fast connections to Basel (as is planned) and Zurich (which is nowhere on the horizon), and Switzerland keeps building more tunnels to feed the Gotthard Base Tunnel (which is in the Rail 2035 plan but with low average speed), then people from much of central and southern Germany could visit select Swiss ski resorts in a handful of hours.

Non-urban travel

The green transition as I think most people understand it in the 21st century is an intensely urban affair. Berlin offers a comfortable living without a car, and as the German electric grid replaces coal with renewables (slower than it should, but still) it slowly offers lower-carbon electricity, even if it is far from Scandinavia or France. Small towns in contrast have close to 100% car ownership, the exceptions being people too poor to own a car. But the world isn’t 100% urban, and even very developed countries aren’t. So what about travel outside cities large and small?

The answer to that question is that it depends on what cities and what railroads happen to be nearby. This is to a large extent also true of ordinary economic development even today – a farming town 20 km from a big city soon turns into a booming commuter town, by rail or by highway. Popular forests, trails, mountains, and rivers are often accessible by railroad, depending on local conditions. For example, some of the Schwarzwald valleys are equipped with regional railways connecting to Freiburg.

Here, it may be easier to give New York examples than Berlin ones. Metro-North runs along the banks of the Hudson, allowing riders to see the Palisades on the other side. The vast majority of travelers on the Hudson Line do not care about the views, but rather ride the train to commute from their suburbs to Manhattan. But the line is still useful for leisure trips, and some people do take it up on weekends, for example to Poughkeepsie. The Appalachian Trail intersects Metro-North as well, though not many people take the train there. Mountains are obstacles for rail construction, but rivers are the opposite, many attracting railroads near their banks, such as the Hudson and the Rhine.

Conversely, while New York supplies the example of the Hudson Line, Germany supplies an urban geography that facilitates leisure travel by rail out of the city, in that it has a clear delineation between city and country, with undeveloped gaps between cities and their suburbs. While this isn’t great for urban rail usage, this can work well for leisure rail usage, because these gaps can be developed as parkland.

Where’s the catch?

Trains are great, but they travel at 300-360 km/h at most. An aggressive program of investment could get European trains to average around 200-240 km/h including stops and slow zones. This allows fast travel at the scale of a big European country or even that of two big European countries, but does not allow as much diversity of climate zones and biomes as planes do.

This does not mean trains offer monotonous urban travel. Far from it – there’s real difference in culture, climate, topography, and architecture within the German-speaking world alone, Basel and Cologne looking completely different from each other even as both are very pretty. But it does limit people to a smaller tranche of the world, or even Europe, than planes do. A Berliner who travels by train alone can reach Italy, but even with a Europe-scale high-speed rail program, it’s somewhat less than 4:45 to Venice, 5:00 to Milan, 5:30 to Florence, 6:45 to Rome, 7:45 to Naples. It’s viable for a long vacation but not as conveniently as today by plane with airfare set at a level designed to redraw coastlines. Even in Italy, there’s great access to interesting historic cities, but less so to coastal resorts designed around universal car use, located in topographies where rail is too difficult.

The situation of Spanish resorts is especially dicey. There isn’t enough traffic from within Spain to sustain them, there are so many. Germany is too far and so is Britain if planes are not available at today’s scale. What’s more, people who are willing to travel 7 or 8 hours to a Spanish resort can equally travel 5 hours to a French or Italian one. The French Riviera has gotten expensive, so tourism there from Northern Europe feels higher-income to me than tourism to Alicante, but if people must travel by train, then Nice is 4:30 from Paris and Alicante is 7:30, and the same trip time difference persists for travelers from Britain and Germany.

Is it feasible?

Yes.

High carbon taxes are not just economically feasible and desirable, but also politically feasible in the context of Europe. The jet fuel tax the EU is discussing as part of the Green Deal program is noticeable but not enough to kill airlines – but what environmental policy is not doing, the corona virus crisis might. If low-cost air travel collapses, then much of the market for leisure travel specifically will have to reorient itself around other modes. If Europe decides to get more serious about fighting car pollution, perhaps noticing how much more breathable the air in Paris or Northern Italy is now than when people drive, then taxes and regulations reducing mass motorization become plausible too.

The transition may look weird – people whose dream vacation involved a long drive all over Italy or France or Germany may find that said vacation is out of their reach. That is fine. Other vacations become more plausible with better rail service, especially if they’re in big cities, but also if they involve any of a large number of natural or small-town destinations that happen to be on or near a big city-focused intercity rail network.

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.

Eurail?

Here’s one potential pan-European high-speed rail map, incorporating existing and likely future high-speed lines in France, Spain, Britain and Italy; the lines I’ve argued Germany should be building; and plausible and semi-plausible extensions into Eastern Europe.

Here’s a small version of the map:

For full-size 56 MB link, click here. Blue lines exist or are under construction, red ones are either under planning or proposed solely by me or by local activists.

The Polish network is fairly optimized, but the rest of Eastern Europe isn’t, relying on long-range international connections that may or may not flop due to a possible international trip penalty. I only took it up to a point, so yes, there’s that link via (North) Macedonia and Kosovo, but I drew the line at some point and did not add a line from Warsaw up the Baltics and under sea to Helsinki; the Baltic capitals just aren’t big enough, and the light at the tunnel, Helsinki, isn’t big enough either.

Note also that some cities gain through-tracks on this map that they don’t currently have, especially Paris. This is to be a four-track system connecting Gare du Nord to Gare de Lyon and Gare de l’Est to Gare Montparnasse; since there’s no chance of building the main station under Les Halles this side of the 1970s, the station would have to be at a somewhat skew location relative to city center, most probably around where Gare du Nord and Gare de l’Est are now. Additional cities with notable through-tracks: Milan, Rome, Munich, Florence; Madrid gets through-tracks but those are already under construction as part of the third Cercanías axis, at typically low Spanish costs, and Marseille gets through-tracks as is the plan for the mixed classical/LGV system for Provence.

The trip times are always net of station dwell times and short timed connections at major junctions, so they can be added across the map. In Germany I sat down and figured out frequencies, running consistent stopping patterns every half hour; this doesn’t work Europe-wide, as some places are too low-density and have to make do with hourly patterns, like Eastern Europe (and, if it keeps its baroque fare system, Spain).

What Europe Can Learn From Asia

Most of what I write about is what North America can learn from Europe, but the rich countries of Asia are extremely important as well. But what’s more interesting is knowledge sharing between Western Europe and the rich countries of East Asia. These two centers of passenger rail technology have some reciprocal exchange programs, but still learn less from each other than they should.

The ongoing coronavirus outbreak made the topic of Western learning from East Asia especially important. To be clear, none of the examples I’m going to talk about in this post is about the virus itself or at all about public health. But the sort of reaction in democratic East Asia that’s staved off the infection, compared with the failure of the West to do much in time, is instructive. When the virus was just in China, nobody in the West cared. I went to a comedy night in Berlin a month ago and it was the Asian comic who joked about how all they needed was to cough and the white people gave them space; it was still viewed as an exclusively Asian epidemic. By the same token, Korea’s success in reducing infections has made it to parts of Western media, but implementation still lags, leading to an explosion of deaths in Italy and perhaps soon France and the US. Hong Kong (from the bottom up) and Taiwan (with government assistance) have limited infection through social distancing and mask wearing, and the West refuses to adopt either.

If it’s Asian, Europeans as well as Americans view it as automatically either inferior or irredeemably foreign. Whatever the reasoning is, it’s an excuse not to learn. Unlike the United States, Europe has pretty good public transportation in the main cities, and a lot of domestic innovations that are genuinely better than what Japan, South Korea, and Taiwan do; thus, it can keep going on like this without visible signs of stagnation. Nonetheless, what Japan has, and to some extent the other rich Asian countries, remains a valuable lesson, which good public transport advocates and managers must learn to adopt to the European case.

Urban rail and regional rail: network design

Tokyo and Seoul both have stronger S-Bahn networks than any European city. This is not just an artifact of size. Paris and London are both pretty big, even if they’re still only about a third as big as Tokyo. In Tokyo, the infrastructure for urban and regional rail is just far better-integrated, and has been almost from the start. Among the 13 Tokyo subway lines, only three run as pure metro lines, separate from all other traffic: Ginza, Marunouchi, Oedo. The other 10 are essentially S-Bahn tunnels providing through-service between different preexisting commuter lines: the Asakusa Line connects the Keisei and Keikyu systems, the Hibiya Line connects the Tobu Skytree Line with Central Tokyo and used to through-run to the Tokyu Toyoko Line, etc.

This paradigm of cross-regional traffic is so strong that on lines that do not have convenient commuter lines to connect to, there are suburban tails built just to extend them farther out. The Tozai Line hooks into a reverse-branch of the Chuo Line to the west, but to the east has little opportunity for through-service, and therefore most trains continue onto an extension called the Toyo Rapid Railway.

On the JR East network, there are a few subway connections to, but for the most part the network has its own lines to Central Tokyo. This is an early invention of mainline rail through-running, alongside the Berlin S-Bahn; the Yamanote ring was completed in 1925. Further investment in through-service since then has given more lines dedicated tracks through Central Tokyo, for capacity more than anything else.

The issue is not just that there are many through-running lines. Tokyo has 15-16 through-running trunks, depending on how one counts, and Paris, a metro area about one third the size, will soon have 4.5. It’s not such a big difference. Rather, Tokyo’s through-running lines function well as a metro within the city in ways the Berlin S-Bahn, the Paris RER, the Madrid Cercanías, and any future London Crossrail lines simply don’t.

What’s more, future investment plans in Europe do not really attempt to turn the commuter rail network into a useful metro within the city. Berlin has a strong potential northwest-southeast S-Bahn route forming a Soviet triangle with the two existing radial trunks, but it’s not being built, despite proposals by online and offline advocates; instead, current S21 plans call for duplicating north-south infrastructure. In Paris, the RER C doesn’t really work well with the other lines, the RER E extension plans are a mess, and most of the region’s effort for suburban rail expansion is spent on greenfield driverless metro and not on anything with connections to legacy mainlines. In London, the subsurface Underground lines are historically a proto-S-Bahn, with some mainline through-service in the 19th century, but they are not really used this way today even though there is a good proposal by railfans.

While Europe generally does the longer-distance version of regional rail better than Japan, the vast majority of ridership is S-Bahn-type, and there, Japan absolutely crushes. What’s more, Korea has learned from Japan’s example, so that the Seoul Subway Line 1 is an S-Bahn and many other lines are very long-range; Seoul’s per capita rail ridership is much lower than Paris’s, but is increasing fast, as South Korea is a newly-industrialized country still building its infrastructure at low cost to converge to Western incomes.

Rolling stock

Tokyo outdoes the closest things to its peers in the West in S-Bahn network design. Japan is equally superior when it comes to the rolling stock technology itself. It has all of the following features:

  • Low cost. Finding information about rolling stock costs in Japan is surprisingly hard, but Wikipedia claims the 10000 Series cost 1.2 billion yen per 10-car, 200-meter train, which is around $60,000/meter, compared with a European range that clusters around $100,000.
  • Low weight – see table here. European trains are heavier, courtesy of different buff strength regulations that are not really needed for safety, as Japanese trains have lower death tolls per p-km than European ones thanks to accident avoidance.
  • All-MU configuration – Japan has a handful of locomotives for passenger service for the few remaining night trains, and runs all other trains with EMUs and sometimes DMUs. Parts of Europe, like Britain, have made this transition as well, but Zurich still runs locomotives on the S-Bahn.

The one gap is that Europe is superior in the long-range regional rail segment with a top speed of 160-200 km/h. But Japanese trains are better at the more urban end up to 100 km/h thanks to their low cost and weight and at the high-speed end of 300+ km/h thanks to low cost and weight (again) and better performance.

Shinkansen equipment is also more technically advanced than European high-speed trains in a number of ways, in addition to its lower mass and cost. The N700-I has a power-to-weight ratio of 26.74 kW/t, whereas European trains are mostly in the low 20s. Japanese train noses are more aerodynamic due to stringent noise regulations and city-center stations, and the trains are also better-pressurized to avoid ear popping in tunnels. As a result, the Shinkansen network builds single-bore double-track tunnels hardly bigger than each individual bore in a twin-bore European rail tunnel, helping reduce cost relative to Japan’s heavily mountainous geography. The EU should permit such trains on its own tracks to improve service quality.

The Shinkansen

The Shinkansen works better than European high-speed rail networks in a few ways, in addition to rolling stock. Some of it is pure geographic luck: Japanese cities mostly lie on a single line, making it easy to have a single trunk serve all of them. However, a few positive decisions improve service beyond what pure geography dictates, and should be studied carefully in Britain, Germany, and Italy.

  • Trains run through city centers with intermediate stops rather than around them. This slightly slows down the trains, because of the stop penalty at a city, and sometimes a slightly slowdown for an express train. This is especially important in Britain, which is proposing an excessively branched system for High Speed 2, severely reducing frequency on key connections like London-Birmingham and London-Manchester.
  • Trains run on dedicated tracks, apart from the Mini-Shinkansen. This was enforced by a different track gauge, but a sufficiently strong national network should run on dedicated tracks even with the same gauge. This is of especial importance in Germany, which should be building out its network to the point of having little to no track-sharing between high-speed and legacy trains, which would enable high-speed trains to run more punctually.
  • Train stations are through-stations (except Tokyo, which is almost set up to allow through-service and errs in not having any). If the legacy station is a terminal, like Aomori, or is too difficult to serve as a through-station, like Osaka, then the train will serve a near-downtown station a few km away, like Shin-Aomori 4 km from Aomori and Shin-Osaka 4 km from Osaka. Germany does this too at Kassel and has long-term plans to convert key intermediate terminals into through-stations, but France and Italy both neglect this option even when it is available, as in Tours and Turin.
  • Rolling stock is designed for high capacity, including fast egress. There is no cafe car – all cars have seats. There are two wide door pairs per car, rather than just one as on the TGV. There is full level boarding with high platforms. Express trains dwell even at major stations for only about a minute, compared with 5 minutes on the TGV and even slower egress at the Paris terminals. Trains turn at the terminals in 12 minutes, reducing operating expenses.
  • Pricing is simple and consistent, without the customer-hostile yield management practices of France, Spain, and much of the rest of Europe.

Reliability

Japan is renowned for its train punctuality. As far as I can tell, this comes from the same place as Switzerland: system design is centered around eliminating bottlenecks. Thus it’s normal in both Japan and Switzerland to leave some key commuter lines single-track if the frequency they run allows timed meets; both countries also employ timed overtakes between local and express trains on double track.

Where I think Japan does better than Switzerland is the use of track segregation to reduce delays. Captive trains are easier to control than highly-branched national rail networks. In Switzerland, there is no room for such captive trains – the entire country has fewer people than Tokyo, and the city of Zurich has fewer people than many individual Tokyo wards. But a big country could in effect turn long lines into mostly separated systems to improve punctuality. This goes against how the S-Bahn concept works in the German-speaking world, but the Tokyo and Seoul lines are in effect metros at a larger scale, even more so than the RER A and B or the Berlin S-Bahn. France, Germany, Spain, Italy, and Britain could all learn from this example.

The heavy emphasis on punctuality in Japanese railroad culture has been blamed for a fatal rail accident. But even with that accident, Japanese rail safety far surpasses Europe’s, approaching 80 billion passenger-km per on-board passenger fatality where Europe appears to be in the low teens.

Is this everything?

Not quite. I will write a companion piece about what Asia can learn from Europe eventually. For one, East Asia appears to optimize its rail operating culture to huge cities, much like France and Britain, and thus its smaller cities have less per capita rail usage than similar-size Central European ones; on this list, compare Fukuoka, Busan, and Sapporo with Stockholm, Prague, Vienna, Munich, Stuttgart, Rome, Frankfurt, Barcelona, and Hamburg. Europe is also better when it comes to 160-200 km/h regional rail.

However, the bulk of intercity rail traffic even in Europe is on high-speed trains, an area in which Europe has more to learn from Japan than vice versa. Similarly, the bulk of individual boardings on trains are on metro and short-range S-Bahn trains even in the German-speaking world; there there is a lot of learning to be done in both directions, but at the end of the day, Tokyo has higher rail usage than Paris and London.

China Won’t Save You

The construction costs of Britain’s just-approved domestic high-speed rail network, High Speed 2, are extreme. The headline costs are, in 2019 figures, £80.7-88.7 billion per the Oakervee review, with one estimate going up to £106.6 billion, all for a system only 530 km in length in mostly flat terrain. This includes rolling stock, but that is less than 10% of the projected cost. At the end of the day, Britain has decided to spend around $200 million per kilometer, a cost comparable to that of base tunnels and mostly-tunneled high-speed lines.

And now the People’s Republic of China has offered to build the entire thing for cheaper with a 5-year timeline, and everyone acts as if it’s a serious offer. So let me dust off my construction costs database and tell you: the PRC won’t save you. There is no alternative to developing good internal cost control. This requires learning from lower-cost countries, but Chinese high-speed rail construction costs are not really low.

Vietnam

Ho Chi Minh City and Hanoi are both building metros. Hanoi uses Chinese financing, HCMC uses Japanese financing. Both have very high construction costs – my database has HCMC’s 13% underground Line 1 at $320 million/km, 82% underground Line 2 phase 1 at $535 million/km, and 84% underground Line 5 phase 1 at $590 million/km, whereas Hanoi’s 74% underground Line 2A is $215 million/km and 32% underground Line 3 is $365 million/km.

The system in Hanoi has been plagued with delays. Line 2A was supposed to be operational by 2016. Construction was only completed in 2018, but the line is yet to open. Testing is ongoing, but Chinese experts couldn’t return to Vietnam after the Chinese New Year holiday because of the coronavirus quarantine. The South China Morning Post has compared the Hanoi project negatively with that of HCMC, which is for the most part on time, if expensive.

Like many developing-world cities, HCMC is paying more for a subway tunnel than Japan pays at home; to get to the cost range of HCMC in Japan, one needs to go to complex regional rail tunnels in Tokyo dipping under multiple older tunnels in city center. In that it is no different from Dhaka or Jakarta. The primary explanation must be that importing Japanese technology means using techniques optimized for a high-skill, high-wage labor force and cheap domestic capital, rather than ones optimized for a low-skill, low-wage labor force and expensive imported capital.

But that does not explain why the Hanoi Metro is so expensive. Chinese metros cost less (though not universally – Shanghai’s construction costs are rising fast): I want to say about $250 million/km on average, about the same as the non-Chinese global median, but the actually big set of data is unpublished so you guys can’t nitpick my sources yet. So what’s going on here? Vietnam is poorer than China, but the difference is not so big. It’s about half as rich as the PRC. It’s comparable to Europe, where Romania and Bulgaria are about half as rich as Western Europe, and they have low construction costs, lower than parts of Eastern Europe closer to Western incomes.

Chinese high-speed rail

The construction costs of high-speed rail in the PRC are fairly high, especially in its richer parts. The costs remain lower than those of tunnel-heavy lines like those of Italy, Japan, and South Korea, but by low-tunnel standards, they are high.

There is a perception that Chinese costs are low, but it comes from using the wrong currency conversion. Here, for example, is a World Bank report on the subject:

[P. 39] Figure 4.1 shows the construction cost of 60 projects. The average cost of a double-track HSR line (including signaling, electrification, and facilities) is about Y 139 million/km (US$20.6 million/km) for a 350 kph HSR line, about Y 114 million (US$16.9 million) for a 250 kph HSR line, and about Y 104 million (US$15.4 million) for a 200 kph HSR line. These costs are at least 40 percent cheaper than construction costs in Europe (European Court of Auditors 2018, 35).

The problem is, the exchange rate of $1 = ¥6.75 is incorrect. The OECD’s PPP conversion factor today is much higher, $1 = ¥3.5; for high-speed lines built a decade ago, it would be even higher, about $1 = ¥3.3, with ten years of American inflation since. Using the correct modern rate, the cost is about $40 million per kilometer, which is not lower than in Europe but rather higher. Beijing-Shanghai, as far as I can tell a ¥220 billion project for 1,318 km of which just 16 km are in tunnel, rises to $50 million per km, and more like $60 million per km in today’s money. It’s still cheaper than High Speed 2, but more expensive than every Continental Europe high-speed line that isn’t predominantly in tunnel, like Bologna-Florence.

There are all these longwinded explanations for why the PRC does things cheaper and faster than the first world, and they are completely false. China is not cheap to build in, especially not high-speed rail. The only reason Chinese costs aren’t even higher is that Eastern China is pretty flat. Even then, China has not taken advantage of this flatness to build tracks at-grade to minimize costs. Instead, it has built long viaducts at high cost, in contrast with the at-grade approach that has kept French LGV costs reasonable.

The PRC doesn’t even build things particularly quickly. Total actual construction time from start to finish per line segment is 4-6 years per Wikipedia’s list, which is comparable to recent LGVs. What is true is that China has been building many lines at once, and each line is long, but this is a matter of throughput, not latency. The limit to throughput is money; the PRC made a political decision to spend a lot of it at once as stimulus in the late 2000s and early 2010s, and by the same token, the UK has just made a political decision to spend just less than £100 billion on High Speed 2, in a trickle so that the system will take 15+ years to complete.

Why are they like this?

The myth of hyper-efficient Chinese construction seems never to die; I’ve seen it from the first days of this blog, e.g. then-US Secretary of Transportation Ray LaHood in 2012. It relates to a mythology that I think is mostly part of Anglo-American culture, of the tension between freedom and efficiency. The English-speaking world in this mythology is the epitome of freedom, with a gradation of less free, more efficient paces: Germany, then Japan, then finally China. It’s a world in which people’s ideas of what totalitarianism looks like come from reading George Orwell and not from hearing about the real-life Soviet Union’s comic incompetence – the gerontocracy, the court politics, the drunk officials, the technologically reactionary party apparatchiks – all of which was happening in real time in Nazi Germany too, which was fighting less efficiently than the UK and US did.

It’s equally a world in which people think rights Germans and Japanese take for granted, like various privacy protections, do not even register as important civil liberties. I dare any reader to try explaining to a British or American transit manager that really, no, you do not need our data, Central Europe manages to plan better than you without smartcards tracking users’ every move and storing the data in servers with infosec that screams “steal me.” Nor do Americans make much of an effort to import policing regimes from democracies with one twentieth their rate of police shootings per capita.

China’s incompetence is now visible to the entire world, in the form of a virus outbreak that local officials flailed about for a month, too afraid to acknowledge mistakes lest they take the fall for them. And yet it’s easier for American and British business leaders and politicians to point to China as an example to emulate than to Pareto-better France or Germany.

If anything, High Speed 2 is low-key overlearning some French lessons, leading to inferior infrastructure planning – but it’s messing up key details leading to cost explosion, such as “don’t build new signature urban train stations.” But my suspicion is that French and German rail experts will point out all those details. To us, if Britain changes some detail in a way that isn’t truly justified by local conditions, we will point it out – and push back when British blowhards try to explain to use that they do things differently because they’re morally superior to us. British people know this – they know they can’t pull rank. Americans are the same, except even less capable of dealing with other nations as equals than the British are.

The way forward

High Speed 2 is a mess, largely because of the cost. To move forward, talking to China about how it’s built high-speed rail may be useful, but it can’t be the primary comparison, not when Continental Europe is right here and does things better and cheaper. For Asian help, Japan has some important lessons about good operations and squeezing maximum use out of limited urban space. A lot of scope can be removed. A lot more can be modified slightly to connect to regional lines better.

More conceptually, Britain has a problem with costs and benefits chasing each other. If benefits are too high, the political system responds with sloppy cost control, for example by lading the project with ancillary side projects that someone wants or by giving in to NIMBY opposition. If the costs are too high, the political system responds with scrounging extra benefits, for example counting the consumer surplus of high-speed rail travelers as a benefit, by which standard every government subsidy to anyone has a benefit-cost ratio of at least 1.

Bringing in the PRC won’t help. It’s value-engineering theater, rather than the hard work required to coordinate infrastructure and timetable planning or to tell Home Counties NIMBYs that the state is not in the business of guaranteeing their views; there is so much tunneling on the proposed line that isn’t really necessary. None of the countries that builds trains cheaply did so by selling its civil service for spare parts; why would Britain be any different?

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

\mbox{Pop}_{A}\cdot\mbox{Pop}_{B}/d^{2}.

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.