High-Speed Rail for the Eastern United States

Yesterday, I tweeted this proposal for a high-speed rail network for the eastern half of the United States:

I’d like to go over what the map means and address questions that have appeared on Twitter.

The color scheme

Red denotes high-speed lines, with a top speed in the 300-360 km/h range, not including the occasional enforced slow zone. The average speed would be around 225-250 km/h in the Northeast, where the routes are all compromised by existing infrastructure, and 300 km/h in the Midwest, where flat expanses and generous rail rights-of-way into the major cities should allow the same average speeds achieved in China. The South is intermediate, due to the rolling terrain and extensive suburban sprawl in the Piedmont.

Yellow denotes high-speed lines as well, but they are more marginal (in the linked tweet this is purple, but yellow is friendlier to the colorblind). This means that I expect much lower social return on investment there, so whether these lines could succeed depends on the price of fuel, trends in urban sprawl, and construction costs within the normal first-world range. Some of these lines, namely Atlanta-New Orleans and the connection from Savannah to Jacksonville, should be legacy lines if HSR does not pan out; others, like Kansas City-Oklahoma City, are unlikely to be worth it.

Blue denotes legacy lines that are notable for the network. It does not include the entire set of legacy intercity lines the US should be running, but does include all lines that I believe should get through-service to high-speed lines; but note that some lines, like Minneapolis-Duluth and Charleston-Greenville, do not have through-service. Some of these lines are potentially very strong, like New Haven-Springfield as a Northeast Corridor extension. Others are marginal, like Binghamton-Syracuse, which Adirondacker has recurrently criticized in comments on the grounds that New York-Syracuse is much faster on HSR and the intermediate cities are too small to justify more than a bus.

This is not meant to be an exhaustive list. Some of the alignments may not be optimal, and one of the red lines, Albany-Montreal, can plausibly be reclassified as yellow due to the weakness of travel markets from the United States to Montreal.

Trip times

The schedules I’m proposing are fast – all faster than in Germany and Italy, many faster than in France and Spain. The reason for this is the long expanses between American cities. Germany and Italy have high population density, which is in theory good for HSR, but in practice means the closely-spaced cities yield lines with a lot of route compromises. In Britain people who advocate for the construction of High Speed 2 complain that England’s population density is too high, making it harder to build lines through undeveloped areas (that is, farms) between big cities the way France and Spain did.

Out of New York, the target trip times are:

  • Boston: 1:40
  • Philadelphia: 0:40
  • Washington: 1:35
  • Albany: 0:55, an hour minus half a turnaround time, useful for Swiss run-trains-as-fast-as-necessary timetabling
  • Syracuse: 1:50
  • Rochester: 2:25
  • Buffalo: 2:45
  • Toronto: 3:20
  • Harrisburg: 1:20
  • Pittsburgh: 2:30
  • Cleveland: 3:10
  • Richmond: 2:15
  • Raleigh: 3:10
  • Charlotte: 4:05
  • Atlanta: 5:30
  • Birmingham: 6:15, probably no direct service from New York except at restricted times of day, but hourly or 30-minute service to Atlanta

Out of Chicago, they are:

  • Milwaukee: 0:30
  • Minneapolis: 2:30
  • St. Louis: 1:30
  • Kansas City: 2:50
  • Indianapolis: 0:55
  • Cincinnati: 1:30
  • Louisville: 1:35
  • Nashville: 2:35
  • Atlanta: 4:00
  • Toledo: 1:15
  • Detroit: 1:35
  • Toronto: 2:55
  • Cleveland: 1:50
  • Buffalo: 2:50

Stop spacing

For the most part, there should be a stop in each metropolitan area. What counts as a metropolitan area remains a question; truly multicore regions can get one stop per core, for example there should definitely be a stop in Newark in addition to New York, and South Florida should have individual stops for Miami, Fort Lauderdale, and West Palm Beach. On the Northeast Corridor, what I think the optimal express stopping pattern is is one stop per state, with additional local trains making some extra stops like New London, Stamford, New Rochelle, and Trenton; Wilmington can be a local or an express stop – whether the infrastructure required to skip it at speed is worth it is a close decision.

On most lines, multiple stopping patterns are unlikely to be worth it. The frequency wouldn’t be high in the first place; moreover, the specific stations that are likely candidates for local stops are small and medium-size cities with mostly short-range travel demand, so serving them on a train stopping less than hourly is probably not going to lead to high ridership. Among the lines coming out of Chicago, the only one where I’m comfortable prescribing multiple stopping patterns is the one headed east toward Cleveland and Detroit.

Another consideration in the stop spacing is where most passengers are expected to travel. If there is a dominant city pair, then it can get express trains, which is the justification for express trains on the Northeast Corridor and on Chicago-Detroit and Chicago-Cleveland. However, in Upstate New York, there is no such dominant city pair: travel demand from New York to Toronto is not much more than to Buffalo (the air travel market is around a million people annually, whereas New York-Buffalo is 600,000) even though Toronto is a lot bigger, so there’s little point in skipping Syracuse, Rochester, and Buffalo to speed up end-to-end trips.

Ultimately, stops don’t cost that much time. In 360 km/h territory, a late-model Shinkansen has a stop penalty of a little under 3 minutes excluding dwell time – figure about 4 minutes with dwell. Those minutes add up on short-range lines with a lot of stops, but as long as it’s restricted to about a stop every 150 km or more in high-speed territory, this should be fine.

Highland gaps in service

Several people on Twitter complained about the lack of service to West Virginia and Arkansas. West Virginia is a politically distinguished part of the US nowadays, a metonym for white working-class decline centered on the coal industry, and as a result people notice it more than they do Midwestern poverty, let alone Southern or Western poverty. Poor cities are often served by red lines on my map, if they are between larger cities: Youngstown and Bowling Green are both noticeably poorer than Charleston, West Virginia, and Lafayette, Killeen-Temple, and Erie are barely richer. In the West, not depicted on my map, Pueblo, Chico, and Redding are all as poor as Charleston and are on standard wishlists for upgraded legacy rail while Tucson is a hair poorer and probably should get a full HSR extension of Los Angeles-Phoenix.

The reason Appalachia is underserved is the highland topography. Construction costs go up sharply once tunnels are needed; the route through Pennsylvania connects New York and Philadelphia with Pittsburgh, Cleveland, Detroit, and Chicago, which are big enough urban centers to justify the expense, but additional routes would connect smaller cities. Washington awkwardly gets poor service to the Midwest; a yellow line between Baltimore and Harrisburg may be prudent, but a blue line is not, since the legacy line is so curvy that a high-speed detour through Philadelphia would still be faster. The Piedmont South gets a red line parallel to the mountains and some branches, but nothing that justifies going over the mountains.

Legacy rail additions are still plausible. Amtrak connects Charleston with Cincinnati in 5 hours, but cutting this to about 3.5 should probably be feasible within existing right-of-way, provided CSX does not mind faster passenger rail on its tracks; thence, Chicago-Cincinnati would take around 1.5 hours. However, the negotiations with CSX may be difficult given the line’s use by slow, heavy freight; the blue lines shown on my map are mostly not important freight mainlines.

In Arkansas, the question is whether a line to Little Rock is justifiable. The yellow route between Atlanta and Dallas could plausible detour north through Memphis and Little Rock instead of the depicted direct alignment; Atlanta-Dallas is about the same distance as New York-Chicago, a trip of about 5 hours, so the line would have to survive based on intermediate markets, making the less direct route better. On the other hand, Memphis and Little Rock are small, and while Atlanta and Dallas are big, they’re nowhere near the size of New York, and have very weak centers, encouraging driving rather than riding paid transportation whether it’s a train or plane.

Regional rail additions

As I said above, the blue line list is not intended to be exhaustive. I suspect it is exhaustive among long-range intercity lines, not counting yellow routes like Dallas-Oklahoma City or Atlanta-New Orleans. I was specifically asked about Amtrak’s City of New Orleans route, connecting Chicago, St. Louis, Memphis, and New Orleans, since there is no trace of it on the map beyond the Chicago-St. Louis HSR. There could certainly be a high-speed line down to Memphis, which would place the city around 3 hours from Chicago. However, Memphis is not a large city; St. Louis, Memphis, and New Orleans have all stagnated in the last hundred years, making them weaker candidates for HSR than they were for legacy rail in the postwar era.

In contrast with the deliberate omission of the City of New Orleans routes, there are many regional lines that could be added. In the Northeast, a number of lines are every bit as valuable candidates for a national map as Boston-Portland, including Boston-Cape Cod, Boston-Manchester, New York-Allentown, Philadelphia-Allentown, and maybe Syracuse-Watertown with a timed HSR connections. Boston-Portland could have through-service to the Northeast Corridor or it could not, depending on timetabling in the North-South Rail Link tunnel; my current position is that it should only have through-service to other regional lines, but it’s a close decision.

Outside the Northeast there may be strong in-state networks. I showed the one in South Carolina since it substitutes for lines that I think are just a little too weak to even be in yellow, connecting North Carolina directly with Jacksonville, as well as the one in Wisconsin, based on through-service to HSR to Chicago. But Michigan can have an in-state network, either electrified or unelectrified, connecting cities orthogonally to HSR, and maybe also an electrified spine running the current Wolverines route with through-service to HSR. Indiana can have interregional lines from Indianapolis to outlying cities, but there would need to be more stuff in the center of Indianapolis for such service to attract drivers. Florida has some decent regional lines, even with how unusually weak-centered its cities are, for example Tampa-St. Petersburg and Tampa-Sarasota.

Alignment questions

In a few places, the alignment is either vague or questionable. In the Northeast the biggest question is whether to serve Hartford on the mainline. I dealt with that issue years ago, and my answer has not changed: probably not. The second biggest is which alignment to take across the Appalachians in Pennsylvania; this requires a detailed engineering survey and the line I drew is merely a placeholder, since further design is required to answer questions about the precise costs and benefits of serving intermediate cities like State College and Altoona.

