NW cannonball
Conductor
Good. I expect the Spokane people have some experience dealing with such disruptions, like the endpoint folks deal with from time to time also.It just means that 8(15) is starting from Spokane, not Seattle.About the knock-on effects of this disruption - I checked status at amtrak.com for #8 for today at Seattle, Everett, Leavenworth, Spokane, Whitefish, and MSP - only get Information Unavailable: Sorry, due to a service disruption, we are unable to provide estimated departure and arrival times. For additional assistance, please contact us at 1-800-USA-RAIL
Since I'm not scheduled on this train #8(15) I won't bother Julie - but looks like Seattle didn't have enough spare equipment to let #8 (15) depart SEA .
Where the set that failed on #7 in MSP are now, or whether in-service - who knows?
Looks like the problem is cascading (no pun).
They (amtrak folks) have practical experience and logistic skills.
I remember about 18 months ago on the westbound 7 where the eastbound had engine problems, we on (7) gave engines to eastbound (8) and got a BNSF unit to go on to SEA. All done in the middle of night at Spokane while I walked up and down the long platform there trying to understand all the engine moves -- and #7 was less than an hour late at Everett (where my daughter was at first surprised that the big orange oncoming engine was actually the train that dada was on) Long ago incident.
Hope this current one works out as well.
Last edited by a moderator: