(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)

(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…

(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) (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)

(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

(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 (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)

(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)

(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)

(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)

(1) DC911/@OUC_DC director Heather McGaffin has promised for almost 3 months to tell us why @dcfireems was sent to the wrong location for a car in the Anacostia. 3 people died. Yet we still don't know why this happened. (more) @CMBrookePinto @SafeDC @ChmnMendelson @MayorBowser (2) WATCH: On June 12, McGaffin told ANC2B's monthly meeting, "Within the next few days we will be releasing the Frederick Douglass Bridge after action report." It's a month later & still no report on this or many other serious incidents under McGaffin's watch. (more)

(1) NEW: Only at DC911/@OUC_DC do they dispatch 2 @dcfireems companies for alarm bells at the exact address where 13 fire & EMS companies are already handling a report of a building fire. This isn't an isolated incident. (more) @CMBrookePinto @SafeDC @MayorBowser #FixDC911 (2) LISTEN: At 7:47 pm last night DC911/@OUC_DC dispatched the 13 @dcfireems units to a report of a possible apartment fire at 930 M St. NW. 9 minutes later, DC911 dispatched 2 more units for alarms bells at the same building. (more)

(1) Some people can't get the understaffed 911 center to answer while others can't stop 911 from sending unneeded ambulances to their homes. A dispatcher saying last night, “We do not cancel 911 calls" is an example of the chaos that reigns at DC 911/@OUC_DC. (more)@CMBrookePinto (2) What happened with @dcfireems Ambulance 23 occurs multiple times a day with DC911/@OUC_DC. A person wants to cancel an ambulance on a non-serious EMS call. But often dispatchers ignore those wishes & insist fire & EMS units respond. Listen in the next tweet. (more)

(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 (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)

(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) (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)

(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 (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)

(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 (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)

(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 (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)

(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) (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)

(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) (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)

(1) @fairfaxcounty confirms @wmata gave the wrong address for the Reston Town Center #Metro Station. It delayed fire & EMS getting to a man in cardiac arrest. That man died. How did this mistake occur? #WMATA isn't saying but it fits a pattern. (more) @wmataGM (2) For decades I've reported on Metro's poor communications with 911 centers, firefighters & EMS. Two weeks ago @MetrorailSafety reminded us of this continuing @wmata problem via its investigative report into a Nov. 7 smoke incident at Courthouse. Here's what WMSC wrote: (more)

(1) NEW: At least 7 minutes lost today during another CPR call. We don't yet know why DC 911 sent @dcfireems to 1901 1st St NW & not 901 1st St NW, but this is isn't the first time this exact error was made. (more) @SafeDC @CMBrookePinto @brookepintodc @ChmnMendelson @MayorBowser (2) LISTEN: At 7:19 a.m., DC 911 sent units to a cardiac arrest call with CPR in progress at 1901 1st Street NW at a nursing home. (more)

(1) At least 3 times in less than 2 days last week precious minutes were lost as DC 911 dispatched @dcfireems to the wrong address on serious calls -- a shooting, a confirmed cardiac arrest & one for trouble breathing. Still no answers from @OUC_DC. (more) @SafeDC @CMBrookePinto

https://twitter.com/STATter911/status/1619077194541834242

(2) It took sending @dcfireems to 3 different addresses over 12 minutes to get help dispatched to the correct location for a trouble breathing call at 716 H Street NE. Details here --

https://twitter.com/STATter911/status/1618323886264979457

(more)

(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)

(1) NEW: For the 3rd time in 40 hrs. I'm asking questions about why DC 911 sent @dcfireems to a wrong address. This time it's for a shooting an hour ago near 1200 NJ Ave. SE. @OUC_DC originally dispatched it to 1200 NJ Ave. NW. (more) @CMBrookePinto @SafeDC @MayorBowser (2) LISTEN: As you'll hear, it took more than 5 minutes for @OUC_DC to send the correct units to the correct address for this shooting. Even though someone at DC 911 put in the new address, they didn't tell @dcfireems. The crew from Medic 3 caught it. (more)