SuperbaKnowledge Demonstration release
Platforms
Superba ecosystem
SuperbaHubEcosystem overview — how the environments connect, and the architecture behind them
Live demonstrations
Superba KnowledgeYou are hereOperational maritime knowledge
Carbon Easy MapsMaritime decarbonisation, mappedPSC Easy MapsPort State Control, understood as a system
Training
LearningTraining delivery
ENIT
Superba ecosystem
SuperbaHubEcosystem overview — how the environments connect, and the architecture behind them
Live demonstrations
Superba KnowledgeYou are hereOperational maritime knowledge
Carbon Easy MapsMaritime decarbonisation, mappedPSC Easy MapsPort State Control, understood as a system
Training
LearningTraining delivery
Home › Navigation › MASS Code: the New IMO Framework for Autonomous Ships
Regulatory update

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.

MASS Codeautonomous shipsMSC 111IMO

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.

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

  1. Determine whether ship/operation falls within the MASS Code and Administration regime.
  2. Apply the non-mandatory Code where adopted/accepted by flag and project.
  3. Define modes of operation, human roles, remote-operation arrangements and safety case under the applicable process.
  4. Do not state that EBP has begun until its framework is defined and implemented.
  5. 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

MistakeConsequenceHow 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 statusUse the primary reference and ship-specific procedure

What the PSCO Checks

Scope, approval path, modes, human roles, assurance evidence, interaction with mandatory instruments and accurate roadmap status.

Operational Tips

Preparation checklist

FAQ

Did the MASS Code enter into force as a treaty?
No. It is non-mandatory and took effect on 1 July 2026.
Is the EBP already defined?
The roadmap assigns development of the framework to MSC 112.
Will the Code certainly be mandatory in 2032?
That is the expected roadmap, subject to future development, adoption and entry into force.

Related Topics

Bridge Resource ManagementVTS Traffic Management

Last substantive revision of this page: 31 August 2026 · page fingerprint 51177948c2b7