By far the biggest criticism I’ve gotten about macro alignment concerns how to get between the Midwest and the Northeast. The alignment I drew connects Chicago with points east via Cleveland. Due to the decline of Cleveland and slow growth of Columbus in its stead, multiple people have posited that it’s better to draw the red line well to the south, passing via Fort Wayne and Columbus. This would give Columbus fast service to Chicago, in not much more than 1:30, and also connect Pittsburgh better with Columbus, Cincinnati, and plausibly Louisville.

The problem with the Columbus route is that Detroit exists. The drawn alignment connects Pittsburgh with Detroit in about 1:35 and New York with Detroit in about 4:05, in addition to the fast connection to Chicago. A legacy connection in Fort Wayne would slow Chicago-Detroit to about 2:50, nearly doubling the trip time between the Midwest’s two largest cities; it would lengthen New York-Detroit to around 6 hours via Pennsylvania; the route via Canada would take a little more than 4 hours, but might not even exist without the ability to connect it west to Chicago – Canadian HSR studies are skeptical about the benefits of just Toronto-Windsor.

In contrast, the new city pairs opened by the Columbus alignment, other than Chicago-Columbus, involve small, weak-centered cities. Detroit is extremely weak-centered as well, but Chicago and New York are not, which means that suburban drivers will still drive to the train station to catch a ride to Chicago or New York if HSR is available; in contrast, city pairs like Pittsburgh-Cincinnati are very unlikely to get substantial rail mode share without completely revamping the way the geography of jobs in American cities is laid out.

Changing the geography of the nation

In one of the interminable Green New Deal papers, there was some comment about having HSR obviate the need for air travel. This proposition is wrong and misses what makes HSR work here and in Japan, South Korea, and China. The median distance of a domestic American air trip is well above the point beyond which HSR stops being competitive with air travel.

Counting only city pairs at a plausible HSR range of around 4-5 hours, maybe a bit more for New York-Atlanta, my estimate is that about 20-25% of domestic US air trips can be substituted by rail. This excludes city pairs at plausible HSR distance on which there will never be any reason to build HSR, like El Paso-Albuquerque, Minneapolis-Denver, and Charlotte-Columbus. Higher-end estimates, closer to 25% than to 20%, require all the yellow lines and a few more, as well as relying on some long-range city pairs that happen to be on the way of relatively direct HSR and have no direct air traffic.

However, the fact that people will continue flying until vactrains are invented does not make HSR useless or unnecessary. After all, people fly within Europe all the time, even within individual countries like France. Not only do people fly within Japan, but also the country furnishes two of the world’s top air routes in Tokyo-Sapporo and Tokyo-Fukuoka. As an alternative at its optimum range of under about 1,000 km, HSR remains a solid mode of travel.

Moreover, HSR has a tendency to change the geography of the nation. In France and Japan, it’s helped cement the capital’s central location in national economic geography. Tokyo and Paris are the world’s top two cities in Fortune Global 500 headquarters, not because those cities have notable economic specialization like New York but because a large company in Japan and France will usually be headquartered in the capital.

The likely impact of HSR on the US is different, because the country is too big for a single city’s network. However, the Midwest is likely to become a more tightly integrated network focused on Chicago, Texas and Florida are likely to have tighter interconnections between their respective major cities, and the links between the Piedmont South and the Northeast are likely to thicken. HSR cannot supplant air travel at long distances, but it can still create stronger travel volumes within its service range, such that overall trip numbers will be much higher than those of air travel, reducing the latter’s relative importance.

Fix the Slowest Speed Zones

I am wrapping up a project to look at speedup possibilities for trains between New York and New Haven; I’ll post a full account soon, but the headline result is that express trains can get between Grand Central and New Haven in a little more than an hour on legacy track. In this calculation I looked at speed zones imposed by the curves on the line. The biggest possible speedups involve speed limits that are not geometric – and those in turn come from some very sharp slow zones. The worst is the Grand Central station throat, and I want to discuss that in particular since fixing the slowest zones usually yields the most benefits for train travel times.

Best practice for terminal approaches

Following Richard Mlynarik’s attempt to rescue the Downtown Extension in San Francisco, I’ve assumed that trains can approach terminals at 70 km/h, based on German standards. At this speed, an EMU on level track can stop in about 150 meters. In Paris, the excellent Carto Metro site details speed limits, and at most terminals with bumper tracks the speed limit is 60 km/h, with a few going up to 100 km/h.

Even with bumper tracks, 70 km/h can be supported, provided the train is not intended to stop right at the bumpers. At a fixed speed, the deceleration distance is the inverse of the deceleration rate. There is some variation in braking performance, but it’s in a fairly narrow range; on subway trains in New York, everything is supposed to brake at the same nominal rate of 3 mph/s, or 1.3 m/s^2, and when trains brake more slowly it’s because of a deliberate decision to avoid wearing the brakes out. As long as the train stops 1-2 car lengths away from the bumpers, as is routine on Metro-North, the variation will be much smaller than the margin of safety.

Fast movement through the station throat is critical for several reasons. First, as I’ll explain below, sharp speed limits have an outsize effect on trip times, and can be fixed without expensive curve easements or top-rate rolling stock. And second, at train stations with a limited number of tracks, the station throat is the real limiting factor to capacity, since trains would be moving in and out frequently, and if they move too slowly, they’ll conflict. With its 60 km/h throat, Saint-Lazare on the RER E turns 16 trains per hour at the peak on only four tracks.

American practice

I had a conversation with other members of TransitMatters in Boston yesterday, in which we discussed work to be done for our regional rail project. One of the other members, I forget who, asked me, do European train protection systems shut down in station throats too?

The answer to the question is so obviously yes that I wanted to understand why anyone would ask it. Apparently, the American mandate for automatic train protection on all passenger rail lines, under the name positive train control, or PTC, is only at speeds higher than 10 miles per hour. At 10 mph or less train operators can drive the train by sight, and no signaling is required, which is why occasionally trains overrun the bumpers even on PTC-equipped lines if the driver has sleep apnea.

Without video, nobody could see the facial expressions I was making. I believe my exact words were “…What? No! What? What the hell?”.

The conversation was about South Station, but the same situation occurs at Grand Central. Right-of-way geometry is good for decent station approach speed – there is practically no limit at Grand Central except tunnel clearances, which should be good for 100 km/h, and at South Station the sharp curve into the station from the west is still good for around 70 km/h given enough superelevation.

The impact of slow zones near stations

Last year, I published code for figuring out acceleration penalties based on prescribed train characteristics. The relevant parameters for Metro-North’s M8 is initial acceleration = 0.9 m/s^2, power/weight = 12 kW/t. Both of these figures are about two-thirds as high as what modern European EMUs are capable of, but it turns out that at low speed it does not matter too much.

Right now the Grand Central throat has a 10 mph speed limit starting just north of 59th Street, just south of milepoint 1. The total travel time over this stretch is 6 minutes, a familiar slog to every regular Metro-North rider; overall, the schedule between Grand Central and Harlem-125th Street is 10 minutes northbound and 12-13 minutes southbound, the difference coming from schedule padding. The remaining 65 or so blocks are taken at 60 mph, nearly 100 km/h, and take around 4 minutes.

Now, let’s eliminate the slow zone. Let trains keep cruising at 100 km/h until they hit the closer-in parts of the throat, say the last kilometer, where the interlocking grows in complexity and upgrading the switches may be difficult; in the last kilometer, let trains run at 70 km/h. The total travel time in the last mile now shrinks to a minute, and the total travel time between Grand Central and Harlem shrinks to 5 minutes and change. Passengers have gained 5 minutes based on literally the last mile.

For the same reason, the Baltimore and Potomac Tunnel imposes a serious speed limit – currently 30 mph through the tunnel, lasting about 2 miles; removing this limit would cut 2-2.5 minutes from the trip time, less than Grand Central’s 5 because the speed limit isn’t as wretched.

The total travel time between New York and New Haven on Metro-North today is about 1:50 off-peak, on trains making all stops north of Stamford. My proposed schedule has trains making the same stops plus New Rochelle doing the trip in 1:23. Out of the 27-28 minutes saved, 5 come from the Grand Central throat, the others coming from higher speed limits on the rest of the route as well as reduced schedule padding; lifting the blanket 75 mph speed limit in Connecticut is only worth about 3 minutes on a train making all stops north of Stamford, and even on an express train it’s only worth about 6 minutes over a 73 kilometer stretch.

What matters for high-speed travel

High-speed rail programs like to boast about their top speeds. But in reality, the difference between a vanilla 300 km/h train and a top of the line 360 km/h only adds up to a minute every 30 kilometers, exclusive of acceleration time. Increasing top speed is still worth it on lines with long stretches of full-speed travel, such as the Tohoku Shinkansen, where there are plans to run trains at 360 over hundreds of kilometers once the connection to Hokkaido reaches Sapporo. However, ultimately, all this extra spending on electricity and noise abatement only yields a second-order improvement to trip times.

In contrast, the slow segments offer tremendous opportunity if they are fixed. The 10 mph limit in the immediate Penn Station throat slows trains down by around 2 minutes, and those of Grand Central and South Station slow trains by more. A 130 km/h slog through suburbia where 200 km/h is possible costs a minute for every 6.2 km, which easily adds up to 5 minutes in a large city region like Tokyo. An individual switch that imposes an undue speed limit can meaningfully slow the schedule, which is why the HSR networks of the world invented high-speed turnouts.

Richard Mlynarik notes that in Germany, the fastest single end-to-end intercity rail line used to be Berlin-Hamburg, a legacy line limited to 230 km/h, where trains averaged about 190 km/h when Berlin Hauptbahnhof opened (they’ve since been slowed and now average 160). Trains go at full speed for the entire way between Berlin and Hamburg, whereas slow urban approaches reduce the average speed of nominally 300 km/h Frankfurt-Cologne to about 180, and numerous compromises reduce that of the nominally 300 km/h Berlin-Munich line to 160; even today, trains from Berlin to Hamburg are a hair faster than trains to Munich because the Berlin-Hamburg line’s speed is more consistent.

