Amtrak Releases Bad Scranton Rail Study
There’s hot news from Amtrak – no, not that it just announced that it hired Andy Byford to head its high-speed rail program, but that it just released a study recommending New York-Scranton intercity rail. I read the study with very low expectations and it met them. Everything about it is bad: the operating model is bad, the proposed equipment is bad and expensive, the proposed service would be laughed at in peripheral semi-rural parts of France and Italy and simply wouldn’t exist anywhere with good operations.
This topic is best analyzed using the triangle of infrastructure, rolling stock, and schedule, used in Switzerland to maximize the productivity of legacy intercity line, since Swiss cities, like Scranton, are too small to justify a dedicated high-speed rail network as found in France or Japan. Unfortunately, Amtrak’s report falls short on all three. There are glimpses there of trying and failing, which I personally find frustrating; I hope that American transportation planners who wish to imitate European success don’t just read me but also read what I’ve read and proactively reach out to national railways and planners on this side of the Atlantic.
What’s in the study?
The study looks at options for running passenger trains between New York and Scranton. The key piece of infrastructure to be used is the Lackawanna Cutoff, an early-20th century line built to very high standards for the era, where steam trains ran at 160 km/h on the straighter sections and 110 km/h on the curvier ones. The cutoff was subsequently closed, but a project to restore it for commuter service is under construction, to reach outer suburbs near it and eventually go as far as the city’s outermost suburbs around the Delaware Water Gap area.
Amtrak’s plan is to use the cutoff not just for commuter service but also intercity service. The cutoff only goes as far as the Delaware and the New Jersey/Pennsylvania state line, but the historic Lackawanna continued west to Scranton and beyond, albeit on an older, far worse-built alignment. Thus, the speed between the Water Gap and Scranton would be low; with no electrification planned, the projected trip time between New York and Scranton is about three hours.
I harp on the issue of speed because it’s a genuine problem. Google Maps gives me an outbound driving time of 2:06 right now, shortly before 9 pm New York time. The old line, which the cutoff partly bypassed, is curvy, which doesn’t just reduce average speed but also means a greater distance must be traversed on rail: the study quotes the on-rail length as 134 miles, or 216 km, whereas driving is just 195 km. New York is large and congested and has little parking, so the train can afford to be a little slower, but it’s worth it to look for speedups, through electrification and good enough operations so that timetable padding can be minimized (in Switzerland, it’s 7% on top of the technical travel time).
Operations
The operations and timetabling in the study are just plain bad. There are two options, both of which include just three trains a day in each direction. There are small French, Italian, and Spanish towns that get service this poor, but I don’t think any of them is as big as Scranton. Clermont-Ferrand, a metro area of the same approximate size as Scranton, gets seven direct trains a day to Paris via intermediate cities similar in size to the Delaware Water Gap region, and these are low-speed intercities, as the area is too far from the high-speed network for even low-speed through-service on TGVs. In Germany and Switzerland, much smaller towns than this can rely on hourly service. I can see a world in which a three-hour train can come every two hours and still succeed, even if hourly service is preferable, but three roundtrips a day is laughable.
Then there is how these three daily trains are timetabled. They take just less than three hours one-way, and are spaced six hours apart, but the timetable is written to require two trainsets rather than just one. Thus, each of the two trainsets is scheduled to make three one-way trips a day, with two turnarounds, one of about an hour and one of about five hours.
Worse, there are still schedule conflicts. The study’s two options differ slightly in arrival times, and are presented as follows:
Based on the results of simulation, Options B and D were carried forward for financial evaluation. Option B has earlier arrival times to both New York and Scranton but may have a commuter train conflict that remains unresolved. Option D has later departure times from New York and Scranton and has no commuter train conflicts identified.
All this work, and all these compromises on speed and equipment utilization, and they’re still programming a schedule conflict in one of the two options. This is inexcusable. And yet, it’s a common problem in American railroading – some of the proposed schedules for Caltrain and high-speed rail operations into Transbay Terminal in San Francisco proposed the same.
Equipment and capital planning
The study does not look at the possibility of extending electrification from its current end in Dover to Scranton. Instead, it proposes a recent American favorite, the dual-mode locomotive. New Jersey Transit has a growing pool of them, the ALP-45DP, bought most recently for $8.8 million each in 2020. Contemporary European medium-speed self-propelled electric trains cost around $2.5 million per US-length car; high-speed trains cost about double – an ongoing ICE 3 Neo procurement is 34 million euros per eight-car set, maybe $6 million per car in mid-2020s prices or $5 million in 2020 prices.
And yet somehow, the six-car dual-mode trains Amtrak is seeking are to cost $70-90 million between the two of them, or $35-45 million per set. Somehow, Amtrak’s rolling stock procurement is so bad that a low-speed train costs more per car than a 320 km/h German train. This interacts poorly with the issue of turnaround times: the timetable as written is almost good enough for operation with a single trainset, and yet Amtrak wants to buy two.
There are so many things that could be done to speed up service for the $266 million in capital costs between the recommended infrastructure program and the rolling stock. This budget by itself should be enough to electrify the 147 km between Dover and Scranton, since the route is single-track and would carry light traffic allowing savings on substations; then the speed improvement should allow easy operations between New York and Scranton every six hours with one trainset costing $15 million and not $35-45 million, or, better yet, every two hours with three sets. Unfortunately, American mainline rail operators are irrationally averse to wiring their lines; the excuses I’ve seen in Boston are unbelievable.
The right project, done wrong
There’s an issue I’d like to revisit at some point, distinguishing planning that chooses the wrong projects to pursue from planning that does the right projects wrong. For example, Second Avenue Subway is the right project – its benefits to passengers are immense – but it has been built poorly in every conceivable way, setting world records for high construction costs. This contrasts with projects that just aren’t good enough and should not have been priorities, like the 7 extension in New York, or many suburban light rail extensions throughout the United States.
The intercity rail proposal to Scranton belongs in the category of right projects done wrong, not in that of wrong projects. Its benefits are significant: putting Scranton three hours away from New York is interesting, and putting it 2.5 hours away with the faster speeds of high-reliability, high-performance electric trains especially so.
As a note of caution, this project is not a slam dunk in the sense of Second Avenue Subway or high-speed rail on the Northeast Corridor, since the trip time by train would remain slower than by car. If service is too compromised, it might fail even ignoring construction and equipment costs – and we should not ignore construction or equipment costs. But New York is a large city with difficult car access. There’s a range of different trips that the line to Scranton could unlock, including intercity trips, commuter trips for people who work from home most of the week but need to occasionally show up at the office, and leisure trips to the Delaware Water Gap area.
Unfortunately, the project as proposed manages to be both too expensive and too compromised to succeed. It’s not possible for any public transportation service to succeed when the gap between departures is twice as long as the one-way trip time; people can drive, or, if they’re car-free New Yorkers, avoid the trip and go vacation in more accessible areas. And the sort of planning that assumes the schedule has conflicts and the dispatchers can figure it out on the fly is unacceptable.
There’s a reason planning in Northern Europe has converged on the hourly, or at worst two-hourly, frequency as the basis of regional and intercity timetabling: passengers who can afford cars need the flexibility of frequency to be enticed to take the train. With this base frequency and all associated planning tools, this region, led by Switzerland, has the highest ridership in the world that I know of on trains that are not high-speed and do not connect pairs of large cities, and its success is slowly exported elsewhere in Europe, if not as fast or completely as it should be. It’s possible to get away without doing the work if one builds a TGV-style network, where the frequency is high because Paris and Lyon are large cities and therefore frequency is naturally high even without trying hard. It’s not possible to succeed on a city pair like New York-Scranton without this work, and until Amtrak does it, the correct alternative for this study is not to build the line at all.

