Amtrak On-Time Performance (OTP) Delays Reroutes Annulled

Amtrak and MARC police out on the tracks near West Baltimore station in Maryland at 8:06am EST. Any word on why?

Signal issues on the NEC for track 3 around GROVE near Odenton, MD. Trains taking a 10-15 min hit.

Does anybody know why #29 (9th) westbound Capitol Limited lost 3' 10" from WAS to Rockville?????

shlustig wrote:Does anybody know why #29 (9th) westbound Capitol Limited lost 3' 10" from WAS to Rockville?????

No idea. But it reminds me of an enjoyable ride on that same route that also got delayed a few hours in the same stretch. In that instance, we pulled out of WAS on time and went only a short distance (not even clear of the platform) before stopping. An announcement said there was a signal problem. After a while, an announcement said the signal problem was fixed!, and off we went, but for only another few feet. We were still on the platform! We lingered there without any announced explanation for a long time. During that time there were several irate announcements, but they were instructing crew, not passengers. Turns out the signal had been against us, the signal problem had been "fixed" but the signal was contrary, so there had been a violation and the crew had to observe a certain ceremony and then another crew had to be brought aboard. After a while, that was all done and we steamed out of D.C. and across the Maryland line before stopping again in Silver Spring. A car attendant said there was a problem with the hoses and they would reconnect them. Later, the attendant said the hoses were found to be damaged, so they had to order parts sent from Washington. We were parked at the quietly dignified ruins of an abandoned train platform on a bridge, and everyone stepped out for an unhurried look at downtown Silver Spring. Medics came and ministered to a passenger who felt faint. By and by, we resumed the journey and reached Chicago less than 6 hours late.

Does anybody know why #351 (12th) westbound wolverine on the DET Corridor lost 4' 15" from DET to Dearborn; was 6' 00 " late into CHI.

Does anyone know the issues on the Keystone Corridor today? 640 was around an hour delayed into 30th St this morning and westbound trains were also seeing 45-60 minute delays around Exton.

Amtrak power issues resulted in suspended service between Thorndale and Malvern for a period of time Wednesday morning.

shlustig wrote:Does anybody know why #29 (9th) westbound Capitol Limited lost 3' 10" from WAS to Rockville?????

Hmmm... Usually it's one of the following:

1. A long freight broke down with numerous HAZMAT materials in that area and inspecting it took time.
2. A derailment happened.
3. Since there was many at-grade crossings, ether a person or a car was hit by a freight.
4. A rail break, and CSX crews were out to fix it.
5. Big signal issues around QN.

A quick check of the news crosses off #2 and #3, and the weather makes #4 and #5 more likely, since temperatures were dropping like a rock past noon.

Does anybody know why #352 (13th) eastbound wolverine on the DET Corridor lost 2' 35" at Battle Creek??

Does anybody know why #22 (13th) eastbound Texas Eagle on AM of 14th Ar. @ STL 49" Early and Dp. 2' 54" late; Ar. CHI 3' 45" Late.

Does anybody know why westbound DET Corridor Wolverines #'s 351 and 355 (16th) lost 5'00" and 2'55" respectively from Pontiac to Dearborn?

A friend in Texas sent me a note saying the Texas Eagle hit a loaded tractor trailer at a grade crossing in San Marcos TX at 7:51 PM Monday night December 18th. He did not provide the train number, so I must assume it was train 21 based on the location and time of day. He did not specify how long the train was delayed.

According to KXAN, 1 hour and 50 minutes on Texas Eagle Amtrak 21. https://kxan.com/2017/12/18/amtrak-trai ... an-marcos/" onclick="window.open(this.href);return false;

Does anybody know why DET Corridor Wolverines #'s 354 and 355 (19th) each lost about 6'15" in the vicinity of Kalamazoo???

Anyone know why the EB Cardinal #50 was held in eastern Indiana for 10 hours?