The same logic applies to all travel, and not just high-speed rail. The most important part of a regional railway to speed up is the slowest station throats, followed by slow urban approaches if they prove to be a problem. The most important part of a subway to speed up is individual slow zones at stations or sharp curves that are not properly superelevated. The most important part of a bus trip to speed up is the most congested city center segment.

The Rhine-Neckar Region

The weekend before last, I visited Kaiserslautern and Mainz; I have photos from Mainz and will blog about it separately later this week. Due to a train cancellation, my 2.5-hour direct train to Kaiserslautern was replaced with a three-leg itinerary via Karlsruhe and Neustadt that took 5.5 hours. Even though neither Kaiserslautern nor Karlsruhe is contained within the region, they are both served by the Rhine-Neckar regional rail network. After riding the trains I looked up the network, and want to explain how things work in a metro area that is not very well-known for how big it is.

How polycentric is the system?

The Rhine-Neckar is polycentric, but only to a limited extent. It does have a single central city in Mannheim, with 300,000 people, plus another 170,000 in Ludwigshafen, a suburb across the Rhine. With Heidelberg (which has 160,000 people) and many surrounding suburbs, the total population of this region is 2.5 million, about comparable to Stockholm, Copenhagen, and Hamburg.

The liminal polycentricity comes from the fact that Mannheim has a distinguished position that no single central city has in the Ruhr or Randstad. However, Heidelberg, Neustadt, Worms, and Speyer are all independent cities, all of which have long histories. It’s not like Paris, where the suburbs were all founded explicitly as new towns – Versailles in the Early Modern era, and the rest (Cergy, La Defense, Evry, Marne-la-Vallee, etc.) in the postwar era.

The rail network has the same liminal characteristic, which is what makes it so interesting. There is an S-Bahn, centered on Mannheim. There are two main trunk lines, S1/2 and S3/4: every numbered line runs on an hourly clockface schedule, and S2 and S4 provide short-turn overlays on the S1 and S3 lines respectively, giving half-hourly service on the combined lines. Some additional lines are not Mannheim-centered: the S33 is circumferential, and the S5/51 are two branches terminating at Heidelberg. Additional lines fanning out of Mannheim are under construction, to be transferred from the RegionalBahn system; already S6 to Mainz is running every half hour, and there are plans for lines going up to S9.

However, it is wrong to view the Rhine-Neckar regional rail network as a Mannheim-centric system the way the RER is Paris-centric and the Berlin S-Bahn is Berlin-centric. The Mannheim-centered S-Bahn lines run alongside a large slew of legacy RegionalBahn lines, which run on hourly clockface schedules. The S3 serves Karlsruhe and the S1 and S2 serve Kaiserslautern, but this is not how I got from Karlsruhe to Kaiserslautern: I took a regional train via Neustadt, running on a more direct route with fewer stops via Wörth and Landau, and transferred to the S1 at Neustadt.

Integrated timed transfers

Kaiserslautern is not really part of the Rhine-Neckar region. It is too far west. However, it is amply connected to the core of the region: it has S1 and S2 rail service (in fact it is the western terminus of the S2), and it has regional trains to Mannheim as well as to other cities within the region. The regional train from Mannheim to Kaiserslautern and points west is timed to leave Neustadt a few minutes ahead of the S1, as it runs on the same line but makes fewer stops.

In addition, all these trains to cities of varying levels of importance have a system of timed transfers. I took this photo while waiting for my delayed train back to Paris:

Other than the S-Bahn east, the trains all leave a few minutes after 8:30, and I saw them all arrive at the station just before 8:30, allowing passengers to interchange across as well as between platforms. Judging by static arrival boards posted at stations, this integrated timed transfer repeats hourly.

Some of the lines depicted on the map serve cities of reasonable size, including Mannheim and Heidelberg, but also Homburg, the western terminus of the S1. Others don’t; Pirmasens is a town of 40,000, and the intermediate towns on the line as it winds through the Palatinate valleys have a few thousand people each. Nonetheless, there is evidently enough demand to run service and participate in the integrated timed transfer plan.

Population density and the scope of the network

As I’ve mentioned above, neither Kaiserslautern nor Karlsruhe is properly part of the Rhine-Neckar. Neither is Mainz, which is within the Frankfurt region. Nonetheless, all are on the Rhine-Neckar S-Bahn, and Kaiserslautern isn’t even an outer terminus – it’s on the way to Homburg.

This is for two reasons. The first is that this is a new S-Bahn network, cobbled together from regional lines that were formally transferred to the S-Bahn for planning purposes. It lacks the features that bigger S-Bahn networks have, like strong urban service. The Rhine-Neckar is about the same size as Hamburg, where the S-Bahn provides 10-minute frequencies to a variety of urban neighborhoods; in contrast, the S1/2 and S3/4 trunk lines in Mannheim aren’t even set up to overlay to exact 15-minute frequencies on the shared segment to Heidelberg.

I’ve talked about the distinction between regional and intercity service in the context of Boston. In Boston I recommend that some lines be run primarily as intercities, with long-range service and fewer stops, such as the Providence and Lowell Lines, both serving independent urban centers with weak inner suburbs on the way, while others be run primarily as locals, with more urban stops, such as the Fairmount-Franklin Line, which has no strong outer anchor but does pass through dense neighborhoods and inner suburbs.

The same distinction can be seen in Germany, all falling under the S-Bahn rubric. Wikipedia has a map of all S-Bahn systems in Germany at once: it can be readily seen that Hamburg, Berlin, Munich, Stuttgart, and Frankfurt have predominantly local systems, while Hannover, Nuremberg, the Rhine-Neckar, and Middle Germany (where the largest city is Leipzig) have predominantly intercity systems that are run as if they were S-Bahns.

The second reason owes to the urban geography of the Rhineland. Paris, Berlin, and Hamburg are all clearly-defined city centers surrounded by rings of suburbs. The Rhineland instead has a variety of smaller urban centers, in which suburb formation often takes the form of people hopping to a nearby independent city and commuting from there. All of these cities have very small contiguous built-up areas relative to the size of their metropolitan regions, and contiguous suburbs like Ludwigshafen are the exception rather than the rule.

Moreover, the background population density in the Rhineland is very high, so the cities are spaced very close together. This enabled the Rhine-Ruhr to form as a polycentric metro area comparable in size to London and Paris without having any core even approaching the importance of Central London or central Paris. The Upper Rhine is not as industrialized as the Ruhr, but has the same interconnected network of cities, stretching from Frankfurt and Wiesbaden up to Karlsruhe. In such a region, it’s unavoidable that commuter lines serving different urban cores will touch, forcing an everywhere-to-everywhere network.

To reinforce the importance of high density, we can look at other areas of high population density. The Netherlands is one obvious example, underlying Randstad and an extremely dense national rail network in which it’s not really possible to separate different regions for planning purposes. England overall is dense as well, but the south is entirely London-centric; however, the same interconnected network of cities typical of the Middle and Upper Rhine exists in Northern England, which not only invented the railway but also maintains a fairly dense rail network and has a variety of connecting services like TransPennine. Finally, the Northeastern United States has commuter rail line on nearly the entire length of the Northeast Corridor, touching in Trenton between New York and Philadelphia, with perennial plans to extend services in Maryland, Connecticut, and Rhode Island to close the remaining gaps.

Swiss lessons

Switzerland has long had a national integrated transfer timetable, overlaying more local S-Bahn trains in the biggest cities. As long as there is more than one node in such a network, it is necessary to ensure travel times between nodes permit trains to make multiple transfers.

This leads to the Swiss slogan, run trains as fast as necessary, not as fast as possible. This means that, in a system based on hourly clockface schedules, the trip times between nodes should be about an hour minus a few minutes to allow for transfer time and schedule recovery. Potentially it’s possible to set up some intermediate nodes to have transfers at half-integer hours rather than integer hours, allowing half-integer hour timed transfers. Switzerland’s main intercity lines run on a half-hourly takt, with timed transfers on the hour every half hour in Zurich, Bern, and Basel, which are connected in a triangle with express trains taking about 53 minutes per leg; additionally, some smaller cities have timed transfers 15 and 45 minutes after the hour.

Germany’s rail network is less modern than Switzerland’s, and the Rhine-Neckar schedule shows it. S-Bahn trains run between Kaiserslautern and Mannheim in a few minutes more than an hour, which is why the S-Bahn train depicted in the photo above does not participate in the hourly pulse. In contrast, the regional express trains take 45 minutes, which allows them to participate in the pulse with a little bit of wasted time at Mannheim. Potentially, the region may want to level these two service patterns into one local pattern with a one-way trip time of about 50 minutes, through speeding up the trains if possible. A speedup would not be easy – the rolling stock is already very powerful, and the line is 64 km and has 16 stations and a curvy western half. Discontinuing service on the S2 to two neighborhood stations in Ludwigshafen, which the S1 already skips, is most likely required for such a hybrid S-Bahn/RegionalExpress service.

However, it’s critical to stress that, while Germany is lagging Switzerland, Austria, the Netherlands, and Sweden, it is not to be treated as some American basket case. The Rhine-Neckar rail network is imperfect and it’s useful to understand how it can improve by learning from comparable examples, but it’s good enough so as to be a model for other systems in polycentric regions, such as New England, the Lehigh Valley, Northern England, and Nord-Pas-de-Calais.

The Fish Rots from the Head

All reform agendas run into the same problem: someone needs to implement the reform, and this someone needs to be more politically powerful than the entrenched interests that need reform. The big political incentive for a leader is to swoop in to fix an organization that is broken and get accolades for finally making government work. But whether this work depends on what exactly is broken. If the fish rots from the tail, and better management can fix things, then reformist politicians have an easy time. The problem is that if the fish rots from the head – that is, if the problem is the political leaders themselves – then there is no higher manager that can remove underperforming workers. My contention is that when it comes to poor American public transit practices, the fish usually rots from the head.

Whither fixing construction costs?

I wrote my first comment documenting high New York construction costs at the end of 2009. By 2011 this turned into my first post in my series here with some extra numbers. By the time I jumped from commenting to blogging, the MTA had already made a reference to its high costs in a 2010 report called Making Every Dollar Count (p. 11): “tunneling for the expansion projects has cost between three and six times as much as similar projects in Germany, France and Italy.” New York City Comptroller Scott Stringer has been plagiarizing my 2011 post since 2013.

However, the early recognition has not led to any concrete action. There has not been any attention even from leaders who could gain a lot of political capital from being seen as fixing the problem, such as governors in California, New York, and Massachusetts, as well as successive New York mayors. That Governor Cuomo himself has paid little attention to the subway can be explained in terms of his unique personal background from a car-oriented city neighborhood, but when it’s multiple governors and mayors, it’s most likely a more systemic issue.

What’s more, there has been plenty of time to come up with an actionable agenda, and to see it pay dividends to help catapult the career of whichever politician can take credit. The MTA report came out 9 years ago. An ambitious, forward-thinking politician could have investigated the issue and come up with ways to reduce costs in this timeframe – and in the region alone, four politicians in the relevant timeframe (Mayors Bloomberg and de Blasio, Cuomo, and Governor Christie) had obvious presidential ambitions.

Evidently, there has been action whenever a political priority was threatened. The LIRR had long opposed Metro-North’s Penn Station Access project, on the grounds that by sending trains through a tunnel used by the LIRR, Metro-North would impinge on its turf. As it was a visible project and a priority for Cuomo, Cuomo had to remove the LIRR’s obstruction, and thus fired LIRR President Helena Williams in 2014.

So what’s notable is that construction costs did not become a similar political priority, even though rhetoric of government effectiveness and fighting waste is ubiquitous on the center-left, center, and center-right.

Who benefits?

That successive powerful American leaders have neglected to take on construction costs suggests that there is no benefit to them in fixing the problem. The question is, who benefits from high costs, then?

The answer cannot be that these politicians are all corrupt. The inefficiency in construction does not go to any serious politician’s pockets. Corruption might, but that requires me to believe that all relevant mayors and governors take bribes, which I wouldn’t believe of Italy, let alone the United States. One or two crooks could plausibly lead to cost explosion in one place, but it is not plausible that every serious politician in the New York area in the last decade has been both corrupt and in on the exact same grift.

Another answer I’d like to exclude is powerful interest groups. For example, if the main cause of high American construction costs were unions, then this would explain why governors all over the more liberal states don’t make an effort to build infrastructure more cheaply. However, there are enough high-cost states with right-wing politics and anti-union laws. The other entrenched interest groups are quite weak nationwide, for example planners, who politicians of all flavors love to deride as unelected bureaucrats.

The pattern of competence and incompetence

In my dealings with New York, I’ve noticed a pattern: the individual planners I talk to are curious, informed, and very sharp, and I don’t just mean the ones who leak confidential information to me. This does not stop at the lower levels: while most of my dealings with planners were with people who are my age or not much older, one of my sources speaks highly of their supervisor, and moreover my interactions with senior planners at the MTA when Eric Goldwyn and I pitched our bus redesign were positive. Eric also reports very good interactions with bus drivers and union officials.

In contrast, the communications staff is obstructive and dishonest. Moreover, the most senior layer of management is simply incompetent. Adam Rahbee describes it as “the higher up you get, the less reasonable people are” (my paraphrase, not a direct quote); he brings up work he proposed to do on reworking on the subway schedules, but the head of subway operations did not have the budget to hire an outside consultant and the higher-up managers did not even know that there was a problem with trains running slower than scheduled (“running time”).

A number of area observers have also noticed how MTA head Ronnie Hakim, a Cuomo appointee, was responsible to much of the recent spate of subway slowdowns. Hakim, with background in law rather than operations, insisted speed should not be a priority according to Dan Rivoli’s sources. The operations staff seem to hate her, judging by the number and breadth of anonymous sources naming her as one of several managers who are responsible for the problem.

The pattern is, then, that the put-upon public workers who run the trains day in, day out are fine. It’s the political appointees who are the problem. I don’t have nearly so many sources at other transit agencies, but what I have seen there, at least in Boston and San Francisco, is consistent with the same pattern.

Quite often, governors who aim to control cost institute general hiring freezes, via managers brought in from the outside, even if some crucial departments are understaffed. For example, Boston has an epidemic of bus bunching, is staffed with only 5-8 dispatchers at a given time, and can’t go up to the necessary 15 or so because of a hiring freeze. The 40 or so full-time dispatchers who are needed to make up the difference cost much less than the overtime for bus drivers coming from the bunching, to say nothing of the extra revenue the MBTA could get if, with the same resources, its buses ran more punctually. In the name of prudence and saving money, the MBTA wastes it.

The risk aversion pattern

The above section has two examples of political interference making operations worse: a hiring freeze at the MBTA (and also at the MTA), and Ronnie Hakim deemphasizing train speed out of fear of lawsuits. There is a third example, concerning capital planning: Cuomo’s interference with the L shutdown, well covered by local sources like Second Avenue Sagas, in which the governor effectively took sides in an internal dispute against majority opinion just because engineering professors in the minority had his ear. All three examples have a common thread: the negative political interference is in a more risk-averse direction – hiring fewer people, running slower trains, performing ongoing maintenance with kludges rather than a long-term shutdown.

The importance of risk-aversion is that some of the problems concerning American construction costs are about exactly that. Instead of forcing agencies that fight turf battles to make nice, political leaders build gratuitous extra infrastructure to keep them on separate turf, for example in California for high-speed rail. Only when these turf battles risk a visible project, such as the LIRR’s opposition to Penn Station Access, do the politicians act. Costs are not so visible, so politicians let them keep piling, using slush funds and raiding the rest of the budget.

In New York, the mined stations, too, are a problem of risk-aversion. Instead of opening up portions of Second Avenue for 18 months and putting it platforms, the MTA preferred to mine stations from a smaller dig, a five-year project that caused less street disruption over a longer period of time. An open dig would invite open political opposition from within the neighborhood; dragging it over five years may have caused even more disruption, but it was less obtrusive. The result: while the tunneling for Second Avenue Subway was about twice as expensive as in Paris, the stations were each seven times as expensive. The overall multiplier is a factor of seven because overheads were 11 times as expensive, and because the stop spacing on Second Avenue is a bit narrower than on the Paris Metro extension I’m comparing it with.

In contrast with the current situation in New York, what I keep proposing is politically risky. It involves expanding public hiring, not on a massive level, but on a level noticeable enough that if one worker underperforms, it could turn into a minor political scandal in which people complain about big government. It involves promoting smart insiders as well as hiring smart outsiders – and those outsiders should have industry experience, like Andy Byford at New York City Transit today, not political experience, like the MBTA’s Luis Ramirez or the FRA’s Sarah Feinberg; by itself, hiring such people is not risky, but giving them more latitude to operate is, as Cuomo discovered when Byford began proposing his own agenda for subway investment.

On the engineering level, it involves more obtrusive construction: tunnels and els, not bus lanes that are compromised to death – and the tunnels may involve cut-and-cover at stations to save money. Regional rail is obtrusive politically, as modernization probably requires removal of many long-time managers who are used to the current way of doing things (in Toronto, the engineers at GO Transit obstructed the RER program, which was imposed from Metrolinx), and in New York the elimination of Long Island and the northern suburbs’ respective feudal ownership of the LIRR and Metro-North. The end result saves money, but little kings of hills will object and even though American states have the power to overrule them, they don’t want the controversy.

The fish rots from the head

American transportation infrastructure does not work, and is getting worse. The costs of building more of it are extremely high, and seem to increase with every construction cycle. Operating costs for public transit run the gamut, but in the most important transit city, New York, they are the highest among large world cities, and moreover, the cheapest option for extending high-quality public transit to the suburbs, regional rail, is not pursued except in Silicon Valley and even there it’s a half-measure.

The problems are political. Heavyweight politicians could use their power to force positive reforms, but in a number of states where they’ve been able to do so on favorable terms, they’ve done no such thing. On the contrary, political influence has been negative, installing incompetent or dishonest managers and refusing to deal with serious long-term problems with operations and maintenance.

The reason politicians are obstructive is not that there’s no gain in improving the state of public services. On the contrary, there is a huge potential upside to getting credit for eliminating waste, fraud, and abuse and delivering government projects for much cheaper than was thought possible. But they look at minor controversies that could come from bypassing local power brokers, who as a rule have a fraction of the influence of a governor or big city mayor, or from building bigger projects than the minimum necessary to be able to put their names or something, and stop there.

One animal analogy for this is that the fish rots from the head: the worst abuses come from the top, where politicians prefer slow degradation of public services to a big change that is likely to succeed but risks embarrassment or scandal. The other animal analogy is that, through a system that rewards people who talk big and act small, American politics creates a series of chickenshit leaders.

Where Line 2 Should Go Depends on Where Line 1 Goes

A city that is building a rapid transit network piecemeal has to decide on priorities. There are tools for deciding where to build the first line, such as looking at the surface transit network and seeing what the busiest corridor is. These are relatively well-understood. In this post I’d like to focus on where to build the second line, because that question depends not only on the usual factors for where to build transit, but also on how the first line is expected to change the network. This is relevant not only to cities that are building a new rapid transit system, but also to cities that have such a network and are adding new lines one at a time: the usual tools can straightforwardly suggest where to build one line, but figuring out where to build a second line requires some additional work.

A toy model

Consider the following city, with its five busiest buses, labeled A-E from busiest to fifth busiest:

