(1) You be the judge. In a statement today Metro says there's "no evidence" in last night's Red Line fire "a train was directed to perform a track inspection where there was report of smoke or fire." But the radio traffic seems to show there may actually be some evidence. (more)
(2) This episode started the exact same way as the tragic 2015 L'Enfant Plaza fire that killed Carol Glover -- with a fire alarm from a Metro pumping station connected to a Metro tunnel (@NTSB report excerpts below). Only this time the alarm was received & Metro reacted. (more)
(3) LISTEN: Radio traffic shows Metro sent a supervisor to the alarm & Rail Operations Control Center (ROCC) initially tried to reach Train 108 to stop at Woodley Park. But the controller couldn't reach the operator of Train 108 before he left Woodley with his passengers. (more)
(4) LISTEN: At 9:11:03 the controller says quite clearly, 3 times, they want Train 108 with passengers aboard to perform a "track inspection". Metro wanted 108 & its passengers to determine if there's smoke or fire to go with that smoke alarm. 108 acknowledged the order. (more)
(5) My question is now that ROCC had clear radio contact with Train 108 why wasn't the order given to STOP immediately and have 108 return to Woodley Park? Why continue to send them toward potential danger? That's not explained in Metro's statement. (more)
(6) LISTEN: A little more than two minutes after being ordered to head towards potential danger Train 108 found it. Arcing & sparking on the right wall of the tunnel. Train 108 stopped. It took at least 20 minutes to get them back to Woodley Park. (more)
(7) There's important history here you should know. For decades, @wmata sent passengers to check for fires & other dangers. In 2000 it trapped & injured scores of riders during a Foggy Bottom electrical fire. But Metro continued taking passengers along on inspections. (more)
(8) When Carol Glover's train became trapped after being sent to find smoke in January 2015 @NTSB told Metro to stop sending passengers to look for smoke and fire. Metro complied ... sort of. (more)
(9) In Dec 2019 & Feb 2020 STATter911 found two incidents where passengers were sent to look for smoke or fire. In one, people were stuck in a tunnel smelling smoke for 50 minutes. @MetrorailSafety came down hard on Metro. (more) statter911.com/2020/03/03/met…
(10) Metro's workers were splitting hairs over what constituted smoke or fire (arcing, sparking, etc). In March 2020 @wmata cleared it up, telling @justingeorge & me that no passengers will be on any train doing any kind of track inspection. (more) washingtonpost.com/transportation…
(11) Now that you've heard the radio traffic & know the context is Metro correct there's "no evidence a train was directed to perform a track inspection where there was report of smoke or fire"? Or is Metro again splitting hairs over orders meant to keep the public safe?
(12) BTW, in case you don't hit ALT to see the image description, this picture of @dcfireems at Saturday's fire on the Red Line is from @knolkatie who was a passenger on one of the trains that off-loaded at Dupont amid the smoke.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
(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…
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)
(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)