Category: High-Speed Rail

On Penn Station South

There’s an article in the New York Times by its architecture critic Michael Kimmelman, making a forceful case for the Gateway Project’s necessity. Like nearly all transit activists in New York, I think new Hudson tunnels are the top infrastructure priority for regional rail; like nearly all transit activists, I groan at Amtrak’s proposed budget, now up to $16 billion (but unlike most, I think that it should not be built unless costs can be brought down – I’d peg their worth at $5 billion normally, or somewhat more in a crunch). I would like to explain one specific piece of scope in Amtrak’s plan that can be eliminated, and that in fact provides very little transportation value: Penn Station South.

Like all proposals for new Hudson tunnels, Gateway is not just a simple two-track tunnel between New Jersey and Penn Station. No: the feuding users of Penn Station all think it needs more tracks. The rejected ARC proposal had a six-track multilevel cavern, and Gateway has Penn Station South, a proposal to demolish an entire block south of Penn Station and build seven additional platform tracks. The cost of just the real estate acquisition for Penn South: $769 million to $1.3 billion, at today’s prices. Trains using the preexisting tunnels would have to go to the preexisting Penn Station tracks, which I will call Penn Classic; trains using the new tunnels could go to either Penn Classic or Penn South, but the junction is planned to be flat. For illustration, see PDF-p. 12 of a press release of the late Senator Lautenberg, and a clearer unofficial picture on

As a result of this proposed track arrangement, train services would initially suffer from the capacity limitations of flat junctions. Like Penn Station’s tracks 1-4, Penn South would be terminal tracks. This means that the only service possibilities are as follows:

1. Schedule all through-trains, such as Amtrak trains, through the preexisting tunnels.

2. Do not schedule any westbound trains from Penn South or any eastbound trains entering the preexisting Penn Station tracks: for example, no westbound trains from Penn South in the morning peak, and no eastbound trains entering Penn Classic in the afternoon peak.

3. Schedule around at-grade conflicts between opposing traffic.

Option #2 is impossible: Penn South has 7 tracks. If trains can enter but not leave in the morning, there will be room for 7 trains entering in the morning, a far cry from the several dozens expected. Option #1 is the better remaining option, but is ruled out, since Amtrak wants to use the new tunnels for its own trains. This leaves option #3, which restricts capacity, and complicates operations. Thanks to Amtrak’s imperialism, taking over regional rail projects for its own ends, Penn South has negative transportation value relative to just building new tunnels to Penn Classic’s tracks 1-4 (the transportation value relative to doing nothing is of course positive).

I emphasize that the negative transportation value of Penn South comes entirely from Amtrak’s involvement. The same infrastructure, used by passenger rail agencies that were more interested in providing high-quality public transportation than in turf wars, would have positive transportation value. However, as I explained to Kimmelman, this positive transportation value is low, and does not justify even the cost of real estate acquisition, let alone that of digging the station.

Briefly, as can be seen in the diagrams, the interlocking between the two new tunnel tracks and Penn’s eleven terminal tracks – tracks 1-4 of Penn Classic, and all of Penn South – is exceedingly complicated, which would limit approach speed, and not provide much flexibility relative to the number of tracks provided. This is to a large extent unavoidable when two approach tracks become eleven station tracks, but it does lead to diminishing returns from extra tracks. This is one of the reasons it’s easier if trains branch: it’s easier to turn 12 trains per hour on two tracks than to turn 24 on four (although both are done in Tokyo – indeed, the Chuo Line still turns 27 tph on two tracks).

Avoiding large crunches like this at urban terminals a benefit of through-running. This is hard to realize initially unless the new tunnel is what I call ARC-North. It’s still possible to through-run trains, pairing the new tunnels with the southern pair of East River Tunnels and the old tunnels with the northern pair, but it requires a lot of diverging moves at interlockings, limiting speed. Penn Station plans should be built with a long-term goal of simple moves at interlockings, to (slightly) increase speed and capacity and reduce maintenance needs.

However, it’s still possible to square the circle by requiring trains to turn fast on tracks 1-5 of Penn Station (track 5 splits to a terminating end and an end that runs through east of New York). Tokyo would be able to turn a full complement of 24 trains per hour on these tracks. Most other cities would not. However, as somewhat of a limiting European case, the RER A turns a peak train every 10 minutes on single track at Le Vésinet-Le Pecq, the next-to-last station on the Saint-Germain-en-Laye branch; Le Pecq has two through-tracks (also hosting a train every 10 minutes) and one terminal track. See map and schedule. This does not scale to 24 tph on four tracks; somewhat tellingly, those trains do not continue to the terminus, which is a three-track station, implying turning 12 tph on three tracks is problematic. The RER E turns 16 tph at the peak at Haussmann-Saint Lazare, a four-track city terminus, pending under-construction extension of the line to the west, which would make it a through-station.

If we accept 16 tph as the capacity of new Hudson tunnels without new Penn Station tracks, then the question should be what the most cost-effective way to raise future capacity is. An extra 9 tph, the equivalent of the difference between 16 tph and the 25 tph that the current tunnel runs and that Amtrak projects for Gateway, is within the capabilities of signaling improvements and better schedule discipline. Again looking to Paris for limiting cases, the combined RER B+D tunnel between Gare du Nord and Châtelet-Les Halles runs 32 tph, without any stations in the tunnel (the RER B and D use separate platforms), while the moving block signaling-equipped RER A runs 30 tph on its central segment, with stations (as do the S-Bahn systems of Berlin and Munich). The RER E was planned around a capacity of 18 tph, but only 16 tph are run today. 18+32 = 50 = 25+25. France is not Japan, with its famous punctuality: French trains are routinely late, and as far as I remember, the RER B has on-time performance of about 90% based on a 5-minute standard, worse than that of Metro-North in its better months.

More importantly, dropping Penn South from the Gateway plan saves so much money that it could all go to through-running, via a new tunnel from tracks 1-5 to Grand Central. This is about 2 km of tunnel, without any stations; in a normal city this would cost $500 million, the difficulty of building in Midtown canceling out with the lack of stations, and even at New York construction costs, keeping the tab to $2 billion should be doable. The 7 extension is $2.1 billion, but includes a station; an additional proposed infill station at 10th Avenue, dropped from the plan, would’ve $450 million, giving us $1.6 billion for about 1.6 revenue route-km, rising to 2.3 km including tail tracks – less than a billion dollars per kilometer.

At $2 billion, the premium over $1 billion of impossible-to-cut real estate acquisition costs is down to $1 billion. It’s unlikely the construction cost of Penn South could be just $1 billion, without general reductions in city construction costs, which would enable the Penn-Grand Central link to be cheaper as well. Each Second Avenue Subway station is about a billion dollars, and those stations, while somewhat deeper than Penn Station, are both much shorter and narrower than a full city block. The result is that building a Penn-Grand Central link is bound to be cheaper than building Penn South, while also providing equivalent capacity and service to a wider variety of destinations via through-running.

One difficulty is staging the tunnel-boring machines for such a connection: building a launch box involves large fixed costs, especially in such a crowded place as Midtown. One of the reasons Second Avenue Subway and the 7 extension are the world’s most expensive subway project per kilometer is that they’re so short, so those fixed costs are spread across less route length. The best way to mitigate this problem is to build the link simultaneously with the new Hudson tunnels. The staging would be done on Penn’s tracks 1-4, whose platforms would be temporarily stripped; the construction disruption involved in the tunnels is likely to require shutting those tracks down anyway. Depending on the geology, it may even be possible to use the same tunnel-boring machine from New Jersey all the way to Grand Central.

This doesn’t save as much money – the Penn-Grand Central link is extra scope, with its own costs and risks. However, unlike Penn South, it is useful to train riders. Penn South allows terminating trains at Penn Station more comfortably, without having to hit the limit of large-city terminal capacity; the Penn-Grand Central link creates this capacity, but also lets riders from New Jersey go to Grand Central and points north (such as Harlem, but also such more distant commercial centers as Stamford), and riders from Metro-North territory go to Penn Station and points west (such as Downtown Newark).

Normally, I advocate unbundling infrastructure projects, because of the tendency to lump too many things together into a single signature plan, which then turns into political football, a sure recipe for cost overruns. However, when projects logically lead to one another, then bundling is the correct choice. For example, building an entire subway line, with a single tunnel-boring machine and a single launchbox, usually costs less than building it in small stages, as is the case with Second Avenue Subway. New Hudson tunnels naturally lead into a new tunnel east of Penn Station, regardless of where this tunnel goes; and once a tunnel is built, its natural terminus is Grand Central.

Putting Rail Lines in Highway Medians

North Americans are in love with trains that go in highway medians. A large fraction of urban rail construction since World War Two, both light rail and full metro, has used highway medians as cheap at-grade rights-of-way to extend train service, often deep into the suburbs. Some proposed longer-range lines are supposed to go in medians as well: Florida had reserved space in the I-4 median for Orlando-Tampa high-speed rail, and Xpress West planned to go from Las Vegas to the outskirts of the Los Angeles area in the I-15 median. The Texas Central Railway, a private group backed by JR Central planning high-speed rail between Dallas and Houston, is considering several alignments, but markets the route as following I-45 (no mention of median) in some public discussions. In nearly all cases, both urban and intercity, it borders on incompetent to design rail lines in highway medians; intercity lines frequently follow highways on one side, but even that tends to be overrated in American discussions in my experience.

Urban Rail

For urban rail, the reason to use highways is that, in most of North America, they’re everywhere, and they’re usually equipped with generous medians and shoulders, allowing relatively cheap placement of rail tracks. Of note, this is generally not the cheapest option: construction on extant (often disused) rail rights-of-way tends to be cheaper. However, in many cases, a rail right-of-way is unavailable, hosts heavy freight traffic, has been permanently turned into a trail, or has commuter trains without integration into the rest of the urban transit network. Examples include the Dan Ryan half of the Red Line and both halves of the Blue Line in Chicago, the Orange and Silver Lines in Washington, the outer ends of BART, the Spadina line in Toronto, and several light rail lines. Often they run on one side of the road, but more frequently they’re in the median, which was often reserved for it when the road was built (as in Chicago and Calgary).

The problem is that nobody wants to live, work, or hang out next to a busy grade-separated road. Living or working a kilometer or two away, with easy access by car, is great for the driver, but within close walking distance, there is just too much noise, pollution, and blight, and the pedestrian environment is unwelcoming. The transit-oriented development in Metrotown and Arlington could not have happened next to a freeway. Christof Spieler frames this as a decision of spending more money on routing trains near where people live versus staying on the easy rights-of-way. But this isn’t quite right: the Expo Line in Vancouver was assembled out of an interurban right-of-way and a city center tunnel, both out of service; the line’s high ridership comes from subsequent development next to Metrotown and other stations.

