Dave Statter Profile picture
Jan 27, 2023 6 tweets 5 min read Read on X
(1) Within 12 hrs of tweets--including one from @STATter911--that @dcfireems was dispatched to a bad location for a pedestrian hit, @OUC_DC responded it wasn't its fault, tagging @SafeDC . On a Saturday morning! But total silence about 3 incidents this week. (more) @CMBrookePinto
(2) Almost 24 hrs ago, @dcfireems was sent to the wrong address on a shooting, losing 5 mins. 48 hrs ago 4.5 mins were lost with a bad dispatch for a cardiac arrest call. And about 60 hrs ago, 12 mins were lost checking out 2 bad addresses on a trouble breathing call. (more)
(3) What is it about the elderly cardiac arrest patient, the shooting victim & the person with trouble breathing that @OUC_DC believes their cases aren't worthy of an answer? Could it possibly be because OUC has determined mistakes were made? (more)
(4) @OUC_DC's leadership likes to claim transparency without really practicing it. Just ask David Griffin's daughter @agirllikemeeeee or Sheila Shepperd's family if you want to understand just how cruel DC 911 can be in withholding info about the deaths of their loved ones.(more)
(5) It's transactional transparency with @OUC_DC. They stay quiet & usually refuse to release info (claiming privacy) when news isn't good. It's rare for DC 911 to own up to errors, even in the 11 previous deaths STATter911 uncovered where there were clearly 911 mistakes. (more)
(6) When will people, including the @councilofdc & other city leaders, wake up to how poorly the public is served by DC 911? When will they demand change? When will they finally #FixDC911?

• • •

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!

PDF

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

Aug 28, 2023
(1) The @dcdistrictdogs flood shows @MayorBowser's administration doesn't care who gets hurt in its quest to keep DC911/@OUC_DC's mistakes buried. The fact they still refuse to admit what happened is part of a years-long shameful pattern. Here's a history lesson. (more)
Image
Image
(2) 4 years ago this month @MayorBowser shielded @OUC_DC from a multi-agency investigation of the tragic 708 Kennedy St NW fire that killed Yafet Solomon & Fitsum Kebede. As with @dcdistrictdogs, OUC gave non-sensical answers to key questions. (more)
thedcline.org/2020/08/18/dav…
(3) 4 years before Kennedy St., @MayorBowser showed she didn't want outsiders probing DC911/@OUC_DC. Her administration refused a @NTSB recommendation for an OUC operations audit after the deadly L'Enfant Plaza Metro fire. It was never done. The fire killed Carol Glover. (more) Image
Read 13 tweets
Aug 22, 2023
(1) NEW: In a press conference where she made things worse & not better, DC911 boss Heather McGaffin's unusual excuses for a major 911 failure aren't passing the smell test. None more so than blaming a dispatcher who "misspoke" for the 15 min. delay sending emergency help. (more) Image
(2) LISTEN: McGaffin kept saying a dispatcher simply "misspoke" when he dispatched the initial call to @dcdistrictdogs as a "water leak". What she didn't explain is how a different dispatcher on a different channel also misspoke 3 minutes later, using the very same words. (more)
(3) A likely explanation for this coincidence of the pair misspeaking in the exact same way is that it wasn't a coincidence at all. They likely both read from the dispatch computer where this call was misclassified as a non-emergency "water leak" or "public assist". (more) Image
Read 12 tweets
Aug 21, 2023
(1) BREAKING: DC911/@OUC_DC's Heather McGaffin finally admits DC911 messed up in the @dcdistrictdogs response. As we told you last Monday the 15-minute delay would come down to what the first 911 callers said. They said plenty about how bad the situation was. It was an EMERGENCY! The walls were coming down during the flooding with people & dogs inside. But DC911 dispatched this as a non-emergency water leak. (more details to come)

The release of this information and the 911 transcripts would not have come without the outrage of the people impacted, some tenacious reporters & @ZacharyforWard5.
(2) At the press conference McGaffin called this an "unprecedented incident" that OUC "hadn't fully prepared ourselves for or our staff for". That's an astounding statement. A 911 center that isn't prepared to understand flooding in a building where a wall has come in & people & dogs are inside is an EMERGENCY is not prepared to do the job on a daily basis. This is not unprecedented. (more) @ANCCostello @RealTimeNews10 @RamirezReports @SegravesNBC4 @tomsherwood
(3) In the press conference, which I am just replaying, McGaffin talks about DC911/@OUC_DC needing to do a better job of relaying the dispatch notes/updates. That's something STATter911 has pointed out for years. Last year I had a top official at OUC tell me reading those is the job of @dcfireems. (more)
Read 4 tweets
Jul 17, 2023
(1) This evening, yet another example of DC911/@OUC_DC making the same mistakes over & over because of a lack of leadership, supervision, situational awareness & training. As usual, @dcfireems saved the day. Listen in the next tweet. (more) @CMBrookePinto @SafeDC @MayorBowser Image
(2) LISTEN: At 6:41 pm DC911/@OUC_DC sent Engine 6 & Truck 4 to 1730 7th St for alarm bells. At 6:45 pm DC911 sent a full structure fire assignment of 13 units to the same address, totally forgetting they sent E6 & T4 just 4 minutes earlier. (more)
(3) Thankfully Engine 6 caught the mistake & alerted DC911/@OUC_DC. This type of error--it happens frequently--has caused confusion, missed assignments on the fireground & wastes resources. You have to wonder how this gets by the supervisors & dispatchers so often. (more) Image
Read 5 tweets
Jul 16, 2023
(1) Within 4 minutes today DC911/@OUC_DC dispatched 3 separate assignments sending @dcfireems to these locations for a crash:
• 2:50 a.m. Washington Blvd. & Memorial Ave. SW
• 2:52 a.m. Lincoln Memorial Circle NW
• 2:53 a.m. Rock Creek Pkwy & Ohio Dr. NW
(more)
Image
Image
(2) It should be obvious to anyone at DC911/@OUC_DC all 3 are likely the same crash. I get that the locations need to be checked but why didn't dispatchers let the responding units know what was going on? Why, as usual, did they leave @dcfireems in the dark? (more) Image
(3) The @dcfireems units couldn't even hear for themselves that they were all operating in the same area, likely on the same call, because one of the units was assigned a different radio channel. (more) Image
Read 5 tweets
Jul 12, 2023
(1) Right on cue--as if we needed more evidence--DC911/@OUC_DC helped to further justify @councilofdc's OUC transparency act. When @CaseyNolen did a story about the emergency legislation OUC refused to comment. Of course they did. But there's more. (more) @CMBrookePinto @SafeDC
(2) A key point of the emergency act that passed yesterday is real data on daily staffing. The staffing stats are something STATter911 has pushed for over many months. Why? Because we now learn even @ChmnMendelson couldn't get a live person on the phone when calling 911. (more)
(3) Watch: @ChmnMendelson tells a story so many others told us over the last year -- no call-taker picked up when he called 911. It seems to be the rule rather than the exception that 911 in the nation's capital doesn't answer right away. (more)
Read 9 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

Don't want to be a Premium member but still want to support us?

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

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(