(1) DC 911/311 is being audited by @ODCA_DC. The remarkable email I published today from @OUC_DC's interim director Cleo Subido does some of the heavy lifting for the auditor. For the first time, the veil is lifted & we see what's really going inside OUC. (more)
(2) The email clearly shows, despite comments to the contrary from @MayorBowser's administration, that @OUC_DC has long been in crisis. It finally has a leader--at least for now--willing to get to the root causes of why DC 911 has performed so poorly for so long. (more)
(3) I've long reported the symptoms of OUC's ailment--delayed & inaccurate dispatching, failure to answer radios, poor knowledge of DC's geography, difficulty relaying emergency info. But Cleo Subido is the first to diagnose the disease & create a real treatment plan. (more)
(4) No one should expect Subido--or any other director brought in--to be able to stop the symptoms that translate to poor service to the public without addressing the root causes outlined in the email. It would be an impossible task. (more)
(5) Subido's plan is basic & nothing radical. @OUC_DC's employees must: show up for work, work the entire shift DC pays them for, follow orders, use the chain of command, have a clear understanding that they're there to serve the public & not themselves. (more)
(6) Subido's email has likely pissed-off some people. When the shock wears off I hope everyone realizes this is a key inflection point. Dr. Subido has written a prescription. It's one that can cure what ails DC 911. Will DC's leaders get it filled or toss it in the trash? (more)
(7) Here's Part 1 of my story on the email to the staff at @OUC_DC -- statter911.com/2021/07/18/exc…
(8) And here's Part 2 -- statter911.com/2021/07/18/exc…

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Dave Statter

Dave Statter Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @STATter911

6 May
(1) In December, when power was lost, trapping passengers on 2 trains between Ft. Totten & Georgia Ave/Petworth, I learned of safety concerns about Metro's handling of the evacuation. It took five months of bugging Metro to finally get answers. (more) DC Fire & EMS photo
(2) @WMATA now confirms its workers did not set up warning devices known as WSADs that would sound in case electrical power was accidentally restored while trains were being evacuated. It's a decades old safety procedure that was ignored. (more)
(3) @WMATA also got back to me about it taking almost 30-minutes to get accurate information to @dcfireems about an injured worker inside a tunnel near Ft. Totten on February 27. Metro confirms it failed to relay the correct details to DC 911. (more)
Read 5 tweets
16 Apr
(1) Carol Glover's 2015 death didn't do it. The past 15 months of news about failures during rail emergencies didn't do it. @MetrorailSafety's sharp criticism & many orders didn't do it. Is there anything that will change the culture at @wmata? (more) Image
(2) My story today on a passenger being the first to call DC 911 about a stranded train & the need for an ambulance, along with the usual poor communications between & by @wmata's ROCC & @OUC_DC is sadly just business as usual. (more) bit.ly/3gkUiHM
(3) It's the rule & not the exception that there'll be serious safety lapses anytime @wmata handles a rail emergency, whether big or small. And it's the same mistakes made over & over again. Is anyone surprised about the news this week? (more)
Read 6 tweets
12 Apr
(1) There should be a lot of people screaming "WTF" after reading the @WMATA stories by @tomroussey7news @AdamTuss & @justingeorge on the March 26 debacle at Rhode Island Ave. But a major safety issue is missing from the news reports & apparently in Wiedefeld's memo. (more)
(2) There's no acknowledgment of another major break down in communications between ROCC & @OUC_DC. The inability to relay timely emergency information is a big part of what killed Carol Glover in 2015. It's painfully obvious these failures continue to this day. (more)
(3) Because of poor communication between ROCC & OUC, @dcfireems was first dispatched for an EMS call at R.I. Avenue. Then for people trapped on an elevator. And then for a decoupled train. All of this wrong info evolved over 16 minutes. Why? How does this happen? (more)
Read 8 tweets
27 Feb
(1) 6 years after Carol Glover's death @WMATA & @OUC_DC show, once again, they can't communicate. It took almost a half-hour before the correct assignment was sent for an injured worker inside a tunnel. DC 911 initially dispatched it as a "sick person" at the station. (more)
(2) A supervisor reported the incident at 10:16 am. Within 2 minutes it was clear this was a worker with an injured leg who couldn't walk. It wasn't dispatched by @OUC_DC until 10:28 when Ambulance 14 was sent for a "sick person" at the Fort Totten station. (more)
(3) It's unclear what new information they had, but @OUC_DC sent Engine 14 on the call at 10:30. When Engine 14 arrived at Ft. Totten they initially couldn't find a sick person at the station or anyone who knew anything about an ambulance being needed. (more)
Read 7 tweets
20 Oct 20
(1) The discussion following today's @MetrorailSafety report about the Feb. 4 L'Enfant Plaza smoke incident was particularly interesting. Chairman Christopher Hart noticed something that caught my attention when I first reported this story. bit.ly/3ksQseM (more)
(2) @wmata's ROCC controller never said "smoke" when sending a train with passengers to do a track inspection, even though smoke was the obvious problem. Acknowledging smoke or fire would have meant stopping rail traffic & emptying the inspection train of passengers. (more)
(3) LISTEN: You'll also hear that instead of telling the various supervisors what was going on via the radio, the controller asked each one to call ROCC by phone. But again, no mention of the word "smoke". (more)
Read 11 tweets
15 Oct 20
(1) Why did it take DC 911 almost 14-minutes to dispatch @dcfireems to Friday's train decoupling on @wmata's Red Line? @OUC_DC hasn't answered that question, but the dispatch delay fits a pattern that DC's leaders have long ignored. Details here- bit.ly/2GZPxUI (more)
(2) LISTEN: @wmata confirms it notified @OUC_DC at 12:22 pm, within two minutes of learning of the decoupling. Radio traffic from @OpenMHz shows OUC didn't dispatch @dcfireems until 12:36 pm, about 14-minutes later. (more)
(3) WATCH: This dispatch delay occurred a year -- almost to the day -- after the delay & confusion following last year's Farragut West Metro Station collision. @MayorBowser still hasn't answered the question @paulcwagner asked in the days following that incident. (more)
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!