Home Open Account Help 208 users online

Passenger Trains > Amtrak 7 of the 13th


Date: 05/14/13 11:23
Amtrak 7 of the 13th
Author: sethamtrak




Date: 05/14/13 19:59
Re: Amtrak 7 of the 13th
Author: GenePoon

Nothing happened between Red Wing and St. Paul. 7(13) arrived St. Paul only four minutes late.

It lost a big chunk at St. Paul, departing 5:31 late and it has been losing time steadily ever since,
now about ten hours late.



Edited 1 time(s). Last edit at 05/14/13 20:00 by GenePoon.



Date: 05/14/13 22:08
Re: Amtrak 7 of the 13th
Author: kodachrome9319

Has BNSF 5031 on the point.



Date: 05/15/13 00:52
Re: Amtrak 7 of the 13th
Author: GenePoon

Besides the all-too-frequent story of an Amtrak engine going belly-up, there were HEP problems with
the remaining Amtrak power, that had to be fixed before departing St. Paul. Then there were slow
orders in northern North Dakota. Train has now disappeared into Service Disruption status, probably
because it has been decided to give up on it at Spokane and put the passengers on buses.



Edited 1 time(s). Last edit at 05/15/13 00:57 by GenePoon.



Date: 05/15/13 03:39
Re: Amtrak 7 of the 13th
Author: The_Chief_Way

terminates at Spokane



Date: 05/15/13 16:12
Re: Amtrak 7 of the 13th
Author: kodachrome9319

GenePoon Wrote:
-------------------------------------------------------
> Then there were slow orders in northern North Dakota.

Nothing out of the ordinary that'd delay it more.

It was held at Wadena, MN for high winds, then took a hit at MP 167.1 Glasgow Sub for an integrity failure, Oswego MT for rough track (possible broken rail). Had a decent trip to Spokane after it left Minneapolis, really.



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