Let’s stipulate that there’s a wealth of arterial roads radiating in the right directions, and no motorways entering city center, so the exceptions to the rule that trains should go where the busiest buses are don’t apply. Let’s also stipulate that the other buses in the city don’t affect the internal ranking of the first five much – so if there are a bunch of north-south buses close to route C not depicted on the map, they’re not busy enough to make it busier than route A.

Clearly, based on the A > B > C > D > E ranking, the top priority for a first rapid transit line is A. Not only is it the busiest bus but also it is parallel to the second busiest.

But the second priority is not B, but C. The reason is that a rapid transit line on A captures east-west traffic, and then from the eastern and western neighborhoods people on route B are likely to walk south or ride a circumferential bus to get to the train. In the presence of a subway underneath the arterial carrying route A, the strongest bus corridor will almost certainly become C, and thus planners should aim to build a subway there as their second line, and begin design even before the first subway opens.

Fourth Avenue in Vancouver

Vancouver already has a rapid transit system, with three SkyTrain lines. However, the issue of the second line crops up when looking at remaining bus corridors and future subway plans. The strongest bus route is by far Broadway, which had higher ridership than the buses that became the Millennium and Canada Lines even when those lines were planned. The Millennium Line was only built first because it was easier, as it is elevated through the suburbs, and the Canada Line because Richmond demanded a SkyTrain connection.

Fortunately, Broadway is finally getting a subway, running from the Millennium Line’s current terminus at VCC-Clark to Arbutus, halfway toward the corridor’s natural end at UBC. The question is, what next? The second busiest bus corridor in Vancouver is Fourth Avenue, where the combined ridership of the 4, 44, and 84 buses and the part of the 7 that is on Fourth exceeds that of any corridor except Broadway; only Hastings, hosting the 95 and 160, comes close.

And yet, it is obviously wrong to plan any subway on Fourth Avenue. Fourth is half a kilometer away from Broadway; the 44 and 84 are relief for the 99 on Broadway. TransLink understands it and therefore there are no plans to do anything on Fourth – the next priority is extending the Expo Line farther out into Surrey or Langley, with the exact route to be determined based on political considerations.

Regional rail and subways in New York

In New York, two commonly-proposed subway extensions, down Nostrand and Utica, are closely parallel. The fact that they are so close to each other means that if one is built, the case for the other weakens. But these two corridors are so strong it is likely that if one is built, the second remains a very high priority. The only subway priority that is plausibly lower than the first of the two and higher than the second, regardless of which of Utica and Nostrand is built first, is a 125th Street crosstown extension of Second Avenue Subway.

But a more serious example of one future line weakening another occurs for regional rail. The top priority for regional rail in New York is four-tracking the tunnels to Penn Station under the Hudson; based on this priority, organizations that look beyond the next gubernatorial or congressional election have come up with farther-reaching proposals. Here, for example, is the map from the RPA’s Fourth Regional Plan:

In addition to four-tracking the North River Tunnels under the aegis of the Gateway project, the RPA calls for two additional two-track tunnels under the Hudson, in phases 2 and 3 of its proposal. Both are to feed Midtown: the phase 2 tunnel is to connect regional rail lines to be reactivated with Columbus Circle, Grand Central, and other destinations in the city, and the phase 3 tunnel is to then carry the same line out of the city and back into New Jersey via Hoboken and the existing commuter lines serving southern and southwestern suburbs.

The logic, as I understand it, is that Midtown is the core of the New York region, and so it is the most important to connect there. I don’t know if this is what the RPA was thinking, but I asked at an IRUM meeting in 2010 why all plans involve connections to Midtown rather than Lower Manhattan and was told Lower Manhattan was not as important a business district.

The toy model has one fixed city center and varying outlying areas, the opposite of the situation here. Here, my criticism is of plans that serve the dominant city center while ignoring the second most important center. The total number of jobs in Midtown is 800,000 whereas Lower Manhattan has 250,000 – but Lower Manhattan is more compact, so a single station at Fulton with several exits can plausibly serve the entire area, whereas Midtown has areas that are too far from both Penn Station and Grand Central. The next pair of tracks should serve Midtown, but the pair after them should serve Lower Manhattan, to ensure good coverage to both business districts.

The Soviet Bloc Way of Building Rapid Transit

Based on positive feedback from Patreon backers, I am expanding my post about the American way of building rapid transit into a series covering various national traditions. The Soviet bloc’s tradition is the most globally widespread, as Soviet advisors trained engineers in the USSR’s entire sphere of influence, ranging from just east of the Iron Curtain to North Korea. It is especially fascinating as it evolved independently of Western and Japanese metro-building traditions, from its origins in Moscow in the 1930s.

Like the American tradition, the Soviet tradition has aspects that are worth emulating and ones that are not. But it’s useful to understand where the design aspects come from. It’s especially interesting as Moscow has influences from London, so comparing where the Russians did better and where they did worse is a good case study of adapting a foreign idea to a different national context. Similarly, China imported Russian ideas of how to build metro networks while making considerable adaptations of its own, and I hope to cover China more fully in a future post, discussing there too how the tradition changed in the transmission.

Technical characteristics

The Soviet way is characterized by four major features:

Wide station spacing: the average interstations on the systems in question are all long. Moscow’s is 1.7 km, and for the most part cities in the former USSR with metros have similar interstations; in this table, length is in the row labeled 1 and number of stations in the row labeled 3. This is also true of the metro systems in China and North Korea, but in the Eastern European satellite states it’s less true, with Prague and the newer lines in Budapest averaging not much more than 1 km between stations.

Very little branching: Soviet lines do not branch, with a small handful of exceptions. Moscow’s only branching line, Line 4, is unique in multiple ways, as it was redesigned with American influence after Nikita Khrushchev’s visit to the United States. Eastern European satellite state metros do not branch, either, in contrast with contemporary postwar Western European networks like those of Stockholm and Milan. China has more branching, albeit less than Western and Japanese systems of comparable scope.

Radial network design: what I call the Soviet triangle, while not really a Soviet invention (it has antecedents in Boston and London), became a rigid system of network design in the communist bloc. Subway lines all run as rough diameters through the disk of the built-up area, and meet in the center in a triangle rather than in a three-way intersection in order to spread the load. Moscow adds a single circular line to the mix for circumferential travel, subsequently refined by a second and soon a third ring. Here, China diverges significantly, in that Beijing has grid elements like parallel lines.

Deep boring: Soviet and Soviet-influenced metro networks run deep underground. Traditionally, there was limited above-ground construction, for reasons of civil defense; in Moscow, only Line 4 is shallow, again due to American influence.

London’s long shadow

The decision to deep-bore the Moscow Metro was undertaken in the 1920s and 30s, long before the Cold War and the militarization of Soviet society. It even predates the turn to autarky under Stalin; as Branko Milanovic notes, the USSR spent most of the 1920s trying to obtain foreign loans to rebuild after the Revolution, and only when foreign capital was not forthcoming did it turn to autarky. The NKVD arrested the British advisors, conducted show trials, and deported them for espionage in 1933; the basic technical characteristics were already set then.

In London, the reason for deep boring is that the city has one street wide and straight enough for a cut-and-cover subway, Euston Road hosting the Metropolitan line. In Moscow, such streets are abundant. British planners were exporting both the idea of constructing wide throughfares based on modernist planning principles and that of deep-boring metro lines, an invention based on the context of a city that lacks such throughfares.

The network design bears similarity to what London would have liked to be. London is not as cleanly radial as Moscow, but it clearly tries to be radial, unlike New York or Paris. In general, it’s best to think of the early Moscow Metro as like early-20th century London Underground lines but cleaner – stations spaced farther apart, more regular radial structure, none of the little quirks that London’s had to build around like the Piccadilly line’s since-closed Aldwych branch.

Transit and socialism

The Soviet method of building metros may have originated in British planning, but its implementation throughout the 20th century was under socialist states, in which there was extensive central planning of the entire economy. Decisions regarding who got to live in the cities, where factories were to be sited, what goods were to be produced, and which sectors each city would specialize in were undertaken by the state.

There are several consequences of this political situation. First, by definition all urban development was social housing and all of it was TOD. Housing projects were placed regularly in ever-expanding rings around city center, where all the jobs were. There was no redevelopment, and thus density actually increased going out, while industrial jobs stayed within central cities even though in the capitalist bloc they suburbanized early, as factories are land-intensive.

Of note, some of this central planning also existed under social democracy: Sweden built the Million Program housing in Stockholm County on top of metro stations, creating a structure of density enabling high transit ridership.

But a second aspect is unique to proper communism: there were virtually no cars. Socialist central planning prioritized capital goods over consumer goods, and the dearth of the latter was well-known in the Cold War. At the same time, modernist city planning built very large roads. With no cars to induce people to fight for livable streets nor anything like the Western and Japanese New Left, urban design remained what today we can recognize as extremely car-oriented, before there were any cars. Major Eastern European cities are thus strongly bifurcated, between ones where a centrally planned metro has ensured very high per capita ridership, like Prague, Budapest, and Moscow (and also Bratislava, with trams), and ones where as soon as communism fell and people could buy cars the tramway network’s ridership cratered, like Tallinn, Riga, and I believe Vilnius.

The third and last aspect is that with extensive central planning, the seams that are visible in cities with a history of competition between different transit operators are generally absent. The incompatible gauges of Tokyo and the missed connections of New York (mostly built by the public-sector IND in competition with the private-sector IRT and BMT) do not exist in Moscow; Moscow does have missed connections between metro lines, but not many, and those are an awkward legacy of long interstations.

Of note, the autocratic aspects of socialism do not come into play in Soviet metro design. One would think that the Stalinist state would be able to engage in projects that in democracies are often unpopular due to NIMBYism, such as cut-and-cover subways, but the USSR did not pursue them. China does build elevated metro lines outside city centers, but evidently its plans to extend the Shanghai Maglev Train ran into local NIMBYism. People complained that the separation between the tracks and adjacent buildings was much less than in the German Transrapid standards; the Chinese state’s credibility on environmental matters is so low that people also trafficked in specious concerns about radiation poisoning.

