(1) The discussion following today's @MetrorailSafety report about the Feb. 4 L'Enfant Plaza smoke incident was particularly interesting. Chairman Christopher Hart noticed something that caught my attention when I first reported this story. bit.ly/3ksQseM (more)
(2) @wmata's ROCC controller never said "smoke" when sending a train with passengers to do a track inspection, even though smoke was the obvious problem. Acknowledging smoke or fire would have meant stopping rail traffic & emptying the inspection train of passengers. (more)
(3) LISTEN: You'll also hear that instead of telling the various supervisors what was going on via the radio, the controller asked each one to call ROCC by phone. But again, no mention of the word "smoke". (more)
(4) After the deadly 2015 L'Enfant Plaza fire, @NTSB's report led to a @WMATA order that passengers were not to be aboard inspection trains to look for smoke or fire. I've been reporting on that issue since the 2000 Foggy Bottom fire that trapped passengers. (more)
(5) But it had become obvious since the Dec 10, 2019 Tenleytown track fire that almost trapped passengers, some @WMATA workers were playing semantic games about "smoke" & "fire" or avoiding stating the obvious. (more) bit.ly/3dKJAHk
(6) That's why it was rewarding to finally see in @justingeorge's Mar 4 article the Feb 4 incident was the catalyst for @WMATA finally talking about an order ceasing the practice of sending passengers aboard any inspection trains, whether for smoke, fire or anything else. (more)
(7) BTW, the smoke was so obvious on Feb 4 that L'Enfant Plaza passengers were even tweeting about it. The smoke was from Metro workers cutting a lock in a room near the platform. (more)
(8) What brought my attention to this incident was this dispatch sending @dcfireems to L'Enfant Plaza for smoke removal. That was a little odd since normally they are called to find & help mitigate the source of the smoke. (more)
(9) Feb 4 was relatively minor as far as danger to passengers, but it was a major screwup. One @WMATA acknowledged right away. When I asked if train traffic should have been halted immediately & DC Fire & EMS notified earlier, a spokesman said, "Unequivocally, yes and yes."(more)
(10) My hope is the Feb 4 L'Enfant Plaza incident is the last time ROCC sends a passenger train toward known potential danger & ROCC has stopped playing games when it comes to smoke & fire.
(11) And here's @MetrorailSafety's report into the Feb. 4 incident at L'Enfant Plaza. WMSC's work is routinely impressive. It's a shame it took decades of safety neglect, injuries & death to get this kind of oversight. wmsc.gov/wp-content/upl…
• • •
Missing some Tweet in this thread? You can try to
force a refresh
(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)
(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)
(1) A bizarre DC 911 dispatch Wednesday evening. The people in charge at @OUC_DC should be embarrassed by it. OUC sent a full box alarm for a boat fire that land units would have to travel 4 miles into Virginia to access. OUC didn't coordinate with VA jurisdictions. (more)
(2) LISTEN: The location was the Potomac River at Four Mile Run. Question 1 is why @OUC_DC sent 5 engines & 2 trucks for a reported boat fire in the river? It wasn't at a marina. There are no structures nearby. That alone was a bit strange, But there's much worse. (more)
(3) This part of the Potomac belongs to DC. But access to the western shore, where Four Mile Run is located, can only be reached via water or Virginia roads. The first due from @dcfireems are Engine 13 & Truck 10 from Southwest. They're 5 miles from the reported boat fire. (more)
(1) 8 months & not one elected or appointed official or investigation has focused any attention on why it took 22-mins to get @dcfireems to the scene of 2 @wmata trains colliding on October 7. Today's @MetrorailSafety report confirms the timetable but has no explanation. (more)
(2) WATCH: When @Fox5Wagner asked @MayorBowser about the delay 5 days after the Farragut West collision occurred, this was her answer. @MurielBowser still hasn't answered that question or addressed any of the problems at @OUC_DC that contributed to the delay. (more)
(3) @charlesallen@CMCharlesAllen is in charge of oversight for @OUC_DC. In the 8 months since the collision he has not publicly asked OUC's director or anyone else about the lost 22-minutes. An outrageous response time to an emergency & he just doesn't care. (more)
(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
(1) @ABC7News will @ScottTaylorTV report that today's indictments prove clearly Seth Rich was not involved in stealing of DNC emails & all those "exclusive" stories from Scott promoted fact deficient, unsubstantiated conspiracy theories? @willsommer@farhip@brianstelter
(2) Will someone at @ABC7News finally apologize for @ScottTaylorTV failing to scrutinize--as good journalists do--Jack Burkman's claim that @DCPoliceDept mismanaged the investigation? No details of what was mismanaged. No SME to give an independent view.
(3) Will someone at @ABC7News explain why @ScottTaylorTV had Jack Burkman's June 20, 2017 press conference pinned to the top of his Twitter page for more than a month and that it wasn't removed until I tweeted about it?