(1) Another needless delay: The station mngr. immediately reported there was a person down in the roadway on Track 1 at 9:26 pm. Somehow--once again--there was a problem & the appropriate & needed Metro rescue assignment wasn't sent for 11 minutes--approx. 9:37 pm. (more) #wmata 
(2) @dcfireems was initially dispatched for a cardiac arrest call at 9:30 pm. It took the officer of Engine 4 to read through the dispatch computer notes along with a little delay getting @wmata's fire liaison on the radio before the correct assignment was dispatched. (more)
(3) Why is it key to promptly get the correct fire & EMS units going? Because @dcfireems needs the special equipment to operate safely on the tracks. The difference between a patient being on the platform or in the roadway is huge. (more)
(4) I don't have enough info to say if this was a fault of @wmata or @OUC_DC or both. With the historic lack of transparency at both agencies we may never learn exactly what happened from either. Maybe @MetrorailSafety can learn why the info wasn't relayed &/or acted on. (more)
(5) As we saw on the football field in Cincinnati, mins & secs count for survival after cardiac arrest. When a person's on a subway track, virtually everything has to be in their favor for survival. Tonight, it wasn't. Let's hope, despite that, there's a positive outcome. (more)
(6) The mishandling of rail emergency coordination between @wmata & @OUC_DC is well documented thanks to @NSTB & @MetrorailSafety investigations &, quite frankly, my reporting. Here's what's not well documented: Area leaders caring enough to make fixing this a priority.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