The role of regional rail

The European socialist states all inherited the infrastructure of middle-income countries with extensive proto-industry – in particular, mainline rail. Russia had even completed the Trans-Siberian Railway before WW1. The bigger cities inherited large legacy commuter rail networks, where they operate commuter EMUs.

But while there are many regional trains in the European part of the former Soviet bloc, they are not S-Bahns. There was and still is no through-service, or frequent off-peak service. Connections between the metro and mainline rail were weak: only in 2016 did Moscow start using a circular legacy railway as its second urban rail ring.

The situation is changing, and just as Moscow inaugurated the Central Circle, so is it planning to begin through-service on radial commuter rail, called the Moscow Central Diameters. However, this is early 21st century planning, based on Western European rapid transit traditions.

Does this work?

In the larger cities, the answer is unambiguously yes: they have high transit ridership even when the population is wealthy enough to afford cars. The smaller cities are more auto-oriented, but that’s hardly the fault of Soviet metro planning when these cities don’t have metro networks to begin with; the fault there concerns urban planning more than anything.

Three aspects of Soviet metro planning deserve especial positive mention. The clean radial structure best approximates how single-core cities work, and Moscow and the cities it inspired deserve credit for not wasting money on low-ridership tangential lines, unlike Mexico City or (at smaller scale) Paris. It’s not too surprising that the Soviet triangle in particular exists outside the Soviet bloc, if not as regularly as in Eastern Europe.

The second positive aspect is the use of headway management in Moscow. With no branching and high frequency, Moscow Metro lines do not need to run on a timetable. Instead, they run on pure headway management: clocks at every station count the time elapsed since the last train arrived, and drivers speed up or slow down depending on what these clocks show relative to the scheduled headway between trains. At the peak, some lines run 39 trains per hour, the highest frequency I am aware of on lines that are not driverless (driverless metro technology is capable of 48 trains per hour, at least in theory, and runs 42 in practice on M14 in Paris).

The third and last is the importance of central planning. All public transportation in a metro region should be planned by a single organ, which should also interface with housing planners to ensure there is ample TOD. If anything, one of the bigger failures of Soviet metro planning is that it did not take this concept all the way, neither integrating metros with regional rail nor building a finger plan.

In contrast with these three positive aspects, station design is lacking. As frequent commenter and Patreon supporter Alexander Rapp noted in comments, there are some cross-platform transfers in Moscow; however, the initial three lines do not have such transfers, and instead the transfers became congested early, creating the impetus for the Circle Line. The deep-bored stations are expensive: Line 4 was built cut-and-cover to save money, not out of some cultural cringe toward New York, and today Russia is looking at cut-and-cover stations as a way to reduce construction costs.

Moreover, the wide interstations are too clean. The Underground has long interstations outside Central London and short ones within Central London, facilitating interchanges; while London has eight missed connections, these result from seams on lines running alongside each other or on branches, and only one pair of trunks has no transfer at all, the Metropolitan line and the Charing Cross half of the Northern line. In contrast, the relentlessly long interstations in Moscow lead to more misses.

Technology and Public Transit

I have noticed a trend in tech media in the last few years: people assert that new technology is about to make public transportation and the walkable urbanism that underlies it obsolete, and therefore it’s a waste of time to invest in the latter. The top examples of this are ride-hailing apps and autonomous cars, but electric cars are also a common excuse not to build urban rail. In addition, there are knock-on effects, causing transit agencies to neglect core functions like good service in favor of tech gimmicks, like Andrew Cuomo’s genius challenge.

In contrast, I’d like to present two much-anticipated technological changes that have the opposite effect: they should make the case for public transit easier. In no case is this directly about public transportation. Rather, it’s about making it easier to design cities for the exclusive use of pedestrians, cyclists, and public transit riders. One of these changes is still in the proof-of-concept stage; the other is already happening, and it’s on cities to capitalize on it.

Drone delivery

There is ongoing experimentation about using aerial drones to deliver goods. The examples Wikipedia has are high-value, low-weight, such as passports and drugs. The current state of technology is such that delivering such goods by drone is feasible, though not yet at commercial scale, but there is research into bigger drones.

The impact of drone delivery is on how cities are built for freight movement. All freight transportation in cities today is done by truck, except for the occasional low-end bike delivery. Rail freight is completely infeasible: it operates at long ranges – in fact, two papers, one by Vassallo-Fagan and one by Furtado, find that 45% of the difference in rail freight modal share between the US and Europe is an artifact of longer distance for inland transportation in the US. Moreover, whatever rail freight exists is of low value – in the US, rail had 4% of the total value of goods shipped and 47% of ton-km in 2002. The stuff drones can plausibly carry goes by truck at any distance today.

So the potential is there for drones to take some of the most critical goods away from trucks, reducing city truck traffic, and with it, the demand for car-friendly street design. The socioeconomic class most opposed to giving public transit higher priority (at least in New York), the shopkeepers, cites deliveries as the primary reason to maintain curbside access.

Of note, drone delivery is also useful for rural areas with bad roads – it makes goods more easily available there. The likely effect of widespread drone delivery on urbanity has two components: reducing the consumption amenities of cities, since a more efficient transportation network makes it easier to ship goods to remote areas; and increasing the production amenities of cities, since it’s easier to design cities for maximum transportation efficiency of people, not to mention the office jobs created by the need to maintain drone software (the latter point also made by Masahita Fujita re new economic geography).

Automation of manufacturing

The increase in automation of manufacturing means that manufacturing employment is trending down. This is not an artifact of offshoring: Dani Rodrik’s paper about premature deindustrialization finds that the share of manufacturing in total employment is trending down in a large variety of poor and middle-income countries, and even in South Korea the manufacturing share peaked in 1989. Rather, there is a shift in the nature of low- and medium-skill work away from industry and toward services.

This is good for any attempt to get people to commute by public transit. Factories have not been conducive to public transportation for a hundred years. Electrification has encouraged single-story atria with plenty of space, replacing cramped multistory buildings like the Triangle Shirtwaist Factory. Moreover, the rise of trucking has meant that the best site for a factory is one with very good highway access. The industrial site of the last few generations is not walkable, and any worker who earns enough to drive will. Serving such a site by transit is in theory possible, but employment is so spread out that the bus or train would underperform.

But today, manufacturing is increasingly irrelevant to commuting. Working-class employment concentrates in areas that are part of the middle class’s regular travel routine: hotels, casinos, and airports are destinations for middle-class travelers, shopping centers are destinations for middle-class consumers, hospitals and universities are large employers across all social classes from professors down to unskilled workers. With the exception of airports, these destinations are already fairly walkable or at least can be built this way, and in some cases, like that of the French Riviera, this could lead to public transit serving the working class better than the middle class.

In most of the top transit cities in the developed world, this process has already run its course. There is practically no industry left in New York, London, and Paris. But it does matter to some cities, such as Singapore, with its vast port with no passenger rail service. Los Angeles is not a transit city and it’s not because it has relatively high industrial employment for an American city, but the high manufacturing concentration does not help. Understanding that these jobs are slowly disappearing, not from one country but from the world, will help cities plan accordingly, especially in lower- and middle-income countries.

Cross-Platform Transfers

I did a complex Patreon poll about series to write about. In the poll about options for transit network design the winning entry was difficult urban geography, covered here and here; the runner-up was cross-platform transfers.

Subway users have usually had the experience of connecting at a central station so labyrinthine they either were lost or had to walk long distances just to get to their onward train. Parisians know to avoid Chatelet and New Yorkers know to avoid Times Square. It’s not just an issue for big cities: every metro system I remember using with more than one line has such stations, such as T-Centralen in Stockholm, Waterfront in Vancouver, and Dhoby Ghaut in Singapore. To prevent such connections from deterring passengers, some cities have invested in cross-platform interchanges, which permit people to transfer with so little hassle that in some ridership models, such as New York’s, they are treated as zero-penalty, or equivalent to not having to transfer at all.

Unfortunately, improving the transfer experience is never as easy as decreeing that all interchanges be cross-platform. While these connections are always better for passengers than the alternative, they are not always feasible, and even when feasible, they are sometimes too expensive.

Cross-platform transfer to wherest?

Consider the following two-line subway interchange:

A cross-platform transfer involves constructing the station in the center so that the north-south and east-west lines have platforms stacked one on top of the other, with each east-west track facing a north-south track at the same platform. The problem: do eastbound trains pair up with northbound ones and westbound trains with southbound ones, or the other way around?

In some cases, there is an easy answer. If two rail lines heading in the same general direction happen to cross, then this provides a natural pairing. For example, the Atlantic Branch and Main Line of the LIRR meet at Jamaica Station, where the cross-platform transfer pairs westbound with westbound trains and eastbound with eastbound trains. In Vienna, this situation occurs where U4 and U6 intersect: there is a clear inbound direction on both lines and a clear outbound lines, so inbound pairs with inbound and outbound with outbound.

However, in most cases, the transfer is within city center, and there is no obvious pairing. In that case, there are two options.

Near-cross platform transfer

Some transfers are nearly cross-platform. That is to say, they have trains on two levels, with easy vertical circulation letting people connect between all four directions. In Berlin, there is such a transfer at Mehringdamm between U6 and U7 – and in the evening, when trains come every 10 minutes, they are scheduled to offer a four-way timed interchange, waiting for connecting passengers even across a level change.

Multi-station transfer complex

Singapore, Stockholm, and Hong Kong all offer cross-platform transfers in multiple directions by interweaving two lines for two or three consecutive stations. The three-station variant is as in the following diagram:

At the two outer transfer stations, the cross-platform connections are wrong-way relative to the shared trunk corridor: eastbound pairs with northbound, westbound pairs with southbound. At the middle station, connections are right-way: eastbound pairs with southbound, westbound pairs with northbound.

