offroad437
Service Attendant
- Joined
- Jul 14, 2014
- Messages
- 131
Not sure but I think the reports of the fatalities being on the ground would appear accurate. I would guess it was the crew with the backhoe.
Last edited by a moderator:
Nor will that Amfleet I right behind the engine.This article from Philly.com show the front end damage to ACS-64 #627. Pretty smashed up. That one will not be back in service for a while.
Philly.com
Yes, that is one seriously beaten up ACS-64. Saw the same photo on the Washington Post website, but your link is better for the photo.This article from Philly.com show the front end damage to ACS-64 #627. Pretty smashed up. That one will not be back in service for a while.
Philly.com
Not off subject to me, thanks. But I gather it will be a while until service returns WIL-NYP?A bit off subject but now service is moving between dc and Wilmington.
Currently using 2252's equipment to run as 88 up to Wilmington, and turn for 195 and head back to dc.
There is a path available for quite some time. Just awaiting for the OK from the scene.Through movement shouldn't be too much longerNot off subject to me, thanks. But I gather it will be a while until service returns WIL-NYP?A bit off subject but now service is moving between dc and Wilmington.
Currently using 2252's equipment to run as 88 up to Wilmington, and turn for 195 and head back to dc.
Why should you be surprised? There were numerous trains in that area with a very limited area to accomplish much. There are also crew constraints to contend with. Sending more trains into an area without a lot of maneuverability is usually not recommended, particularly if you're not taking the majority of the passengers were they want to go. Remember, you have MARC between WAS-BAL, so all you're really adding is WIL.I was really a bit surprised with the suspension of service between Washington and Baltimore and Wilmington. I guess the problem was stationing someone who could uncouple and couple engines at Baltimore or Wilmington.
Which makes me wonder if Amtrak keeps a contingency plan in place for closure of tracks in various segments of the system. Ideally there would be an outline playbook for handling track closures between any two major stops, since afterall there really are not that many to start with.
Thank you!There is a path available for quite some time. Just awaiting for the OK from the scene.Through movement shouldn't be too much longerNot off subject to me, thanks. But I gather it will be a while until service returns WIL-NYP?A bit off subject but now service is moving between dc and Wilmington.
Currently using 2252's equipment to run as 88 up to Wilmington, and turn for 195 and head back to dc.
Right. Good point.Why should you be surprised? There were numerous trains in that area with a very limited area to accomplish much. There are also crew constraints to contend with. Sending more trains into an area without a lot of maneuverability is usually not recommended, particularly if you're not taking the majority of the passengers were they want to go. Remember, you have MARC between WAS-BAL, so all you're really adding is WIL.I was really a bit surprised with the suspension of service between Washington and Baltimore and Wilmington. I guess the problem was stationing someone who could uncouple and couple engines at Baltimore or Wilmington.
Which makes me wonder if Amtrak keeps a contingency plan in place for closure of tracks in various segments of the system. Ideally there would be an outline playbook for handling track closures between any two major stops, since afterall there really are not that many to start with.
This conjecture makes sense. Logical. Interested to see cause for this effect.Looks suspiciously like the backhoe was actually working on track 4, but was partly and most likely unintentionally, fouling track 3 when 89 came by and got side swiped by the backhoe, spinning the backhoe around to have part of strike the first coach, while derailing the front truck of the engine. Just my guess from the multiple pictures and the layout of things.
Right. Good point.Why should you be surprised? There were numerous trains in that area with a very limited area to accomplish much. There are also crew constraints to contend with. Sending more trains into an area without a lot of maneuverability is usually not recommended, particularly if you're not taking the majority of the passengers were they want to go. Remember, you have MARC between WAS-BAL, so all you're really adding is WIL.I was really a bit surprised with the suspension of service between Washington and Baltimore and Wilmington. I guess the problem was stationing someone who could uncouple and couple engines at Baltimore or Wilmington.
Which makes me wonder if Amtrak keeps a contingency plan in place for closure of tracks in various segments of the system. Ideally there would be an outline playbook for handling track closures between any two major stops, since afterall there really are not that many to start with.
BTW, the only somewhat reliable info on what Amtrak trains are running in NJ at present appears to be NJ Transit's Departure Vision. The Amtrak train status stuff seem to be completely confused or stating many trains that are running to be is Disruption. Weird. And normally I trust the NJT Departure Vision less when it comes to Amtrak trains.
That is good to know since the status system hinted that they were cancelled or disrupted or something.51(3) and 79(3) operated through the area.
88 is showing service disruption (on Paul's site) and 2252 is showing as overdue. But, as stated above and on FB, 2252's train set is being used for 88. So, as mentioned before, switching the #'s, etc, messes the statuses up.That is good to know since the status system hinted that they were cancelled or disrupted or something.51(3) and 79(3) operated through the area.
I suppose track 1 was pretty much in the clear right? Track 2 was probably intruded upon a bit by the derailed ACS on track 3?
Enter your email address to join: