MASS Code: the New IMO Framework for Autonomous Ships
The MSC.595(111) MASS Code is a non-mandatory instrument effective from 1 July 2026; the EBP and future mandatory Code follow an expected roadmap, not already adopted obligations.
Operational Explanation
MSC 111 adopted the non-mandatory MASS Code by resolution MSC.595(111); it took effect on 1 July 2026, wording distinct from treaty entry into force. MSC 112 is to develop the EBP framework. The 2030/2032 dates are expected milestones subject to future development, adoption and SOLAS amendments.
Regulatory Reference
MSC.595(111): non-mandatory MASS Code. IMO revised roadmap: MSC 112 development of EBP framework; expected mandatory-Code adoption by 1 July 2030 and entry into force 1 January 2032, subject to future action.
The MASS Code adopted on 21 May 2026 provides that the ConOps should describe operational modes, criteria for changing mode, allocation of functions to humans or software, supervision and the location of the agents involved (II/8.6). Crew and remote operators responsible for operations should be able to understand system outputs, supervise decisions and intervene or override the system when required. A human master should remain responsible regardless of operating mode and have the means to intervene (II/8.7). These provisions belong to the non-mandatory Code; they do not establish a new binding regime. IMO — MSC.595(111), II/8.6–8.7.
EBP means Experience-Building Phase. As of 15 September 2026, the published roadmap assigns development of its framework to MSC 112 in December 2026. Existing trials or projects do not by themselves establish that this framework has already been approved. IMO: MASS roadmap.
Scope of Application
Cargo ships within SOLAS Chapter I under the non-mandatory Code's scope; recommended application to other MASS under the instrument. SOLAS, COLREG and other mandatory instruments continue to apply.
Procedure / How to Complete It
- Determine whether ship/operation falls within the MASS Code and Administration regime.
- Apply the non-mandatory Code where adopted/accepted by flag and project.
- Define modes of operation, human roles, remote-operation arrangements and safety case under the applicable process.
- Do not state that EBP has begun until its framework is defined and implemented.
- Treat 2030/2032 as expected roadmap, updating only after future formal decisions.
Practical Example
A project uses the Code from July 2026 as a non-mandatory framework; it does not claim a treaty entered into force or that the ship automatically becomes mandatory in 2032.
What Typically Goes Wrong
Saying entered into force, inventing a two-year voluntary introduction period, treating EBP as begun, or turning 2030/2032 into legal certainty.
Common Mistakes Mistake Library
| Mistake | Consequence | How to Avoid It |
|---|---|---|
| Saying entered into force, inventing a two-year voluntary introduction period, treating EBP as begun, or turning 2030/2032 into legal certainty. | Incorrect operational decision or regulatory status | Use the primary reference and ship-specific procedure |
What the PSCO Checks
Operational Tips
- Use took effect for the non-mandatory instrument.
- Cite MSC.595(111).
- Always label 2030/2032 as expected and subject to future adoption.
Preparation checklist
- MSC.595(111) identified
- Non-mandatory status clear
- Effective 1 July 2026
- EBP not anticipated
- 2030/2032 expected
- SOLAS/COLREG still applied
FAQ
Related Topics
Last substantive revision of this page: 16 September 2026 · page fingerprint e92726099d6d