Amtrak On-Time Performance (OTP) Delays Reroutes Annulled

Looks like something amiss in Philadelphia tonight. There's nothing that hasn't lost an hour there. Snow, maybe?

This is from much earlier but still going on.
Amtrak Northeast
‏
Verified account

@AmtrakNECAlerts
1h
1 hour ago


More
Service Disruption: Due to signal power issues between Trenton (TRE) and Philadelphia (PHL), all service through the area is currently suspended. Maintenance crews are en route. We will update as more information becomes available

Weather related outages north of PHL are causing issues up and down the NEC, including cancellations.

Also next week, hearing that 151 is cancelled on Tuesday and Wednesday, and 136/196 combined cancelled on Wednesday. MARC will cover WAS to Perryville.

The fun continues:
SERVICE ADVISORY KEYSTONE LINE: Due to a down tree on the tracks the following adjustments have been made. Trains 601, 605, 607 are cancelled no alternate transportation; Trains 640, 642, 600 will operate PHL-NYP only no alternate transportation HAR-PHL.

2:44 AM - 16 Nov 2018
(Apologies in advance if this belongs on the Keystone Forum.)

They actually picked up enough branches to operate 607.

30 (16) made it as far as the throat of Union Station. We've been stopped here for about two hours now. The conductor has told us the cab signals were not functioning (or not tested), so we're waiting for mechanical to fix them. Also, he mentioned the conductors (but bizarrely not the engineer) were on short time. Do long distance C&E pools swap at different locations?

CNJGeep wrote:30 (16) made it as far as the throat of Union Station. We've been stopped here for about two hours now. The conductor has told us the cab signals were not functioning (or not tested), so we're waiting for mechanical to fix them. Also, he mentioned the conductors (but bizarrely not the engineer) were on short time. Do long distance C&E pools swap at different locations?

You're not showing up at all on the track-a-train map, although allegedly due in PGH about 7:30.

The Engineer may have started the trip after proper time off and rest, while the Conductor may have recently worked another train.

With all the current Wildfires in Ca this past week,is the Coast Starlight running,or has UP shut down the Coastline Sub due to fire damage??

30 (16) managed to lose more time during the night and we're currently five hours down at Cleveland.

CNJGeep wrote:30 (16) managed to lose more time during the night and we're currently five hours down at Cleveland.

Out of curiosity, what's the mood of the riders and the crew...and are they saying anything about the cause of the delays? Hope you weren't planning to connect with 42!

Does anybody know why eastbound "Wolverine" #354 (16th) lost about 6'00" from CHI to Michigan City??

ohioriverrailway wrote:

CNJGeep wrote:30 (16) managed to lose more time during the night and we're currently five hours down at Cleveland.

Out of curiosity, what's the mood of the riders and the crew...and are they saying anything about the cause of the delays? Hope you weren't planning to connect with 42!

UPDATE: took 24 hours and change to make the trip.

The initial Chicago conductor explained the cab signal issue, but other than that most of the announcements we got were "Sorry for the delays, the next station will be ___," "We are caught behind/waiting for freight traffic."

There were some passengers continuing on to 97 and 19 in Washington, who were less than thrilled. Amtrak did a good turn here, though, and held those two trains for the connecting passengers. Passengers Baltimore-NY were placed on Train 90, and passengers going beyond NY were moved to 66.

Cab signals? There shouldn't be cab signals on the NS Chicago Line. Did Amtrak hold up the train short of 21st St? That should not be cab signaled either.

NS installed PTC on the NS Chicago Line but it is not active except for a couple of test freight trains. The "Cab Signals" comment seems bogus (and there are procedures to keep the trains moving even if cab signals fail).