Comments on: BART Radio Communications Tell Tale Of Train Accident That Killed Two (Audio) http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/ SF Appeal: San Francisco's Online Newspaper Sun, 06 May 2018 15:59:00 +0000 hourly 1 https://wordpress.org/?v=4.9.24 By: John Smith http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24202 Mon, 21 Oct 2013 05:51:00 +0000 http://sfappeal.com/?p=58704#comment-24202 The uploader also posted transmissions of one of the two late BART employees reporting to dispatch/operations control that his work order was to be between c40 and c50 (where they were hit). Operations confirms the locations immediately and accurately, but then an automated message states that nobody is on the track, and then the human operator quickly corrects it and says [disregard the machine, there are persons wayside between c40 and c50]. This exchange likely happened before they went onto the tracks. Later, the order told to train 963 (the train that hit the employees) was that the work was being done near c53 and c54, 3 miles away from the accident. In someone’s transcript of the recording of the accident, the operations-control dispatcher tells train 963 that the work order around c53 and c54 was cancelled. According to another article I read, the train hit the two at 70 mph, full speed.

Now my conjecture: Somewhere down the line, operations control had the wrong information despite it being provided to them accurately before the incident by one of the two victims. My guess is that the victim submitted a work order earlier in the day with c53 and c54 and changed the work order it to c40 and c50 before entering the tracks. The fact that he radio’d in his position and the dispatcher confirms the new location, makes me believe that a change in work order is common practice, or at the very least can be handled properly by operations control. However, the automated message makes me believe that either (A) information was entered incorrectly into the computer OR (B) nobody changed the work order in the computer. Either way, I think the computer had the wrong information or none at all. All of the BART trains are operated by computers. The train operators only hit the e-brakes and hold the “door-open” button to let people on and off the train. They can also press buttons that put speed-restrictions on the train. Now I may be exaggerating based on information I heard from BART management, but they aren’t holding down a gas-pedal so they can’t let off when they see something off. I don’t think the operator expected anyone on the track at that point of the incident (he wasn’t told anyone was there), so I can’t blame him. When workers foul the tracks, one person is supposed to be a flag man and watch out for trains. The worker who called in explicitly made note that he knew the third (power) rail was live and that he’d respect operational trains. So I guess he was expecting the speed restriction on his section of track which makes the train max out at 20 mph (or something similar) via computer control. So he wasn’t expecting a 70 mph train to barrel down the tracks. Obviously, neither saw or heard the vehicle which makes me think that they were both breaking protocol by not watching out, which is unfortunate, but 70 mph train moves 100 feet per second, so a two second lapse in vigilance and 200 feet visibility could be fatal. Especially when the track is next to a freeway (which it was) creating high background noise levels. In this scenario I can see two mistakes: (1) the computer controller had the wrong info and (2) the employees weren’t watching.
Of course, my conjecture is just that. I look forward to the full report to make sure this never happens again.

It’s a true shame this happened. My heart goes out to the families of the two deceased. Truly, these members of the BART community will be missed greatly. Their dedication to keeping the BART system running as good as possible will be missed.

]]>
By: CAL FIRE NEWS http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24197 Sun, 20 Oct 2013 18:43:00 +0000 http://sfappeal.com/?p=58704#comment-24197 Matthew Keys did not capture this rcording he just repackaged it… such a tool he never learns… #RR

]]>
By: DrDuran http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24191 Sun, 20 Oct 2013 01:20:00 +0000 http://sfappeal.com/?p=58704#comment-24191 the first two people you hear on the recording are not on the train involved, they are moving train cars in one of the yards, then you hear Central talk to train 963 (the train involved in the accident) followed by train 963 declaring an emergency after striking the people working on the track.

]]>
By: withak30 http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24189 Sat, 19 Oct 2013 23:46:00 +0000 http://sfappeal.com/?p=58704#comment-24189 This is pretty messed up. When someone is working on the track like this there is supposed to be one person whose only responsibility is to watch for trains, even if no trains are scheduled to be there.

]]>
By: Michael Rocker http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24188 Sat, 19 Oct 2013 23:29:00 +0000 http://sfappeal.com/?p=58704#comment-24188 If there is a strike the trains should not have been running. PERIOD

]]>
By: Forrest Blocker http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24187 Sat, 19 Oct 2013 23:28:00 +0000 http://sfappeal.com/?p=58704#comment-24187 http://www.contracostatimes.com/news/ci_24345866/bart-train-strikes-two-people-near-walnut-creek

There is an audio recording of the whole incident. A manager (not engineer) was directing the train. Very clear.

]]>
By: bartr http://sfappeal.com/2013/10/bart-train-reportedly-strikes-two-people/#comment-24185 Sat, 19 Oct 2013 21:43:00 +0000 http://sfappeal.com/?p=58704#comment-24185 not pedestrians…BART workers, stop the lies

]]>