Other times, the routing comes from a deliberate decision to integrate the trains with cars, with large park-and-rides at the ends. This is common on newer light rail systems in the US (though not Canada, as Calgary prefers integration with connecting buses) and in the Washington and San Francisco suburbs. This makes things even worse, by extending the radius within which the environment is built for cars rather than for people, and by encouraging the same park-and-ride construction elsewhere, along abandoned railroads and greenfield routes, where the preexisting environment is not car-oriented.

I do not want to categorically say that cities should never build urban rail alongside highways. But I cannot think of a single example in which this was done right. Calgary is a marginal case: it did build light rail along highways, and had some success with transit-oriented development, but those highways are arterials rather than freeways, and this makes the pedestrian environment somewhat better.

The situation is somewhat different for suburban rail, but usually the scale of suburban rail is such that there’s not much new construction, only reappropriation of old lines. These lines are long and the environments low-density, making it hard justify the costs of new lines in most cases. Where new suburban rail is built, for examples the Grand Paris Express, and various airport connectors, it is typically in environments with such expected traffic density that the rules for urban rail apply, and we tend to see more underground construction or usage of extant rights-of-way.

Intercity Rail

The reasons favoring highway alignments intercity rail in the US are somewhat different. Tellingly, HSR in Europe is frequently twinned with motorways. It is not about integration with cars, since those alignments are rarely if ever meant to have major stops in their middle. Instead, it’s about picking a pre-impacted alignment, where there are fewer property takings and fewer NIMBYs. This logic is sound, but I often see Americans take it to extremes when discussing HSR.

The first problem is that roads are almost never as straight as HSR needs to be. The design standards I have seen after briefly Googling give the radius of a motorway capable of about 120 km/h as, at a minimum, 500-700 meters. With these curves, trains, too, are capable of achieving about 120 km/h – less at 500 meters without tilting, more at 700 meters with tilting. The most recent high-speed lines are built with a minimum curve radius of 7 km; about the absolute minimum that can be done, with design compromises and tilting trains, is 4 km. This implies that the trains have to deviate from the motorway alignment whenever it curves. In flat regions the road curves are much gentler than the minimum, but still too sharp for full-speed running. Both Florida HSR and Xpress West noted that the trains would have to slow down whenever the Interstate curved, because the need to run in the median would prevent them from curving gently enough to maintain full speed.

Of note, the European examples of HSR running in motorway alignments have it running alongside the roads, not in the medians. I invite the reader to spend a few minutes following French LGVs on Google Maps and seeing this. This is because there invariably have to be small deviations from the road, which in a rural area are trivial when one runs next to the road but require viaducts when one runs between the road’s two carriages.

There may also be an issue regarding reusing the Interstates. To transit supporters who view HSR as a replacement for freeways, this has an element of poetic justice, or just plain practical reuse of infrastructure they think is obsolete. I chanced upon this while looking up Interstate design standards, but I’ve seen similar proposals elsewhere, as well as dissimilar proposals making use of interstate terminology, as a reminder of past national greatness. It comes from the same place as proposals to reuse auto factories to produce rolling stock: there’s a romantic aspect in addition to or instead of an economic one.

But the most fundamental problem is that the contentious experiences of the freeway revolts and modern-day NIMBYism have soured Americans on any process that involves brazen takings. What I mean by brazen is that carving a new right-of-way, especially through a populated area, looks obvious on a map. In contrast, sticking to a preexisting right-of-way and incrementally widening it or straightening curves is less controversial, even when it involves eminent domain as well, and opposition remains much more local, based on the specific properties being taken, rather than stated in general principles. I am not completely sure why this is so; my suspicion is that widening and straightening are more easily justified as things that must be done, whereas a new right-of-way looks gratuitous.

In either way, Americans have convinced themselves that NIMBYs are a major obstacle to infrastructure construction. While zoning is a notoriously NIMBY-prone process, infrastructure often isn’t. In the English common law world, expropriations are if anything easier than in France, where farmers are especially powerful, or Japan, where rioters threatened to block the construction of Narita Airport. NIMBYs are good at getting their names out in the media, but when it comes to blocking construction, they are relatively powerless; California HSR is facing NIMBYs in the Central Valley, many of whom are conservative and politically opposed to the project regardless of local impact, but so far they have not managed to delay construction.

However, NIMBYs are a convenient bogeyman for public projects, as their motives are openly selfish. They give charismatic, authoritarian leaders the opportunity to portray their infrastructure projects as battles between the common good and backward-looking parochial interests. As I’ve noted multiple times before, New York’s livable streets community (which is similar politically to the set of HSR supporters in the US) tends to overblow the importance of NIMBYs to the point of seeing NIMBYs even when the concerns have nothing to do with NIMBYism: see, for example, the reaction to the opposition of two Harlem politicians to a plan to speed up only the whitest bus route through the neighborhood.

Coordinated Planning and High-Speed Rail

High-speed rail and rapid transit both change economic geography, in that they compress distances along the lines built, emphasizing connections along the lines at the expense of ones perpendicular to them. I’ve written about this before, giving the example of the division of Uptown Manhattan into East and West Sides. In contrast to the similar implications for economic geography, we see different political treatment of transportation planning: rapid transit is usually planned centrally within a city, together with lower-capacity perpendicular forms of public transit, but there is less centralized planning of high-speed rail and connecting legacy lines.

It’s against this background that I’ve read two recent posts on Itinerant Urbanist, one advocating Northeast-wide intercity rail planning, and one expressing skepticism of plans to run trains from New York to Pittsfield along the Housatonic Railroad, whose southern end hosts the Danbury Branch. In the second post, Sandy shows how, even today, it is faster to get from New York to Pittsfield via Albany, along existing Amtrak routes, than it could be via the curvy Housatonic. The trains from New York to Albany are not HSR, but are some of the fastest in the US outside the Northeast Corridor, and that’s enough to obviate the need for some adjacent lines. But we can extend this analysis further, looking at potential HSR routes and identifying the effect on other regional and intercity lines mentioned in Sandy’s first post.

For our main example, consider Providence-Worcester. There is a direct line, the Providence and Worcester mainline, which hosts no passenger trains. I have previously called for running passenger service on the southern 25 km of the line, from Providence to Woonsocket, and integrating the schedules with MBTA trains to Boston and future HSR; in 2009, the Providence Foundation made a similar proposal, finding that it was possible to slot a reasonable frequency of in-state regional trains between the Providence and Worcester freight trains. Superficially, one might think that trains should not turn at Woonsocket, but go all the way to Worcester, a distance of 69 km, providing a key crosstown link in a New England-wide rail network.

The problem is that the presence of HSR makes the line completely useless for end-to-end traffic. HSR averages between 180 and 260 km/h, whereas regional trains average between 50 and 90, with a few trains overlapping with intercity rail going up to 120. This makes it worthwhile to go two to three times as long as the most direct route, if this can be done on high-speed lines.

It’s 70 km from Providence to Boston; from Boston to Worcester, it’s 71 along the present Worcester Line, while an HSR line following I-90 would be about 65, serving Worcester at an outlying station at the intersection with Route 122 (and the Providence and Worcester line), 6 km outside the legacy station. My attempt to work out a schedule for Providence-Boston gives about 20.5 minutes for nonstop HSR; Boston-Worcester is probably similar, giving 41 minutes plus a short transfer time. (Trains with intermediate stops would stop at Back Bay, and if the transfer can happen there, then it saves about 3 minutes total.) Let’s say the transfers at Boston are not optimized, and the total travel time is 50 minutes.

It is not easy to achieve this travel time on the legacy Providence and Worcester line: 69 km in 50 minutes is 83 km/h, and 63 km (from Providence to I-90 and Route 122) is 76. The latter speed is very ambitious, and the former even more so. While there are regional lines in New England that could approach 100, this is not one of them. The line hosts some freight traffic, so it requires additional sidings if passenger trains go at intercity rail speeds and not at regional rail speeds, which are similar to freight speeds. There is a significant commuter market at the Providence end, requiring more stops in Providence and its inner suburbs: the end-to-end travel time in the schedule I constructed for Providence-Woonsocket is 26 minutes, an average speed of 59 km/h. To get to I-90 in 50 minutes, trains would need to average 94 km/h north of Woonsocket; achieving this makes it almost impossible to stop anywhere in Massachusetts except Worcester, which defeats the purpose of the line. Worcester-Woonsocket is not important enough a travel market to reopen a passenger rail line for. For the same reason, there is no hope of achieving sufficient speed by including a mix of local and express trains: there’s not enough demand to support multiple service patterns.

The Providence-Worcester example is somewhat unfair in that it’s unlikely such a line could be activated without interstate cooperation in intercity rail planning. The same cooperation that could restore service on the Providence and Worcester line would first push for faster intercity trains on the Northeast Corridor, which would be the first step in obviating this direct line. I bring this up because it’s a very clean example of how the presence of HSR allows for circuitous routings on some city pairs, and how this should be reflected in rail planning. There are less clean examples, pitting a unified system with HSR as a trunk and branches feeding the trunk against potential in-state projects and priorities:

1. Unless HSR fares are designed to discourage this, the fastest way to get to New York from suburbs far out along the New Haven Line, and to a lesser extent the Northeast Corridor Line in New Jersey, would be to take commuter rail to New Haven or Trenton and then backtrack on HSR. This changes the optimal service patterns, away from express trains to New York and toward local trains in the outer service area, and this in turn influences planning for capacity improvement. For example, fitting HSR and commuter trains on existing tracks in New Jersey probably requires giving up express service south of Rahway, but at the outer end of the line, around Princeton Junction, going out to Trenton and backtracking on HSR would make this not as onerous as commuters may initially think. On the level of station design, the presence of backtracking means that stations may need to be reconfigured to have more access points from northbound to southbound platforms, to make transfers easier.

2. New Jersey Transit has plans from last decade to reactivate passenger rail service along the West Trenton Line. The presence of HSR makes West Trenton a less useful commuter rail station, to either Philadelphia or New York. In Philadelphia it remains useful if one wants to go to destinations on the Reading side of SEPTA, such as Temple University, or even Market East, but in New York, the nearest job center to West Trenton is Newark, which is on the Northeast Corridor. This means that better transit service from West Trenton to Trenton becomes a greater priority than direct rail service from West Trenton to New York.

3. There is a secondary rail line from New London to Norwich, passing next to Mohegan Sun. It is not very useful if intercity trains remain as they are, but the presence of HSR makes it a good feeder, and also allows trains to beat express buses for trips from New York to the casino.

