Discover and read the best of Twitter Threads about #fixdc911

Most recents (13)

(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
Read 7 tweets
(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)
(3) LISTEN: Both Medic 2 & Engine 12 realized something is wrong. They knew there's no nursing home at 1901 1st NW but that the JB Johnson Nursing Center, a very common location for EMS runs, is at 901 1st NW. (more)
Read 7 tweets
(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
(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 -- (more)
(3) @OUC_DC also hasn't explained why 16 hours after the H Street NE call @dcfireems was sent to a marina instead of an assisted living facility 8 miles away, losing 4.5 minutes for a man in cardiac arrest. Details here -- (more)
Read 6 tweets
(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)
Read 6 tweets
(1) NEW: 8 miles apart & 2 very different DC locations. One is a tour boat dock in SW. The other is assisted living on the Walter Reed campus in NW. STATter911 has learned these addresses got mixed up during a DC 911 cardiac arrest call yesterday. (more) @CMBrookePinto @SafeDC
(2) LISTEN: The first call was dispatched at 4:58 p.m. DC 911/@OUC_DC sent 3 @dcfireems units for a person in cardiac arrest at 1320 Maine Avenue SW Suite 117. 1320 Maine Avenue SW is the address for DC Harbor Cruises. (more)
(3) LISTEN: At 5:03 p.m., DC 911 sent 3 different @dcfireems units to a similar sounding address about 8 miles away -- 1320 Main Drive NW. This was also a cardiac arrest call. The building is part of Abrams Assisted Living on the old Walter Reed campus. (more)
Read 7 tweets
(1) NEW: Once again, DC 911 failed to effectively use the technology DC residents paid for to confirm an address. They missed the location of a car crash by almost 3 miles & lost 12 minutes, even though the correct information was available to them. (more) Image
(2) At 3:58 Tuesday morning, DC 911 dispatched @dcfireems Engine 10 & Ambulance 3 to 12th St. & Maryland Ave. in Northeast for a crash. (more)
(3) At 4:06 am, Engine 10 reported they found nothing at 12th & Maryland in Northeast and asked the dispatcher to check back with the person who called 911. (more)
Read 10 tweets
(1) NEW: A @dcfireems battalion chief spotted this fire yesterday & called it in via the radio. But he had a very difficult time getting @OUC_DC to dispatch the call. It took more than 3 minutes. Very similar to the tragic 708 Kennedy St NW. First, your history lesson. (more) Image
(2) Watch: It took 4 mins to dispatch @dcfireems to a @DCPoliceDept officer desperately calling for help for 2 people trapped in the burning Kennedy St home in 2019. One of numerous excuses by @OUC_DC's Karima Holmes was that getting such calls by radio was extremely rare. (more)
(3) It was absurd then & is now for anyone to accept that a major city 911 center has more difficulty handling a report of a fire coming in by radio than by a 911 call. So, let's dissect what went wrong yesterday to better understand why @OUC_DC still can't get this right. (more) Image
Read 12 tweets
(1) NEW: DC 911 abandoned an emergency radio channel again today. It's the 4th time in as many months. It went unanswered as 2 different ambulance crews tried to reach @OUC_DC six different times over 2.5 minutes. Listen in the next tweet (more) Image
(2) LISTEN: The abandoned emergency channel -- Channel 12 -- is used for EMS calls in Northwest & Southwest DC. Ambulance 9 unsuccessfully tried to get an apartment number for the call they were on using 2 different channels. They finally just said "disregard". (more)
(3) This had been a chronic problem. Former interim director Cleo Subido addressed the issue in a March 2021 hearing responding to @CMLewisGeorgeW4. With the new rules it seemed to abate by July of last year. It's unclear if the rules Subido mentioned are still in place. (more)
Read 4 tweets
(1) DC VIOLENCE -- IMPORTANT!!: With DC in the middle of a violent crime crisis, the call for help goes first to DC 911. But 911 is in the middle of its own serious crisis. Don't just take my word. Read the words one week ago from @OUC_DC's interim director. ImageImageImageImage
(2) With the exception of @AugensteinWTOP no news media is covering DC 911's crisis where:
• 911 can't meet minimum staffing because half the work force isn't available
• Only 35% of staff vaccinated
• Part of the work force defies orders in place to better manage 911 (more) Image
(3)
• Some 911 staff routinely fail to put in a full day's work
• 911 mistakes aren't passed through the chain of command for investigation
• Staffing shortage is so bad that training staff is now assigned to answer 911 calls, impacting efforts to better train workers (more) Image
Read 6 tweets
(1) Do you know what's missing in @SafeDC's statement on Cleo Subido telling DC 911's staff to show up for work, ready to work & follow orders? Let me help you. Zero support for Subido or her efforts to right the ship. Read on. You'll see this likely wasn't an oversight. (more) Image
(2) I gave @SafeDC a second opportunity to voice support for Cleo Subido's efforts to deal with @OUC_DC's systemic problems. I asked for info on 7 items. The Subido support inquiry was my first question & the only one not answered. It sure makes you wonder. (more) ImageImage
(3) Compare this to @MayorBowser's unwavering support for @OUC_DC's previous director whenever reporters dared to ask about the many DC 911 problems. Remember, Karima Holmes was in charge for 5 years, allowing the problems to fester that Cleo Subido is now trying to fix. (more)
Read 16 tweets
(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
(1) Let's play "OUC's 395/695/295 Roulette"? The game where there are no winners. Whenever DC 911 sends a call to the 15 miles of 395/695/295, the dispatch is almost always wrong. The job of @dcfireems is to guess the real location where help is needed before someone dies.(more)
(2) LISTEN: This afternoon, a frustrated @dcfireems battalion chief was one of 5 units sent to I-295 NB at I-695 in Southeast for a crash. After 17 minutes of back & forth with the @OUC_DC dispatcher the crash was found on I-395N in Southwest. (more)
(3) So, @OUC_DC misses it by 3 miles, dispatches @dcfireems to the wrong quadrant & wrong highway & wastes 17 minutes. What's the big deal? Apparently, not much. This happens multiple times a day & no one in charge cares. (more)
Read 6 tweets
(1) It was a chaotic & mysterious noon hour at DC 911 today. We've shared many calls where @OUC_DC dispatched @dcfireems to the wrong quadrant of the city. This is the first time I'm sharing one where they sent the call first to SE, then to NE & then back to SE. (more) #FIXDC911
(2) LISTEN: Don't know if this was on @OUC_DC or @washingtongas or both, but it took 3 dispatches & almost 30 minutes & they still hadn't determined with certainty if the reported gas leak was on 12th Street SE or 12th Street NE. (more) #FIXDC911
(3) LISTEN: At the time the 12th Street mystery unfolded another mystery played out. Who dispatched Engine 24 to a roll over in the 400 bl of Oneida Street NE? @OUC_DC claims there was no such call. A battalion chief said it was a phantom call. Lots of confusion. (more) #FIXDC911
Read 6 tweets

Related hashtags

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.00/month or $30.00/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!