The Amtrak station building in Columbus, Wisconsin. From Wikimedia user Downspec, CC-BY-SA |
I had a nice little trip on Amtrak's Borealis this past Saturday, May 25th, which allowed me to visit Winona for a few hours. My trip down was smooth, though I got a bit frustrated by delays on the way back. It turns out that my trip to Winona was on the best-performing Borealis train trip so far, and the only one to arrive in Chicago with zero delay up til now. However, my trip back ended up arriving 40 minutes late. I'll take a look at what may be going on with the eastbound/southbound train no. 1340 in the future, but for now I'd like to take a look at one of the likely reasons why my return trip, the westbound/northbound train no. 1333, picked up so much delay.
I included this chart in my previous post welcoming the beginning of Borealis operation. It's a stringline diagram, showing the approximate scheduled location of each train on a particular corridor over time. What I'd like to focus on in this post is the first crossing point of the longer lines, which occurs near the "CBS" horizontal line representing Columbus station in Wisconsin.
The difference of just 6 minutes between the schedule of these two trains will mean that they will often both want to be at Columbus station at the same time, or at least in very close proximity. If they're both running exactly on time, they should run headlong into each other just west of town.
The good news is that there is double-track in Columbus, which should allow the two trains to pass each other. Google Streetview even shows two platforms at the station, though they are in poor condition according to this imagery from 2021.
Google Streetview image of the Columbus station platforms and tracks, with a simple wire fence between them |
However, looking through location history of trains that have run so far, the westbound Borealis is frequently getting stuck at a point east of Columbus, halfway between Astico and Reeseville, waiting for the Empire Builder or other trains to pass. This is one of the most obvious places causing delay for westbound trains, a slowdown which is proving hard for trains to recover from as they make their way to St. Paul.
Borealis trains are racking up significant delays between Milwaukee and Columbus |
So, what's going on here?
Well, first off, I'm hoping this is just a temporary situation. Columbus is one of Amtrak's many stations that are undergoing construction to upgrade platforms, walkways, and other parts of the station area to current ADA standards. Work is expected to be completed in Amtrak's next fiscal year, meaning sometime after October 1st. While this won't provide high platforms like those present in many East Coast cities, they will be raised up several inches and will get yellow tactile pavers like what we're accustomed to at urban rail and enhanced bus stops.
Based on video from news outlets and YouTube channels such as Trains Are Awesome, where Thom visited Columbus for an afternoon, it looks like only one of the two platforms is currently able to be used.
Okay, so one track is out of commission for passenger service. That shouldn't be such a big deal, right? The trains can just cross over to the other track somewhere nearby, right?
Well, no, unfortunately.
The map above shows the area of double- and single-tracking near Columbus (zoom in to see the track hidden by the icons). Double-tracked sections are shown in an orange-yellow color, and single-tracked sections are shown in dark red. I've included green "X" icons showing where switches are located, and stoplight icons indicate ends of signal blocks, generally spaced about 2 miles apart. Columbus is in a long stretch of about 23 miles of double-tracking, but unfortunately, the nearest crossing between those tracks is about 6 miles east of the city, which is where the westbound Borealis is often getting stuck.
Critically, that crossover point is on the opposite side of town from where the Empire Builder and Borealis are scheduled to meet each other. West of the station, there aren't any real crossing points that can be used in this situation. The double-track section begins around 7 miles west of town, but that only provides the eastbound trains the option of going on the track with the out-of-service platform. Combined with the nearly 11-mile single-track stretch running from near Doylestown west to Wyocena, that effectively creates a 24-mile single-track section for passenger trains (from Wyocena through Columbus to the crossover between Astico and Reeseville).
That distance really closely corresponds to the delays the no. 1333 trains have been experiencing. Pretty wild that a 400-foot stretch of missing pavement can have such an effect—get delayed by 15 minutes or so getting to Columbus as the track clears, only to arrive late to the congested east Twin Cities region, and get delayed even further due to missed windows.
Well, I'm taking a bit of a leap in assuming that's what's going on, but it seems to be the simplest explanation. I hope the station construction can be accelerated, at least enough to get both platforms usable.
I'm not sure how the train crews will the different groups of riders, especially since Columbus hasn't had a station attendant since 2017—it would probably make sense for this station to be staffed, just since someone should be around to shepherd people around to the right places before the trains show up. They're long enough to block the nearby crossings while boarding and disembarking happens, so it's really important for passengers to be in the right spots ahead of time. The station has had a simple fence between the tracks since 2016, so it appears that passengers have to walk down to Ludington Street just east of the station to cross over to the other side.
A more robust solution would be to add crossover tracks west of the station, to allow trains to switch tracks much closer to the stop and at a point that naturally aligns with the schedule. It would mean that only one platform would need to be used, and would also help reduce the chance that a late Empire Builder would induce even greater delays. There is a set of block signals about half a mile away from the station past Lewis Street that would probably be an ideal spot to add switches.
There are track improvements planned in La Crosse, La Crescent, and Winona that are supposed to help the Borealis and any future added service operate more smoothly. Perhaps that will shift the schedules a bit too. If those changes allow the Empire Builder to consistently arrive a several minutes earlier, that would shift the meeting point east of Columbus station and reduce the need for any track changes there.
Of course, a lot of this trouble would be eliminated if we could get a commitment to converting much more of the whole route to double-tracking. The single-track corridors that dominate rail in the U.S. definitely make it much harder to add new passenger service here vs. what's possible in Europe and elsewhere. That flexibility would be priceless.
Mike, speaking of Columbus, I notice there is no longer any public transport from there into Madison. Basically Amtrak seems to have given up in serving the capitol. Is there something I'm missing, or is there really no way to use the Borealis or Builder to access Madison without a taxi or prearranged ride?
ReplyDeleteCorrection, I see now Megabus is in the route, but their service from CBS does not connect to any EB Amtrak, and the service from MAD only connects to the Builder WB, with a nearly 3h layover.
ReplyDeleteOh, interesting. Yeah, despite the branding change, it's looking to me like the Megabus/CoachUSA route is basically the same as the previous one operated by Lamers Connect. I see from this WisDOT page and map that it's a state-supported route, so they probably have a schedule that hasn't changed for a long time, and just contract it out to whoever is willing to run it
Deletehttps://wisconsindot.gov/Pages/travel/pub-transit/bus-service.aspx
https://wisconsindot.gov/Documents/travel/pub-transit/icbus-map.pdf
I'm not immediately finding old Amtrak timetables showing a Thruway connection between Columbus and Madison, but I did find some that show it connecting in the opposite direction from Columbus up to Green Bay, so it's probably been a very long time now since there was good service to Madison:
https://juckins.net/amtrak_timetables/archive/timetables_Empire_Builder_20180429.pdf
I guess we'll have to see if something gets added. It's not a whole lot further to get to Portage, so some people may have better connections heading that way, though it looks like the bus only goes northbound? It must turn somewhere and go in a giant loop to some other part of Wisconsin.
I rode the Madison to Columbus connection from the staffed Madison (Milwaukee Road) station in December 1975. Briefly before that, it was operated by Greyhound.
ReplyDelete