Home Open Account Help 319 users online

Passenger Trains > Service Disruption #29 ?


Date: 08/21/16 00:13
Service Disruption #29 ?
Author: Vistadomescott

Anyone know why Capitol Limited #29 shows a Service Disruption tonight 8/21 through Cleveland from Washington?

Posted from Android



Date: 08/21/16 05:10
Re: Service Disruption #29 ?
Author: joemvcnj

Expected 2-1/2 lat at Toledo, already past Sandusky. Something happened between Pittsburgh and Alliance. It seems to have had an effect on 49 too.



Date: 08/21/16 05:20
Re: Service Disruption #29 ?
Author: RevRandy

I don't see why something happening between Pittsburgh and Alliance should have an effect on 49.  Remember, correlation is not causation.
 



Date: 08/21/16 06:23
Re: Service Disruption #29 ?
Author: milkcow

We understood while waiting at Alliance OH that 29 was involved in a trespasser incident just leaving Pittsburgh.

Posted from Android



Date: 08/21/16 08:11
Re: Service Disruption #29 ?
Author: altoonafn

http://www.wpxi.com/news/2-hit-killed-by-train-in-ambridge/427447779

Hit two trespassers around Ambridge

Posted from iPhone



Date: 08/21/16 08:12
Re: Service Disruption #29 ?
Author: joemvcnj

Ambridge, PA:  2 raced #29 to a crossing and paid the ultimate price of losing:

http://triblive.com/news/regional/11008608-74/train-ambridge-police



Edited 2 time(s). Last edit at 08/21/16 10:54 by joemvcnj.



Date: 08/21/16 16:28
Re: Service Disruption #29 ?
Author: andersonb109

Why is a train only 2+ hours late into Service Disruption? It wasn't annulled. Just late. 



Date: 08/21/16 16:47
Re: Service Disruption #29 ?
Author: milkcow

Sure scared us sitting at Alliance at 1:15 am. Then Julie was tied up with an endless set of recordings. Finally one person on the platform announced that on Trackatrain 29 was moving again @ 72 mph.
And of course several endless container and manifest trains drug by going west. We passed a couple after Waterloo and two more near Hobart.
David

Posted from Android



Date: 08/21/16 21:50
Re: Service Disruption #29 ?
Author: ProAmtrak

Those idiots sure did screw up a good run for not only 29, but whatever freights in the area too!

Posted from Android



Edited 1 time(s). Last edit at 08/23/16 19:30 by ProAmtrak.



Date: 08/22/16 03:44
Re: Service Disruption #29 ?
Author: MILW86A

Explains why the regular Toledo crew got dog caught at South Bend. I was on 30.

MILW86A

Posted from Android



Date: 08/22/16 14:11
Re: Service Disruption #29 ?
Author: Tominde

MILW86A Wrote:
-------------------------------------------------------
> Explains why the regular Toledo crew got dog caught at South Bend. I was on 30.
>
> MILW86A


Why would at strike with 29 cause crew on 30 to be out of hours?   Not sure I follow.



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