Dave Statter Profile picture
Jun 8 7 tweets 6 min read Twitter logo Read on Twitter
(1) NEW: You know what else is at Code Maroon? DC911/@OUC_DC. This agency is hazardous to our health. The problems aren't as visible as wildfire smoke. You have to know what you're looking for to fully understand DC911 remains in crisis. (more) @CMBrookePinto @SafeDC @MayorBowser Image
(2) Yesterday's vehicle fire is a good example of the symptoms. The fastest way to get fire & EMS to parts of DC's 14th St & Case bridges often means dispatching @ArlingtonVaFD. But DC911/@OUC_DC waited 12 minutes before doing that. Think about that -- 12 minutes! (more) Image
(3) Sending @ArlingtonVaFD has been SOP for months but @OUC_DC still can't get it right. It took 8 minutes on a 2nd call last night. Few will care about this until someone dies in a burning car or from cardiac arrest while DC911 takes its time alerting Arlington. (more) Image
(4) And few care DC911/@OUC_DC constantly wastes key @dcfireems resources sending double & even triple responses. It happened on the vehicle fire & 2 other calls yesterday--all in a little more than 3 hrs. I guess it will take the right person dying before it's addressed. (more) ImageImageImage
(5) DC 911 is at a point where the public constantly complains they don't get an answer when they call. At the same time, @dcfireems never knows if they'll get a reply when calling @OUC_DC by radio. This is on top of blown addresses & other mistakes. (more) Image
(6) What makes DC911/@OUC_DC particularly hazardous to our health is its complete lack of transparency & accountability. Without honest, direct answers, detailed information about errors & reliable statistics it's hard to see the needle dropping into the healthy range. (more) Image
(7) Sorry my latest DC911/@OUC_DC health check is so dismal. But unfortunately it's the truth. As always, this isn't about the workers on the floor, but OUC's training, management, & leadership. Read more details in my latest post. #FixDC911. statter911.com/2023/06/08/dc-…

• • •

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

Jun 7
(1) Time for a map quiz with a touch of history. The map shows us that 5638 Mount Vernon Memorial Highway is in
a. Alexandria
b. Mt. Vernon
(more) Image
(2) If you work as a public information officer for @FairfaxCountyPD you're bound by oath to say "screw the map" and choose "a", Alexandria. As in, "Yet another crime occurred 'in Alexandria'", even though Alexandria is an independent city not in Fairfax County. (more) Image
(3) Of course, this address, like the address for @FairfaxCountyPD's Mt. Vernon District carries an Alexandria mailing address. But the PIOs don't tell us their police station is "in Alexandria" or bother to change the name. They save that for the bad news -- the crime. (more) Image
Read 6 tweets
May 2
(1) NEW: @OUC_DC dispatched fire & EMS to the wrong street for a call this morning at the Giant on Connecticut Ave. Even though @dcfireems rapidly told DC 911 it was a bad address it still took 7 minutes to correct. (more) @CMBrookePinto @SafeDC @MayorBowser Image
(2) LISTEN: At 9:06 a.m., @OUC_DC dispatched @dcfireems to 4303 Wisconsin Ave. for a disoriented person at Giant. Engine 20 immediately told DC 911 it was a bad address. There's a Giant at 3336 Wisconsin. The dispatcher tried to call the 911 caller but got no answer. (more)
(3) LISTEN: At 9:12 a.m., Engine 20's officer found the correct address of 4303 Connecticut Ave. in the dispatch notes -- but no one alerted them by radio. The dispatcher said a call-taker entered that info. At 9:13 the call was re-dispatched. (more)
Read 4 tweets
Apr 21
(1) @OUC_DC's statement, sent to me without having to file a FOIA (more on that later)!! IMPORTANT note: As usual, OUC won't tell us what the 911 caller said or show location data. This is NOT the transparency Heather McGaffin promised. (more) @CMBrookePinto @SafeDC @MayorBowser Image
(2) That factual call info & location data were immediately available to @OUC_DC & would help us understand what occurred. Based on OUC's history--recent & more distant--they may not want us to understand. That's because there's a good chance it's more bad news for them. (more) Image
(3) I base this on the fact Heather McGaffin hasn't provided details or explained what errors were made during numerous blown locations & other problems during her time in charge. Some are listed below. It's a continuation of longstanding @OUC_DC policy to hide bad news. (more)
Read 9 tweets
Apr 21
(1) Why did @OUC_DC send @dcfireems to the 11th St Bridge for a car in the water under the Douglass Bridge? With 3 dead there should be a detailed accounting. Was it caller or call-taker error, or both? Will anyone demand answers? (more) @CMBrookePinto @SafeDC @MayorBowser Image
(2) LISTEN: At 10:31 p.m. @OUC_DC sent @dcfireems to the 11th Street Bridge for a car in the Anacostia River. The big question is what did the caller say and, if available, what did location data show? Was there more than 1 caller? (more)
(3) LISTEN: It's not clear to me from the available radio traffic when & how @dcfireems finally learned this was actually under the Douglass Bridge -- which carries South Capitol Street over the Anacostia. But it was a significant number of minutes. (more)
Read 7 tweets
Apr 13
(1) For almost a month, @fairfaxcounty has shared a false narrative surrounding the death of a man at a Reston @wmata station. Despite finally correcting the record on one key part of the story they insist on telling us things happened in a way that they clearly did not. (more) Image
(2) In order to continue its dubious claim the 10 minute delay caused by sending @ffxfirerescue to the wrong @wmata station is completely Metro's fault, @fairfaxcounty officials want us to ignore what we can all clearly hear in the recording of the call. (more) Image
(3) Read this from 2 @fairfaxcounty responses Tuesday:
"DPSC requested verification of the address given by the ROCC during the initial call several times".
"Following the second confirmation of the physical address, DPSC dispatched Fairfax County Fire and Rescue (FRD)". (more) Image
Read 8 tweets
Apr 12
(1) NEW: Remember the botched CPR call to the wrong Reston Metro station? It didn't go down as Fairfax Co. 911 had us believe. A recording of the call by Metro & other data received in a FOIA by @HCBright10 puts doubt on @fairfaxcounty's claim it was all @wmata's fault. (more) Image
(2) LISTEN: Here's a key moment from the call @wmata made to @fairfaxcounty 911/DPSC. The Metro worker clearly says the correct Metro station. Just as clearly, she gives a bad address. Fairfax County only told us about the bad address. (more)
(3) It took @fairfaxcounty learning yesterday that STATter911 had a recording of the March 20 call before they did the right thing & changed a March 21 statement. It finally corrects wrong info that @wmata reported the emergency was "at the Wiehle Metro Station." (more) ImageImage
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

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 on Twitter!

:(