4. It is vanishingly unlikely Pennsylvania will try to build in-state rail service to Erie. However, if it does, Erie-Pittsburgh service would be similar to Providence-Worcester service, with Cleveland fulfilling the same function as Boston in New England.

Difficult Transit

Many people have heard that certain regions are well-suited for these projects, for example the Northeast Corridor is unusually good for HSR because it links four major cities and several medium-size ones on a single line. By implication, there has to be a flip side, i.e. regions that are poorly-suited for HSR and cities that are poorly-suited for new rapid transit. If there weren’t – if every region were like the Northeast Corridor – then the ridership models would just have higher first-order estimates. Several proposals I’ve seen in comments and on my blogroll in the last few days are in areas where the urban geography makes it harder to justify such projects. These and a few others are the examples I will use in this post.

As usual, there’s a caveat that difficult does not equal bad. Some of these ideas are worth pursuing, but have more challenges that their easier counterparts do not, and if those challenges are solved, then they can perform well. One of the biggest success stories of modern rail investment, the TGV, is in an urban geography that’s not particularly conducive to rail: France’s secondary cities surround Paris in all directions (although Lyon and Marseille are collinear with Paris), the stub-end layout of stations in Paris and many other cities forces awkward branching, Lyon needed a business district to be built from scratch around Part-Dieu. France made this work, and it’s possible some of the projects on this list can be made to work in similar vein.

High-Speed Rail in Sweden

Project: greenfield HSR lines connecting Stockholm with Sweden’s major secondary cities, Gothenburg and Malmö.

The problem: Stockholm, Gothenburg, and Malmö do not lie on a straight line. The three cities are quite small by the standards of more populated countries: Stockholm has a bit more than 2 million people, Gothenburg has a bit less than a million, Malmö has 700,000. A line connecting just two of them, or even a Y-shaped line, is unlikely to get enough ridership to justify the construction costs of full HSR. There are no large intermediate cities: the largest, Linköping, has about 100,000 people. As noted above, French urban geography is not great for HSR, either, but at least the LGV Sud-Est could serve both Lyon and Marseille, and France’s greater population ensures that its secondary cities are large enough to generate enough traffic to fill an HSR line.

As a silver lining, Malmö is adjacent to Copenhagen, and the difficult part, bridging the Øresund, has already been done. While international lines tend to underperform, the tight cultural and economic connections between the Scandinavian countries make it likely that international projects within Scandinavia would be exceptions to the rule. Copenhagen would add another 2 million people at the end of the line. However, even that is unlikely to generate enough ridership to pay for 500-odd kilometers of greenfield HSR (plus a connection to Gothenburg).

Because of its poor urban geography for conventional HSR, Sweden has investigated cheaper solutions, allowing higher speeds on legacy track or on greenfield tracks built to lower standards. As a result, there is research into the possibility of high-speed tilting trains, running faster than the 250 km/h Pendolino. This research is likely to be useful in the UK and US, where the urban geography is better-suited for HSR but fully greenfield construction is obstructed by suburban development near the rights-of-way and by high construction costs, but the original context was faster speeds within Sweden.

High-Speed Rail in the Pacific Northwest

Project: greenfield HSR connecting Portland, Seattle, and Vancouver. This is not officially proposed anywhere that I know; current plans focus on incremental improvements to the Amtrak Cascades. However, every American HSR fantasy map I’ve seen (including the ones I’ve drawn) includes this link, since at least superficially based on city populations it would succeed.

The problem: getting out of the major cities involves a slog on curvy legacy track in areas where it’s hard to straighten the right-of-way. Heading north of Seattle, the route goes along the water, in terrain that is too hilly for an easy inland cutoff all the way to Everett, 50 km north. Getting out of Vancouver is also hard, because of suburban development in Surrey, and becomes even harder if one wants the Vancouver station to be Waterfront rather than Amtrak’s current stop, the less centrally located Pacific Central. The Northeast Corridor is said to have slowdowns near the major stations, leading to proposals to bypass them with new tunnels, but at no point are there 50 nearly-continuous km of low curve radii; the New Haven Line does not look as curvy, while the Shore Line farther east is easy to bypass on I-95.

The Seattle-Portland segment is much easier: the route heading south of Seattle is not constrained, and north of Portland it is possible to run alongside I-5. However, the most important intermediate cities, Tacoma and Olympia, can only be served with exurban stations, since getting into their centers would require the mainline to detour on curvy alignments.

Through-Run Commuter Rail in Chicago

Project: there are many proposals by transit activists to construct new infrastructure to enable through-running on Metra, analogous to Crossrail, SEPTA Regional Rail, the Paris RER, and multiple S-Bahns. Details differ, but other than the lines through Union Station, through-running generally means connecting Metra Electric to some of the lines feeding into Union Station from the north or the Union Pacific lines; UP-North is especially notable for serving dense neighborhoods and not having any freight traffic.

The problem: the layout of the lines entering the Chicago central business district makes it hard to build a coherent network. What I mean by coherent is that commuter lines can make multiple CBD stops to serve different CBDs, or different parts of the same CBD: in New York, a Penn Station-Grand Central connection would let trains serve both the West Side and the East Side. Look at the map proposed by Sandy Johnston, in the second link above: there is no station on the Near North Side, there is no connection from the West Loop stations to the Loop, and effectively lines are still going to be split between lines bound for the West Loop and lines bound for the Loop in the through-run system.

None of this is the fault of any of the people drawing these maps. To serve both the West Loop and the Loop, a line would have to go east-west in the vicinity of Union Station, where there is no legacy line pointing in the right direction. The options boil down to a long greenfield east-west subway, and an awkward transition to the preexisting east-west lines, BNSF (which is too far south) and UP-West (which is too far north), which to add another complication carry heavy freight traffic.

A system prioritizing north-south connections runs into different dilemmas, concerning the tradeoff between service to the Near North Side and easier connections to the rest of the North Side Metra lines. A north-south line connecting UP-North to Metra Electric through the Near North Side would be beautiful, and miss all other Metra lines and most L lines. Sandy’s proposal has Metra Electric swerving west to meet UP-North just north of its terminus at Ogilvie Transportation Center, meeting all L lines and potentially the North Side Metra lines but missing the job centers in the West Loop and Near North Side.

Rail to LaGuardia

Project: construct some rail extension to LaGuardia Airport. Which rail extension varies based on the proposal. The most mainstream proposal, in the sense that it was supported by Giuliani until it was torpedoed by neighborhood opposition, would have extended the Astoria Line east to airport grounds. More recent proposals from various activists have included not just the Astoria Line extension, but also a Northeast Corridor spur, an AirTrain from the Astoria Line, an AirTrain from Jamaica with JFK connections, a subway shuttle under Junction, and a subway running from the airport to 125th Street along the route of the M60 bus.

The problem: all of the above ideas face the same pair of problems. At the airport end, the airport competes with other urban destinations, rather than complementing them by lying on the same straight line with them. An extension from the west, such as the Astoria Line extension, needs to choose between serving the airport and serving the Astoria Boulevard corridor, which has high residential density and no nearby subway service; Astoria Boulevard itself is so wide that as with Queens Boulevard, an elevated line in its middle would be an improvement. Farther east, there is nothing that a LaGuardia extension could be continued to, because of Flushing Bay. An extension across the bay going to Flushing or College Point could be useful, but an extension of the 7 to College Point would be even more useful and avoid underwater tunneling. The bay, and more generally the Long Island Sound, dooms any proposal for a loop returning to the mainline, in the manner of Zurich Airport, while a spur would again compete for capacity with more important lines. Compare this with LAX, which, going along the Harbor Subdivision, is collinear with Inglewood, the Slauson corridor, and Union Station, and would have an easy connection to El Segundo.

At the other end, the question with every airport extension is, what does it connect the airport to? The answer for LaGuardia has to be the Upper East Side, where as I remember most riders originate; but there is no good way of connecting to the Upper East Side, which has no east-west subway line, and shouldn’t, as there are perhaps a hundred kilometers of higher-priority tunnels in the region. A connection to 125th Street is ruled out by the fact that Second Avenue Subway has an even better connection to 125th. The Astoria Line serves the Midtown hotel cluster well, and has a connection to the Lexington trains to the Upper East Side, but I doubt that it can beat a taxi across the bridge in non-rush-hour traffic.

Providence East Side Tunnel

Project: restore rail service through the East Side Rail Tunnel, with a new connection to Downcity at the western end and connections to new or restored rail lines in and beyond East Providence. In Jef Nickerson’s version, the trains are light rail and drop to the surface at the Downcity end. In mine, they continue elevated through Downcity, with a new station replacing Providence Station for both commuter and intercity rail. All versions include a stop at Thayer Street for Brown University service, should one be constructable at reasonable cost.

The problem: there’s no real need for local or regional service from the east along the tunnel (intercity service could be sped up by about half a minute to a minute by avoiding curves in Pawtucket). Light rail service would run into the problem of incredibly spread-out suburbanization east of Providence. Commuter rail would run into separate problems: the legacy lines go along the water in East Providence and don’t serve the town itself well; beyond East Providence, the line going north serves the same suburbs as the existing Providence Line minus Pawtucket, while the line going south would need extensive and costly restoration work to get to Fall River, and only passes through small and low-density intermediate points.

Cutting off Providence Station to move the city’s main station to the south is useful, but the only rail from Providence to Pawtucket and Woonsocket goes due north of Downcity and would be left out of this system. Shoehorning it to the same station that leads to the East Side Tunnel would produce every adverse impact of viaducts on cities: heavy visual impact coming from elevated-over-elevated grade separation, squeal coming from low curve radii, takings of condo buildings near the existing Providence Station.

California HSR Should Not Have Been Funded This Way

Last month, California made a budget deal for the formula that would be used to distribute its cap-and-trade revenues. The state’s cap-and-trade bill does not deed the money to the general budget but to a separate account, to be distributed based on a variety of goals including subsidies to programs that reduce greenhouse gas emissions. The recent deal is to give most of the money to transportation (including transit-oriented development): this year the budget gives $600 out of $850 million to transportation (see PDF-p. 6 here), of which $250 million will go to high-speed rail, and according to an informational hearing the long-term deal gives 80% of revenues to transportation, including 15% to high-speed rail. Transit bloggers who are not in the process of moving across oceans covered the issue last month as the deal was made: Streetsblog wrote about the plan, Robert Cruickshank wrote multiple times in support of the decision, and Bruce McFarling explained how HSR’s projected emissions reductions should entitle it to a share of the cap-and-trade proceeds.

In reality, although it’s a good thing that California HSR is getting funded, it’s a bad way of funding it, betraying both environmental incompetence and political mistrust. The basic problem is that the HSR project is not going to reduce emissions enough to justify 15% of the pot, nor is transportation such a big share of California’s emissions inventory to deserve 80%: it accounts for only 37% of statewide emissions. Electricity, and related sources of emissions such as building heating and industrial emissions, get far less than their share of emissions.

