Ro-pax drill: vehicle-deck fire and SMS follow-up
A fictional case connects technical response, passenger management, ship–shore coordination, debrief and action verification while keeping ISM, SOLAS and STCW references distinct.
Operational explanation
Demonstration scenario: a fire indication is simulated on the vehicle deck of the fictional ro-pax ship Aurora while underway. No real emergency is in progress. The drill observes technical response, communications, passenger management and shore support separately.
Why this is a ro-pax-specific case
- The scenario originates in a vehicle/ro-ro space whose arrangement and fire protection must be reflected in the ship plan.
- The technical response must be coordinated with passenger information, movement, assembly and accountability.
- People needing assistance and the competence of personnel assigned passenger-management duties must be considered.
- Bridge, engine room, vehicle-deck teams, passenger service and shore functions produce different but connected evidence.
Demonstration sequence
- Define the scenario and limits: technical and passenger objectives, participants, observers, controls and stop conditions.
- Coordinate the response: alarm assessment, communications and roles across bridge, engine room, vehicle deck and shore.
- Exercise passenger management: messages, flows, assembly, accountability and assistance without creating real risks.
- Run the debrief: compare each objective group with observations and record limitations and open issues.
- Close the follow-up: assign actions, owners and dates, then verify implementation and result separately.
References and sources
SMS baseline: the ISM Code requires companies to identify potential shipboard emergencies, establish response procedures and prepare drill programmes. It does not itself set ro-pax details.
Protection and vehicle spaces: the official SOLAS II-2 summary identifies training/drills and additional requirements for vehicle, special category and ro-ro spaces.
Emergency preparedness: the official SOLAS III summary covers emergency training and drills and additional passenger-ship requirements.
Passenger management: resolution MSC.417(97), table A-V/2-1 includes implementation of muster and evacuation plans and assistance along routes. The IMO Passenger ships area frames ship-specific requirements and crowd management.
Applicability, the current edition, frequencies and ship arrangements must be confirmed against official sources, approved plans and the SMS. These references support the case method; they do not establish that every step applies identically to every ship or voyage.
Recurring mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Treating fire response and passenger management as one generic objective | The debrief cannot show which part worked or requires follow-up | Define and observe technical, passenger and ship–shore objectives separately |
| Making the scenario realistic by creating crowding or using real personal data | The drill introduces unnecessary operational or privacy risks | Use fictional data and injects, stop conditions and controlled simulations |
| Considering the drill closed at the end of the debrief | Actions are assigned without evidence of implementation or result verification | Record owners and dates and keep later verification separate |
Preparation checklist
- Ship arrangement and scenario scope checked
- Technical, passenger and ship–shore objectives separated
- Real roles taken from the muster list, plans and SMS
- Observers, criteria and stop conditions defined
- Communications and accountability included
- Assistance considered without using real personal data
- Debrief structured by observation area
- Actions, owners, dates and later verification recorded
Take-away result
The demonstration file contains scenario and objectives, participants and observers, communications timeline, technical and passenger-management observations, debrief, actions with owners and dates, and later evidence. Documentary completion alone does not prove effectiveness.
Related topics
Last substantive revision of this page: 23 September 2026 · page fingerprint 378f6245090f