Interactive project report
Francis Scott Key Bridge collapse / supply chain report
The port that bent but didn't break.
A visual project report on how Baltimore's channel closure exposed specialized cargo lanes, uneven rerouting capacity, and the difference between local disruption and national market shock.
Format
Interactive project report
Event
March 26, 2024
Focus
Supply chain resilience
Core question
What bent, and what broke?
the incident
A bridge failure became a cargo-specific stress test.
On March 26, 2024, the Dali struck the Francis Scott Key Bridge. Six road workers died, the bridge collapsed, and the port's main shipping channel closed almost instantly. The supply-chain story afterward was not one clean collapse. It was several failures moving at different speeds.
Incident brief / 2024
The closure was severe, but the market impact depended on cargo substitutability.
Coal, Ro/Ro vehicles, containers, and local trucking each had different backup paths. That difference is the real story.
- Closure
- 78 days
- from collapse to full federal channel restoration
- Debris
- 50,000+ tons
- removed from the Fort McHenry Federal Channel
- Channel
- 700 ft x 50 ft
- restored operating dimensions
channel access
Recovery arrived as a sequence of usable widths.
The port did not switch from closed to open in one moment. Temporary channels let limited traffic move before deep-draft access returned. The timeline matters because each clearance changed what kind of cargo could move.
channel recovery / 01
The recovery was not binary. Each clearance changed which vessels could move.
Mar 26 / Bridge collapse
0 ft wideby0 ft deep
The Dali struck the bridge and blocked the main harbor channel.
Access returned in stages
0%
Progress shown against the final 700 ft by 50 ft channel restoration milestone.
cargo profile
Baltimore was specialized, not generic.
The port's importance was easy to flatten into a container-port story. But Baltimore's differentiator was autos, Ro/Ro machinery, and rail-linked coal. That mix is why different parts of the market felt different levels of strain.
cargo exposure / 02
Baltimore changes shape when the unit changes.
Coal exports
bulk export
This is where the closure shows up most clearly.
28M tons
Autos/light trucks
Ro/Ro
Baltimore led U.S. ports in vehicle handling before the collapse.
1.6M tons
Farm/construction machinery
high and heavy
Ro/Ro cargo needs ramps, storage, processors, and trucks.
1.3M tons
Containers
containerized
Big container ports had more room to help.
11.7M tons
Tons
Coal looks dominant
bulk exports show the sharpest closure scar
Value
Autos become the headline
vehicle trade makes Baltimore strategically visible
Units
Ro/Ro and containers split
the operating problem depends on terminal equipment
alternate paths
The workaround network split into separate relief valves.
Containers could lean on larger East Coast gateways. Ro/Ro cargo needed yards, ramps, processors, and truck networks. Coal depended on rail-linked export terminals and barge workarounds. The network worked, but unevenly.
reroute network / 03
There was no single substitute port. The workaround split by cargo type.
coal shock
Coal carried the clearest scar of the closure.
If one chart proves the shutdown mattered, it is coal. April loadings nearly vanished. June then shows the other side of the story: once access came back, Baltimore started clearing the backlog.
coal displacement / 04
Coal is where the shutdown becomes unmistakable.
63,658
short tons
April is the break in the line. June shows the backlog release once deep-draft access returned.
market absorption
The auto headline was exposure, not panic.
Baltimore was the country's top vehicle-handling port, so the risk was real. But a port disruption becomes a consumer-market shock only when there is no slack elsewhere. Alternate Ro/Ro ports and healthier dealer inventories absorbed much of the stress.
market absorption / 05
Autos were exposed, but the consumer market had buffers.
Exposure
No. 1
U.S. vehicle-handling port before the collapse
Inventory
80 days
new-vehicle supply before the disruption
Relief valve
10K
auto/high-heavy units diverted to Brunswick in April
system lesson
The port bent where optionality was real.
The useful lesson is not that the disruption was small. It was that fragility was uneven. Cargo tied to Baltimore's exact channel and inland links waited. Cargo with backup terminals bent around the damage.
resilience ledger / 06
The network bent where cargo had real backup paths.
| Cargo | Backup options | What broke | What bent | Recovery pattern |
|---|---|---|---|---|
| Containers | Easier | Baltimore vessel calls and local drayage | NY/NJ and Virginia | Alternate terminals and rail bridges picked up volume |
| Autos/RoRo | Harder | Vehicle acreage and processing lanes | Brunswick, Newark, Norfolk, Wilmington | Inventory and alternate Ro/Ro ports bought time |
| Coal | Hard | Rail-linked export terminals behind the bridge | Norfolk, barging, and midstream loading | June backlog surge after deep channel access |
| Local trucking | Hard | Bridge route, hazmat detours, nearby port work | Longer regional routes | Much slower than the channel itself |
Final insight
Resilience is not a property of a port. It is a property of the routes around it.
Baltimore bent because enough cargo had alternate terminals, rail bridges, inventory buffers, and specialized operators willing to reroute. It still broke locally because those options were not evenly distributed.
Back to projectsLiked this kind of work?
You might enjoy the Osprey landscape analytics report.
It turns another operational system into a readable model: messy field-service records, margin signals, and practical decisions for managers.