Bruce’s post runs the numbers on HSR, notes that the projections are currently $250-400 in construction costs per ton of CO2 reduction, and proposes that if cap-and-trade results in a carbon cost of $75 per ton then this justifies using the revenues for 20-35% of the cost of HSR. The projected revenue from cap-and-trade is a range whose top end is $5 billion statewide, corresponding to about $11 per metric ton; at this level, assuming HSR saves $250/t-CO2 means it should get 4.4% of its funding from emissions reduction, or (at the current cost of $53 billion in constant dollars) about $2.3 billion over the lifetime of the program. If the revenue is indeed $5 billion a year, this spending level is projected to be reached in 3 years.

For some evidence of what the state is really doing, consider how the deal comments on each share of the funding. The informational hearing details the investment strategy as follows:

25% for a permanent source of funding for transit operations, distributed based on greenhouse gas criteria.
20% for affordable housing and miscellaneous urban planning goals (including TOD), of which at least half must be for affordable housing (including TOD, again); the money is to be distributed based on “competitive GHG performance.”
15% low-carbon transportation, based on both long-term clean air and GHG goals.
13% energy, including electricity and building efficiency.
7% natural resources, waste diversion, and water projects.
15% HSR.
5% “new or existing” intercity rail, based on GHG criteria.

Note that internally to four categories, comprising 65% of the total funds, the hearing mentions greenhouse gas criteria. In three out of the four, comprising half of the funds, the hearing implies that the decision of how to distribute the funds will be based on competitive grants according to which project reduces emissions the most.

The key point here is that the state has effectively said what the best way is to ensure the spending side of cap-and-trade will reduce emissions optimally: projects will compete for scarce funding based on greenhouse gas criteria. Once it has made the political decision to distribute funds by a formula that disproportionately goes to transportation, it has no objection to using greenhouse gas criteria internally to each category. The problem is that the transportation projects in general and HSR in particular would never make it out of a grant process based on such criteria if they were not shielded from competition with non-transportation priorities.

There are two legitimate ways to distribute funds coming out of an externality tax, which is what cap-and-trade really is. One is to let the tax side do the work of reducing impact, and put the money into the general budget. This is common practice for most developed countries’ fuel taxes (though not the US’s). In this approach, HSR would compete with all of the state’s other budget priorities. If the state wanted to reduce other taxes against the cap-and-trade funds rather than raise spending, it could. If it wanted to spend the money on unrelated things, such as education, it could as well. There already is a more or less open and democratic budget process for this.

The other way is to reduce all political discretion, and distribute the funds based entirely on greenhouse gas criteria, without breaking the money into categories. The state seems to prefer this way, judging by its use of this process within each category. With other externality taxes there is another option, of giving the money directly to victims of the externality, e.g. spending cigarette taxes on lung cancer treatment; however, the bulk of damage caused by climate change is to developing countries, and spending cap-and-trade revenues on targeted aid to vulnerable developing countries is politically unacceptable.

The state’s hybrid approach is effectively a slush fund. High-level politicians, including Governor Jerry Brown, want to build a visible legacy, and HSR is far more visible than making household appliances consume less electricity. Emissions reductions are secondary to this concern. They’ll be happy to make their legacy a project that reduces greenhouse gas emissions, but they have no quantitative preference for projects that reduce emissions more than others. On the contrary, when they pull strings, they might even make decisions that make these projects less environmentally beneficial: the decision to connect Los Angeles to Bakersfield via Palmdale rather than directly has no technical merit, and judging by LA County’s support appears to be motivated by concerns for development in the Palmdale area. As the incremental cost of going through Palmdale is about $5 billion, nearly 10% of the HSR cost, the result is that the state is going to spend a substantial amount of cap-and-trade money on spurring more development in the High Desert exurbs.

Needless to say, when the cap-and-trade bill was passed, it did not state or even imply that the state could use the money to spur more development in the exurbs. The bill did not adopt a GHG-only approach, but listed several additional goals, none of which included transportation. Chapter 1, Part 2, paragraph h states,

It is the intent of the Legislature that the State Air Resources Board design emissions reduction measures to meet the state wide emissions limits for greenhouse gases established pursuant to this division in a manner that minimizes costs and maximizes benefits for California’s economy, improves and modernizes California’s energy infrastructure and maintains electric system reliability, maximizes additional environmental and economic co-benefits for California, and complements the state’s efforts to improve air quality.

There is an explicit mention of air quality, and explicit mentions of energy and electricity, which are only getting 13% of the funding despite accounting for 54% of emissions. Elsewhere the list of legislative intents includes vague terms such as technological leadership, but the only explicit mention of transportation in the bill is in paragraph c, which says that historically California provided leadership on several environmental issues, including emissions limits on cars as well as energy efficiency and renewable energy.

However, the cap-and-trade bill is older than the current administration, and the political priorities have changed. Since a regular budget process giving HSR the money it needs would run into opposition from competing priorities, it’s best to raid a new source of revenue, one without legislative inertia or established supporters directing the money to more useful purposes.

Hence, a slush fund.

Empire High-Speed Rail

At the beginning of the month, New York State released its draft environmental impact statement for high-speed rail from New York to the Upstate cities. The costs of HSR as proposed by the state are excessive, and as a result the state has eliminated the high-speed option. It is only considering medium-speed options – the fastest is 125 mph, for the cost of full-fat high-speed rail; it sandbagged the full-speed options. Consider the following passage, from the main document, section 3.2.2:

The dedicated right-of-way of the very high speed (VHS) alternatives would result in significant travel time savings (5:17 and 4:23 respectively for 160 mph MAS and 220 mph MAS), and commensurately higher estimated ridership (4.06 and 5.12 million respectively for 160 mph MAS and 220 mph MAS).

The length of New York-Buffalo is about 690 km. At 4:23, it is an average speed of 157 km/h. To put things in perspective, the Hikari express trains in the 1960s achieved an average of 162 km/h (515 km in 3:10) in 1965, with a maximum speed of 210 km/h.

In section 3.3.5, the 125 mph alternative, which involves greenfield dedicated track from Albany to Buffalo, is said to have an average speed of 77 mph, or 124 km/h. Considering that British express trains on the legacy East Coast and West Coast Main Lines restricted to the same top speed average about 130-140 km/h, this is unimpressive.

Likewise, the cost estimates seem too high. The cost proposed for 125 mph is $14.71 billion. That’s on existing track south of Albany with minor improvements; as per exhibits 3-19 and 3-21, 83% of the cost is said to be Albany-Buffalo, a distance of 380 km on new track plus 76 on existing track. This makes sense for a full-speed, 350 km/h line. But the cost of the full-speed 220 mph option is $39 billion, around $55 million per km from New York to Buffalo in an area with a topography that justifies at most half that.

The study also sandbags the higher-speed options, from 125 mph up, by overplaying the importance of skipped small cities. A greenfield line cannot reasonably serve Schenectady, Amsterdam, and Rome. It could serve Utica, but with some takings because the sharp curve from the tracks at the downtown station to the I-90 right-of-way to the west. Lack of service to Utica would be a drawback, but the study for some reason thinks that those four stations would need their own dedicated intercity line to New York, using a connection to Metro-North, which is said on PDF-p. 37 to have capacity problems on the Hudson Line (the Hudson Line runs 12 trains per hour at the peak today, and is four-tracked). I am told that people drive all the way from Watertown to Syracuse to take Amtrak; none of the skipped four stations is that far from Albany or Syracuse. If a regional train is needed, it can connect at Albany.

The problem is that the alignments studied are uninspiring. I don’t just mean it as a synonym for bad. I mean they avoid locations that look difficult at first glance but are actually reasonably easy. CSX bypasses Albany already; it is not a problem to run high-speed trains at low speed on the existing line between Rensselaer and a spot west of Albany where the line could transition to the Thruway, and yet exhibit 3-20 shows a passenger rail bypass of Albany.

For the full-speed option, I do not know how much tunneling and bridging the state thinks is necessary for its west-of-Hudson I-87 alignment from New York to Albany, but there’s an alignment east of the Hudson with only about 7 km of tunnel, all through the Hudson Highlands. Briefly, such a line would go east of the built-up area in Dutchess County and points north, with a possible station at the eastern edge of the Poughkeepsie urban area and another near Rhinebeck, closer to the city and to the bridge to Kingston than the present Rhinecliff station. In Putnam and northern Westchester Counties, it would utilize the fact that the ridge lines go northeast to southwest to swing to the southwest, to hook up to the Hudson Line slightly north of Croton-Harmon. With a curve radius of 4 km, and a maximum grade of 3.5%, only two tunnels are needed, one under Peekskill of about 2 km and one under the crest in Putnam County of about 5 km. Some additional viaducts are needed through the valleys in the Hudson Highlands, but from Dutchess County north the line would be almost entirely at-grade.

There is generally a tunnel vision in American high-speed rail documents like this, consisting of any of the following features:

– Excessive avoidance of greenfield alignments, even in relatively flat areas. The flip side is excessive usage of freeway rights-of-way. The Syracuse-Rochester segment is actually greenfield in the study, which is good, but there is no thought given to greenfield New York-Albany alignments, which are frankly much easier east of the Hudson than west of the Hudson.

– Questionable assumptions about the abilities of existing track in urban areas to have higher capacity, which often leads to excessive multi-tracking (as in California); there is never any effort to construct an integrated timetable to limit the construction of new tracks.

– No rail-on-rail grade separations. The study talks about Spuyten Duyvil capacity problems, which are very real if traffic grows, but says nothing about the possibility of grade-separating the junction from the Empire Connection to the Metro-North mainline to Grand Central.

– With the exception of California, which erred in the other direction, uninspiring speeds. It’s actually hard to construct a 350 km/h line that only averages 157; actual high-speed lines around the world in the 270+ range average about 180 or higher.

It’s not surprising New York is sandbagging HSR. A year and a half ago, the Cuomo administration killed an HSR study on the grounds that in a recession, the state can’t afford to build such an expensive project. Given how long it takes from the initial study to the beginning of construction, the argument is so transparently wrong that it raises the question of what the real motivation was. But whatever the real reason was, the state is not interested in HSR, and wrote a lengthy environmental impact study to justify its disinterest.

Metro-North-Everything Compatibility

The Regional Plan Association has a new study warning that Metro-North’s infrastructure is falling apart, and demands $3.6 billion in immediate spending on state of good repair. In general, my line on deferred maintenance is “you mean the agency deferred maintenance all those years and didn’t tell us?”. But in this case, despite the language, most of the proposed spending is improvements, namely rehabilitation or replacement of old movable bridges with low speed limits, rather than ongoing maintenance folded into long-term capital spending.