Of note, the shared trunk has four tracks and no track sharing between the two different subways. I’ve proposed this for the North-South Rail Link. The reason three stations are needed for this and not two is that with only two stations, passengers would have to backtrack in one pairing. Nonetheless, backtracking is common: Stockholm has three stations for the transfer between the Green and Red Lines but only the northern one is set up for wrong-way transfers, so passengers connecting wrong-way in the south have to backtrack, and Singapore has two stations between the East-West and North-South Lines, since one of the pairings, west-to-south, is uncommon as the North-South Line extends just one station south of the transfer.

Why are they not more widespread?

The inconvenience of Parisian transfers is a general fact, and not just at Chatelet. Two lines that meet usually meet at right angles, and the platforms form a right angle rather than a plus sign, so passengers have to be at one end of the train to have easy access to the connecting platforms. The reason for this is that Paris built the Metro cut-and-cover, and there was no space to reorient lines to have cross-platform transfers.

In contrast, both Stockholm and Singapore had more flexibility to work with. Singapore deep-bored the MRT for reasons of civil defense, contributing to its recent high construction costs; the tradeoff is that deep boring does permit more flexibility underneath narrow streets, which all streets are compared with the footprint of a cross-platform interchange. Stockholm used a mixture of construction methods, but the four-track trunk carrying the Green and Red Lines is above-ground in the Old City but was built with a sunk caisson at T-Centralen.

In London, similarly, there are cross-platform transfers, involving the Victoria line. It was built in the 1960s around older infrastructure, but at a few spots in Central London, the tubes were built close enough to old lines to permit cross-platform interchange in one direction (northbound-to-northbound, southbound-to-southbound). In contrast, the surface network, constrained by land availability, does not feature easy interchanges.

While deep boring makes cross-platform transfers easier, either can exist without the other. If I understand this correctly, U6 was built cut-and-cover. There were even weaves on the IND in New York, but they were expensive. Moreover, when two lines are built under a wide street with two branching streets, rather than on something like a grid (or even Paris’s street network, which is gridded at key places like where M4 runs under Sevastopol), cut-and-cover construction can produce a cross-platform transfer. Conversely, such transfers do not exist in all-bored Moscow and are rare in London.

The importance of planning coordination

Ultimately, cross-platform transfers boil down to coordinated planning. Some cities can’t build them even with coordination – Paris is a good example – but absent coordination, they will not appear no matter how good the geography is. Stockholm, Berlin, Vienna, Singapore, and Hong Kong are all examples of centrally planned metro networks, without the haphazard additions of New York (which was centrally planned on three separate occasions) or London (where the early lines were built privately).

Even with coordination, it is not guaranteed cross-platform transfers will appear, as in Moscow. Planners must know in advance which lines they will build, but they must also care enough about providing a convenient transfer experience. This was not obvious when Moscow began building its metro, and regrettably is still not obvious today, even though the benefits are considerable. But planners should have the foresight to design these transfers when possible in order to reduce passenger trip times; ultimately it is unlikely to cost more than providing the same improvements in trip times through faster trains.

Public Transit is Greener Than It Seems

The main way to judge how good public transportation is for the environment is to measure how many car trips it displaces. But in reality, it’s better, and I’d like to explain why. As a warning, this is a theoretical rather than empirical post. My main empirical evidence for it is that European car usage is lower relative to American levels than one might expect given public transit mode shares; in a way, it’s an explanation for why this is the case.

While the explanation relies on changes in land use, it is not purely a story of zoning. The population density in much of my example case of auto-oriented density – Southern California – is well below the maximum permitted by zoning, thanks to the lack of good transit alternatives. Thus, even keeping zoning regimes mostly as they are, public transportation has an impact on land use and therefore on car pollution.

Transit always displaces the longest car commutes

In an auto-oriented city, the limiting factor to the metro area’s density is car traffic. Adding density with cars alone leads to extra congestion. Devin Bunten’s paper entitled Is the Rent Too High? finds that, assuming no changes in travel behavior (including no change in the option of public transit), zoning abolition would actually reduce American welfare by 6%, even while increasing GDP by 6%, because of much worse congestion; optimal upzoning would increase GDP by 2.1% and welfare by 1.4%, which figures are lower than in the Hsieh-Moretti model.

The upshot is that if there is no public transportation, people live at low density just because the alternative is the traffic jams of dense car-oriented cities; Los Angeles is the most familiar American example, but middle-income examples like Bangkok are denser and worse for it. Low density means people travel longer to reach their jobs, by car, increasing total vehicle travel.

In the presence of mass transit, people don’t have to sprawl so far out. Los Angeles’s “drive until you qualify” mentality is such that, if there were room for a million transit users in the inner parts of the region, then no matter which exact group of million people from the five-county area started taking transit, ultimately the shuffle would be such that there would be a million fewer people driving in from Antelope Valley, Victor Valley, and the Inland Empire.

The model

Consider a city that comprises concentric rings, as in the following diagram:

The average density of the city region is 1,660 people per square kilometer, and the weighted density is about 3,400; both figures are typical for the denser American Sunbelt cities, like Los Angeles, San Diego, Miami, and Las Vegas (see table as of 2000 here).

Let us assume that the amount of v-km per inhabitant within each concentric circle is proportional to the outer radius of the circle, so people in the outermost ring drive 5 times as long as those in the inner circle. For concrete numbers, let us assume these figures are 5,000, 10,000, 15,000, 20,000, and 25,000 v-km per year; they average about 13,550 v-km/capita, which is somewhat less than the US average, just below 16,000 per FRED. Note that the outermost ring has 10.8% of the city’s population and 20% of its v-km.

If the modeled density is close to optimal for congestion management given the current state of public transit, then adding transit means subtracting people from the outer ring, not from the inner rings. Say the city builds rapid transit reaching the inner two rings, allowing these areas to densify by exactly 22.5%, which is the ratio of the outer ring’s population to the inner two’s total’s. The total non-auto mode share will rise by 10.8 percentage points, divided between public transit and walking because people in dense, walkable neighborhoods have the option of non-motorized transport; but v-km and the attending greenhouse gas emissions will fall 20%.

If the city keeps growing, the situation is even more extreme. We can add a sixth ring, on the same model, with a density of 250 people per km^2, 30,000 annual v-km per capita, and population equal to 6.6% of the total of the five existing rings or 6.2% of the six-ring total. This 6.6% increase in population raises v-km by 14.7%; in contrast, a transit system capable of supporting this population increase would show an increase of 6.2 points in the non-auto mode share even while avoiding a 14.7% increase in car traffic.

European car usage

We can obtain total v-km per capita by country from a table of traffic accident fatalities: the OECD reports numbers per capita and per v-km, so if we go to PDF-p. 60 of its report, divide the per-capita figure by the per-v-km figure, and multiply by a scaling factor of 10,000, we get v-km per capita. In the US, this figure is just short of 16,000, just as in the FRED graph. The US’s transit mode share for work trips is 5%, so this is about as close as possible to a purely auto-oriented country.

In the Western European countries for which there’s data, including France and Germany, the figure is just short of 10,000. This is close to INSEE’s figure of 756 billion passenger-km in 2016, the difference accounted for by the fact that sometimes multiple people ride in the same car.

The reason people here travel 40% less by car than in the US is not that they instead travel the same distance by public transit. INSEE reports 132 billion passenger-km in buses, trams, and trains excluding TGVs in 2016, and this includes a fair amount of intercity bus and rail travel (9 billion p-km on intercity rail as of 2010 per p. 53 here). Overall, the French modal split is 70% car, 15% transit, 6.7% walk, 4.3% work from home, 4% bike and motorcycle. The American one is 85% car, 5% transit, 2.7% walk, 5.2% work from home. Even relative to the volume of car commuters, the Americans drive 40% further than the French.

Much of my understanding of how provincial France works comes from the Riviera. The Riviera is not the best representative: Alpes-Maritimes is among the richest departments outside Ile-de-France, is among the most conservative, and near-ties Toulouse’s Haute-Garonne and Strasbourg’s Bas-Rhin for third highest provincial transit mode share (13%, behind Rhone’s 23% and Bouches-du-Rhone’s 14%). But it’s a good representative nonetheless of a major provincial city region. There, the coastal towns as well as some interior ones are filled with sprawl, even going up the mountains. There is density in Monaco and Nice, and public transit ridership mostly consists primarily of people who live in Nice and secondarily of people who commute to Monaco. It’s the tramway, the buses, and the general walkability that permit Nice to be what it is, coexisting alongside the offices parks of Sophia-Antipolis and the low-density sprawl up the mountains.

What about zoning?

Devin’s paper is about the economic cost of zoning. Even with the assumption of no change in built form or in transportation modal choice, it does find welfare gains from upzoning, saying that high-demand areas would gain 10-15% in population. This implies that realizing the full environmental gains from public transit requires upzoning areas near stations, to permit the inner two rings in my model city to gain residents who would have otherwise populated a sixth ring.

And yet, the appropriate zoning to some extent already exists. California abolished single-family zoning in 2016 and 2017: accessory dwelling units, or ADUs, are permitted anywhere that residential development is permitted, and homeowners are free to build ADUs in their backyards or carve out ADUs out of their existing buildings. Moreover, in select zones, cities have encouraged transit-oriented development through upzoning or relaxing parking minimums: San Francisco’s TDM process abolished parking minimums anywhere that buildings with at least 10 apartments are permitted, and San Diego slashed parking minimums in an attempt to encourage TOD in North Park along the University Avenue corridor.

The results of TDM in San Francisco are still unclear – the program passed too recently. The same is true of ADUs – existing homeowners react slowly, and new developers may build more two-family houses and fewer single-family houses, but new tract housing would go in the exurbs, not in the coastal cities. But in San Diego the results are clear: developers build more parking than the required minimum at University and 30th, because the public transit option there is a north-south bus that comes every 15 minutes and an east-west bus that comes every 10, which is not actually enough to persuade people who can afford a car not to drive one.

Conclusion

