Just got a newsletter from MnDOT and WiDOT published jointly and the startup is still tentatively scheduled for fall 2023 it says TBD with the marker in the fall part of this year. The proposed schedule is below:
Dp St. Paul: 11:47 a.m.
Ar Milwaukee 5:40 p.m.
Ar Chicago 7:14 p.m.
Dp Chicago 11:05 a.m.
Ar Milwaukee 12:34 p.m.
Ar St. Paul 6:16 p.m.
Approx meeting point for both trains: Somewhere between Tomah and Wisconsin Dells.
That’s an interesting question; I’m not familiar enough with short final in the Twin Cities to know whether a stop in St. Paul with good connections to Minneapolis is ‘better or worse’ than a stop in St. Paul with only a short continuation to Minneapolis as a ‘one-seat ride’.
Perhaps someone more knowledgeable can give the specific costs and difficulties for the ‘expansion’, including comparison of turning the train in the two locations.
The alternatives analysis for a program like this is always available online. If you are interested in details, you can Google the project website and read the environmental documents. For this project, I believe they borrowed heavily from the high speed rail study of 2012 (when there was talk of extending the Madison HSR line to St. Paul, before Madison HSR was canceled).
Short summary, though:
There is no Amtrak station in Minneapolis. There is a commuter rail station at Target Field, which has little in the way of waiting rooms, nothing in the way of facilities for Amtrak customer-facing operations or personnel, and is difficult to access by car whenever the Twins are playing a baseball game.
I believe Amtrak services trains (toilets, water, etc.) at St. Paul Union Depot (SPUD). They also have some facilities near the old Amtrak station (Midway), which is halfway between SPUD and Target Field. If they service the train at SPUD or Midway on its revenue run, the delay will be great enough to kill the time advantage of a one-seat ride versus driving or transit to St. Paul. Instead they would have to deadhead from Target Field back to Midway or SPUD for servicing, which brings us to
The route from SPUD to Target Field goes through some busy freight junctions in the center of the BNSF and UP intermodal facilities. BNSF spent tens of millions of dollars to improve freight flows in this area less than a decade ago. I doubt Amtrak is going to get four additional moves per day (two revenue and two deadhead) through there without paying for improvements. And as the person who was in charge of that BNSF improvement project, I can tell you there aren’t any obvious next steps to take right there that don’t involve insanely expensive and politically unacceptable demolition.
I don’t want to obligate Dan Peltier but I’d like to hear his opinions on this 400-mile-odd round trip to Fargo presumably through Minneapolis and its concerns.
Is there regular enough traffic to and from Fargo (including unversity students) to justify the extension costs? Thruway bus extension to Grand Forks?
Would there be enough hard use by intermediate communities to make the politically-desired intermediate stops, wherever they’d be, practical either?
Where would you turn and service the train in Fargo?
Perhaps most important, what’s North Dakota’s fair share of the ‘corridor subsidy’ that almost without doubt would apply to this service, considering the very small actual route mileage in that state?
I am extremely mindful that 94 and 29 were just shut down for weather. But our current Amtrak would surely cancel the train for anything serious enough to close an Interstate…
Turning trains is a problem. Since the consists are usually fixed I would think Amtrak should start moving away from loco hauled trains outside the NEC.
Push-pulls would be reasonable solution to the turning problems. It has worked wonders on various suburban services and Amtrak uses them on short hauls out of Chicago.
“Turning” trains (in this context) does not mean reversing their direction – it means the same thing as ‘turning’ a hotel room or a restaurant table. Cleaning, reprovisioning, makeready.
To the extent ‘reversing the direction of travel’ is involved - ‘top and tail’ or cabbage/cab car on the other ‘end’ from the power, or assigning something like an Airo set to this extended ‘corridor’ trip, takes care of the issue. If we can tolerate brief interruptions of power due to the deflicted implementation of Amtrak HEP, just set up a ‘shore power’ location and connect the train while a locomotive consist runs around the train or goes to be wyed somewhere.
It is kinda-sorta possible that much of the effort involved with turn maintenance could be conducted in an ‘extended’ stop at St. Paul, with the out-and-back trip to Fargo treated as if it were its own 400-odd-mile corridor trip. Then the only ‘difficulty concern’ would be, as charlie hebdo noted, efficiently reversing the direction of travel at the chosen ‘endpoint’ at Fargo.
IMO it is more important to get the CHI - MSP second train going. It all comes down to what happens in the next 2 weeks. Can we anticipate some entity filing a lawsuit to stop the CP / KCS combination? Any injunction will probably mess up this route, NOL - BTR, and MEI - FTW. Just holding my breath.
What was the proposed expanded route that was going to be worked with an Airo (or Airo-style) trainset, perhaps with a cab car on one end instead of top and tail?
I have the Emails of the DOT contacts for MN and WI for this project and I think you can Google and get them from the website as well if you want I can post a link. However, you can ask them directly and they might answer you. I think the issue there is MN is unwilling to pay for that and I am not sure ND will contribute.
Wisconsin has three cab cars on order from Siemens. No idea if they have been delivered yet but they want to convert the entire Hiawatha Service to Cab Car on one end and Locomotive on the other. They stated the cement full F40 Cabbage weigh too much and burn too much fuel per trip. They also don’t like the loco at end setup.
About halfway down the page is a section called “Studies”, and the first link there is to the 2015 feasibility report, which Amtrak performed at MnDOT’s request after the Wisconsin HSR died. They studied four routes in Minnesota: to SPUD, to Target Field in Minneapolis, to St. Cloud, MN with a stop at Target Field (requiring a backup move), or to St. Cloud with no stop at Target Field (possibly with a stop at the Fridley commuter rail station). I haven’t read it, but I would suggest that those who are interested should do so.
The thing to understand about Minnesota is that 55% of the state’s population (about 3.2 million people) live in the seven counties that are part of the Metropolitan Council (the regional planning and services authority that, among other things, provides sewer and public transit services to its region). Much of the rest lives in the southeast quarter of the state. There’s just not many people to serve going west or north from the Twin Cities. The Twin Cities, like Kansas City or DFW, owe their historical prominence largely to the fact that they are on the western edge of civilization. (Civilization in the sense of a diversified economy including including urban commercial centers and industry - I am NOT saying that the good folks of the Great Plains are uncivilized!)
There are three ways you could hypothetically extend a Saint Paul train to Fargo. The first would be to follow the current Empire Builder route, which uses the former NP line most of the way. This was not studied, but a shorter extension alo
So who owns the rail line or former rail right of way that heads North from SPUD to Cardigan Junction?
Seems to me that Minnesota has an option there…though a lot more expensive to cut a significant dog leg off the SPUD to Minneapolis and then Northeast routing.
It’s that dogleg that is making the line uncompetitive, in my view.
The problem I have with these Amtrak proposals is some of the routes like this one are going to be real difficult to get competitive travel times and to me it just looks like Amtrak does not care.
Geez DFW took a 70 mile largely abandoned or sunk in the Mud Rock Island line and redid the rail to turn it into partly double track 70 mph Commuter Rail line with Bombardier Cars. Including LOTS of new concrete overpasses and some elevated portions. Seems Amtrak and it’s proponents in Congress always shy away from a project like that and attempt to make a questionable late 1800’s or early 1900’s rail alignment viable that is seriously handicapped from the start.
You can’t always build or rebuild a rail corridor on a Beer Budget. Outside the sprawl of the Twin Cities this cooridor is mostly rural…so C’mon spend a little more money for the future and do it right.
The Soo Line came in from the east, and at Cardigan Junction it split into two lines: one to Shoreham Yard and Minneapolis, and one to St. Paul.
The line to Saint Paul flew over the NP near Jackson and Arlington streets, paralleled the NP down the Trout Brook Valley, and had its own tunnel near the NP tunnels. It ended at SPUD and the Soo Line freight terminal on 4th St. At the flyover location, there was a connection from the NP to the Cardigan Junction / St. Paul line. This connection is still there (it’s called Soo Line Junction); south of there, most of the line St. Paul branch of the Soo Line is abandoned and the land incorporated into the relatively new Trout Brook Nature Preserve.
The only connection between CP’s former Soo Line properties and their former Milwaukee Road properties is by trackage rights over BNSF.
This line from Soo Line Junction on the NP to Cardigan Junction - and then from there to Shoreham Yard - was very lightly used until about 2013. Until then CP trains used their BNSF trackage rights all the way from Hoffman to the University control point at Shoreham Yard. To reduce congestion at University, CP rehabbed the line up through Cardigan Junction and started running most of their westbound trains that way instead. (I understand that somewhere between Shoreham and Cardigan there is a killer eastbound grade, hence why it is used for westbounds only.)
Sorry, I’m a little lost. Which service are you referring to when you say “making the line uncompetitive”