Home | Open Account | Help | 393 users online |
Member Login
Discussion
Media SharingHostingLibrarySite Info |
Passenger Trains > Empire Builder (Westbound)Date: 11/28/22 12:30 Empire Builder (Westbound) Author: widowsihler Does anyone know what the wrinkle in the time-space continuum is that results in No 7 leaving Chicao on time and fetching up in Columbus an hour late? (And of course downhill from there.) It was OK three days ago but mostly it's the same old same old.
Date: 11/28/22 13:48 Re: Empire Builder (Westbound) Author: illini73 If it's 7 of the 27th you're referring to, sethamtraks last two posts have the explanation - Eng 301 had electronics issues at the first stop (Glenview, IL) and the ensuing consequences have him now over 4 hours late at Stanley, ND.
Date: 11/28/22 16:38 Re: Empire Builder (Westbound) Author: jp1822 BNSF freight locomotive called out to replace #301 - or provide lead power. Train #8/28 left its second unit at Minot so it could be added to the consist. Not sure if the BNSF freight loco was left on the lead, or the unit that #8/28 left behind is now leading. So in this case - we are looking at ALC42 issues that started just as the train left Chicago......... Train #7/27 running over 4 hours late in eastern Montana on evening of Nov 28. Ten years ago, Amtrak operations folks would be watching to see if this train needed to be short turned at Spokane so as to preserve an on time #8/28 returning back east. Lot of things ahead before the train reaches the West Coast that could make it later or try to keep it under at the 4 hour late mark.
Date: 11/28/22 17:06 Re: Empire Builder (Westbound) Author: MM171 jp1822 Wrote:
------------------------------------------------------- > Train #7/27 running > over 4 hours late in eastern Montana on evening of > Nov 28. Lets hope the head power keeps up. The deeper #7 gets into Montana the colder it will be. -4.0f at Browning tonight. Date: 11/28/22 21:01 Re: Empire Builder (Westbound) Author: illini73 widowsihler Wrote:
------------------------------------------------------- > Does anyone know what the wrinkle in the time-space continuum is that results in No 7 > leaving Chicao on time and fetching up in Columbus an hour late? The continuum is wrinkled again this afternoon - 7(28) OT out of Chicago, about an hour late at Columbus. Update: Not "downhill from there" this time, however: nearly all the time lost has been recovered from schedule padding; only 10 mins late out of Glasgow, MT Tuesday afternoon. The "wrinkle," when it appears, seems to be between Milwaukee and Columbus. Edited 1 time(s). Last edit at 11/29/22 12:42 by illini73. Date: 11/29/22 09:01 Re: Empire Builder (Westbound) Author: Oregonpaul Wasn't even 10 years ago trains would be turned at Spokane when late. Maybe a year or two.
Date: 11/29/22 10:01 Re: Empire Builder (Westbound) Author: wirelessenabled Amtrak 7 (27) through Otis Orchards, WA at 8:50 PST. I was late to the tracks but a BNSF locomotive was leading with 2 Chargers next. Too far away to determine what was running.
Date: 11/29/22 10:03 Re: Empire Builder (Westbound) Author: Oregonpaul Only 2 chargers? Did they leave broken 301 in Minot maybe?
Date: 11/29/22 10:06 Re: Empire Builder (Westbound) Author: NPRocky If we're lucky, today's 8 will get out of Seattle on about the old Western Star departure of 10 p.m. By the way, it's snowing in Western Washington this morning more than expected, and more, with some wind, is expected later today.
Date: 11/29/22 15:36 Re: Empire Builder (Westbound) Author: jp1822 Train #7/27 that's bound to arrive into Seattle/Portland today, 11/29, should have never been released west of Spokane. Here we go again with a cascade effect of trying to play catch-up on late trains across the Hi Line.......
Date: 11/29/22 17:05 Re: Empire Builder (Westbound) Author: ProAmtrak Put the P40s/42s back on the Builder ASAP, those ALCs are not the answer!
Posted from Android Date: 11/29/22 19:57 Re: Empire Builder (Westbound) Author: Pioneer2526 I was on the builder in march, 301 was the lead unit and it puked out then too.
Posted from iPhone |