
From a Metro employee:
Staging [the reaction to the Clarendon incident] wouldn't be a problem if Metro made a decision and then stuck with it.From Adam:
Instead, someone makes the initial decision, then someone a step higher up changes it, and then the next higher up changes it yet again.
So, in reality, a train operator can be told three different things to do within a 5 or 10-minute period.
Another issue is the chain of command on the scene.
When fire department arrives, they immediately take over the scene in terms of either body recovery or removing the injured person. From what I have been told by those on the scene, the jumper was trying to crawl out from under the train.
The fire department told him to stay put and let them remove him.
Also, the fire department had third rail power removed from the opposite side of the platform.
This was totally unnecessary.
They could have run trains thru the station without stopping--at 5 m.p.h.--with a flagman there at the interlocking in case of personnel there.
Yet the fire department took all power down.
Someone told me that a fireman started crawling up under the train without any verification of the removal of third rail power.
The fire department comes out to local [Metro] shops for a half-day class on what the components on the train do. They learn to remove third rail power and other basic things. Problem is when they arrive on the scene they really do not have a true understanding of the track configurations or the power distribution at the scene. So they just kill ALL the power.
Metro has never stepped in to say there is a better way.
Also, Kubicek [Metro's #2] did not show up at the scene.
There was some junior flunky safety officer who had never worked a jumper scene before, so we was useless. All he kept doing was question and confront people about having an improper safety vest or an older model "hot stick" (a tool used to test whether there is electrical current).
In other words, he was in way over his head and instead of stepping back and trying to learn standard operating procedures, he kept trying to micromanage the scene.
I first heard about the incident from a supervisor. I hadn't heard about it on the Metro radio. Neither had he. He said he heard about it on a local radio station because they usually tell us before Metro does.
During the meltdown Tuesday, the station manager at Court House was ripping people off.
I got to Court House about 20 minutes after the incident. I didn't know that there was going to be at least a 2-hour delay until I was down on the platform and saw it on the message board.
Neither did damn near everybody else.
Rather than wait two hours, I went back up to find alternative transportation.
So did most everyone else.
But here's the question: Why weren't people informed about the delay until AFTER they had paid their fare? '
The station manager on duty said nothing about any delays, and since Court House is an Orange Line only station, surely she should have known.
I sat there and watched her for about ten minutes as people paid their fare and went down to the platform, only to come back up again five minutes later.
She said nothing to any of them.
That's kind of horsesh-t behavior on the part of the station manager.
UnSuck Fan · 702 weeks ago
former employee · 702 weeks ago
no one · 702 weeks ago
Criminal Organization.
anon2 · 701 weeks ago
There are no station managers and union employees who will deny," ....we love the money, why do you think we work here and stand around?"
Soylent Green Line · 702 weeks ago
We're paying more than we used to pay, and the service isn't improving. At all. Of course, the workers get a 9% pay raise (granted, over three years), but what do we, the much-vaunted "riding public" receive in return? Nothing.
If anything, since the fare increases, service across the board has actually worsened. So why are we mad? Why are we fed up?
We are paying more for less. Worse, we are treated like noisome busybodies by WMATA for the crime of wanting to utilize reliable public transit. Listen to Stessel's interview. At any point does he formally apologize on behalf of WMATA?
But then again why would he! I almost forgot, nothing that happened was WMATA's fault!
As usual, WMATA's after-action report on another colossal clusterfuck leaves me tired and disgusted, but not surprised.
anon · 701 weeks ago
John · 702 weeks ago
ANON · 702 weeks ago
1. Dan Stessel
That is all.
Radner · 702 weeks ago
Not an actual story, but they do have a link to it on the top of the local section. They also grab from this blog and reference it. I feel like throwing the readers to this blog means they admit that they couldn't cover it any better and they don't feel like using their resources to do what's already been done. I don't know if it's a good thing or a bad thing.
UnSuck Fan · 702 weeks ago
Anyway, I just look at it as how people and organizations are getting their information is changing and either those said parties who are not changing are getting left behind or they'll have to do something different to catch up. Personally, I think they should give up trying to be the first to break a story; it's old and sad about how competitive they get. Of course, like everything else, there's no "i" in team so instead of working with and/or referencing UnSuck, it gets to be pathetic. By the time a "regular" media source covers it, I already knew about it because the story broke here first.
insider · 702 weeks ago
Why else would an old guy like that leave his family behind to come "run" Metro. He's looking to make his life as easy as possible.
Not leading any one or anything.
former employee · 701 weeks ago
@suzer · 702 weeks ago
The major problem is communication and the lack of training of the operators and the station managers. Metro has failed to address this time after time. It is really sad when the updates from Twitter are more accurate than those from WMATA
duh · 702 weeks ago
Also why was the bus bridge going from Rosslyn all the way out to Ballston? Couldn't they have run to Court House instead? Maybe there's no place to turn around. If that's the case, are there no places for the trains to turn around between Rosslyn and Ballston? Scary.
Mainland · 702 weeks ago
FYI · 702 weeks ago
n2deep · 702 weeks ago
FYI · 701 weeks ago
This mess was Metro fault. Who is in charge, who knows what is doing. Soup sandwitch.
anon · 701 weeks ago
n2deep · 701 weeks ago
ever been at a cross tie fire when the FD shows up? they request all third rail power removed so they can not have to think about safety. then they will take 15 minutes to "put out' a smoldering tie that could have been done with a 1 gallon bucket of water.
what you fail to consider is the FD does not have the same priorities as metro. they do not care about trains moving safely past or how long they putter around on the tracks holding up service. for most it is something they don't get to do but maybe once in a blue moon. sort of like "on the job training". i have witnessed this on several occasions. while two guys are tending to the 1 gallon of water needed fire the other 6 are looking around asking others what this rail is or what that thing there does etc.
so until metro and the FD get on the same page with this incidents do not expect anything to change. or move along any faster for that matter.
mike · 701 weeks ago
FYI · 701 weeks ago
tomato or tamato · 701 weeks ago
Dave · 701 weeks ago
Open Circuit = All voltage, no current flow...
Ohms law · 701 weeks ago
stop it · 701 weeks ago
jkuchen · 702 weeks ago
And before someone replies with "they switch at Vienna all the time with oncoming traffic," that's a common practice, above ground, in a non-emergency situation, where operators know that something like that is happening. You don't want a switching situation like that with limited sight distance in manual mode in an area where few if any operators have dealt with that situation.
anon · 701 weeks ago
HotSauce · 702 weeks ago
YTK · 702 weeks ago
Rob · 702 weeks ago
mike · 701 weeks ago
Guest · 701 weeks ago
aanon · 701 weeks ago
Just Me · 701 weeks ago
former employee · 701 weeks ago
n2deep · 701 weeks ago
Danny · 701 weeks ago
anon · 701 weeks ago
Danny · 701 weeks ago
Kathryn · 701 weeks ago
Mike · 701 weeks ago
@MegE_N · 701 weeks ago