(1) @wmata tried to refute a July STATter911 story that it--once again--sent passengers toward danger, on an inspection that found smoke & fire. Today, @MetrorailSafety issued a report that confirms our story & shows #wmata's statements weren't true. (more) @knolkatie picture
(2) Here's @wmata's statement plus comments given to @justingeorge following the fire & explosions/arcing between Woodley Park & Dupont Circle. Despite its own rules prohibiting sending passengers on an inspection train, #wmata desperately tried to justify the action. (more)
(3) The rule that no passengers are supposed to be aboard any inspection train was announced in March of 2020 by the same spokesperson attempting to justify the actions during the July 30 Red Line incident. Here's a comparison:
(4) The @MetrorailSafety report makes clear--as STATter911 initially reported--@wmata sent passengers towards danger by ordering the inspection without first off-loading the train. This was also a key @NTSB finding in the 2015 L'Enfant Plaza fire that killed Carol Glover. (more)
(5) @MetrorailSafety also found--as @RailTransitOPS first reported--that once Train 108 discovered smoke & fire @wmata was slow in getting the train & its passengers to safety back at the Woodley Park Station. (more)
(6) As it has with many other rail emergencies, @MetrorailSafety found significant problems with @wmata's overall handling of the incident. There are also other parallels with the 2015 L'Enfant Plaza tragedy, including poor handling of fans. (more)
(7) @wmata provided misleading & flat out wrong info following this incident. It contradicted radio traffic & even ignored the fact the director of the Rail Operations Control Center issued a reminder about track inspections with passengers just hours after the incident. (more)
(8) This happened during @wmataGM's very first week. Let's hope he comes away from this realizing the timely release of factual information helps restore trust better than a knee-jerk defense that isn't candid. Read the @MetrorailSafety report here: bit.ly/3H6xo2F
• • •
Missing some Tweet in this thread? You can try to
force a refresh
(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)
(3) We don't know how this happened. It's possible, @OUC_DC may explain at some point. But transparency is not the agency's normal SOP. We've tweeted at them looking for details on 2 calls yesterday that went to the wrong address. So far, no response. (more)
(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)
(1) NEW: Trying to learn more about confusion at DC 911 over sound-alikes 8th St, A St & H St. This IS NOT a claim DC 911 made the error. I'm tweeting because it's the only way for me to get 911 call info from @OUC_DC. (more) @CMBrookePinto@brookepintodc@SafeDC@MayorBowser
(2) LISTEN: At 1:10 this morning, Ambulance 8 was dispatched to a rowhouse at 716 8th Street NE for someone with trouble breathing. (more)
(3) LISTEN: At 1:17 a.m., Truck 7 & Ambulance 6 were sent to 716 A Street NE -- also a rowhouse -- for someone with chest pains. (more)
When being "#1 Worldwide" is not a good thing. Lots of people watching @Qantas 144 after the pilot declared a mayday upon losing an engine. Here's hoping for a safe landing in Sydney. dailymail.co.uk/news/article-1…#aviation#qantas
On final approach now.
FlightRadar24 shows it on the ground taxiing off the runway with as many as 135K watching.
(2) @SenatorCardin also gets it. He makes the case I've made for a long time -- there is no "culture of safety" at @wmata. It has never existed. Without @MetrorailSafety there's zero chance for it to exist. If anything, they should be giving WMSC more teeth. (more)
(3) Sorry @mkorman, this is wrong. Not everyone agrees "safety is the goal". Despite decades of lip service about "safety first" -- including Smedberg on Monday -- history, recent WMSC investigations & my own reporting shows that just isn't the case with @wmata. (more)
(1) Paul Smedberg & @wmata board started out this drama yesterday with a lie. They closed an emergency meeting with claims "premature release" of their discussions would "compromise public safety." What they were actually discussing is how to "compromise public safety." (more)
(2) And then I'm sad to see @MarkWarner's statement: “Both entities need to stop fighting and figure out how to work cooperatively and productively as Congress intended to ensure both safety and reliability for Metro’s riders.” (more)
(3) @MarkWarner Do you really think the priority is to have @MetrorailSafety to work cooperatively with @wmata after Metro's half-century long horrible safety record? I want WMSC to be a kick-ass oversight agency that Metro must cooperate with. (more)