Safe Return to Port: The Design Principle for Passenger Ships
Safe Return to Port applies to passenger ships constructed from 1 July 2010 above the stated thresholds; in May 2026 MSC 111 approved the non-mandatory Explanatory Notes MSC.1/Circ.1369/Rev.1.
Operational Explanation
SOLAS II-2/21 applies to passenger ships constructed from 1 July 2010 with length L of at least 120 m, defined by II-1/2.5 under the Load Lines Convention, or at least three main vertical zones. Do not substitute subdivision length for L. Apply the relevant construction definition (keel laid or equivalent stage), without automatically importing contractual triggers from other instruments. MSC.216(82).
Regulatory Reference
SOLAS II-1/8-1 addresses essential systems after flooding; II-2/21 addresses return to port and safe areas within the casualty threshold; II-2/22 supports evacuation and abandonment beyond that threshold. MSC 111 approved MSC.1/Circ.1369/Rev.1 according to the IRS report. Consult the final text through the flag for its criteria and dates; a meeting report is not a substitute. IRS MSC 111 report.
Return capability also requires safe-area services, communications and recovery procedures under the design. It is neither a guarantee of return after every casualty nor an instruction to delay abandonment: assess actual damage, available systems and operating conditions under the emergency plan.
Scope of Application
Check applicability of II-2/21–22 and II-1/8-1, their referenced definitions and the approved configuration separately. Application dates for revised Explanatory Notes do not replace SOLAS requirement dates.
Procedure / How to Complete It
- Document construction date and length L under the definitions of the applicable provision.
- Check the alternative dimensional thresholds.
- Apply SRtP rules to the relevant configuration.
- For MSC.1/Circ.1369/Rev.1 test the stated triggers and retain its guidance status.
Practical Example
Example: after a fire in a technical space contained within the design threshold, the crew of a passenger ship subject to SRtP isolates the damage, verifies that the redundant propulsion and electrical systems (physically separated from the affected space) are still available, and brings the ship back to port without the need for evacuation, in line with the SRtP design logic.
What Typically Goes Wrong
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Treating SRtP system redundancy as purely a design feature, without verifying its operational upkeep over time | Progressive degradation of the actual return-to-port capability compared with what was foreseen at the design stage | Include verification of SRtP redundancy upkeep in the planned maintenance programme |
| Crew not trained on the distinction between the return-to-port scenario and the evacuation scenario according to the ship's design damage threshold | Emergency operational decisions not aligned with the ship's design logic | Train the crew on the specific design damage threshold of their own ship, not on a generic SRtP concept |
What the PSCO Checks
Operational Tips
- Know your ship's specific design damage threshold: it is not a uniform concept, it varies from ship to ship.
- Maintain the physical separation of redundant systems as designed: unplanned changes during maintenance work can silently compromise it.
- Train the crew to recognise when an event falls within the SRtP threshold and when it instead requires activation of evacuation procedures.
Preparation checklist
- Construction date documented under the applicable rule
- 120 m/three-MVZ threshold checked
- MSC.1/Circ.1369/Rev.1 treated as approved guidance
- Final revised Notes and their applicability checked
FAQ
Related Topics
Last substantive revision of this page: 15 September 2026 · page fingerprint 20fecadb9f2a