$2.8 billion of the proposed program is for replacing five bridges: Pelham Bay, Cos Cob (over the Mianus), Walk (over the Norwalk River), Saga (over the Saugatuck), and Devon (over the Housatonic). I believe all five should be replaced in the medium term, but the cost proposed is much higher than it should be. $560 million per bridge is quite high, and out of line with Amtrak found on PDF-pp. 29 and 56 of the Northeast Corridor Master Plan. Amtrak cites the cost of replacing the Pelham Bay Bridge alone at $100 million, and the cost of both replacing it and modifying curves on the Hell Gate Line at $500 million. It cites the cost of replacing both the Saga and Walk Bridges at $600 million.

Now, the RPA lists Saga as the easiest bridge to replace since it’s two two-track bridges, so work can be done one bridge at a time with less disruption to ongoing service, but conversely Pelham Bay is also quite cheap according to Amtrak.

But there’s a more serious problem, which is the avoidance of talking about service plans for commuter and intercity rail. If there is serious effort at adding Metro-North service to Penn Station or at raising intercity rail speeds, then the worst speed and capacity restrictions should get priority, and the infrastructure construction should be based on what promotes the desired service plans. It is very expensive and probably cost-ineffective to six-track everything from New Rochelle to Stamford, to allow three speed regimes: local, express, and intercity. I have argued before that it’s better to leave it at four tracks and bypass bad curves, around Port Chester, and make this the six-track segment. This is of course independent of maintenance issues, but suggests which bridge replacements are necessary to support these bypasses (Cos Cob) and which aren’t (the rest are less critical, especially Walk, which intercity trains should bypass on a straighter I-95 segment).

Likewise, there’s a capacity crunch west of Stamford but not one east of Stamford, and this again suggests Cos Cob as the most important priority. Finally, the slowest segment of the NEC away from immediate station areas is the western corner of Connecticut, from the state line to Stamford; Stamford’s curves are mild, while those heading out of Port Chester all the way across the Mianus are quite bad, and straightening the segment would also require straightening the bridge, which can be done easily if it’s replaced. Despite all this, the RPA and Amtrak are saying Cos Cob needs rehabilitation and not replacement, which misses opportunities to both improve reliability and speed up a slow segment.

Moreover, there is no mention of grade-separating Shell Interlocking, just south of New Rochelle. While not a state of good repair issue even in theory, the interlocking’s tight curves impose a limit of either 30 or 45 mph (so, 50-70 km/h), depending on source, in an area that could otherwise support 200 km/h or more. It is very difficult to straighten New Rochelle to sufficient curve radius for that, but 150 requires only minor takings. This may be necessary, independent of speed issues, to raise capacity enough to allow Metro-North service to both Grand Central and Penn Station. It’s possible to schedule trains through the flat junction, but this imposes an additional constraint on the schedule, on top of track-sharing with Amtrak and, in the East River Tunnels, the LIRR.

Sometimes, Half a Line is as Good as No Line

The perfect is not the enemy of the good when it comes to rail projects. The half-done job is. In a trivial sense it’s obvious that half a tunnel across a mountain is useless. But even partial lines that have some uses are sometimes so much less useful than the full line, that the economic benefits of completing the half line to the full system are actually greater than those of building the first half. In many cases, even partial lines that are very good on their own have relatively easy extensions with very good economics.

This is primarily true for intercity rail, since costs are roughly proportional to route-km whereas benefits (e.g. high-speed rail operating profits) are proportional to passenger-km: once a first-phase rail line is in place, any future phase such that passengers will use the first phase for much of their travel will generate a large amount of passenger traffic relative to infrastructure construction. Probably the simplest example of this is extending California HSR to Sacramento: once a Los Angeles-San Francisco system is in place, especially if the route goes over Altamont Pass, extending to Sacramento requires only about 100 km of additional construction (180 if the LA-SF route is via the currently planned Pacheco Pass route), in flat land, but people would be taking the train from Sacramento to Los Angeles, a distance of about 600 km. Thus, despite generating much lower ridership than San Francisco, Sacramento is a highly beneficial extension of California HSR, once the LA-SF first phase is in place.

There are several more places in North America that are like this. When I tried applying a very primitive ridership model to American city pairs, what I found is that next to the Northeast Corridor, the highest-performing lines are extensions of the Northeast Corridor to the south. This is for the same reason as with Sacramento: once Boston-New York-Washington is in place, an extension to Richmond would generate 540 passenger-km of New York-Richmond travel on just 180 route-km of Washington-Richmond HSR, and thence extensions to Raleigh and Norfolk would be similarly high-performing, and so on. Some of those extensions would add about 40 million passenger-km per route-km of new construction, compared with about 28 million on the Northeast Corridor alone; in other words, assuming constant per-km cost, the rate of return on some of the extensions is higher than on the Northeast Corridor trunk. Similarly, although international HSR links are overrated, once New York-Buffalo is in place, an extension into Toronto becomes high-performing (with about 30 million passenger-km per new route-km after a fudge factor accounting for the underperformance of international city pairs), which is especially useful given that New York-Buffalo’s projected traffic based on said primitive model is marginal.

In those cases, the picture is bright, in that the first phase is strong on its own, and then future phases become natural extensions, which can be funded on the heels of the first phase’s success.Unfortunately, in many cases the situation is different, and the first phase is really a half-built line that isn’t much better than nothing, at least on the proposed merits. For example, High Speed 2’s rising costs are causing the cost-benefit analysis to head well into marginal territory: as per PDF-page 15 of a Parliamentary primer, the benefit-cost ratio of the first phase, London-Birmingham, is now down to 1.4, while this of the full system as proposed by the Cameron administration, going to Manchester and Leeds, is 1.8. Although 1.4 > 1, common practice in Europe is to build only projects with benefit-cost ratios higher than 1.2 or 1.3, because of the risk of further cost escalations (although the stated cost includes a generous contingency factor). The environmental benefits are likewise lopsided in favor of full construction, according to pro-HSR group Greengauge 21: three quarters of the benefits come from the second phase. This is because few people fly from London to Birmingham or Manchester already, since the existing medium-speed trains are fast enough at these distances to outcompete low-cost flights; however, there’s a large volume of people flying from London to Glasgow, and it is expected to take the full opening of HS2 to get enough of those fliers to switch to make a significant difference.

In this case, HS2’s first phase is better than nothing, and the problem stems from extremely high costs: without contingency, London-Birmingham, a distance of about 180 km, is projected to be about $23 billion after PPP conversion, which at nearly $130 million per km is worse than California HSR, which has to tunnel under tall mountain ranges. With contingency, it is $175 million per km, not much less than the projected cost of the majority-underground Chuo Shinkansen maglev. If the costs were brought down to reasonable levels, the first phase alone would be highly beneficial, as can only be expected given the size of London and the secondary cities of the West Coast Main Line.

In some other proposed cases, even the benefits are marginal. Worse, sometimes attempts to cut costs lead to steeper cuts in benefits. The example that motivated this post is a recent story of a proposal for HSR in Colorado, which is not planned to serve the built-up area of Denver at all, but instead stop at the airport. An airport stop without a downtown stop is unacceptable anywhere, especially given Denver’s airport’s large distance from downtown (30 km, vs. 15 km in Shanghai, where most HSR trains stop at the domestic airport and only a few stop downtown at Shanghai Station). It is especially unacceptable given that Denver is to be connected to cities that are within easy driving or medium-speed rail distance: Fort Collins is 100 km north of Denver, Colorado Springs is 110 km south, and Pueblo, which is only proposed as part of a larger second phase together with a Rocky Mountain crossing, is 180 km south. At the distances of Fort Collins and Colorado Springs, the egress time would eat all time advantage of HSR over driving; at the distance of Pueblo, it would eat most of the time advantage. Saving money is nice, but not when it makes the entire project useless except to the occasional Fort Collins- or Colorado Springs-based flier.

One can go further and ask why even build HSR at such short distances. On the Northeast Corridor, full-service HSR is a great investment, because of the combination of extremely thick city pairs at the 360 km mark (New York-Washington and New York-Boston) and one reasonably thick pair at the 720 km mark (Boston-Washington), which is too far for medium-speed rail to compete with air. Philadelphia’s presence boosts the case for HSR – it conveniently provides a source of reverse-peak traffic away from New York and Washington, adds long-distance travelers to Boston, and adds short-distance high-speed travelers to New York – but by itself it’s not worth it to build HSR at the distance of New York-Philadelphia. If Boston and Washington weren’t there, then incremental upgrades with a top speed of 200 km/h or maybe 250 km/h would be best, and higher speeds would just waste money on more expensive trains and create noise pollution and higher energy consumption.

The same analysis is true of faster-than-HSR travel modes. The other motivation for this post, in addition to Colorado’s proposal, is Japan’s attempt to export maglev to the US, proposing the Northeast Corridor as the route to run maglev on, with Baltimore-Washington as the first segment, which Japan proposed to build for free, as a loss leader. Nobody needs maglev from Baltimore to Washington: the egress time is going to ensure the benefits of maglev speeds over HSR speeds are small, and even the benefits of HSR speeds over fast commuter rail speeds are limited. The Chuo Shinkansen is only planned to be about 440 km long, but it’s a capacity boost on a line that already has HSR with extremely high ridership, and not just a speed upgrade. Elsewhere, Japan builds conventional HSR rather than maglev, even for inter-island travel, where people fly today since the Shinkansen takes 5+ hours and flying takes an hour.

Part of my distaste for Hyperloop essentially comes from the same problem: it tries to compete with HSR at a distance where HSR is appropriate and faster trains are not. All of the technical problems of Hyperloop – thermal expansion, claustrophobic vehicles, extreme levels of lateral acceleration – are solvable, at the cost of more money. The technology is feasible; it’s Musk’s order-of-magnitude-too-low cost estimate that I object to. The problem is that at LA-SF distance, access and egress time and security will eat the entire time advantage over conventional HSR, in similar vein to the problem with siting Denver’s HSR station at the airport. Conventional HSR still involves regular trains that can run on electrified legacy lines, so it’s cheap to go the first and last miles within the Bay Area and the LA Basin; maglev doesn’t have this ability and neither do vactrains. Thus there will always be the problem with the first and last mile, which can be solved only by spending even more money – even in the case of the Chuo Shinkansen, JR Central decided that Shinagawa, just outside Central Tokyo, is good enough, and there’s no need to spend further money to get trains into Tokyo Station. But the access, egress, and security time penalties are constant, whereas the time advantage over slower modes of transportation grows with distance.

