Home Open Account Help 339 users online

Passenger Trains > Train #8 (30) - Mechanical Failure, Waiting on Rescue


Pages:  [ 1 ][ 2 ] [ Next ]
Current Page:1 of 2


Date: 08/31/24 06:57
Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

So Train #8 (30) Empire Builder is stuck east of Ephrata, while Train #7 (29) is also now delayed waiting on Train #8 (30) to clear the way. Train #8 (30) will be running OVER 8 hours late and hopefully there will be a spare ALC42 or P42 in Spokane, but highly doubtful. Otherwise it gets a freight unit all the way to Chicago.......Meanwhile if Train #7 (29) doesn't get to Seattle in less than 2 hours late, it will have a delayed departure starting a new cycle of delays for the Empire Builder. UGH!As of 7:40 AM MT Service Update: Train 8 remains stopped east of Ephrata (EPH). The rescue freight train is in the process of adding the engine to bring train 8 into Spokane (SPK). A delay of over 8 hours is expected once on the move. We sincerely apologize for the inconvenience during this delay. Updates to come.

As of 6:49 AM PT Service Update: Train 7 remains stopped east of Ephrata (EPH) due to a disabled train blocking the route ahead. A rescue freight train is assisting to get the disabled train back on the move. Updates to follow as more information becomes available.

 



Date: 08/31/24 07:46
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: G600DRVR

8 is back underway, estimating 8:45 minutes late at Spokane. They will keep the freight engine for the duration of the trip. Amtrak does not keep spare equipment anywhere except for base terminals. 



Date: 08/31/24 08:27
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: ts1457

Does the Seattle section get only one locomotive?

Is the train running without HEP?



Date: 08/31/24 08:34
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

ts1457 Wrote:
-------------------------------------------------------
> Does the Seattle section get only one locomotive?
>
> Is the train running without HEP?

The Portland section gets one locomotive WEST of Spokane, as does the Seattle section. 

Portland Section these days: 
- Superliner Sightseer Lounge
- Superliner Coach
- Superliner Coach/Baggage
- Superliner Sleeper

Seattle Section these days: 
- Baggage
- Superliner Trans-Dorm Sleeper
- Superliner Sleeper
- Superliner Sleeper
- Superliner Diner
- Superliner Coach

The 2nd Seattle Superliner Coach went to the Southwest Chief just recently. 

Amtrak used to keep a spare locomotive in Spokane that rotated to/from Portland and the Empire Builder train set at one time. But that practice seems to be LONG over!



Date: 08/31/24 08:42
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: ts1457

jp1822 Wrote:
-------------------------------------------------------
> ts1457 Wrote:
> -------------------------------------------------------
> > Does the Seattle section get only one locomotive?
> >
> > Is the train running without HEP?
>
> The Portland section gets one locomotive WEST of
> Spokane, as does the Seattle section. 

Thanks, so if the disabled Amtrak unit is not able to provide HEP, east of Spokane the locomotive from Portland should be able to take care of it.



Date: 08/31/24 09:44
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

ts1457 Wrote:
-------------------------------------------------------
> jp1822 Wrote:
> --------------------------------------------------
> -----
> > ts1457 Wrote:
> >
> --------------------------------------------------
> -----
> > > Does the Seattle section get only
> one locomotive?
> > >
> > > Is the train running without HEP?
> >
> > The Portland section gets one locomotive WEST
> of
> > Spokane, as does the Seattle section. 
>
> Thanks, so if the disabled Amtrak unit is not able
> to provide HEP, east of Spokane the locomotive
> from Portland should be able to take care of it.

Absolutely - as long as it is functional!!! If not, then they got problems!!!



Date: 08/31/24 13:52
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: NPRocky

Given all of Amtrak's engine problems, I'm frankly surprised that BNSF allows Amtrak to run the Empire Builder through the Cascade Tunnel (nearly 8 miles long) with only one unit.  I'd call that a risk.  The Seattle section used to have two units assigned all the time between Seattle and Spokane, not just in winter.



Date: 08/31/24 14:30
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

At this point, I am surprised BNSF doesn't require Amtrak borrow one of their freight units to tie on the front of the Empire Builder sections ALL the time with all that they've been through. Course BNSF has its freight train failures too......



Date: 08/31/24 14:54
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: NPRocky

Given all of Amtrak's engine problems, I'm frankly surprised that BNSF allows Amtrak to run the Empire Builder through the Cascade Tunnel (nearly 8 miles long) with only one unit.  I'd call that a risk.  The Seattle section used to have two units assigned all the time between Seattle and Spokane, not just in winter.



