(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) A map shows Rt 1 & Huntington sits on the border of 2 well-known communities in Fairfax County. But @FairfaxCountyPD's unwritten policy is to only use those names for good news. For crime, they use the mailing address so they can say it happened "in Alexandria". (more)
(2) This lets the public think all the bad stuff occurs in the City of Alexandria. While it's bad news for @AlexandriaVAPD, @AlexandriaVAGov & its citizens it's great news for Fairfax County because they have a very large area--about 100 sq miles--with Alexandria addresses.(more)
(3) You'd think competent & effective police PIOs would want to narrow down a location to less than 100 sq miles by letting the public know what community a crime occurred in. Not @FairfaxCountyPD. (more)
(1) @justingeorge's latest provokes more questions about @wmata board's culpability in Metro's decades old failure to adopt a safety culture. Just take the last 3 years. If safety was really a priority every board meeting would focus on @MetrorailSafety's latest findings. (more)
(2) Investigative reports @MetrorailSafety adopts monthly are a road map to the constant Metro safety problems. If the board looked at & discussed them each month the recent @MetrorailSafety power report citing a “culture of noncompliance” wouldn't have been a surprise. (more)
(3) Anyone who reads @MetrorailSafety reports knows issues surrounding shutting off third rail power, safely restoring it & related communications are routine findings by WMSC's investigators. How many of these reports have been publicly addressed by @wmata's board? (more)
(1) When I say @wmata hasn't made safety a priority since before trains began running I'm referring to a 1970s battle over bus & rail car flammability. Jackson Graham pushed back against the Natl Bureau of Standards, Natl Academy of Science & DC's fire marshal on this. (more)
(2) A National Academy of Science report said, "fire safety appears to have been evaluated without approaching the subject systemically & without requiring that meaningful specifications be defined & met." (more)
(3) I talked a couple of times with the late John Breen. He was DCFD's fire marshal at the time. Chief Breen went up against Metro. He said things got tense. The area fire chiefs first expressed concern about what materials would be used in subway cars way back in 1967. (more)
(1) This is the big lie @wmata's board has told itself & us for decades. The truth is safety has never been Metro's "top priority." Wiedefeld's big 2016 program & mantra "Safety Trumps Service" has proven repeatedly to be a bunch of words that didn't change the culture. (more)
(2) @MetrorailSafety's order today on power restoration is another enormous embarrassment that again proves @wmata can't get the basics right when it comes to safety. The document even has a section titled "Metrorail’s culture of noncompliance." (more) wmsc.gov/wp-content/upl…
(3) These are Metro truths: safety is not the priority & hasn't been since even before trains began running 46 years ago (go back & look at DCFD Fire Marshal John Breen's 1970's battles with WMATA); everything trumps safety; Metro currently has neither safety or service. (more)
(1) NEW: DC 911 confirms an ambulance crew requesting paramedics for a patient early Friday got no response on an emergency radio channel. This is at least the 3rd time radio channels weren't answered for minutes at a time since April 1. (more) @charlesallen@Janeese4DC
(2) Listen: Ambulance 19 called 3 times before changing radio channels in search of a dispatcher to help them. After telling @OUC_DC no one was working Channel 11 a dispatcher returned to the abandoned radio channel apologizing for not answering. (more)
(3) Adding paramedics to an existing emergency response usually takes less than 30 seconds. In this case it took 3 minutes. From February 2020 to July 2021 STATter911 documented 17 times DC 911 abandoned radio channels for minutes at a time. (more)
(1) For 7-minutes yesterday a Metro train operator was caught in the middle of a dispute between @MetroTransitPD & the Rail Operations Control Center (ROCC) over which train would do a second search for a man struck & killed by a train. Listen in the next tweet. (more)
(2) Radio traffic indicates @MetroTransitPD or "Transit" boarded Train 106 at 2:36 pm, cleared it of passengers & wanted to be taken on a "track inspection" to find the man who was struck. That didn't sit well with ROCC. (more)
(3) The @OpenMHz radio traffic shows ROCC telling Train 106's operator multiple times the track inspection was not authorized & to re-board the passengers. ROCC had planned for Train 111 to take @MetroTransitPD on the search. (more)