The container ship DALI struck the Francis Scott Key Bridge while departing Baltimore on 26 March 2024. Part of the collapsed bridge came to rest across the vessel's bow. Salvage work first had to free the ship and cargo from the wreckage.

That physical obstruction was only the first release boundary. After the shipowners declared general average, the appointed adjuster stated that cargo could be released only after acceptable general-average security had been provided. Cargo might become physically recoverable or dischargeable while remaining commercially unavailable for delivery.

The event was a casualty. The execution relationship it exposed had existed in published carriage terms years before the bridge was struck.

Two controls over the same cargo

MSC confirmed that it had customer cargo aboard the Maersk-chartered vessel. On 11 April 2024, MSC reported that the shipowners had declared general average and appointed Richards Hogg Lindley as general adjuster. According to MSC, the adjuster intended to keep all containers under its control, including MSC containers, until security arrangements had been made for both general average and salvage.

The next day's instructions from Richards Hogg Lindley made the release condition explicit. Cargo interests with insurance were required to provide an average guarantee signed by the cargo insurer, together with the cargo invoice and, where necessary, freight information. Uninsured cargo required an average bond, invoice information and a cash deposit in place of an insurer's guarantee.

The instructions did not state that insurance itself produced automatic release. Insured cargo still required a completed insurer guarantee and supporting information. Uninsured cargo followed a different security path whose cash-deposit level had not yet been set when the instructions were issued.

The distinction was operational, not theoretical. The adjuster said a daily list would identify cargo for which sufficient security had been provided. Cargo owners were to contact their shipping company about delivery once their container appeared on that list.

The condition existed before the casualty

MSC's official published Bill of Lading terms carried an issue/revision date of January 2017. Clause 22 addressed general average and salvage. It provided that an average agreement or bond, together with any cash deposit required as additional security for the goods' contribution and for salvage or special charges, had to be furnished before delivery or forwarding.

Those terms pre-dated the DALI allision by more than seven years. They do not establish that every cargo interest aboard DALI held identical contractual wording, and no conclusion is drawn here about the provision's legal effect in any individual bill. They do establish that MSC's published carriage structure already distinguished physical carriage from the security condition attached to later delivery or forwarding.

The casualty did not create that distinction. It activated it for cargo carried aboard a named vessel.

Salvage progress did not complete release

The ship and cargo moved through successive physical states after the collision. Wreckage lay across the bow. Salvors worked to remove it. The vessel was refloated in May. On 24 June, the U.S. Coast Guard announced that DALI would sail under its own power from Baltimore to Virginia International Gateway, accompanied by tugboats and a salvage vessel. Roughly 1,500 containers were scheduled to be offloaded there to reduce draft before the ship moved for further salvage and repairs.

Each step increased physical access to the cargo. None displaced the separate security process described by the adjuster. Dischargeability answered whether a container could be removed from the vessel. The release list answered whether the cargo interest had satisfied the stated condition for delivery arrangements.

The two processes could progress at different speeds because they depended on different actors and information. Salvors, vessel operators, ports and authorities controlled physical recovery. The adjuster, cargo interests, insurers and freight forwarders populated the security record.

Consolidated cargo added another identification boundary

Richards Hogg Lindley's instructions separately addressed less-than-container-load and groupage cargo. Freight forwarders were asked to provide a full breakdown of the individual shipments inside each consolidated container, including house bill numbers, descriptions, weights, shippers and receivers.

That requirement made the unit of physical handling different from the unit of security processing. A terminal could handle one container as a single object. The general-average process needed to identify the separate cargo interests within it. The adjuster warned that cargo could not be released until the requirements were met.

The point is not that all groupage cargo suffered an established additional delay; the public record does not quantify release time by container or shipment. It is that physical access to a consolidated box did not itself identify every interest whose security had to be recorded before the contents entered the delivery path.

What the declaration did—and did not—establish

Associated Press reported that the owner initiated general average while extraordinary salvage work continued and that the ship carried about 4,000 containers. MSC described the declaration as indicating that owners expected extraordinary costs for which they sought contributions from salvaged interests.

That was the owners' position as conveyed by MSC. The declaration did not fix each cargo interest's final contribution. The adjuster's requested guarantee, bond or deposit was security for a later process, not evidence of the amount ultimately payable. The public material reviewed here does not establish the final adjustment, the release date of each container or whether any particular cargo interest disputed the demand.

Nor does the release sequence decide casualty liability or the legal validity of general average for any individual contract. Those questions are outside the event-specific execution boundary shown by the sources.

Recovery and release were separate completion states

The ordinary account describes a ship trapped by a collapsed bridge and the salvage operation required to free it. It does not fully describe why cargo could remain unavailable after the physical obstacle began to clear.

The published terms and the casualty instructions support a narrower editorial inference. In carriage structures containing a pre-delivery security condition, physical recovery does not complete cargo release. Delivery or forwarding remains dependent on a separate chain: identification of the cargo interest, supporting value and freight information, and an acceptable guarantee, bond or deposit.

That dependency is structurally visible before any casualty occurs. The event itself need not be predictable. The prior arrangement already determines whether physical recovery and commercial release will move together, or whether one can stop after the other has resumed.

The boundary the event made visible

By late June, DALI could sail under its own power and a large block of containers could be offloaded. That did not make the security condition disappear. Under the adjuster's stated process, a container entered the delivery sequence after sufficient security was recorded and it appeared on the release list.

The cargo therefore occupied two states that ordinary accounts often merge. It could be salved, moved and discharged as a physical object. It was not yet releasable as a commercial shipment until the required security process was complete.

Sources

Return to Contract Breakpoint Analysis →