Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

onehandle

(51,122 posts)
Wed Jun 10, 2015, 11:16 AM Jun 2015

NTSB: Amtrak engineer wasn't using cellphone during derailment

Source: Philadelphia Inquirer

The Amtrak engineer driving Train 188 when it crashed last month in Frankford, killing eight and injuring more than 200, was not using his cellphone during or before the deadly derailment, the National Transportation Safety Board announced this morning.

NTSB analysis of engineer Brandon Bostian's phone records shows no call, text or data usage occurred while he was operating the train - nor did Bostian access the train’s Wi-Fi system while he was at the controls. Bostian, who was injured in the May 12 nighttime disaster, had told investigators he doesn't remember anything in the minutes before or during the crash.

In the days after the crash, the NTSB found that the train was traveling at 106 mph - more than twice the posted speed limit at the curve in the tracks where the train derailed.

Investigators found no problems or malfunctions with the signals systems, the NTSB has also said. That leaves speed and a lack of proactive safety technology as the primary problems NTSB investigators have uncovered so far. Several passengers have filed lawsuits focusing on the train's speed, as well as Amtrak's failure to implement mandated technology such as Positive Train Control in the area where the crash occurred.

Read more: http://www.philly.com/philly/blogs/dncrime/NTSB-Amtrak-engineer-wasnt-using-cellphone-during-derailment.html



Related:

Murderous House GOP measure would cut Amtrak by $242M
http://www.democraticunderground.com/10141114099
17 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
NTSB: Amtrak engineer wasn't using cellphone during derailment (Original Post) onehandle Jun 2015 OP
Well, that's a good thing, I guess. TheCowsCameHome Jun 2015 #1
This could have been prevented by descreased regulation and a tax break for billionaires Orrex Jun 2015 #2
And more guns. nt DRoseDARs Jun 2015 #6
Yes. Always more guns. Orrex Jun 2015 #8
Clearly. onehandle Jun 2015 #16
I'm betting fatigue. Brickbat Jun 2015 #3
Never Thought RobinA Jun 2015 #4
Surely it wasn't totally outside the realm of possibility? Nye Bevan Jun 2015 #7
To My Way RobinA Jun 2015 #9
Finally,the cell phone thing is over. Wellstone ruled Jun 2015 #5
Didn't something hit Liberalagogo Jun 2015 #10
That hasn't been ruled out. I wonder if the driver was knocked out riderinthestorm Jun 2015 #12
The inspection did rule that out. nt onehandle Jun 2015 #15
This is turning out to be something of a mystery matt819 Jun 2015 #11
The union has said that it was caused by fatigue. Xithras Jun 2015 #13
It may be fatigue. I've said that the curve where the accident happened... onehandle Jun 2015 #14
This Was My RobinA Jun 2015 #17

Orrex

(63,224 posts)
2. This could have been prevented by descreased regulation and a tax break for billionaires
Wed Jun 10, 2015, 11:57 AM
Jun 2015

Thanks, Obama.

onehandle

(51,122 posts)
16. Clearly.
Wed Jun 10, 2015, 08:17 PM
Jun 2015

Guns could have been fired into the darkness, producing a counter-effect to re-balance the weight of the train.

The ever so dreamy gun can do anything...

RobinA

(9,894 posts)
9. To My Way
Wed Jun 10, 2015, 01:14 PM
Jun 2015

of looking at it it was pretty unlikely given the facts. I don't think talking on a cell phone would cause a person to go speeding down the tracks at twice the speed limit. Cell phone distraction maybe if he blew a stop signal or some other inattention thing. You have to actively speed up a train, it's not something that would happen while gabbing to a friend.

 

Wellstone ruled

(34,661 posts)
5. Finally,the cell phone thing is over.
Wed Jun 10, 2015, 12:19 PM
Jun 2015

Remember what the fellow said after the wreck,he had to rummage through his day bag to find his phone in order to make a 911 call. Check the F--n on board computers,these have been known to crash. Blame the operator first,duh,check the equipment.

 

Liberalagogo

(1,770 posts)
10. Didn't something hit
Wed Jun 10, 2015, 01:18 PM
Jun 2015

the front or the windshield of the train. I though I heard that. Was that ruled out?

 

riderinthestorm

(23,272 posts)
12. That hasn't been ruled out. I wonder if the driver was knocked out
Wed Jun 10, 2015, 06:36 PM
Jun 2015

by whatever hit the windshield.

It's about the only thing that makes sense.

He got knocked unconscious and fell against the accelerator.


matt819

(10,749 posts)
11. This is turning out to be something of a mystery
Wed Jun 10, 2015, 04:38 PM
Jun 2015

The engineer doesn't come across as being a nut, or suicidal, or irresponsible, and yet there he was, going twice the speed limit, so far with no explanation.

I wonder whether it might be helpful to call in outside experts from Europe or Japan. Of course, they'll laugh at the state of our infrastructure, but they may have a new take on the accident and help come up with an answer.

Xithras

(16,191 posts)
13. The union has said that it was caused by fatigue.
Wed Jun 10, 2015, 07:07 PM
Jun 2015

Amtrak implemented new schedules a few months ago that made engineer schedules more erratic, shortened their downtime, and made it impossible to put your body on a regular sleep schedule. The union has been fighting the proposal since late last year, and as recently as last March filed a petition with the Federal Railroad Administration asking for an emergency audit because the schedules would dramatically increase fatigue and danger to both train passengers and bystanders. In spite of members of Congress expressing support for the workers, Amtrak fully implemented the schedule changes a couple of months ago.

Bostian has said that he wasn't fatigued, but his union has stated that he was, and there's some indication that Bostian's statement may have been ass-covering.

onehandle

(51,122 posts)
14. It may be fatigue. I've said that the curve where the accident happened...
Wed Jun 10, 2015, 08:09 PM
Jun 2015

...is the last curve of several as you leave 30th Street Station. I live minutes away from the station and the crash site.

Usually the train speeds up considerably after that curve towards stops in New Jersey and beyond.

I think the engineer thought he was past that curve. Without the electronics that the murderous GOP House is denying them, it would be an easy mistake to make in the dark. Especially if you were fatigued, thanks to the murderous GOP House's cuts to manpower.

Did I mention that this Republican Controlled House are a bunch of Murderous Bloodthirsty 99% hating GOPNRAteahadist thugs?

RobinA

(9,894 posts)
17. This Was My
Thu Jun 11, 2015, 08:32 AM
Jun 2015

theory before they started down the "something hit the train" path. I am familiar with this route, but not engineer-familiar. When I read that it was the last curve before they speed up, it was night, he seems to have purposely speeded up and then eventually tried to panic stop... It seemed reasonable to me that he lost his place and thought he was past the curve and then tried to save the situation when he saw the curve. Too late. Fits the facts so far released. Reeks of fatique.

If this is what happened, he wouldn't even necessarily know he was fatiqued. Fatiqued doesn't mean "falling asleep," particularly in this job that requires a fair amount of attention. Plus, I would guess that there's a certain amount of habituation to operating while fatiqued in this field. Even had he been falling asleep on his feet, my bet would be he couldn't step off the train in Philadelphia and said, Oh sorry, I'm too tired to finish this trip.

Latest Discussions»Latest Breaking News»NTSB: Amtrak engineer was...