Late Trains: A Fact of Life.
Some twenty years ago, I was heading west on the Empire Builder and having lunch in the dining car with a delightful gentleman from the U.K. He was taking six weeks to see the U.S., all by Amtrak.
Just as we were finishing our meal, a conductor came through the diner and stopped at our table. “I’m sorry to tell you this,” he said, “but there’s a freight up ahead with a broken wheel on one of the cars. They’re working on it, but it’s going to be some time before we get moving again. As of now, we’re probably going to be four hours later into Seattle.”
My British table mate positively beamed. “Jolly good!” he said. “Then we really are getting our money’s worth, aren’t we!” As far as he was concerned, we were going to get four additional hours of train ride at no extra cost.
When crossing the country on one of Amtrak’s long-distance trains, we would all be well advised to adopt the Brit’s attitude. It is an indisputable fact that long-distance trains often arrive several hours late and, most of the time, the cause is beyond Amtrak’s control.
The list of reasons why a train runs seriously late is almost endless, although the freight railroads giving priority to their trains on their track is by far the most common. Furthermore, when problems occur, they often often compound to make the situation worse. For instance, by the time a work gang gets the boulder removed from the tracks, the operating crew—the engineers and conductors—have reached their legal time limit and have “gone dead”. That means Amtrak has to locate a new crew and have them delivered to the train. That can take additional hours.
When putting together a trip that involves a long-distance train, plan on the train being late! Be very wary of making connections—and not just from one train to another. What if your train to Los Angeles is so late you miss a World Series game or a Bruce Springsteen concert? Worse, what if you miss an important family event—a wedding or a funeral—because you were counting on your train being on time or close to it?
And so my best advice continues to be: Don’t take a chance. Add a day to your schedule, spend a night in a hotel, and continue on the next day relaxed and refreshed. It beats the hell out of all those alternatives!
This is why I won’t travel on a train. I can’t take extra time because Amtrak can’t keep even close to schedule!
Think of it this way: Your train travel is not simply a mode of transportation, it is PART of your vacation experience, and in that case, being late by a few hours is of no consequence.
Back in 2014 we were about an hour late into Emeryville from Seattle. Actually I would not have minded being later as I could not book into my hotel but had to leave my bags and wander. I had been many hours late travelling across on the Empire Builder from Chicago to Glacier National Park then on to Seattle (about 8 hours late). Anyway my car attendant said Amtrak is not late if it arrives the day it is suppose to.
You all but described the trip I just completed. On the last leg I didn’t trust the two hour SW Chief/Coast Starlight connection in LA, so I booked a hotel. Sure enough the Chief arrived on the advertised. There are always things to do in LA I spent a productive day. My Starlight ended up arriving in Tacoma five hours late. But, I felt like the Brit. My dinner partners agreed when I said that I’d rather spend the five hours on a late train than on an on-time airplane.
I was under the impression that the Amtrak was virtually always late, so I was surprised when my train arrived early.
Every so often, they fool ya.