The Key Bridge Mayday — Ninety Seconds on March 26, 2024
It happened — best read as remarkable timing, not the miraculous.
The account
When the container ship Dali lost power 3,200 feet from Baltimore's Francis Scott Key Bridge at 1:24:59 a.m. on March 26, 2024, the pilot's mayday gave Maryland Transportation Authority police about 90 seconds to halt traffic at both ends before the ship struck a pier at 1:28:45 and the span fell; the stopped cars are why officials called the responders heroes, and the six road workers filling potholes mid-span — whom one officer was preparing to drive out and warn — received no warning at all.
Read the full account →Collapse the account ↑
The container ship Dali lost electrical power at 1:24:59 a.m. on March 26, 2024, about 3,200 feet from the Francis Scott Key Bridge in Baltimore. The main engine shut down nine seconds later. Power came back, failed again at 1:27:04, and came back again at 1:27:36. In between, at about 1:27, the pilot issued a mayday: propulsion lost, collision with the bridge possible. Maryland Transportation Authority police dispatch ordered traffic stopped at 1:27:53. Officers near the bridge halted eastbound traffic within about 20 seconds and westbound traffic by 1:28:58. At 1:28:45 the ship struck a support pier at about 8 knots, and the span fell into the Patapsco River.
One officer had radioed that he would drive onto the bridge to alert the construction crew working mid-span once backup arrived. The bridge fell first. On the dispatch audio, another officer: 'The whole bridge just fell down.'
The Work Crew and the Drivers
Six men received no warning. They were road workers employed by Brawner Builders, filling potholes on the span: Maynor Yassir Suazo Sandoval, 38, who had come from Honduras; Miguel Angel Luna Gonzalez, 49; José Mynor López, 37; a 35-year-old man from Mexico; a 26-year-old man from Guatemala; and a sixth man whose name was not made public. All six died in the collapse. The last of them was recovered from the river on May 7, six weeks after the bridge fell. Two other people survived: one man pulled from the water seriously injured, and an inspector rescued unhurt from a standing section.
Officers had halted traffic at both ends in the minutes before the strike. The bridge carried more than 30,000 vehicles a day, and cars were crossing it less than two minutes before the collapse. Governor Wes Moore said of the responders: 'These people are heroes. They saved lives last night.'
What the Investigation Found
The National Transportation Safety Board adopted its final report on November 18, 2025. The probable cause was a single loose signal wire: wire-label banding had prevented the wire from being fully seated in a terminal-block spring-clamp gate, and the bad connection opened a breaker that began the blackout sequence. The ship's high-voltage breakers were also set to manual rather than automatic mode, which stretched the first blackout from a possible 10 seconds to 58. 'This was preventable,' said NTSB Chairwoman Jennifer Homendy. The same report credited the human chain precisely: 'quick actions of the Dali pilots, shoreside dispatchers and the Maryland Transportation Authority to stop bridge traffic prevented greater loss of life.'
Reviewer Notes
We weigh a claim on two things, kept separate from the story above.
Assessed by Miracles Jar AI
A designed warning chain worked inside 90 seconds and the hour kept the span nearly empty; the same chain had no channel that reached six road workers on the span. Both findings are in the NTSB record.
The verdict: "A designed warning chain worked inside 90 seconds and the hour kept the span nearly empty; the same chain had no channel that reached six road workers on the span. Both findings are in the NTSB record."
The question here is whether the timing was more than coincidence. Read element by element, the saving conjunction is a designed system doing what it was designed to do. Maydays are protocol. Dispatchers relay. Officers sat near a major crossing because patrol patterns put them there — positioned at a major crossing on routine patrol. The hour of night, not any arrangement, set the traffic density; timing-of-day is the dominant variable in the casualty count, and it is chance, not arrangement. A collapse at rush hour would have found the span carrying its share of more than 30,000 daily vehicles.
What remains on the other side is the width of the window: a blackout slightly closer to the bridge leaves no warning at all, and slightly farther out the ship may have recovered or anchored. Ninety seconds happened to be exactly enough for the cars (the eastbound stop within about 20 seconds, westbound by 1:28:58). It was not enough for the men on the span, and the record states why without any mystery: the chain that could stop traffic at the ends of the bridge had no channel that reached the workers in its middle. This is timing that no design guaranteed — but it is scored as a weak signal for more than coincidence.
The NTSB's two findings stand side by side and have to be read together: the response prevented greater loss of life, and the event that demanded the response — found preventable, caused by a loose wire and breakers left in manual mode — should never have happened.
The timeline is fixed to the second by the ship's voyage data recorder, police dispatch audio, and a federal investigation: blackout 1:24:59, mayday about 1:27, dispatch order 1:27:53, both directions of traffic stopped by 1:28:58, strike 1:28:45 — probably the most precisely timestamped event in the catalog. Every element of the saving chain is a designed system operating as designed — mayday protocol, dispatch relay, officers positioned at a major crossing on routine patrol — and the NTSB credits the chain in exactly these terms: quick actions that prevented greater loss of life. The 1:28 a.m. hour set the traffic density; the same collapse at rush hour would have found the span carrying its share of more than 30,000 daily vehicles — timing-of-day is the dominant variable in the casualty count, and it is chance, not arrangement. The warning chain that emptied the roadway had no channel that reached the six workers on the span; one officer was preparing to drive out to alert them when the bridge fell — the same record carries both halves; the NTSB found the collapse itself preventable — a loose wire and breakers left in manual mode.
Evidence ledger — what the verdict rests on
The timeline is fixed to the second by the ship's voyage data recorder, police dispatch audio, and a federal investigation: blackout 1:24:59, mayday about 1:27, dispatch order 1:27:53, both directions of traffic stopped by 1:28:58, strike 1:28:45
Probably the most precisely timestamped event in the catalog
Every element of the saving chain is a designed system operating as designed — mayday protocol, dispatch relay, officers positioned at a major crossing on routine patrol
The NTSB credits the chain in exactly these terms: quick actions that prevented greater loss of life
The 1:28 a.m. hour set the traffic density; the same collapse at rush hour would have found the span carrying its share of more than 30,000 daily vehicles
Timing-of-day is the dominant variable in the casualty count, and it is chance, not arrangement
The warning chain that emptied the roadway had no channel that reached the six workers on the span; one officer was preparing to drive out to alert them when the bridge fell
The same record carries both halves; the NTSB found the collapse itself preventable — a loose wire and breakers left in manual mode
The believer-side residue is the width of the window: a mayday and a 90-second response that were exactly enough for the cars
A blackout slightly closer to the bridge leaves no window at all; slightly farther out, the ship may have recovered or anchored
What would raise this score: Independent documentation shrinking the coincidence window (timestamps, third-party records) would move this.
What would lower it: Evidence the timing window was wider than reported would move it down.
How this works
We keep two questions apart on purpose — so a thin record can’t make an impossible thing look proven, and a strong record can’t dress up an ordinary one as a miracle. First: Was it more than coincidence? (taking the account as true for the moment.) Nothing here breaks a law of nature — the question is whether the timing and arrangement were more than coincidence. Second: is there real evidence it happened? A claim only stands out when both hold up — and we never call anything certain either way. How ratings work →
The natural explanation
The leading natural account for this case is coincidence & the law of truly large numbers. Read what it explains — and where it stops.
The same wonder, across traditions
This claim is one of many that make the same assertion across faiths. See it side by side in Deliverance Against the Odds.
Sources
Tagged by proximity to the event. Primary sources are direct or contemporaneous; tertiary are downstream retellings.
- 1.Primaryinvestigation
The November 18, 2025 final-report findings: the loose signal wire and wire-label banding, the manual breaker mode (58 versus a possible 10 seconds), Homendy's 'this was preventable,' and the credit to pilots, dispatchers, and MDTA for preventing greater loss of life
- 2.Secondaryother
Wikipedia, "Francis Scott Key Bridge collapse — Wikipedia", 2026
The second-by-second VDR timeline (1:24:59 blackout through the 1:28:45 strike), the 1:27:53 dispatch order, the traffic stops at both ends, the recovery dates and details for the six workers, and the two survivors
- 3.Secondarynews
The March 27, 2024 dispatch-audio reconstruction: the 90-second response, the officer preparing to drive onto the span to alert the crew, 'The whole bridge just fell down,' and Maynor Yassir Suazo Sandoval's identification
- 4.Secondarynews
Governor Moore's 'These people are heroes. They saved lives last night,' the dispatcher's stop-traffic order, and the same-day account of the crew that was about to be alerted
Cases like this
Nearest on the map — similar in how miraculous they’d be, and how strong the evidence is.