
Click for larger. It still sucks, but that's what Metro published.
Apparently, Metro has a 50-page report on what happened at the Shady Grove yard late last month when a Metro employee was struck by a train and severely injured.
Metro has made only two pages of that report public, but it would appear they're going to talk about it at the safety and security committee meeting today.
Here's what I've been able to put together based on several Metro sources, two of which were there.
Boiled down, sources say the tragedy was a perfect storm, combining a careless employee and failure by management at the yard to consistently enforce fundamental safety rules.
The employee was struck inside a car washing facility. The area outside the car wash served as an unofficial smoking area for car mechanics because there wasn't an officially designated smoking area for them, sources say.
For the mechanics to leave the smoking area and return to work often required crossing live track. The route through the car wash, which involves entering live tracks, was a commonly used shortcut, sources said.
According to Metro rules, any employee entering live track must request permission. This rule appears to have been loosely enforced at Shady Grove, if at all.
The employee did not request permission to enter a live track area from the yard master, say two sources. But this was a common practice, they said, and management turned a blind eye.
"It was not a good area to have people smoking," said a source. "The way they crossed the tracks like that, it was only a matter of time. No one ever said anything. If you bring stuff up like this at Metro, you risk becoming a black sheep. There's too much go along to get along."
Further complicating the situation was that trains were entering the car wash from the opposite direction from which they normally do. Sources conflict as to how long that had been going on, but all said it was widely known that trains were flowing differently from the norm because of work in the area.
"This guy should have known," said a source.
Adding to chain of events that led to the injury is that the area around the door the mechanic used is a widely known structural blind spot.
Another potential issue is that signs on the door the employee used to enter the car wash, which warned of moving trains inside, had been removed and had not yet been replaced, said a car mechanic at the yard.
"I don't think that's a big deal," said one source.
Once the impact occurred, the employee was dragged 38 feet, according to Metro's own diagram (above).
One source familiar with the case said "we all cannot understand how a train going at less than five miles per hour would have this effect. Even if he stepped into the path of the train, at that speed, he should have been able to either get knocked back or into the pit between the rails. Most of us suspect the train was traveling at a greater speed than five miles per hour."
To add to the horror of the incident, at some point, while the employee was pinned under the train for over an hour as rescue workers tried to free him, "750 volts was energized on the rail he was pinned against," confirmed two sources.
Those there said he "let out a loud deathly scream when the voltage came back up," said a source.
They didn't know if third-rail power was inadvertently restored or was gapped (gapping is when third rail power is dropped in one place, but the train picks it up from another section that hasn't been dropped and bridges the "gap" to re-energize it.) from the rear of the train.
The injured employee remains in critical condition.
After the incident, Metro issued a "safety stand down." I asked a source what that means.
"Considering all the stand downs we've had--nothing," they said.
Sources added that since each new Metro regime comes in with new rules, the rules all pile on top of one another, often conflicting and "after a while you tune them out."
Other items:
Rush+ will force agency to recalibrate on-time metrics/spent $400k on Rush+ PR (Examiner)
Is Red Line graffiti more than vandalism? (WTOP)
Columbia Pike light rail faces hurdles (WaPo)
@davinpet · 666 weeks ago
This shows how carelessness employees are. I think the missing sign is a big deal. Why would they be so stupid to cross a live rail? Why is Metro allowing them to smoke
@wmata · 666 weeks ago
unsuckdcmetro 92p · 666 weeks ago
jkuchen · 666 weeks ago
n2deep · 666 weeks ago
@perkinsms · 666 weeks ago
GlenmontGirl · 666 weeks ago
horseydeucey · 666 weeks ago
FOR HIRE:
Adults
WMATA
ncc · 666 weeks ago
anon · 666 weeks ago
DC Denizen · 666 weeks ago
anon · 666 weeks ago
Dr. Gridlock · 666 weeks ago
Driver · 666 weeks ago
unsuckdcmetro 92p · 666 weeks ago
Seems a bit too simplistic given all that was at play.
Ever n Anon · 666 weeks ago
"What we have here is a lack of communication."
Driver · 666 weeks ago
n2deep · 666 weeks ago
"CAR WASH"
Dan Stessel · 666 weeks ago
Another Nick · 666 weeks ago
Rule #1 of being near tracks of any kind: expect a train from any direction at any time.
That shouldn't be a complication. Its a fact of life, like "jamming a fork in an electric outlet will result in a shock."
AnonE · 666 weeks ago
Radner · 666 weeks ago
Ryan · 666 weeks ago
In the event that the equipment is reenergized unexpectedly, the electricity will take the path of least resistance to ground (the ground strap, not the person touching the equipment).
I guess WMATA doesn't have such a procedure to keep people in contact with normally-live electric equipment safe. Or that procedure wasn't followed.
Either way, it's both unsurprising and inexcusable.
anon · 666 weeks ago
anybody affiliated (as in, a sys admin or superuser) with metroriders.org, please shut down the listserv; seems to have been hacked/zombified. thanks.
Vienna Bound · 666 weeks ago
Guest · 666 weeks ago
+100
No Baloney · 665 weeks ago
unsuckdcmetro 92p · 665 weeks ago
No Baloney · 665 weeks ago
unsuckdcmetro 92p · 665 weeks ago
I hear more and more questions popping up about how fast that train was going.
Again, I'm sorry this happened to a loved one.
Kolohe · 665 weeks ago
http://www.navytimes.com/news/2012/05/navy-essex-...