Mandatory Reporting of Containers Lost at Sea (SOLAS 2026)
Reporting containers lost or observed drifting connects the event, recipients and available data with a timely message. From 1 January 2026 SOLAS V/31–32 distinguishes loss and observation: a loss also requires follow-up information, safe verification and a final report.
Operational Explanation
First identify whether your own ship has lost containers or has observed containers drifting. Prepare the relevant message with UTC, identity, position and available information, clearly distinguishing estimates and unavailable data. Express position in latitude and longitude or, where possible, true bearing and distance in nautical miles from a clearly identified landmark. For a loss, additional information feeds follow-up messages and safe verification of the number or estimate leads to the final message; an exact count is not a prerequisite for initial reporting.
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
MSC.550(108) — SOLAS V/31–32, in force from 1 January 2026. The Company assumes duties to the fullest extent possible for an abandoned ship or an incomplete/unobtainable report. The flag State reports the loss to IMO: direct submission to IMO does not replace the Master’s required recipients.
MEPC.384(81) — MARPOL Protocol I, Article V(3) aligns the report required by Article II(1)(b) for container loss with SOLAS danger messages.
Scope of Application
Within SOLAS chapter V’s scope, LOSS concerns the ship involved in losing freight containers; OBSERVATION concerns a ship observing them drifting at sea. Reporting is not limited to containers with dangerous goods, loaded containers or a particular cause of loss; LOSS also calls for the number or estimated number of empty containers as far as available and practicable. Use applicable communication channels and contacts, checking relevant instructions without assuming one national form applies everywhere.
Procedure / How to Complete It
LOSS — initial/update/final
- Without delay and to the fullest extent possible inform ships in the vicinity, nearest coastal State and flag State.
- State report type; UTC/date; ship identity; sender/representative; recipients; chronological message number for updates.
- Report the ship’s position at loss; if unknown, the estimated loss position; if that cannot be determined, the position on discovery; total or estimated number; dangerous-goods status and UN number if known; dimensions/type and empty estimate as available.
- Send additional information at the earliest opportunity. At the earliest safe and practicable opportunity verify by inspection the number or estimated number and send the same recipients a report marked final.
- The Company assumes the obligations to the fullest extent possible only if the ship is abandoned or the report is incomplete or unobtainable.
OBSERVATION
- 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.
- State report type, UTC/date, ship identity, Master as sender, recipient and UTC/date/position of observation.
- 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 number or estimate, or triggering Company fallback generically whenever the Master cannot communicate.
Common Mistakes Mistake Library
| Mistake | Consequence | How to Avoid It |
|---|---|---|
| Observation automatically sent to flag State as SOLAS duty | Recipients for the two events are confused | Use nearest coastal State and ships in vicinity for observation |
| Loss report limited to position and number | Prescribed fields and updates are missing | Use initial/update/final model with message number |
| Company fallback generalised | Company role exceeds Regulation 31 | Apply only for abandoned ship or incomplete/unobtainable report |
What the PSCO Checks
Operational Tips
- Do not wait for every field before the initial message: provide available information and send updates as soon as possible.
- Distinguish known data, estimates and unavailable information; do not report “no dangerous goods” when contents are unknown.
- The final follows inspection at the earliest safe and practicable opportunity and may give a verified estimated number, clearly qualified. Do not expose crew to danger to obtain an immediate exact count.
- Keep loss and observation distinct and retain messages, times and recipients.
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 number or estimate
- 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
Certified substantive revision: 16 October 2026 · page fingerprint d946d35f8d73