So by all means, let’s think about maglev from New York to Chicago and Miami and from Los Angeles to Seattle, where HSR is too slow to compete with air travel; let’s think about a vactrain at transcontinental scales, were open-air maglev is too slow. There’s a reason this year’s April Fool’s post emphasized that the vactrain system should be intercontinental and globally connected. I don’t think maglev in the US or a vactrain anywhere pans out in the next few decades, but at least at this greater scale they wouldn’t be crowding out a technology that can succeed, i.e. conventional HSR at the scale of the Northeast Corridor or California.

Sometimes, starting small means failing. A strong first phase with stronger second phases, such as LA-SF or Boston-NY-DC, is likely to become a success and motivate the political system to spend additional money, partly from first-phase profits, on extensions. A weak first phase that needs additional phases to pan out won’t lead to the same extensions. When a white elephant project opens, nobody listens to critics who say it should’ve been built bigger, even in the uncommon cases when those critics are right. Colorado HSR as proposed is going to get faltering ridership, not enough to justify the cost, and cause widespread disaffection even with potentially strong rail projects in Colorado. The same is true of any faster-than-HSR project that tries to replace HSR instead of capitalize on its strength in serving much longer-distance city pairs. If Musk succeeds in causing the median Californian to turn away from HSR and build Hyperloop instead, then first Hyperloop will turn out to cost ten or more times as much as Musk predicted (for which people won’t blame Musk but the government – Musk’s sycophants will tsk-tsk from the sideline and say that if only he had been in charge), and second the ridership won’t cover the costs, leading people to decide that any linear transportation corridor is bad and the government should stick to highways and airports.

Is Low-Cost Intercity Rail Possible?

Update: see corrected Shinkansen staffing numbers below

The last few decades have seen the growth of airlines and bus operators that reduce operating costs using a variety of lean-production ideas, chiefly using the equipment for more hours per day to earn more revenue with the same fixed costs. This hasn’t generally happened for rail, even in the presence of competition between operators. There is one low-cost option, on the TGV network, which like Ryanair and easyJey cuts costs not only by leaner production but also by reducing passenger comfort and convenience. I contend that an intermediate solution should be investigated: lean like Southwest and JetBlue, but without the extra fees, which are lower on those two airlines than on legacy US airlines.

First, the preexisting fares. In Japan, JR Central charges an average of $0.228 per passenger-km on the Shinkansen, JR East charges $0.245, JR West charges $0.208. In Japan nearly all intercity service is Shinkansen; averaging all JR East rail other than Tokyo-area commuter rail, even commuter rail around Sendai and Niigata, drops the average marginally, to $0.217. European intercity rail fares per passenger-km are lower: €0.104 on RENFE (PDF-p. 27), €0.108 on DB, and €0.112 on SNCF. All of those companies are profitable and do not receive subsidies for intercity rail, with the exception of RENFE, which loses small amounts of money (-0.8% profit margin). This is far lower than Northeast Corridor fare, which, as of the most recent monthly report, averages $0.534 per passenger-km on the Acela and $0.292 on the Regional.

Now, we can try penciling what operating costs should be. The most marginal costs, which grow linearly with the addition of new service, look a lot like those of low-cost private bus operators: crew, cleaners, energy, rolling stock acquisition, rolling stock maintenance. I am specifically handwaving the peak factor – frequency is assumed to be constant, to establish the operating cost of the base rather than that of the peak. I am going to assume 1,120 seats per train, all coach, about the same as a 16-car Shinkansen with 2+2 standard-class seating, or 70 per car. First class should be thought of as an equivalent of buying extra seats – fares should scale with the amount of space per passenger, and at any rate most cars are coach. Occupancy rate will be taken to be 57%, for a round 40 passengers per car; this is well within the range of HSR occupancy.

The cost turns out to be quite low – this is similar to the analysis in Reason & Rail from 2 years ago, except for now I’m leaving out infrastructure costs, which in that analysis are the dominant term, and so excluding them leads to very low costs. It is about three cents per passenger-km in operating and maintenance costs. This is of course not what HSR currently costs, but should be thought of as a lower limit or as the marginal cost of increasing base service.

A crew on a high-speed train is a train driver and a conductor. A 16-car Shinkansen train appears to have one conductor judging by the single conductor’s compartment has three conductors (see Andrew in Ezo’s comment below); the TGV has much more staffing, with the low-cost TGV having four. US salaries are high because the railroads have good unions: according to the Manhattan Institute’s applet for public employees’ salaries, on the LIRR, the average train driver makes $103,000 a year (search for “engineer”) and on Metro-North $115,000 (search for “locomotive engineer”). This is higher than on the Shinkansen. A conductor makes $98,000 on the LIRR and $105,000 on Metro-North. Figure $240,000 per year for a two-person crew $440,000 per year for a four-person crew.

We need to convert this to operating hours. On the LIRR and Metro-North, there are about 4,500 revenue car-hours per driver-year, which translates to about 600 revenue train-hours. At an average speed of 200 km/h, HSR would cost $2 $3.67 per train-km, or $0.003125 $0.0057 per passenger-km. But Metro-North and the LIRR are inefficient due to a prominent peak making smooth scheduling difficult; HSR can schedule a simple shift with a roundtrip of about 6-7 hours plus rest time, and if each employee does this 5 days a week minus holidays this is 1,200 revenue hours. This halves the cost. Conversely, going to 4 conductors, with a five-person crew paid a total of $540,000 per year, raises the cost to $0.007 per passenger-km, still low.

Electricity consumption can be calculated from first principles based on acceleration characteristics, or based on real-life HSR consumption levels. For the latter, a UIC paper claims 73 Wh/passenger-km on PDF-p. 17; this appears to be based on an assumption (see PDF-p. 33) of 70% occupancy but a train that is smaller (397 seats for 8 cars) and heavier (425 t vs. 365 t for an 8-car Shinkansen). Correcting for these gives 54 Wh/p-km. When I try to derive this from first principles assuming Northeast Corridor characteristics but with substantial segments upgraded to 360 km/h, I get about 50 Wh/p-km; this doesn’t include losses between catenary and wheel or regenerative braking, which mostly cancel each other out with losses being a little bigger. Rounding up to 56 Wh/p-km and using a transportation-sector electricity cost of $0.125 per kWh, we get $0.007 in electricity cost per passenger-km.

Cleaning should be done as fast as possible, with large crews working to turn trains around in the minimum amount of time based on safety margins and schedule recovery. JR East cleans Shinkansen trains in 12 minutes of Tokyo turnaround time minus 5 minutes for letting passengers disembark; the team size is 1 cleaner per standard-class car and 2-3 per green car, for a total of 22. This does not mean we can pencil in just 7 minutes of cleaning, since this doesn’t take into account the cleaning crew’s time waiting for a train to arrive, or downtime in case trains don’t arrive exactly one turnaround time apart. For a 4 tph operation, 15 minutes are fine, but for a 6 tph one, 10 may not be enough, requiring going up to 20. This is once per train run, so once per 720 km. With a team size of 24, that’s 24 person-hours per 720 train-km, or 32 in the 6 tph version.

Again using Manhattan Institute data, cleaners make $50,000 a year; it’s possible wages will have to go up to attract people who can consistently clean a car on the tight schedules posited, but there’s no base of comparison of companies having both Japanese standards for scheduling and American union scales. Say $30 per hour on the job (including downtime and waiting for a train, but not scheduled breaks). In the 6 tph version, this costs $0.002 per passenger-km.

RENFE’s above-linked executive summary includes a breakdown of employees by category (regular, support, and managerial) and gender on PDF-p. 46, whence we can obtain that for each operations employee there are 0.2 managers and 0.07 support employees. For capital projects, the California HSR estimates add 20% for overhead, management, and design, not including contingency, and the Penn Design estimate adds 18% (PDF-p. 247). This should be taken as the marginal cost of extra managers to oversee extra employees hired to provide additional service. In total, this is roughly $0.019 per passenger-km assuming higher crew staffing, and $0.013 $0.0175 assuming lower staffing.

Rolling stock is more expensive, and should spend as much time earning revenue as feasible based on established maintenance protocols. A large share of the operating costs of high-speed rail comes from the rolling stock: 20% on Madrid-Barcelona according to a RENFE presentation to California HSR whose official source is now a dead link, and, from eyeballing, perhaps 25% according to PDF-p. 8 of a UIC presentation about track access charges. The low-cost TGV doubles train utilization to about a million kilometers a year. This should be routine on Northeast Corridor operations: two round-trips per train, about 14-15 hours per day including turnaround time, 1 million train-km a year. Procurement of new N700s costs about $3 million per car, and Japanese depreciation schedules are over 20 years. Other trains capable of more than 250 km/h cost $4 million per car in China; with mid-life refurbishment of non-trivial cost, they can last up to 40. With 4% interest cost, depreciation and interest are about $280,000 per car-year either way, and if a car travels a million km with 40 people on average, that’s another $0.007 per passenger-km, a substantial sum so far.

Rolling stock maintenance is also relatively expensive. California HSR’s 2012 business plan has a list of costs around the world on PDF-p. 136. JR Central’s rolling stock maintenance is $7.20 per trainset-mile, which with our assumptions translates to $0.007 per passenger-km. European rolling stock maintenance costs are $4.16 per trainset-mile, which appears to be for an 8-car train, so scaling up by a factor of two gives $0.008 per passenger-km. Note that the maintenance of the rolling stock costs as much as the depreciation and interest on its acquisition.

In reality, maintenance depends on both time and distance, so increasing rolling stock utilization leads to lower costs per train-km. Since with those assumptions, the rolling stock costs about as much as the actual operations, this is a major cost cutter, though not a game changer given other costs. Note that the RENFE presentation slide also includes a large array of fixed costs and infrastructure (maintenance, which is very cheap at about $100,000 per route-km per year, and depreciation and interest on construction, which aren’t so cheap) as well as managerial overheads, hence the 20%; the UIC presentation includes some overheads as well. However, those fixed costs are more affordable if they’re spread across more service. A line built to have a 6 tph capacity has the same infrastructure cost at any frequency up to 6 tph.

So far, adding up all the operating and rolling stock costs totals to about $0.03 $0.033 per passenger-km. This means $11 $12 direct operating costs between New York and Washington or New York and Boston. It’s also a quarter what the Europeans charge for HSR tickets, and an eighth of what the Japanese charge. Despite this, the California HSR numbers are similar, so this analysis passes a sanity check. Again referring to the business plan’s PDF-p. 136, the table claims operating costs per trainset-mile that, after scaling from 8- to 16-car trains, are $0.04 per passenger-km. They exclude rolling stock acquisition, but include maintenance; but the assumptions in the Operations and Maintenance Peer Review are worse than in this post, with worse train utilization (turnaround times are assumed to be 40 minutes on PDF-p. 21) and more staff on board each train (an engineer, a conductor, an assistant conductor, a ticket collector, and a special services employee per 8-car unit, for a total of ten employees for 16 cars).

