Amtrak On-Time Performance (OTP) Delays Reroutes Annulled

TheOneKEA wrote:http://blog.amtrak.com/2016/04/update-p ... -train-89/

Amtrak train #89 collided with a backhoe on the tracks south of 30th Street Station. The lead engine derailed after the collision. The blog posting says that there were 341 passengers and 7 crew members on board and that some people were injured. All service between NYC and PHL is suspended.

ABC news in Philadelphia reports two fatalities..opretator of the backhoe that was struck, plus one yet unidentified.
http://6abc.com/news/2-dead-in-amtrak-t ... d/1274225/

ohioriverrailway wrote:

TheOneKEA wrote:http://blog.amtrak.com/2016/04/update-p ... -train-89/

Amtrak train #89 collided with a backhoe on the tracks south of 30th Street Station. The lead engine derailed after the collision. The blog posting says that there were 341 passengers and 7 crew members on board and that some people were injured. All service between NYC and PHL is suspended.

ABC news in Philadelphia reports two fatalities..opretator of the backhoe that was struck, plus one yet unidentified.
http://6abc.com/news/2-dead-in-amtrak-t ... d/1274225/

A dedicated thread for that is here: viewtopic.php?f=46&t=162269" onclick="window.open(this.href);return false;

Amtrak 151 annulled 2016-04-04 per Maryland MTA notification via WBAL-TV.

#3(18) hit a person on the track near the US 550 station in Bernalillo, being held at the Downtown Bernalillo station
for the investigation,NMRX service also affected.
#3(18) was released at 6:20p local time,left ABQ at 7:31p local time,NMRX returning close to schedule.

Surpised nobody mentioned the brush fire on the meadowlands this afternoon, that cause moderate delays
http://image.nj.com/home/njo-media/widt ... 66ac18.jpg" onclick="window.open(this.href);return false;

Also train 494 just struck 2 trespassers in Wallingford CT

Does anybody know why:

#19 (19th) southbound Crescent Dp. NYP 1' 45" late; and

#63 (20th) westbound Maple Leaf shows no times after Dp. POK; shows "Service Disruption"

shlustig wrote:Does anybody know why:

#19 (19th) southbound Crescent Dp. NYP 1' 45" late; and

#63 (20th) westbound Maple Leaf shows no times after Dp. POK; shows "Service Disruption"

From the date, I suspect that the Crescent delay was covered in the post above yours...

AMT63(20) died just north of Hyde Park the air compressor on the 712 was the culprit. Not the first time this particular engine has had air issues. Passengers taken to ALB by AMT69 and later west on AMT281

Does anybody know why #313 (23rd) on the KCY Corridor lost 6'00" between Kirkwood and Washington, MO?

shlustig wrote:Does anybody know why #313 (23rd) on the KCY Corridor lost 6'00" between Kirkwood and Washington, MO?

Here's what a participant on the trainorders.com board says:
Been hearing on the radio that AMTK 52 broke down somewhere past Washington MO if anyone get pics of her new leader if anyone plans to go out for that night time move wouldn't mind seeing that for myself

Another post says that UP 8378 was the rescue power.
Andy

A rare mileage detour opportunity …

I have read (elsewhere) that on Monday April 25th, Amtrak Empire Service trains (presumably including 48/49 and 63/64) will temporarily detour between ALB and AMS, bypassing SDY, due to track work being performed by CSX. This will involve operating on the Carman Branch and the Selkirk Branch, CP 156 - South Schenectady - CP 169 Hoffmans.

Those of you who have been riding long enough will recall that this detour route was Amtrak's normal route thru the Schenectady area until around 1979-1980, at which time time NY DOT funded the return of passenger service to downtown Schenectady on the original New York Central route.

I will speculate that the Adirondack and the Ethan Allen Express will follow their normal route thru SDY since their connection to/from CP is at the west end of the Schenectady station.

Actually you would have had a better shot yesterday, CSX is pretty quick with theses types of repairs. The detour may be done by this afternoon. Now with 281/284 not running on the Mohawk for the next 12 weeks or so if you could get stuck in AMS until 64 gets in

Does anybody know why #314 (26th) lost 5'12" on the run. Looks like 2 separate happenings: 1' 20" right out of KCY and the remainder near JEF.

Railjunkie wrote:Actually you would have had a better shot yesterday, CSX is pretty quick with theses types of repairs. The detour may be done by this afternoon. Now with 281/284 not running on the Mohawk for the next 12 weeks or so if you could get stuck in AMS until 64 gets in

Hi RJ,
Listening to the Mohawk Feed on Sunday night I heard NC give #288 permission to run east of CP 169 for head room on the Selkirk Branch to meet #49, which ran on Amtrak's Hudson Sub. Were the switches at 169 still being worked on when that happened?
Any idea what other work is taking place between 169 and ?175?
Thanks!
Andy

Does anybody know what happened to #22 (29th) eastbound Texas Eagle; shows no times after Mineola, TX and was 19'30" late into CHI?'