The PRR had four tracks running side by side over most if not all of this route. When Conrail took over they removed one of the tracks. How difficult would it be to replace that track for high speed passenger service only. The right of way is already there, owned by NS. Upgrading the roadbed and installing ties and rail would be the expense. In most new rail route building the land aquistion is the most costly feature of the enterprise.
Lines West was mostly two track, but the idea is a logical one worth exploring, except for two things:
-
The freight railroads do not want the bother of passenger services, certainly nothing beyond what is already there, and will find many reasons why “that won’t work.”
-
HSR is not likely in the current political climate.
As logical as it sounds it is also not as easy as it sounds. There has been some realingments for wider and higher cars, longer distances between track centers, different banking on curves, etc. Then there are tne special needs of HSR which might interfere with the needs of contemporary freight needs. Not that it is necessarily impossible, just not as easy and therefore there would be a lot of flak from the freight railroads…which their lawyers have already produced in the form of passenger train accident liability. American transportation businesses, like all American businesses, are at a point where they’ve got to decide if they have to make 70 or 80 percent of $100 or if they can settle for 40 or 50% of $200. Once we get that operating ration, return on investment, whatever you want to call it, settled, then we can start building for the future.
Even the wonderful PRR didn’t really have an alignment that would work very well for HSR. The best the PRR ever did was 15-1/2 hrs. You might squeeze a couple more out if you really tried. Harrisburg to Huntingdon, you might get 90 mph in for a few stretches. Huntingdon to Pittsburgh - what you have now is about it. Pittsburgh to Alliance - maybe some 90 mph in spots. West of Alliance there might be some opportunity, but the route doesn’t go thru population centers. If you want to do NY to Chicago as HSR, wouldn’t you want Cleveland and Toledo on your route, or Columbus and Indy?
The NYC route west of Albany to Chicago has more places were you could get to and sustain 110 mph. It also was four tracks wide. It would be a better choice. But, since the market for HSR is generally <500 miles, why consider NY - Chicago as a route. Let’s start with the easy, cheap NEC extensions. How about extending NY to Albany west to Syracuse and Buffalo as a start?
The number of origin-destination pairs with comparable trip times as driving is large when you can tie the service into the existing NEC network.
That, indeed, is where some of the money earmarked for Wisconsin, Ohio, Florida, and New Jersey is going!
Until the state of Ohio buys into HSR the route is dead in the water.
But as others have posted we need Higher speed rail first to establish a proven demand. The time frame will have to be about 40 years to get to the point a dedicated ROW can be built for these routes.
Using AMTRAK mileage which may be longer or shorter on high speed line(s). These assume a 2 or 3 stop super express run at 220 MPH with no slowing except at the terminal ends and intermediate stations. Additional stops for regular express will take longer
NY - Cle 618 4 HR (lakeshore route) 580 miles by PIT
NY - PIT 444miles 3 HR
Wash - PIT 300 2
PIT - CLE 140 .75
CLE - CHI 341 2
Ask me in 40 years how close we are.
If a HSR route from CHI to NYC were to happen, I think it would work best by hitting as many large metro areas as possible. CHI-DTW-CLV-PIT-PHI-NYC would make the most sense to me. Though it wouldnt be a very straight line. At 220 MPH, one can deviate a bit from the most direct route and not lose too much momentum. The Pittsburg to Philly route could run at top speed if good infrastructure were built.
While I usually promote the concept of thinking outside the box, I think here we should look at more traditional “corridors”: i.e., the Water Level (ex New York Central) and the former PRR routes. Amtrak does Pittsburgh-Youngstown- Cleveland-Chicago but is that best? NYC from NY to ALbany, Utica, Syracuse-Rochester-Buffalo-Erie-Cleveland-Toledo-Chicago serves a lot of people. Perhaps there should be NY-Phila-Harrisburg-ALtoona-Pittsburgh-Youngstown-Fort Wayne-Chicago HSR with a connecting HSR P’brgh-Cleveland branch…
…HSR is a new technology to us…achievable speeds and attending accompolishments could produce different product and service than traditional or reinforce the the paths as set up by PRR or even B&O. But real market surveying and planning must be done, not political track laying.
-
NY-CHI won’t work in the marketplace unless it is true HSR.
-
Using/sharing the existing heavily used ex-PRR and/or ex-NYC routes seems unfeasible, as they really don’t want HSR b/c compatibility problems. What about abandoned or lightly used RoW’s from PRR, NKP, or Erie?
Ideas…good ones. But proof will be in market survey and planning. The past is mere prologue and may or may not be the bellweather for the future; we won’t know until it is studied. The Erie route sounds great from Jersey City to Chicago but misses a lot of major markets almost in its entire length, so would it pay to put HSR on that track? Or should freight be put on that track/row and put HSR on the NYC and/or PRR rouites? There’s a lot of thinking, studying, planning and, unfortunately, politicking that’s gotta be done.
You really are making far too much of market survey and planning, as though that solved everything. We all know where the metro areas are. The Erie was just a thought. Perhaps the ex-NYC parallel West Side trackage could work to Buffalo? In any case, you can’t force CSX or NS freight off their tracks. The ex-PRR east of Pittsburgh has too many curves for HSR to work, and is heavily used. Use ex-PRR west of Crestline to CHI? Maybe. Some cities will get left out. The idea would be rebuilding in segments, on existing AND usable RoW, to reduce costs. [The Cali HSR does not use existing RoW’s as much as they could, IMO, and thus has an overly high price tag.]
I can see two things happening neither good. Cresting at Galitzen all passengers must be wearing seatbelts to prevent the equivalent of hitting an air pocket in a plane when the transitioning from uphill to downhill at over 200mph. All passengers are forbidden from standing from Altoona to Pittsburgh due to the curves so no one is ejected.
But Schlimm, we can’t attract investors nor build what will work until we find what the market wants and will pay for what it wants. Build a 90 mph railroad because it is cheaper to build when people want aand need a 150mph railroad and you wont get the riders. Set a schedule that leaves a 5 when the public wants to leave at 7 and nobody will be at the station. I want to ride the ACELA, but I have no reason to, so I will ride the Regional service instead, even a commuter service if it serves the purpose, my purpose. But somebody gotta get from NYC to Boston fast, in comfort, and in a cost effective manner for their needs and desires, then ACELA is the way to do it. But if you have just one chance to build the right thing, then you gotta study it, and build it right the first time. As a railfan, it don’t make a difference, I’ll ride as I have a chance or even possible need. But non railfans want the privacy and availability of their automobile, the speed of a jet plane, and the cost of walking. You’ve got to build the right shoe horn to get the right fit.
Existing carriers don’t want HSR anywhere near their property…from a liability standpoint if nothing else. Operating HSR on a existing property is totally out of the question.
The Interstate system already has identified traffic volumes between metropolitan areas. Were HSR to be built along segments of Interstates…a HSR whistling past at 180 with road traffic doing 80 in a 70 would be eye catching.
Existing railroad rights of way were not laid out with any inkling of HSR and what it requires and what construction techniques can be applied in the 21st Century that weren’t even a wild eyed idea in the 19th Century when the existing rights of way were laid out and engineered and those 19th Century rights of way were laid out for the benefit of moving freight at minimum cost…passenger in the day, just came along for the ride. While we marvel at the MILW’s ‘Slow to 90’ curves for the Hiawatha’s…HSR needs to be built for a ‘Slow to 150’ standard with service from and to significant Origin/Destinations no more infrequent than every two hours, with the preference toward ‘Clocker’ type operations.
HSR with the power/weight ratio necessary to attain speeds in the 180 MPH range, has sufficient power to attack virtually any grade in much straighter line than is necessary to lug 20K tons of freight over the grade. By the same token, the curvature that permits 20K ton trains to surmount existing grades is sheer death to attaining ‘high speed’.
Interesting thought! The early highways followed the railroads; now HSR would follow the highways … and for the same reason.
Water courses were followed by footpaths then roads, such as they were, followed by canals and railroads through the 20th Century…then concrete and gasoline virtually leveled the hills and now HSR can follow them in many places. And along these transportation corridors dots of civilization’s towns and cities settled. The Erie Canal actually, after following water courses across New York cause the development of virtually every city and town from Buffalo to Rome and enriched those along the Mohawk from there to Albany and on down the Hudson to New York City. The railroads connected those dots in the 1830’s and 40’s and our highway system beginning in the 1910’s, strengthened in the 1930’s by CCC projects then the Eisenhower era Federal highways putting the two laners to rest. The highways first went where the rails made towns, not the other way around.
That sounds like a very good idea. I hope it could be developed.
However the interstate system has many curves that are greater than the required 1 degree or less to maintain 150 MPH+. A HSR line would need to deviate from the I- corridor to counteract that problem.
I am not advocating exact adherence to Interstate rights of way…I am just saying that the Interstate System provides a easy way to measure the amounts of inter city traffic. Some (repeat some) Interstate rights of way could be used for a number of miles in many instances…especially when it comes to figuring a route into a city center … the cost to purchase new rights of way would be mind bogglingly expensive. While many Interstate routes into city centers are not 55 to 70 MPH routes, they are generally less curve bound than rail rights of way into the same cities.
When it comes to HSR, there will not be one solution that fixes all problems…like any big transportation project significant segments o
Very true. It is easy for critics (who mostly are looking for reasons to not do anything) to nit pick and find a million reasons why not. The RoW of I 70 in Pennsylvania has plenty of curves, though mostly fairly broad, but it is going through some rugged terrain. So, if it were followed and widened for a double-track line (instead of widened for more highway lanes) there might be some stretches under 150 or 125 mph. But overall, the speed could be quite high.