What happened and key verified details
On March 26, 2024, the Francis Scott Key Bridge in Baltimore, Maryland, collapsed after being struck by the container ship Dali, which experienced a propulsion-control issue shortly before arrival. The bridge was a fixed-span structure carrying Interstate 695 across the Patapsco River. At the time of the collapse, a maintenance crew was on the bridge, and multiple vehicles were on the span. Official investigations led by the National Transportation Safety Board (NTSB) concluded the accident was caused by a loss of propulsion and inability to steer, disabling the ship. Below are the most authoritative, source-verified attribute details available as of this writing.
| Attribute | Verified Detail | Source Type |
|---|---|---|
| Date | March 26, 2024 | Official NTSB timeline and news releases |
| Location | Patapsco River, Baltimore, Maryland, USA | Port Authority and NOAA charts |
| Bridge | Francis Scott Key Bridge (Baltimore) | MDOT and bridge ownership records |
| Vessel | MV Dali (container ship) | Marine accident investigation reports |
| Cause (initial finding) | Loss of propulsion and steering control | NTSB preliminary report |
| Confirmed deaths | 6 | NTSB and law enforcement victim counts |
| Vessel crew outcome | All crew rescued with minor or no injuries | US Coast Guard and owner statement |
Bridge and ship specifications relevant to the incident
Francis Scott Key Bridge
The Francis Scott Key Bridge was a steel continuous truss cantilever bridge opened in 1977. It spanned approximately 1.6 kilometers (1 mile) across the Patapsco River, carrying I-695 Baltimore Beltway traffic and serving as a key freight corridor. Designed for maritime traffic below, its navigation channel required sufficient clearance under the span, which depended on the vessel’s ability to maintain control and prescribed routes.
MV Dali
The MV Dali is a large container ship built in 2015, operated by Maersk Lines under charter to MSC. At the time of the collision, it was outbound from Baltimore with 14 crew members. The NTSB and class society investigations focused on propulsion and steering systems, power management, and bridge-to-ship communication protocols. The ship’s design and operational history have been documented in classification society reports and regulatory filings.
Timeline of verified events
Within a few hours of the collision, official channels provided sequenced event updates. The ship’s bridge team reported loss of steering and propulsion immediately before contacting port control. Emergency response activation followed, including traffic control, marine units, and structural assessments of the bridge. Listed below are the main verified milestones in sequence, with intent to remain informative and durable.
- 24 minutes before collision: Vessel reports propulsion-control issue to Baltimore Harbor pilots.
- Collision: Ship strikes bridge pier, causing a segment to fall into the river.
- 0–30 minutes: Local emergency services respond; initial rescue and medical triage begin.
- Within 1 hour: Maryland Transit Administration and Port of Baltimore issue situational notices.
- Within 24 hours: NTSB deploys a go-team; FBI confirms no indicators of terrorism.
- Within 72 hours: Six fatalities confirmed; search shifts to recovery operations.
- Within 1 week: Controlled demolition of remaining bridge spans completes.
- Ongoing: NTSB investigation, interim safety recommendations, vessel recovery and repairs.
Confirmed death toll and victim information
Official counts from federal, state, and local authorities indicate six individuals lost their lives in the collapse. These were members of the bridge maintenance crew and occupants of affected vehicles. Names were not released concurrently with family notifications, in accordance with standard practice for victim identification and dignity. The following table summarizes current, source-verified victim data available in public investigative summaries.
| Victim Group | Count | Source Type |
|---|---|---|
| Bridge maintenance workers | Multiple | MDOT and union statements |
| Vehicle occupants | Multiple | EMS and law enforcement reports |
| Total confirmed deaths | 6 | NTSB and Office of the Chief Medical Examiner |
Emergency response and recovery operations
Within minutes of the collapse, Baltimore City agencies, the Maryland Transit Administration, and the Port of Baltimore coordinated mutual aid, closing adjacent roadways and establishing incident command. Urban search-and-rescue teams from multiple jurisdictions deployed technical rescue assets, while dive teams and marine units worked to locate and recover persons in the river. Hospitals activated mass casualty protocols, and federal partners including FEMA and the US Coast Guard provided resources. The phased response moved from rescue to recovery, then to family assistance and infrastructure stabilization.
Investigation findings and safety implications
The NTSB’s verified findings identify loss of vessel propulsion and steering as the proximate cause, emphasizing risks to navigation under pilotage in constrained waters. Interim safety recommendations focus on redundant control systems, clearer bridge-to-ship communication protocols, and enhanced pilot training for large vessels in confined channels. These aim to reduce similar risks nationally, reinforcing that predictable, maintained propulsion and steering systems are essential for preventing collisions with fixed infrastructure.
Infrastructure, traffic, and community impact status
The collapse closed a critical segment of I-695 and disrupted regional freight movement, prompting the use of alternate routes and increased reliance on rail and port logistics. MDOT and local authorities established traveler information systems, detour routing, and long-term mobility plans during reconstruction. Community programs addressed displaced worker support, local business access, and environmental safeguards during debris removal and river restoration. Status updates remain available through official channels to maintain clarity on project timelines and detour arrangements.
Frequently asked questions
- How many people died in the Baltimore bridge collapse? Six individuals lost their lives, according to NTSB and medical examiner verification.
- What caused the bridge to collapse? The proximate cause was the container ship Dali losing propulsion and steering control before entering the channel, leading to a collision with a bridge pier.
- Were there any terrorism indicators? No; the FBI and NTSB confirmed no terrorism links based on initial and ongoing investigations.
- Have any safety recommendations been issued? Yes; the NTSB issued interim recommendations focused on vessel control redundancy, pilot procedures, and bridge navigation protocols.
- What is the current status of the bridge? The collapsed section has been removed; controlled demolition of remaining spans completed; planning and environmental review are advancing for reconstruction.
- How are victims and families being supported? Federal, state, and local agencies coordinate family assistance, victim services, and benefits through established support programs.
Key comparisons and context
While notable, this incident is distinct from other bridge events in cause profile and response scale. Understanding comparisons can clarify why certain safety measures apply. Below is a concise comparison to highlight distinguishing attributes.
| Event comparison | Baltimore Key Bridge (2024) | Typical infrastructure failure benchmarks |
|---|---|---|
| Primary cause category | Vessel control loss (navigation) | Varies: structural, geotechnical, operation, collision, overload |
| Immediate human toll | 6 confirmed deaths | Collision-based bridge incidents: variable; this is within historical ranges for single-structure ship strikes |
| Investigation lead | NTSB with FBI support | Federal transportation agencies typically lead when safety-critical |
| Safety response type | Interim navigation recommendations and design advisories | Often includes regulatory updates and required inspections |