The bridge was fine. The assumptions about ships were forty years old.
The Key Bridge collapse is a lesson about protective structures designed for a vessel class that no longer exists.
We were not in the room. Every reading on this desk is an outside analysis of public reporting, written to show how the method is applied — not to allege what any organisation knew or decided. Where we go beyond the public record we say so in the text.
On 26 March 2024 the container ship Dali lost power and struck a pier of the Francis Scott Key Bridge in Baltimore. The bridge collapsed within seconds. Six construction workers died. The port was closed to most traffic for weeks. The NTSB investigated and separately examined risk assessment practice for bridges over navigable waterways.
The bridge opened in 1977. Container ships have grown by roughly an order of magnitude in displacement since. The NTSB subsequently pressed owners of dozens of bridges to actually calculate their vulnerability to a modern vessel strike — because in many cases nobody had. The structure did not fail against its design case. Its design case had silently expired.
- Human: six lives.
- Economic: a major US port largely closed for weeks; supply chain and regional employment effects measured in billions.
- Sectoral: an urgent, national re-examination of protective structures around bridge piers.
- Institutional: an uncomfortable finding that the assessment had, in many cases, simply never been redone.
The class is an asset that is still fine and an environment that is not. It applies to any long-lived structure or system whose surroundings evolved faster than its assumptions — port infrastructure against modern vessels, substations against modern load profiles, buildings against modern occupancy, networks against modern traffic. The asset passes inspection. The assumption fails silently.
One decision: what is the credible worst case against this structure given the traffic that actually uses this waterway today? Answering it means holding the structure and its environment in one model, and re-running it when either changes.
- Hold asset and environment in a single model so the assumption is re-tested when the world moves, not when a committee remembers.
- Simulate a strike at today's vessel mass and speed rather than trusting a calculation from a different era.
- Prioritise protective investment across a portfolio by modelled consequence instead of by inspection age.
- Make 'when was this last actually assessed' a query rather than an archaeology project.
The asset register was accurate. It just could not answer a question about the future, because a register records what exists rather than how it behaves under a load it has never met.
Score your own position in five minutes — same model, no email wall. Or read what the levels mean.
Same seven steps, your asset, your data, your decision. That is the first half of a scoping workshop.