Emergency Preparedness and Contingency Plan
Having a written emergency plan is not enough: the ISM Code requires proof, through regular drills, that the crew could really carry it out.
Operational Explanation
The ISM Code (paragraph 8) requires the Company to identify potential shipboard emergencies and establish procedures to respond to them. Emergency preparedness has two main components: contingency plans, which define the best conceivable course of action to protect the ship, personnel and environment in each identified scenario, and regular drills and exercises, which verify the plan's effectiveness and the crew's actual readiness.
The plan must also specify the availability and maintenance of emergency equipment (lifeboats, firefighting equipment, alarms, communication devices), internal and external communication procedures during an emergency (including notifications to the competent authorities and to the Company's top management), and must be updated based on real experience gained, not left unchanged over time.
Regulatory Reference
ISM Code, paragraph 8 (Emergency preparedness): the Company must identify potential shipboard emergencies, establish response procedures and exercise programmes, and periodically review the plan in the light of experience gained.
Scope of Application
Every ship subject to the ISM Code, for all plausible emergency scenarios identified by the Company based on ship type and area of operation.
Procedure / How to Complete It
- Identify, at Company and ship level, all plausible emergency scenarios (fire, flooding, blackout, man overboard, pollution, security).
- Develop a contingency plan for each scenario, defining roles, actions and the operational sequence.
- Schedule regular drills for each scenario, at the frequency required by SOLAS/ISM and the Company's internal procedure.
- Verify during every drill the availability and functioning of the emergency equipment relevant to the scenario.
- Update the contingency plan based on issues emerging from drills or real emergencies, documenting the changes made.
Practical Example
Example of application: after a fire drill reveals a delay in communication between the bridge and the engine room, the contingency plan is updated to clarify the communication sequence, and the next drill specifically verifies that the crew has taken the improvement on board.
Real Cases
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Drill conducted as a simple verbal announcement, without practical use of the equipment | Crew unprepared for the real use of emergency equipment when actually needed | Conduct drills with actual practical use of the equipment, not just announcements |
| Contingency plan never updated after a real emergency or a drill that revealed issues | The same weaknesses recur in subsequent emergencies | Always update the plan based on issues that emerge, documenting the changes |
| Emergency scenarios limited to traditional ones (fire, abandon ship), neglecting scenarios relevant to the specific ship type | Lack of preparedness for plausible but less common emergencies (e.g. prolonged blackout, security) | Identify emergency scenarios specific to the ship type and area of operation, not only the standard ones |
PSC Observations
Operational Tips
- Always conduct drills with practical use of the equipment, not as a simple verbal announcement.
- Update the contingency plan after every drill or real emergency that reveals an issue, documenting the change.
- Identify emergency scenarios specific to the ship type and area of operation, not only the standard ones.
Checklist
- Plausible emergency scenarios identified for ship type and area of operation
- Contingency plan developed for each scenario with clear roles and sequence
- Drills scheduled at the required frequency and conducted with practical use of equipment
- Emergency equipment verified as functioning during every drill
- Plan updated based on issues emerging from drills or real emergencies