The major problems besieging 5 are mostly due to bad luck. Can't do much about mudslides and packs of dogs.
Wouldn't surprise me a bit.Wait till you see strident complaints appear here about how Amtrak mismanagement has caused it not to have ordered completely dog proof rolling stock
Montana Mike, thanks. I will be traveling through there in a few weeks. It will be interesting to see lights blazing away, especially since I am going home and don't have to make a connection in Chicago. Maybe an early fall snow storm too...According to BNSF their work schedules revolve closely around the train schedules and often that means they work 24/7. Not a traditional 9 AM to 5 PM workday for some of the track efforts. I have been on the EB this summer several times already and saw BNSF crews, with lights blaring away, working at all hours of the night. Clearly the daytime is the ideal time, but the number and timing of trains passing through a certain area often outweigh the convenience of working during those hours. Being on a track crew is dirty, dangerous and just downright hard work. I think we are just seeing the modest winding down of planned efforts in certain areas, which is allowing the EBs to get thru with fewer delays--today's EB into CHi-town was a "mere" 45 minutes late--hurrah!!
Ha! Thanks for all the great info these past few months. When we determined our route was the Builder, I have been watching this thread with great interest. We are leaving on a Friday the first part of October, so the delays might be mitigated a bit, according to what you have been posting. I will try to post from the train if I get cell service in the delay zones.Empire Distress!
Surprised they didn't hold it. Usually they do. Any reason why they wouldn't?Yeah, it strained connections all right. I was on 6 and we've been here about half an hour. And 8 is just arriving. Just muddling through the mass confusion at Passenger Services as the Cardinal and CL were not held.
FARGO - The train is late.
Again.
It’s 2:30 a.m. on a Friday, and the Amtrak train that hauls passengers east was supposed to be here 15 minutes ago.
Seventeen minutes, actually, if you’re a stickler for that sort of thing.
Fifteen people, spread among rows of plastic chairs inside Amtrak’s station in downtown Fargo, busy themselves with the kind of chatter that surfaces when strangers spend time together waiting. The heat and its impact on this year’s harvest. Daughters, sons and grandkids. Two men discuss Montana’s amateur boxing circuit from the ’60s and ’70s.
A whiteboard behind the counter cautions that the train heading west, through Minot and Williston to the Pacific Northwest, isn’t expected until 4 a.m. – 30 minutes behind schedule.
The train heading east is even worse. It won’t be in until 5 a.m.
Amtrak’s Empire Builder, which connects Chicago with Seattle and Portland, Ore., is scheduled to arrive daily in Fargo in the dead of the night. But its actual time of arrival more often creeps close to dawn.
Delays in Fargo, long and often, have made the station and others on the Empire Builder a particular concern for Amtrak, which has struggled for years with delay times on its 15 long-distance tracks.
The eastbound train has not been on time in more than four months and just three times so far this year, according to Amtrak records. It’s been six or more hours late twice as often as that in 2013.
Three times since 2008, it has arrived in Fargo a full day late. The average delay since 2008 is 114 minutes, according to an analysis of the company’s records.
Spokesman Marc Magliari said ongoing track maintenance that requires trains to travel slower has been a big factor, including a major, two-year project to protect the railroad from Devils Lake flooding. He hopes the route will be on-time more often when that work is complete, possibly by November....
Looks like it will be 2 hours late arriving today-bummerI had friends who were on 27 last Sunday into PDX and they said they arrived 37 min early. So, I guess it can be done.
I know they need to do the work, but it is interesting how almost that entire segment is now subject to slow orders (and thus the 4+ hour delays into CHI). I have asked my BNSF contacts about this situation and they have all said while active track work is ongoing it is the railroad's policy to keep those speeds down to an absolute minimum-more so for the safety of the crews working on the tracks. The newly improved track beds and rails do indeed require a short and modest "break-in" period, but not at the very low speeds now mandated for crew safety. It is what it is. The November estimate by Amtrak's spokesperson for the reduction or completion in this year's track efforts appears to be accurate according to my MT BNSF folks. These projects are slated to end in the 2nd week of November and then resume about 5-6 months later next Spring!I was on the eastbound 8/28 Thursday night into Friday morning. I could not believe how many stretches between Grand Forks and Fargo where I heard "yellow flag 30" on the scanner, stretches where one or two years ago they were sailing at 60-65mph. It also appeared there were signaling troubles right off the bat Tuesday morning on the Devils Lake line just west of the Grand Forks depot, which plagued the westbound EB.
#8 heading east in MN is now 5 hours late--looks like a very late arrival in CHI tonight--bummer.Looks like it will be 2 hours late arriving today-bummerI had friends who were on 27 last Sunday into PDX and they said they arrived 37 min early. So, I guess it can be done.
I'm in the Metropolitan Lounge in Chicago now and the reader boards indicate a 9pm arrival for thr EB. I hope those folks on it who miss their connections enjoy the free breakfast buffet at the Willowbrook Holiday Inn as much as I did!#8 heading east in MN is now 5 hours late--looks like a very late arrival in CHI tonight--bummer.Looks like it will be 2 hours late arriving today-bummerI had friends who were on 27 last Sunday into PDX and they said they arrived 37 min early. So, I guess it can be done.
Enter your email address to join: