Mandatory Reporting of Containers Lost at Sea (SOLAS 2026)

From 1 January 2026 SOLAS V/31–32 distinguishes loss and observation of freight containers: recipients, Company fallback, fields and updates are not the same.

Operational Explanation

MSC.550(108) introduced two distinct duties. For a loss, the Master informs ships in the vicinity, nearest coastal State and flag State; for an observation, ships in the vicinity and nearest coastal State. Regulation 32 gives each message its own fields and gives a loss an initial/update/final sequence.

Regulatory Reference

Scope of Application

LOSS: ship involved in loss of freight containers. OBSERVATION: any ship observing freight containers drifting at sea. Use applicable communication channels and contact points without inventing one national format.

Procedure / How to Complete It

LOSS — initial/update/final

1. Without delay and to the fullest extent possible inform ships in the vicinity, nearest coastal State and flag State.
2. State report type; UTC/date; ship identity; sender/representative; recipients; chronological message number for updates.
3. Report loss position or best determinable position; total or estimated number; dangerous-goods status and UN number if known; dimensions/type and empty estimate as available.
4. Send additional information at the earliest opportunity. At the earliest safe and practicable opportunity verify the number and send the same recipients a report marked final.
5. The Company assumes the obligations to the fullest extent possible only if the ship is abandoned or the report is incomplete or unobtainable.

OBSERVATION

1. Without delay and to the fullest extent possible inform ships in the vicinity and nearest coastal State; Regulation 31 does not add the flag State as recipient of this report.
2. State report type, UTC/date, ship identity, Master as sender, recipient and UTC/date/position of observation.
3. Report number observed and, if available, dimensions/type, cargo spill, wind, current, drift, sea state and wave height.

Practical Example

LOSS: the ship immediately reports an estimated 12 containers, assigns the message number and includes dangerous-goods status and available data; after a safe inspection it confirms 10 in the final report to the same recipients. OBSERVATION: another ship tells the nearest coastal State and nearby ships the position, UTC and three containers observed, adding available drift and weather.

What Typically Goes Wrong

Using the same procedure and recipients for loss and observation, omitting update/final and verified total, or triggering Company fallback generically whenever the Master cannot communicate.

Common Mistakes Mistake Library

What the PSCO Checks

Operational Tips

• Prepare a documented on-board procedure in advance for the rapid reporting of container loss, with up-to-date contacts.
• Remember that the reporting requirement also applies to containers sighted adrift, not only to those lost from one's own ship.
• In the event of ship abandonment or inability to communicate, the reporting responsibility falls on the Company under Regulation IX/1.2.

Preparation checklist

• LOSS: nearby ships, coastal State and flag State
• LOSS: identity, UTC, position, number, DG/UN, type/dimensions/empty estimate
• LOSS: numbered updates and final verified total
• OBSERVATION: nearby ships and nearest coastal State
• OBSERVATION: UTC/position, observed number and available data
• Company fallback limited to Regulation 31 cases
• Current communication channels and contacts

FAQ

Related Topics

Last substantive revision of this page: 31 August 2026 · page fingerprint 02362a4d9925