It is difficult to build TOD without public transport. The urban middle class of the 21st century expects travel convenience, which can come in the form of a large rapid transit network or in that of cars and freeways. Thus, even when development sites are available, even in expensive cities, developers sometimes build less than they are allowed to, or insist on more parking than is required, if alternative transportation is inadequate.

The upshot is that adding the layer of transit is likely to stimulate development in the affected urban neighborhoods. The people who would live in this development would not otherwise drive to the outer margin of the city to save on rent, but they would still drive, displacing people would then drive further. The exact details of the churn matter less than the net impact, which is that absent urban transit, cities end up sprawling farther out, forcing people to drive ever-longer distances to work and to other destinations.

A city that succeeds in replacing half of its car trips by public transit, such as Paris, will end up replacing far more than just half of its vehicle-km by transit. Even if the trains are densest within the city core, as is the case even in Paris and other cities with expansive regional rail, the net impact of the transit network is reduction in car travel in the outer parts of the built-up area, where distances are the longest. Planetoscope’s figures for car travel and average distance in Ile-de-France point to a total of just 2,900 v-km/capita in this region – less than one third the national average, and barely one half the national average per car commuter.

The benefit of transit thus goes well beyond the people who use it. The car trips it displaces, even if indirectly, are the ones that cause the worst problems – congestion, pollution, car accidents, greenhouse gas emissions – because they are the longest. Building urban rapid transit can have twice the direct mitigating effect on the harms of car travel as might appear based purely on counting mode choice. With twice the apparent positive environmental impact, mass transit must become a higher priority: nearly every new rapid transit line that’s judged as good must be a top priority for public investment, and many projects that appear marginal must be reevaluated and constructed as planned.

Meme Weeding: Unions and Construction Costs

Lately I’ve seen some very aggressive people on social media assert that high American transit construction and operating costs are the fault of unions, and thus, the solution is to break the unions using the usual techniques of subterfuge and breaking implicit promises. A while back, maybe a year ago, I even saw someone argue that gadgetbahn (monorails, PRT, Hyperloop, etc.) is specifically a solution to union agreements covering traditional transit but not things that are marketed as new things. This is an incorrect analysis of the problem, and like many other incorrect analyses, the solutions that would follow were this analysis correct are in fact counterproductive.

American costs are high even without unions

The majority of American transit construction occurs in parts of the country with relatively strong unions. This is for historical reasons: American cities with large prewar cores are both more unionized and more densely populated than newer Sunbelt cities. Thus, a table with cities and their subway construction costs, such as what one might get cobbling together my posts, will show very high costs mostly in cities with American unions.

However, American cities with weak unions build transit too, it’s just unlikely to come with subway tunnels. We can look at above-ground urban rail construction costs in a variety of American states with right-to-work laws. There is one recent above-ground metro line in a right-to-work state, the Washington Silver Line in Virginia, and another proposal, an extension of MARTA. Let’s compare their costs with those of other mostly at-grade urban rail lines in unionized West Coast states:

We can go lower than this range by looking at street-running light rail lines, which are popular in such Sunbelt cities as Dallas, Houston, Phoenix, and Charlotte, but then we can compare them with light rail lines in Minneapolis, which has no right-to-work laws.

Let’s also look at commuter rail. Dallas’s Cotton Belt Line, a diesel line in a disused freight right-of-way, is projected to cost $1.1 billion for 42 km. The cost, $26 million per km, is within the normal European range for greenfield high-speed rail without tunnels, and more than an order of magnitude higher than some German examples from Hans-Joachim Zierke’s site. In Massachusetts, the plans for South Coast Rail cost around $3 billion for 77.6 km before some recent modifications cutting both cost and length, about $40 million per km; this would have included electrification and right-of-way construction through an environmentally sensitive area, since bypassed to cut costs.

Finally, what of operating costs? There, the Sunbelt is unambiguously cheaper than the Northeast, Chicago, and California – but only by virtue of lower market wages. The cost ranges for both sets of states are wide. In Chicago and San Francisco, the operating costs of rapid transit are not much higher than $5/car-km per the NTD, which is normal or if anything below average by first-world standards. Light rail looks more expensive to operate in old unionized cities, but only because Boston, Philadelphia, and San Francisco’s light rail lines are subway-surface lines with low average speeds, which are more expensive to run than the faster greenfield light rail lines built elsewhere in North America. The lowest operating costs on recently-built light rail lines in the US are in Salt Lake City, San Diego, and Denver, and among those only the first is in a right-to-work state.

Non-labor problems in American transit

I urge everyone to look at the above lists of American transit lines and their costs again, because it showcases something important: high American costs are not a uniform problem, but rather afflict some areas more than others. Commuter rail construction costs are the worst, casually going over European levels by a full order of magnitude or even more. Subway operating costs are the best, ranging from no premium at all in some cities (Chicago) to a factor-of-2 premium in others (New York). Light rail construction costs are in the middle. The variety of cost premiums suggests that there are other problems in play than just labor, which should hit everything to about the same extent.

When I’m asked to explain high American construction costs, I usually cite the following explanations:

  1. Poor contracting practices, which include selection of bidders based exclusively on cost, micromanagement making companies reluctant to do business with New York public works, and design-build contracts removing public oversight and encouraging private-sector micromanagement.
  2. Poor project management: Boston’s Green Line Extension is now budgeted at about $1 billion for 7.6 km, but this is on the heels of an aborted attempt from earlier this decade, driving up total money spent beyond $2 billion.
  3. Indifference to foreign practices: Americans at all levels, including transit agencies, shadow agencies like the Regional Plan Association, and government bodies do not know or care how things work in other countries, with the partial exception of Canada and the UK, which have very high costs as well. The area where there has been the greatest postwar innovation in non-English-speaking countries, namely commuter rail, is the one where the US is the farthest behind when it comes to cost control. Explanation #1 can be folded into this as well, since the insistences on cost + technical score bid selection and on separation of design and construction are Spanish innovations, uncommon and obscure in the English-speaking world.
  4. Overbuilding: extra infrastructure required by agency turf battles, extra construction impact required by same, and mined stations. Other than the mined stations, the general theme is poor coordination between different agencies, which once again is especially bad when commuter rail is involved for historical reasons, and which in addition to raising costs also leads to lower project benefits.

Labor is a factor, but evidently, the intransigent BART unions coexist with low operating costs, as do the Chicago L unions. American unions are indifferent to productivity more than actively hostile to it, and in some cases, i.e. bus reforms in New York, they’re even in favor of treatments that would encourage more people to ride public transit.

But union rules force transit agencies to overstaff, right?

In the Northeast, there are unambiguous examples of overstaffing. Brian Rosenthal’s article for the New York Times found horror stories, and upon followup, frequent commenter and Manhattan Institute fellow Connor Harris has found more systematic cases, comparing the ~25 people it takes to staff a tunnel-boring machine in New York with the 12 required in Germany. The unions themselves have pushed back against this narrative, but it appears to be a known problem in the infrastructure construction industry.

So what gives? In Texas, the unions are too weak to insist on any overstaffing. Texas is not New York or even California. Without knowing the details of what goes on in Texas, my suspicion is that there is an informal national standard emerging out of mid-20th century practices in the cities that were big then. I see this when it comes to decisions about construction techniques: features that came out of the machinations of interwar New York, like the full-length subway mezzanine, spread nationwide, raising the cost of digging station caverns. I would not be surprised to discover something similar when it comes to staffing. Obvious economies like running driver-only train are already widespread nearly everywhere in the US, New York being the exception. Less obvious economies concerning maintenance regimes are harder to implement without very detailed knowledge, which small upstart Sunbelt transit agencies are unlikely to have, and if they invite consultants or other experts, they will learn to work in the same manner as the big American transit agencies.

The reality that the entirety of the American transit industry is used to doing things a certain way means that there needs to be a public discussion about staffing levels. There are jobs that look superfluous but are in fact crucial, and jobs that are the opposite. The cloak-and-dagger mentality of anti-union consultants does not work in this context at all. Experimentation is impossible on a safety-critical system, and nothing should be changed without double- and triple-checking that it works smoothly.

Anti-union explanations are harmful, not neutral

While union overstaffing does drive up tunneling costs in the United States, there are many other factors in play, which must be solved by other means than union-busting. By itself, this would make union-busting either neutral or somewhat positive. However, in reality, the politics of union-busting wreck government effectiveness in ways that make the overall cost problem worse.

The people who try to tell me the problem is all about the unions are not, as one might expect, Manhattan Institute hacks. Connor himself knows better, and Nicole Gelinas has been making narrow arguments about pension cuts rather than calling for sweeping changes to leave unions in the dust. Rather, the loudest anti-union voices are people who either are in tech or would like to be, and like using the word “disruption” in every sentence. The Manhattan Institute is pretty open about its goals of union-busting and race-baiting; in contrast, the people who tell me gadgetbahn is necessary to avoid union agreements insist on never being public about anything.

The rub is that it’s not possible to solve the coordination problem of public transit agencies without some sort of public process. Adding gadgetbahn to the mix creates the same result as the XKCD strip about 14 competing standards. The more the people building it insist that they’re disruptive synergistic innovators inventing the future with skin in the game, the less likely they are to build something that’s likely to be backward-compatible with anything or cohere to form a usable network.

Nor is it possible to assimilate good industry practices by cloak and dagger politics. The universe of industry practices is vast and the universe of good practices isn’t much smaller. The only way forward is via an open academic or quasi-academic process of publication, open data, peer review, and replication. A single consultancy is unlikely to have all the answers, although with enough study it could disseminate considerable knowledge.

There needs to be widespread public understanding that the United States is behind and needs to import reforms to improve its transportation network. This can happen in parallel with a process that weakens unions or for that matter with a process that strengthens them, but in practice the subterfuge of managers looking for union-busting opportunities makes it difficult to attack all cost drivers at once. Whatever happens with conventional left-right politics, there is no room for people who reduce the entirety or even the majority of America’s transit cost problem to labor.