Still, I have no expectation that anyone can charge $11 $12 profitably for HSR service between New York and Washington. However, I strongly believe costs could be brought substantially below current rates. I believe the reason SNCF has only begun to do that and other operators not at all comes from two places.

First, infrastructure charges, a third of the cost of both the TGV and the Madrid-Barcelona AVE, are not just about paying off infrastructure costs (both Spain and France are low-construction cost countries for HSR). They transfer profits from the HSR operator to the monopoly infrastructure owner: track access charges were specifically increased in France ahead of the opening of the European rail market to competition, ensuring HSR surplus would go to state-owned infrastructure owner RFF rather than to foreign companies or the customers.

And second, unlike in the US, in Europe low-cost airlines are associated with terrible service: low seat pitch, hidden fees, rigid policies toward carry-on baggage, rigid policies toward missed flights, worse customer satisfaction, secondary airports located far from the cities they purportedly serve. The US has some of this in Spirit Airlines and Allegiant Airways, but it also has Southwest, JetBlue, and Virgin Atlantic, which have high customer satisfaction, flexible tickets, secondary airports located close to city centers (such as Dallas Love Field), and seat pitch equal to or better than that of the legacy airlines, which have degraded service. Europeans hate low-cost flying; Americans hate flying. The result is that Ryanair tars any attempt to lower costs in Europe by associating lean production and high equipment utilization with no-frills third-class service. This might make managers more wary of adopting some of the more positive aspects of low-cost carriers. Japan has no major low-cost carriers, so although it does not have the stigma, it doesn’t have the domestic experience, either.

I do not believe it’s possible for a train to charge $11 $12 one-way between New York and Washington and stay in business. There needs to be some profit margin, plus paying back infrastructure construction costs. However, I do believe it’s possible to charge closer to that than to present European HSR fares for the same distance (about $45), let alone present Amtrak fares. California HSR is actually pointing the way, but has such high construction costs that paying off even part of construction represents a major rise in ticket fares. The Northeast can and should do better.

Loopy Ideas Are Fine, If You’re an Entrepreneur

There is a belief within American media that a successful person can succeed at anything. He (and it’s invariably he) is omnicompetent, and people who question him and laugh at his outlandish ideas will invariably fail and end up working for him. If he cares about something, it’s important; if he says something can be done, it can. The people who are already doing the same thing are peons and their opinions are to be discounted, since they are biased and he never is. He doesn’t need to provide references or evidence – even supposedly scientific science fiction falls into this trope, in which the hero gets ideas from his gut, is always right, and never needs to do experiments.

Thus we get Hyperloop, a loopy intercity rail transit idea proposed by Tesla Motors’ Elon Musk, an entrepreneur who hopes to make a living some day building cars. And thus a fair amount of the media coverage is analysis-free summary of what Tesla already said: see stenography by ABC, Forbes, the Washington Post’s Wonkblog, and even BusinessWeek (which added that critics deal with “limited information”). Some media channels are more nuanced, sometimes even critical; the Wall Street Journal deserves especial credit, but Wonkblog also has a second, mildly critical post. But none has pressed Musk or Tesla about the inconsistencies in his proposal, which far exceed the obvious questions about the proposed $6 billion price tag (compare $53 billion in today’s money for California HSR). For better prior criticism, see James Sinclair’s post and Clem Tillier’s comment on California HSR Blog.

My specific problems are that Hyperloop a) made up the cost projections, b) has awful passenger comfort, c) has very little capacity, and d) lies about energy consumption of conventional HSR. All of these come from Musk’s complex in which he must reinvent everything and ignore prior work done in the field; these also raise doubts about the systems safety that he claims is impeccable.

In principle, Hyperloop is supposed to get people from Los Angeles to San Francisco in half an hour, running in a tube with near-vacuum at speeds topping at 1,220 km/h. In practice, both the costs and the running times are full of magic asterisks. The LA end is really Sylmar, at the edge of the LA Basin; with additional access time and security checks, this is no faster than conventional HSR doing the trip in 2:40. There is a crossing of the San Francisco Bay, but there’s no mention of the high cost of bridging over or tunneling under the Bay – we’re supposed to take it on faith the unit cost is the same as along the I-5 corridor in the Central Valley.

There is no systematic attempt at figuring out standard practices for cost, or earthquake safety (about which the report is full of FUD about the risks of a “ground-based system”). There are no references for anything; they’re beneath the entrepreneur’s dignity. It’s fine if Musk thinks he can build certain structures for lower cost than is normal, or achieve better safety, but he should at least mention how. Instead, we get “it is expected” and “targeted” language. On Wikipedia, it would get hammered with “citation needed” and “avoid weasel words.”

The worst is the cost of the civil infrastructure, the dominant term in any major transportation project’s cost. Hundreds of years of incrementally-built expertise in bridge building is brushed aside with the following passage:

The pods and linear motors are relatively minor expenses compared to the tube itself – several hundred million dollars at most, compared with several billion dollars for the tube. Even several billion is a low number when compared with several tens of billion proposed for the track of the California rail project.

The key advantages of a tube vs. a railway track are that it can be built above the ground on pylons and it can be built in prefabricated sections that are dropped in place and joined with an orbital seam welder. By building it on pylons, you can almost entirely avoid the need to buy land by following alongside the mostly very straight California Interstate 5 highway, with only minor deviations when the highway makes a sharp turn.

In reality, an all-elevated system is a bug rather than a feature. Central Valley land is cheap; pylons are expensive, as can be readily seen by the costs of elevated highways and trains all over the world. The unit costs for viaducts on California HSR, without overhead and management fees, are already several times as high as Musk’s cost: as per PDF-page 15 of the cost overrun breakdown, unit costs for viaducts range from $50 million to $80 million per mile. Overheads and contingencies convert per-mile cost almost perfectly to per-km costs. And yet Musk thinks he can build more than 500 km of viaduct for $2.5 billion, as per PDF-page 28 of his proposal: a tenth the unit cost. The unrealistically low tunnel unit cost is at least excused on PDF-page 31 on the grounds that the tunnel diameter is low (this can also be done with trains if they’re as narrow as Hyperloop, whose capsule seating is 2-abreast rather than 4- or 5-abreast as on HSR; see below on capacity). The low viaduct unit cost is not.

This alone suggests that the real cost of constructing civil infrastructure for Hyperloop is ten times as high as advertised, to say nothing of the Bay crossing. So it’s the same cost as standard HSR. It’s supposedly faster, but since it doesn’t go all the way to Downtown Los Angeles it doesn’t actually provide faster door-to-door trip times.

Nor is the system more comfortable for the passenger. Levitating systems can get away with higher cant than conventional rail because they sway less: Transrapid’s lateral acceleration in the horizontal plane is about 3.6 m/s^2 in Shanghai, and the company claims 4.37 m/s^2 is possible. On standard-gauge rail, the conversion rate is approximately 150 mm of total equivalent cant per 1 m/s^2. HSR cant tops at 180-200 mm, and cant deficiency tops at 180 mm for Talgos and 270-300 mm for medium-speed Pendolinos, so about 2.5 m/s^2 at high speed; this was shown safe by simulation in Martin Lindahl’s thesis, which is also a good source for track construction standards.

But Hyperloop goes one step further and proposes a lateral acceleration of 4.9 m/s^2: 0.5 g. This is after canting, according to the standards proposed:

The Hyperloop will be capable of traveling between Los Angeles and San Francisco in approximately 35 minutes. This requirement tends to size other portions of the system. Given the performance specification of the Hyperloop, a route has been devised to satisfy this design requirement. The Hyperloop route should be based on several considerations, including:

  1. Maintaining the tube as closely as possible to existing rights of way (e.g., following the I-5).
  2. Limiting the maximum capsule speed to 760 mph (1,220 kph) for aerodynamic considerations.
  3. Limiting accelerations on the passengers to 0.5g.
  4. Optimizing locations of the linear motor tube sections driving the capsules.
  5. Local geographical constraints, including location of urban areas, mountain ranges, reservoirs, national parks, roads, railroads, airports, etc. The route must respect existing structures.

For aerodynamic efficiency, the velocity of a capsule in the Hyperloop is

  • 300 mph (480 kph) where local geography necessitates a tube bend radii < 1.0 mile (1.6 km)
  • 760 mph (1,220 kph) where local geography allows a tube bend > 3.0 miles (4.8 km) or where local geography permits a straight tube.

These bend radii have been calculated so that the passenger does not experience inertial accelerations that exceed 0.5 g. This is deemed the maximum inertial acceleration that can be comfortably sustained by humans for short periods. To further reduce the inertial acceleration experienced by passengers, the capsule and/or tube will incorporate a mechanism that will allow a degree of ‘banking’.

0.5 g, or 4.9 m/s^2, is extreme. Non-tilting trains do not accelerate laterally at more than 1.2 m/s^2 in the plane of the track (i.e. after accounting for cant), and at high speed they have lower lateral acceleration, about 0.67 m/s^2 with limiting cases of about 0.8 for some tilting trains relative to the plane of the train floor. For example, the Tokaido Shinkansen has 200 mm of cant and maximum speed of 255 km/h on non-tilting trains on 2,500-meter curves, for 100 mm of cant deficiency, or 0.67 m/s^2.

The proposed relationship between curve radius and speed in the Hyperloop standards is for a lateral acceleration much greater than 4.9 m/s^2 in the horizontal plane: 480 km/h at 1,600 meters is 11.1 m/s^2. This only drops to 5 m/s^2 after perfectly canting the track, converting the downward 9.8 m/s^2 gravity and the sideways acceleration into a single 14.8 m/s^2 acceleration vector downward in the plane of the capsule floor, or 5 m/s^2 more than passengers are used to. This is worse than sideways acceleration: track standards for vertical acceleration are tighter than for horizontal acceleration, about 0.5-0.67 m/s^2, one tenth to one seventh what Musk wants to subject his passengers to. It’s not transportation; it’s a barf ride.

Even 4.9 m/s^2 in the horizontal plane is too much. With perfect canting, it combines with gravity to accelerate passengers downward by 11 m/s^2, 1.2 m/s^2 more than the usual, twice as high as the usual standards. Motion sickness is still to be fully expected in such a case. Transrapid’s 4.37 m/s^2, which adds 0.93 m/s^2 in the vertical component with perfect canting, is the limit of what’s possible.

