| Home | Open Account | Help | 335 users online |
|
Member Login
Discussion
Media SharingHostingLibrarySite Info |
Passenger Trains > Odd delay west of PorterDate: 09/19/21 14:21 Odd delay west of Porter Author: twropr WOLVERINE 353 passed CP 482 and was poised for an early arrival at Chicago, until receiving a stop signal at CP 497. NS' Chicago Terminal DS said there was a track light ahead and wound up reversing the train to CP 494. After resuming travel west, 353 crossed over to TK 2 at CP 496. The train left Hammond 31 min LT, and due to the magic of padding, arrived CHI on time.
Apparently WOLVERINE 352 was held at CP 501 for 353 as it passed 482 about 15 min LT. Andy Date: 09/19/21 14:55 Re: Odd delay west of Porter Author: DevalDragon Sounds like the NS dispatcher made up for Amtrak mechanical's incompetence.
Date: 09/19/21 14:56 Re: Odd delay west of Porter Author: splitreduction Uhhh how would a track indication popping up be Amtrak Mechanical departments fault???
DevalDragon Wrote: ------------------------------------------------------- > Sounds like the NS dispatcher made up for Amtrak > mechanical's incompetence. Posted from iPhone Date: 09/19/21 17:00 Re: Odd delay west of Porter Author: DevalDragon Because the WILD detector indicated the track circuit was caused by the axle on an Amtrak train.
Date: 09/19/21 18:40 Re: Odd delay west of Porter Author: DirtyShirt Wow, so an Amtrak axle had wheels with flat spots bad enough that they set off a WILD detector and broke a rail? That's a rough ride. Surely the problem axle was on a locomotive, not a passenger car. Please tell more if you can.
DevalDragon Wrote: ------------------------------------------------------- > Because the WILD detector indicated the track > circuit was caused by the axle on an Amtrak train. |