Home | Open Account | Help | 311 users online |
Member Login
Discussion
Media SharingHostingLibrarySite Info |
Eastern Railroad Discussion > NS 8102 (PRR) leading 66WDate: 07/04/15 04:08 NS 8102 (PRR) leading 66W Author: TrainStalker Reported still at Conway 0642
Date: 07/04/15 05:11 Re: NS 8102 (PRR) leading 66W Author: EH49 Out of Conway a little after 8.
Date: 07/04/15 05:44 Re: NS 8102 (PRR) leading 66W Author: mw2007 If anyone sees whether it goes Conemaugh line or Pittsburgh line please post-thanks
Posted from Android Date: 07/04/15 06:06 Re: NS 8102 (PRR) leading 66W Author: TrainStalker 66W on CONL now (0906).
Date: 07/04/15 07:25 Re: NS 8102 (PRR) leading 66W Author: mw2007 Through taremtum 1010
Posted from Android Date: 07/04/15 11:23 Re: NS 8102 (PRR) leading 66W Author: reel_smooth Don't know what's going on in Altoona, but, there seems to be quite the traffic jam in both directions. Sounds like 66W is going to be stopping in or near Lilly and it's anybody's guess as to how long it's gonna be there. 10G is stoppoed at Cresson, I think there was at least one more stopped at the brickyard, and it doesn't seem like much has been moving westbound.
Date: 07/04/15 12:15 Re: NS 8102 (PRR) leading 66W Author: reel_smooth On the move again but will be holding at Cresson. Just knocked down the signal at MP254.
** Clear CP MO at 3:30 and is not holding there after all. ** Edited 1 time(s). Last edit at 07/04/15 12:33 by reel_smooth. Date: 07/04/15 12:33 Re: NS 8102 (PRR) leading 66W Author: mw2007 Anyone know what's causing backup ?
Posted from Android Date: 07/04/15 17:45 Re: NS 8102 (PRR) leading 66W Author: reel_smooth mw2007 Wrote:
------------------------------------------------------- > Anyone know what's causing backup ? > > Posted from Android Was listening to the West Slope feed at the time but was barely picking up the Altoona-East dispatcher and I'm not 100% sure, but, it sounded like it was computer related. Date: 07/04/15 19:11 Re: NS 8102 (PRR) leading 66W Author: Forever-Railfan-45 NS system went down today...short duration but they got it back up and running.
Posted from Android |