Date: 08/31/24 15:22
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: MEKoch

Amtrak is totally incapable of managing LD passenger trains. Any other company would have spare locos properly placed. Would have larger extra boards of operations crew. Would not stored any cars during COVID. Would not allow Chicago to become a maintenance nightmare. ETC.

Posted from iPhone



Date: 08/31/24 15:39
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

I cringe to say this, but perhaps Amtrak runs within its semicircle near-all electrified territory from Washington DC to Harrisburg to Albany to Boston, and anything outside the circle goes to an Amtrak 2.0 of some sort (different objectives, funding arrangement, operations/logistics). I mentioned this causally pre-COVID, but maybe there is some sort of merit. Amtrak and Amtrak 2.0 have different operating objectives. PAINS me to say that, and I am doubt that will even work, but it's more than just mechanical and other failures, it's a constant yin-yang battle that's become very divergent in the past two decades. OR, at least cast off the LD trains and leave the semi-circle and State Corridors to Amtrak. But even that creates a bifurcated system. UGH! The genesis of this post is NOT from this particular issue - it just helps fuel the argument for some. Acceptance of the status quo Amtrak is an oxymoron - it's NOT acceptable and hasn't been. 



Date: 09/01/24 09:23
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

Now running 14 hours late coming into Minot, ND. Amtrak has ETA into Chicago at 3:15 am. I think 6 am is a more realistic estimate, at best! I doubt Amtrak had any sense to try and forward an ALC 42 to say Twin Cities on the Borealis service so it could at least drop the freight locomotive and pickup some time.......They had yesterday and today to try and make that maneuver. The lack of action or rather inaction for stuff like this is just mind blowing. Amtrak of the 80s and 90s would have sent an extra unit out on Train #7 (31). The current issues were know before Train #7 (31) left Chicago. I know the excuse - no spares. UGH! Incompetence with logistics and operations drives me NUTS!



Date: 09/01/24 09:28
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: restricted_speed

MEKoch Wrote:
-------------------------------------------------------
> Amtrak is totally incapable of managing LD
> passenger trains. Any other company would have
> spare locos properly placed. Would have larger
> extra boards of operations crew. Would not stored
> any cars during COVID. Would not allow Chicago to
> become a maintenance nightmare. ETC.

Reducing extra boards, eliminating spare locomotives etc. all "cut costs" and add to executive bonuses.



Date: 09/01/24 09:59
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: Drknow

Pass the paper bag that holds the bottle…

Regards

Posted from iPhone



Date: 09/01/24 10:10
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: NPRocky

The Empire Builder Facebook page quotes a member who apparently was on the train as saying a coolant leak was the problem.



Date: 09/01/24 11:03
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: wpdude

IF I ever ride amtrash again, I will definitely bring a bottle of booze in my grip!



Date: 09/01/24 14:31
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: filmteknik

So they sat there for 8+ hours with no HEP? What if it was in daytime heat or a cold winter day?



Date: 09/01/24 20:38
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: illini73

I know this is the Passenger Trains board, but I have to wonder:  What was the effect on BNSF freight trains in the area if the main track was blocked for 7+ hours?  I suppose eastbound freights following #8 out of Wenatchee, WA by more than an hour (#8's running time to Ephrata) could have been held there, but it must have spelled hours-of-service trouble for any westbounds already out of Spokane.



Date: 09/01/24 21:59
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: filmteknik

If an eastbound was coming why not just push Amtrak on to Spokane?



Date: 09/02/24 03:06
Re: Train #8 (30) - Mechanical Failure, Waiting on Rescue
Author: jp1822

In addition to the amount of time the Empire Builder held up the BNSF railroad, here's what I find also a bit ironic.......from Whitefish, MT to Milwaukee, WI, the Empire Builder ran with a freight locomotive and lost only 2 hours enroute. It's not good, but it's also not that bad. I did see the speed of the train reached nearly 70 mph for sections across eastern Montana and North Dakota. And as suspected, this train, if no more other delays, will be rolling into Chicago Union Station this morning around 7 am. 



Pages:  [ 1 ][ 2 ] [ Next ]
Current Page:1 of 2


[ Share Thread on Facebook ] [ Search ] [ Start a New Thread ] [ Back to Thread List ] [ <Newer ] [ Older> ] 
Page created in 0.0537 seconds