Speaking of vertical acceleration, this gets no comment at all in the Hyperloop proposal. At 1,220 km/h, it is very hard to climb grades, which would require very tall viaducts and deep tunnels under mountains. Climbing grades is easy, but vertical acceleration is such that the vertical curve radius has to be very large. A lateral acceleration of 0.67 m/s^2 would impose a minimum vertical curve radius of 170 km, versus 15 km at 360 km/h HSR speed. Changing the grade from flat to 2% would take 3.4 km, and changing back would take the same, so for climbing small hills, the effective average grade is very low (it takes 6.8 km to climb 68 meters).

Nor does jerk get any treatment. Reversing a curve takes several seconds at the cant and cant deficiency of conventional HSR (about 3 seconds by Swedish standards, more by German ones); reversing a curve with the extreme canting levels of Hyperloop would take much longer. Maintaining comfort at high total equivalent cant requires tight control of the third derivative as well as the second one; see a tilting train thesis for references.

The barf ride that is as expensive as California HSR and takes as long door-to-door is also very low-capacity. The capsules are inexplicably very short, with 28 passengers per capsule. The proposed headway is 30 seconds, for 3,360 passengers per direction per hour. A freeway lane can do better: about 2,000 vehicles, with an average intercity car occupancy of 2. HSR can do 12,000 passengers per direction per hour: 12 trains per hour is possible, and each train can easily fit 1,000 people (the Tokaido Shinkansen tops at 14 tph and 1,323 passengers per train).

But even 30 seconds appears well beyond the limit of emergency braking. It’s common in gadgetbahn to propose extremely tight headways, presuming computerized control allowing vehicles to behave as if they’re connected by a rod. Personal rapid transit proponents argue the same. In reality, such systems have been a subject of research for train control for quite a while now, with no positive results so far. Safety today still means safe stopping distances. If vehicles brake at a constant rate, the safe headway is half the total deceleration time; if a vehicle brakes from 1,220 km/h to zero in 60 seconds, the average acceleration is more than 5 m/s^2, twice the current regulatory safety limit for passengers with seat belts.

Most of this could be chalked to the feeling of some entrepreneurs that they must reinvent everything. The indifference to civil engineering costs, passenger comfort issues, and signal safety could all be chalked to this. So could the FUD about earthquake safety of HSR on PDF-page 5.

However, one thing could not: the chart on PDF-page 9 showing that only the Hyperloop is energy-efficient. The chart has a train consuming nearly 900 megajoules per person for an LA-San Francisco trip, about as much as a car or a plane; this is about 1,300 kJ per passenger-km. This may be true of Amtrak’s diesel locomotives; but energy consumption for HSR in Spain is on average 73 Watt-hour (263 kJ) per passenger-km (see PDF-page 17 on a UIC paper on the subject of HSR carbon emissions), one fifth as much as Tesla claims. Tesla either engages in fraud or is channeling dodgy research about the electricity consumption of high-speed trains.

Indeed, a train with a thousand seats, 20 MW of power drawn, 60% seat occupancy, and a speed of 360 km/h can only ever expend 333 kJ per passenger-km while accelerating, and much less while cruising (acceleration at lower speed requires more energy per unit of distance, but cruising at lower speed expends only a fraction of the energy of full-power acceleration). Tesla’s train energy consumption numbers do not pass a sanity check, which suggests either reckless disregard for the research or fraud. I wouldn’t put either past Musk: the lack of references is consistent with the former, and the fact that Musk’s current primary endeavor is a car company is consistent with the latter.

There is no redeeming feature of Hyperloop. Small things can possibly be fixed; the cost problems, the locations of the stations, and the passenger comfort issues given cost constraints can’t. Industry insiders with ties to other speculative proposals meant to replace conventional rail, such as maglev, are in fact skeptical of Hyperloop’s promises of perfect safety.

It’s possible to discover something new, but people who do almost always realize the context of the discovery. If Musk really found a way to build viaducts for $5 million per kilometer, this is a huge thing for civil engineering in general and he should announce this in the most general context of urban transportation, rather than the niche of intercity transportation. If Musk has experiments showing that it’s possible to have sharper turns or faster deceleration than claimed by Transrapid, then he’s made a major discovery in aviation and should announce it as such. That he thinks it just applies to his project suggests he doesn’t really have any real improvement.

In math, one common sanity check on a result is, “does it prove too much?” If my ten-page paper proves a result that implies a famous open problem, then either my paper is wrong or I’ve proved the famous open problem, and it’s up to me to take extra care to make sure I did not miss anything. Most people in this situation do this extra step and then realize that they were subtly wrong. If a famous question could be solved in ten pages, it probably wouldn’t still be open. The same is even true in undergrad-level proof classes: if your homework answer proves things that are too strong, you’ve almost certainly made a mistake.

Musk’s real sin is not the elementary mistakes; it’s this lack of context. The lack of references comes from the same place, and so does the utter indifference to the unrealistically low costs. This turns it from a wrong idea that still has interesting contributions to make to a hackneyed proposal that should be dismissed and forgotten as soon as possible.

I write this not to help bury Musk; I’m not nearly famous enough to even hit a nail in his coffin. I write this to point out that, in the US, people will treat any crank seriously if he has enough money or enough prowess in another field. A sufficiently rich person is surrounded by sycophants and stenographers who won’t check his numbers against anything.

There are two stories here. In the less interesting one, Musk is a modern-day streetcar conspiracy mogul: he has a car company, he hopes to make money off of it in the future and uses non-generally accepted accounting to claim he already does, and he constantly trash-talks high-speed rail, which competes with his product. Since he’s not proposing to build Hyperloop soon, it could be viewed as clever distraction or FUD.

The more interesting possibility, which I am inclined toward, is that this is not fraud, or not primarily fraud. Musk is the sort of person who thinks he can wend his way from starting online companies to building cars and selling them without dealerships. I have not seen a single defense of the technical details of the proposal except for one Facebook comment that claims, doubly erroneously, that the high lateral acceleration is no problem because the tubes can be canted. Everyone, including the Facebook comment, instead gushes about Musk personally. The thinking is that he’s rich, so he must always have something interesting to say; he can’t be a huckster when venturing outside his field. It would be unthinkable to treat people as professionals in their own fields, who take years to make a successful sideways move and who need to be extremely careful not to make elementary mistakes. The superheros of American media coverage would instantly collapse, relegated to a specialized role while mere mortals take over most functions.

This culture of superstars is a major obstacle frustrating any attempt to improve existing technology. It more or less works for commercial websites, where the startup capital requirements are low, profits per employee are vast, and employee turnover is such that corporate culture is impossible. People get extremely rich for doing something first, even if in their absence their competitors would’ve done the same six months later. Valve, a video game company that recognizes this, oriented its entire structure around having no formal management at all, but for the most part what this leads to is extremely rich people like Bill Gates and Mark Zuckerberg who get treated like superstars and think they can do anything.

In infrastructure, this is not workable. Trains are 19th-century technology, as are cars and buses. Planes are from the 20th century. Companies can get extremely successful improving the technology somehow, but this works differently from the kind of entrepreneurship that’s successful in the software and internet sectors. The most important airline invention since the jet engine is either the widebody (i.e. more capacity) or the suite of features that make for low-cost flights, such as quick turnarounds. What Southwest and its ultra low-cost successors have done is precious: they’ve figured how to trim every airline expense, from better crew utilization to incentives for lower-transaction cost booking methods. This requires perfect knowledge of preexisting practices and still takes decades to do. The growth rate of Microsoft, Google, and Facebook is not possible in such an environment, and so the individual superstar matters far less than a positive corporate culture that can transmit itself over multiple generations of managers.

There is plenty of room for improvement in HSR technology, then, but it’s of a different kind. It involves adapting techniques used by low-cost airlines to reduce costs, as SNCF is doing right now with its new low-cost TGV product. It perhaps involves controlling construction costs more tightly, though $5 million per km for viaducts seems like an impossible fantasy. But it has to come from within the business, or from someone who intimately understands the business.

And with the kind of success that US media harps on, this is almost impossible to do domestically. Someone as smart as Musk, or any of many other Silicon Valley entrepreneurs, could find a detailed breakdown of the operating and construction costs of civil infrastructure, and figure out ways of reducing them, Megabus- or Southwest-style. That’s what I would do if I had the unlimited resources Musk has: I’d obtain unit costs at far greater detail than “X meters of tunnel cost $Y” and compare what New York is doing wrong that Madrid is doing right. But I don’t have the resources – in money, in ability to manage people, in time. And the people who do are constantly told that they don’t need to do that, that they’re smart enough they can reinvent everything and that the world will bow to their greatness.

Update: people all over the Internet, including in comments below, defend the low cost projections on the grounds that the system is lighter and thinner than your average train. The proposal itself also defends the low tunneling costs on those same grounds. To see to what extent Musk takes his own idea seriously, compare the two proposals: the first for a passenger-only tube, and the second for a larger tube capable of carrying both passengers and vehicles. On PDF-pp. 25-26, the proposal states that the passenger-only tube would have an internal diameter of 2.23 meters and the passenger-plus-vehicle tube would have an internal diameter of 3.3 meters, 47% more. Despite that, the tunneling costs on PDF-p. 28 are $600 and $700 million, a difference of just 17%.

The same is true of the “but the Hyperloop capsule is lighter than a train” argument for lower pylon construction costs. Together with the differences in tube thickness posited on PDF-p. 27, 20-23 mm versus 23-25, there is 60% more tube lining in the passenger-plus-vehicle version, but the tube and pylons are projected to cost just 24% more. In this larger version, the twin tube has 0.025*3.3*pi*2 = 0.5 cubic meters of steel per meter of length, weighing about 4 tons. This ranges from a bit less than twice to a bit more than twice the weight of a train. To say nothing of the pylons’ need to support their own considerable weight, which is larger than for HSR due to the need for taller viaducts coming from the constrained ability to change grade. They are far more obtrusive than trees and telephone poles, contra the claims of minimal obtrusiveness and disruption.

Update update (12/24): Hyperloop is in the news again; I’ve been getting a lot of pingbacks copying this article. You can read the plan here; the construction costs are now up from a laughable sub-$10 million per kilometer to $10-30 million, which is perfectly feasible if you’re building in flat terrain and if what you’re building is conventional rail and not a vactrain. There’s virtually no discussion of why the costs are so much lower, just an assurance that the team ran the numbers and that they’re looking into minimizing the costs of the construction material (costs that, for conventional HSR, are a small proportion of the total construction costs – concrete is cheap, it’s pouring it that’s expensive). On PDF-p. 19 of the new plan, the accelerations are explicitly stated to be 0.5 g in normal service, which the person heading the team trying to build it claims is not a barf ride in the article, but which is in reality is again worse than the acceleration felt by passengers on an airplane taking off. There already exists a mode of transportation that involves security theater, travel at 1,000 km/h, poor comfort, and motion sickness.