Map Shows Where 220mph Trains Would Go in the U.S.
mashable.com
mashable.com
The route from LA to Seattle, with the branch additional bay-area line, has to deal with the following:
1. The tehachapi mountains, where the current rail line can handle up to 40 freight trains per day. This line is at capacity and cannot handle anything more. Worse even, it is mostly single track with steep grades and sharp curves. No regular passenger trains have run over it since the late 70's. In order to put a high-speed line here, it would cost billions, requiring many long tunnels through solid rock, along with large bridges and fills.
2: The Sacramento River Canyon, north of Redding. This is the only workable pass up to the Klamath River drainage, and quite frankly is extremely tough to pass. It has many tight curves, has had plenty of washouts and is a very steep grade past Dunsmuir. The I-5 alignment goes up and down and up, while taking up the only side of the canyon which can handle a right-of-way. There is no other option to get north, so this is pretty much right out.
3: The Siskiyou mountains, or the cascade mountains, to make it to Eugene. Both of them have rail lines, again with many sharp curves and steep grades. The Siskiyou line is absolutely brutal, which caused the Southern Pacific (the original owner, bought by the Union Pacific in 1996) to sell it off to RailTex. It handles 1 through train daily and is prone to washouts and landslides. The Cascade line is also single track, rough and at capacity. No other passes which can accomodate a line with moderate grades and few curves exist, requiring another expensive series of tunnels.
So, that one is pretty much a wash, as you can tell.
The route to San Diego from LA is already very good with high speeds (90MPH), but for whatever reason they want to route it through San Bernadino. This is absolutely stupid, as the route would follow I-15 and is already extremely rough with many changes in elevation and no consistent routing. There was a previous Santa Fe rail line through here that was promptly abandoned once they built the Surfliner route along the coast.
The route from LA to Denver is a pipe dream, sadly, due to:
1: Cima Hill, which runs through Mojave National Preserve. The only way across is along the existing Union Pacific alignment, which has several nasty curves.
2: The Wasatch Mountains. There is no good pass here outside Soldier Summit, which is rather brutal. Look it up to see what I mean.
3. The Rocky Mountains. You want to put a railroad through that? Go north through echo canyon and across the continental divide in Wyoming. That is the only HST viable route there, wide open for the taking.
The route from New Mexico to Denver is mostly owned by the state of New Mexico and Amtrak, but suffers from the beast that is Raton Pass. 3% grades, very tight curves and lots of general unpleasantness south of Trinidad. The lead up to it is nice, flat and high-speed, but the pass itself is nasty.
I could keep going, but I think the point has been made. Maps are all well and good, but what rules HST design is topography vs. budget. In order to do like the Japanese and punch a line down rough land, you have to spend gobs of cash and years of effort. With tight budgets and a booming national debt, it isn't really an option.
However, the Northeast Corridor is an excellent place, and several other routes across the midwest are also great candidates, should there be traffic to support them. Chicago-NYC would be a very good one, as the route has high demand and can follow water-level routes with gentle grades and few curves.
What makes HST succeed is either great land for it (France) or $$$ (Japan, China) or both in spades (Germany). I want to see it happen, but we have to restrict it to where it makes sense. Those routes are:
1: Chicago/Great-Lakes to NYC
2: LA to San Diego (the surfliner would be packed if the trip was on an HST)
3: Boston-NYC-DC-Richmond. Replace the Acela with something faster on a grade-separated alignment.
4: Texas to Kansas City - this is seriously one of the best places around for HST. Nice, flat, open and fast.
5: Eugene to Seattle. Only tough thing is crossing the Columbia river as the existing rail bridge is at capacity and has a 35mph slow order.
6: Florida. They just need to bite the bullet and do it.
Also, there's not a logistical or technical problem with punching through hills and mountains when needed. Definitely a financial problem, but if you're gonna spend trillions building this thing, what's an extra few million to bore holes in rock? ;-)
A lot of politicians and advocacy groups like to point to existing lines as a solution to crossing mountains and getting through cities. This is rather short-sighted as rail lines in the US are designed for slower moving heavy-tonnage and don't take advantage of the differences HSR alignments have.
When you want to run an HSR line, your requirements are quite different. Regular (read: freight) lines require easier grades and can take sharper curves due to their slower speeds and heavier tonnage. The busiest mountain passes typically have no more than 2-2.5% ruling grades, using curves to lessen the steepness. HSR can use much steeper grades (5%) but requires extremely gentle curves, which then demands a lot of expensive tunnel and bridge work.
When you want to take an HSR rail line across a series of mountains like the Tehachapi range, you run into a major problem. The change in elevation is extremely sudden and drainages are short, curvy and have steep walls. The end result is that you have to do many cuts, fills, bridges and tunnels to get up the grade. The expense is astronomical compared to a regular highway, yet most proposals don't actually take that into account.
However, the man who designed the map is at least a bit more realistic about the cost (several trillion). I do firmly believe that HSR is actually quite viable in the US in many places, it just isn't something we can draw on a map and say "here we go!"
We have to solve the problem of topography vs. budget. If we want a truly national network like shown in the map, we have to accept that the cost will be enormous - likely many times that of the interstate system (in today's dollars). If the people are willing to take that cost, then it should be built, but we should be careful what we propose to make sure it is truly viable.
And Amtrak isn't even very good! Years of neglect and bad regulation have left the service with old cars (except Acela), crumbling infrastructure, etc. But it beats the hell out of air travel, and the differential will only get more dramatic as fuel prices continue to increase.
Sounds good to NYC though—I will consider it for sure.
Also, you highlight an interesting deficiency of the Acela: it's only 30 minutes difference in time. On the BOS->DC route it's only a 70 minute advantage on a ~6.5 hour trip. Sort of makes HSR seem unnecessary when compared to "slow" standard regional train service. It's just not that much better.
They need true grade-separated modern HSR on this route. It would be excellent.
If France can have high speed train from Paris (about the size of Chicago) to Marsaille (about the size of Milwaukee) why can't we have high speed rail between Chicago and Milwaukee (which are much closer together)? Or for that matter Chicago and Detroit, the latter of which is bigger than the 2-4'th largest French metro areas put together?
A train from Detroit-Chicago-Milwaukee-Minneapolis would in a single 700 mile line cover 1/3 the population of France.
Detroit, Chicago, and Minneapolis and their metro areas together have $900 billion in GDP (about 1/3 the whole GDP of France) and several dozen Fortune 500 companies. There aren't three cities together anywhere in France that have comparable economic importance.[1] Yet, there are trains between a whole bunch of these French cities.
[1] France's second largest city, Lyon, has about the same GDP as Milwaukee or Kansas City.
GDP is a better thing to look at then current demand because it gives you an idea of the economic capacity of the region to create demand for travel, on the presumption that demand for travel is intrinsically roughly proportional to economic activity. It's a counter-point to the common refrain that American cities are insufficiently dense and near to support high speed rail. If I can get a high speed train from Frankfurt (GDP: $220 billion) to Paris (GDP: $560 billion), distance 460 miles, why can't I get a high speed train from Detroit (GDP: $250 billion) to Chicago (GDP: $570 billion), distance 280 miles? Why would the demand for travel between the latter pair of cities be intrinsically lower than the demand for travel between the former pair?
The larger point is that while the U.S. may be too big to support HSR criss-crossing from NYC to LA or Atlanta to Seattle, it is divided into several mega-regions, each of which have economic density not that different from that of European countries.
Boston-NYC-PHL-DC, Vancouver-Seattle-Portland, Detroit-Chicago-Minneapolis, Birmingham-Atlanta-Raleigh, even Houston-Dallas-Oklahoma City all link population centers that are roughly the same size and same distance apart as major European cities.
Taking "the northeast" to be New England + New York + Pennsylvania + New Jersey, it covers ~135,000 square miles and has a population of ~56 million people.
New Mexico alone has an area of ~121,000 square miles and has only ~2 million people.
This matters. A lot.
It's harder for a train to go 200mph through densely populated areas where NIMBYs don't want anything built. Cows, on the other hand, don't care. The train also doesn't have to stop very often -- a train can stop in Albequerque and Santa Fe, and zip north to Colorado Springs and Denver.
The biggest challenge to high-speed trains in the US is not population density or technology; the problem is political.
Those rural areas are also largely divided into private property holdings, which have to be resumed meaning compensation for all the property owners.
You're right, the problem is political, in that the politics of the country is set up in such a way that a centralised body cannot just go and throw railways everywhere. But that is a design feature, not a bug. The same governmental processes that stop people ending up with a nuclear waste dump next to their town also apply to railway lines. You can't just plan this stuff from a central office in Washington and make it so.
The real problem is economic, not political.
A NY-SF coach-class train ticket cost $65 in 1870. That may not sound like much, but that was 2.8 ounces of gold -- figure $4700 at current prices.
A first-class ticket with sleeping compartment cost $136 -- almost $10,000 in current dollars.
Right. Because they don't have vehicles, chickens or wildlife in any of the other nations with high-speed rail networks. These are clearly unsolvable problems.
Sometimes it seems like people are just reaching to find any possible excuse to dismiss the idea based on ideology alone, doesn't it?
As far as the problem with wildlife and trucks and rural roads—you just need a grade-separated track with passages above and below. Expensive but necessary and plausible.
There was talk of a new rail line to the south of Rochester, MN a number of years ago and some landowners were unhappy because the proposed line would split their fields, require new fencing to protect livestock, etc.
Here in Oregon, other landowners have gotten letters from the railways demanding payment for driveways across their lines just so they can get to their property. See http://www.kval.com/news/local/Neighbors-on-edge-over-new-ra...
Would it be easier to force a half a dozen farmers/landowners to give up part of their property than thousands of house/apartment dwellers? Of course. But its still forcing people and that results in lawsuits which will drag things out.
Still, it's like an hour longer of a trip than the bus. (I guess I haven't had bad experiences with traffic--on my last trip to Boston, we arrived early.)
http://upload.wikimedia.org/wikipedia/commons/6/6f/High_Spee...
It highlights the boston-washington route (NEC on the map or BosWash some like to say[1]), which seems to be easily the most do-able route in the near future, in terms of people served.
I like it. The idea, I mean. But its hard to get people to come around to spending money on anything remotely like this seems. I think all societies should have very lofty goals published and promoted often[2], but I think at the same time we need to always provide concrete reality-scale plans when trying to make the argument to non-believers, which is why I prefer the ARRA map, or something even smaller.
I think there are some larger societal issues that affect the value of things like this too. I wish Americans would (could) travel more, and see what other developed countries are like.
[1] http://en.wikipedia.org/wiki/Boswash
[2] "If you want to build a ship, don't drum up people together to collect wood and don't assign them tasks and work, but rather teach them to long for the endless immensity of the sea" -Antoine de Saint Exupéry
It is more a map to appease voters, without bearing into mind the cost of building it. If you look at it and go "oh wow, I can go from LA to SF up the coast", you of course can't tell that it would be madly expensive to build.
If they did this, they would realize why high speed rail makes sense in other developed countries but not in the US. Most other developed countries are tiny.
Aomori-Kagoshima (top of Japan to bottom) - 1928 km.
London-Moscow - 2885km.
Paris, France to Mosul, Iraq - 4522km.
NY-LA - 4469km.
And unlike the NY-LA route, all of the routes I mentioned have a lot of destinations in between the endpoints. For example, on the Paris-Mosul route you find Luxembourg, Germany, Austria, Slovenia, Croatia, Bosnia, Serbia, Bulgaria, Turkey and Syria. Between NY and LA there are Omaha, Chicago, Pittsburg, Cleveland, Denver and Vegas.
Even the short London-Moscow route passes through Antwerp, Dusseldorf, Berlin, Warsaw and Minsk.
Your point about destinations is pretty valid though. Getting to california from other parts of the US is an effort. The east coast has a lot of different possibilities though, and even things like Dallas-houston are frequented enough, and the time to get to DFW, go through security, etc. would be compensated easily by just taking a train.
The map the WH offered for the ARRA takes advantage of that fact. When big hubs are built, having single links between them becomes reasonable.
Having less money can actually help the economics of a rail line - if people are poorer (e.g. Europe), they can't afford a car and are stuck taking the train. The limiting case of this is India where low speed rail is extremely popular.
14 hours across the country—or even 8 hours at nearly twice the viable speed—will never match the speed or efficiency of air travel.
High speed rail can compete in the regional corridors where it makes sense. And it should. But the United States is huge. It's not Europe. We shouldn't expect this or desire it.
1) it's much less cost-effective to make a flight comfortable, in terms of leg room, food, space to walk around, than a train trip; this difference only gets bigger as liquid fuel prices go up;
2) as a practical matter you can't build airports in the heart of urban centers.
If there was a 14 hour train between NYC and LA, with the leg room and amenities of existing Amtrak trains, I think it would give air travel a run for its money. Taking a cab to LaGuardia takes about half an hour from Manhattan, and it's like a $40 cab ride. Another half an hour in LA, probably $50+ cab ride. Add at least an hour at the airport for each scenario, plus the 4-5 hours of actual travel time, and you're looking at an 8 hour trip.
Would you rather have 8 hours of cab -> airport -> airplane -> airport -> cab, or 14 hours just walking from a downtown train station, onto a train, and out of another downtown train station? Would you rather spend 5 hours crammed into an economy class seat, or 14 hours in an Amtrak train with a ton of leg room, where you can get up, go to the snack car, etc?
It's a capacity issue. A plane can carry a fixed maximum amount of people, the same as a train. Finding the economic load for any transport solution is a function of what people are prepared to pay plus the fixed and variable costs for operation. So while weight is part of it, that's only as it pertains to the maximum lift of a plane. Weight isn't as important to a train, but a train still has limits to the amount of people and luggage it can carry.
Even ferries have different price/class levels, some using airplane seats, some allowing cabins. This is totally dependent on what the market pays over anything else.
When I worked in Beijing, trips to Shanghai were greatly improved by booking sleeper berths and catching a night express trains out and back. The entire experience was generally extremely low stress and utterly reliable.
2) As a practical matter, you don't need to. It takes you 30 extra minutes to get from the outskirts of cities to the centers, versus an extra 8 hours for train travel to get you to the city center. Perspective.
Sure, you have some good points. Trains might have something for overnight trips with beds. But that's only a fraction of the market, and frankly, only for the West-to-East direction where redeye flights are most prevalent due to the time zone loss. Going East-to-West, the time advantage is ridiculously good: get on a plane in the morning in NYC and arrive in the morning in LA. You just can't beat that.
It's not. There is a reason Amtrak is absolutely destroying air travel in the Northeast corridor, especially among business travelers. I can get work done on a NYC to DC train trip. I can't get any work done on the corresponding airplane trip, between the tight spaces, the cabin pressure changes, etc.
> 2) As a practical matter, you don't need to. It takes you 30 extra minutes to get from the outskirts of cities to the centers, versus an extra 8 hours for train travel to get you to the city center. Perspective.
But not all trips are NYC to LA. The shorter the distance, the more time spent getting from an airport into the city impacts the overall travel time. HSR would get you from downtown NYC to downtown DC in 95 minutes. Getting from downtown to LaGuardia is 30 minutes and from Reagan to downtown is another 15 minutes best case, possibly a lot more with weekday traffic. More importantly to a business traveler, that's 45-60 minutes they're probably not getting any work done, while the train traveler is getting work done the extra 25 minutes the train is actually traveling versus the flight.
HSR is supposed to do Boston to DC in 3 hours, versus 90 minutes for a plane trip. Add in airport time and time spent in the airport, the total travel time is probably a wash, but again much of the travel time for air travel is cabbing and waiting in line at the airport during which you can't get any work done. So the HSR still wins.
DC to Boston is about 450 miles. There are a lot of major North American cities within ~500 miles of each other. E.g. Chicago to Toronto, Minneapolis, St. Louis, Detroit, Pittsburgh, Columbus, Milwaukee, etc. There's tens of millions of people in a ~500 mile radius of Chicago, and HSR would beat air travel for those trips.
It should connect large urban areas as needed, to bring the megalopolises closer together and easier to access, and in a way that's advantageous over air travel. It should not attempt to compete with cross-country flights, since it's not logical given those conditions. If you change the conditions, then sure, it makes perfect sense!
You're absolutely correct about all the routes you mentioned. Those are perfect. I want HSR on those routes. It handily beats air travel in every way.
But NYC to LA? Seattle to DC? Nope. Sure you could do that, but it would make more sense to fly, and that's simply a logical combination of transit for this large country. The map doesn't show that—it shows routes all the way across the country in ways that make no sense. We don't need to connect the coasts with high speed rail, because it's not logical to do so. That was my point, and I'm sure you would generally agree.
And the linked article doesn't seem to take into account the massive operating subsidies that rail requires. It's a money loser nearly everywhere (except, sometimes, in the NE corridor).
"In 1970, the year before Amtrak took over the nation's passenger trains, average rail fares were about one-third less than average airfares—about 18 cents (in today's pennies) versus 27 cents per passenger mile. Four decades of Amtrak management have reversed this ratio and more: by 2011, average rail fares were 110 percent greater than airfares—about 28.5 cents versus 13.8 cents per passenger mile (see Figure 1)." [1]
[1]: www.cato.org/pubs/pas/PA712.pdf
http://www.reddit.com/r/pics/comments/17nvfk/i_really_hope_t...
Theres quite a bit of back and forth, but the main conclusion is that the market for HSR won't support one. It seems in most cases people would rather fly, or the distance is short enough that a HSR doesn't make any sense.
It accommodates the state of the track (in most cases). To go faster would require wholesale replacement of most existing track, which is thought to be too expensive (but is the approach that was used in Japan and France).
> That's at least 12 hours to get from New York to Los Angeles.
I think many people would accept that, if the price was reasonable and the cars had suitable accommodations.
It does not accomodate current tracks. No rail lines in the US are designed for speeds over 150 mph.
Yes, and welded tracks, apparently a universal way to support high speed operations.
NY to SF: 2500 miles.
London to Moscow: 1500.
People who live between NY and SF: 313 million.
People who live between London and Moscow: 731 million.
We'd be much better off to start by improving I80 and just wait for driverless cars (busses) to go 250 mph.
Also, yes, high speed rail in the sprawl (Boswash) makes sense, but it doesn't really make much sense anywhere else except for maybe Seattle to LA. Linking the coasts with high speed rail is probably pretty silly unless you can start getting close to 350-450 mph.
Also: the fact that cars are driverless doesn't change the physics of 250 mph cars...
Of course you don't have to link NY and SF but that's what the map shows, well to be fair the map shows, NY to LA.
And the map shows a lot more than just NYC to LA.