Separate five different milestones

Use precise terms:

1. Attack ceased: no hostile activity currently observed. 2. Immediate danger controlled: life-threatening fire, flooding or exposure is contained. 3. Ship stabilized: trends show the casualty is not worsening within defined limits. 4. Safe to move or remain: navigation, machinery and local conditions support the chosen action. 5. Emergency closed: authorities, company and master agree that special response can end, with residual defects transferred to normal control.

These milestones may occur hours or days apart. A ship can be stable but unfit to sail. It can be safe to tow but not to operate under its own power. It can reach port while the security investigation remains open.

Reports should name the milestone rather than use “all safe.” UKMTO updates commonly distinguish whether an incident is ongoing, whether vessel and crew are safe and whether environmental impact is reported. Those statements are useful, but they do not certify technical fitness.

Keep the threat assessment active

Absence of a visible attacker is not proof that the security threat ended. Drones, small craft, mines, delayed devices or surveillance can remain.

The ship security officer and company security officer should review:

- last confirmed hostile activity; - nearby contacts and warnings; - authority or naval assessment; - unexploded or attached-device risk; - access control and missing equipment; - communications interference; and - route, anchorage or refuge exposure.

Maintain appropriate lookouts and protected positions. Do not send personnel onto exposed decks solely because shooting stopped.

Adjust security level and measures through the approved ship security plan and competent authority process. A company cannot reduce precautions merely to resume cargo.

If the threat is unverified or disputed, state that uncertainty. “No further attack observed for 60 minutes” is stronger than “area secure.”

Account for people beyond the muster total

Confirm every person by name and status, including pilot, contractors, guards and visitors. “All accounted for” does not mean all are fit.

Screen for blast, burns, smoke, toxic exposure, hearing injury, shock and fatigue. Obtain telemedical advice where needed. Track medical evacuations and receiving facilities.

Check that emergency teams have relief. A crew can complete a successful response and then suffer an accident during recovery because watchkeepers are exhausted.

Rebuild a safe watch system before prolonged towing, anchoring or navigation. Record temporary duty changes. Safe manning concerns should be reported to the company and authorities.

Family notifications and welfare support continue after operational stabilization. Do not push survivors into repeated interviews before care and rest.

Prove that fire is out

The disappearance of flame is not final extinguishment. Monitor temperatures, smoke, gas, pressure and adjacent spaces. Inspect remotely or from protected positions.

Set re-entry criteria and fire watch intervals. Account for damaged insulation, electrical circuits, cargo and structural voids. A fixed system discharge may make a space oxygen-deficient or toxic.

Restore ventilation only through an approved plan. Opening a boundary can introduce oxygen and reignite a fire.

Maintain firefighting water, pumps and equipment ready until the competent command declares the fire stable. Replace used extinguishers, breathing apparatus and medical supplies before reducing readiness.

Record the last abnormal reading and the required monitoring period. “Fire out at 0415” should identify the basis and who made the determination.

External firefighters should not demobilize until ship and response command agree on residual heat and access.

Trend flooding and stability

A patched breach, running pump or steady list can conceal ongoing ingress. Continue compartment levels, drafts, trim and list at defined intervals.

Confirm watertight boundaries, pump reliability and temporary-repair limits. Recalculate stability and strength when loading condition or flooding changes. Identify downflooding points and weather limits.

Do not stop pumps to test the patch unless the plan and technical advice support it. A controlled test needs thresholds and backup.

A ship can be stable at anchor but unsafe at speed or in waves. Movement trials belong to the next milestone, not the declaration that flooding is controlled.

Keep naval architect, class and salvor advice connected until the residual condition is understood.

Test machinery as a system

Starting the engine, generator or steering pump proves only that component ran at that moment. Test control, alarms, redundancy, cooling, fuel, lubrication, distribution and response under an approved sequence.

Define the operating envelope:

- available propulsion and revolutions; - steering modes; - electrical sources and endurance; - navigation equipment; - pumps and firefighting systems; - cargo and inert-gas limitations; and - monitoring frequency.

A temporary cable, local control or isolated tank can support refuge movement while remaining incompatible with normal trade.

Class, flag and coastal authorities may require survey or conditions. Record every test and failure. If a system trips twice, do not describe it as restored because it restarted twice.

The master should know the contingency if the repaired function fails during movement.

Cargo and pollution remain separate tests

Confirm cargo containment, tank pressure, temperatures, dangerous-goods condition and lashing or structural damage. Check bunkers and hydraulic systems as well as cargo.

Continue SOPEP or SMPEP actions until the actual or probable discharge threat is controlled and reporting duties are met. A clean sea surface at one time is not proof of no underwater or intermittent release.

Maintain quantity estimates with confidence and method. Notify authorities of revised figures. Do not use a worst-case inventory as the reported actual spill.

Damaged containers or cargo systems may require specialist discharge, isolation or port acceptance. A terminal cannot assume the ship is ready because propulsion returned.

Environmental responders and security teams can demobilize on different timelines.

Authorities and company need a structured handover

The master retains professional judgment for ship safety and security. Coastal, port, rescue, pollution and security authorities each have their own responsibilities. Ask each for explicit status or further requirements.

Issue a stabilization report containing:

- verified facts; - active hazards; - systems restored and unavailable; - temporary controls; - people and medical status; - pollution status; - assistance still required; - operational limits; - next action and authorization; and - next update time.

The company should appoint one coordinator and maintain a decision log. UKMTO should receive required updates and after-action information through the applicable reporting process.

Do not withdraw a distress or urgency message without coordinating with the rescue authority. Do not cancel tugs, escorts or technical teams solely to reduce cost.

Every residual hazard needs an owner and transfer point.

Preserve evidence before normal work resumes

Save VDR data, alarms, logs, media, communications and system states. Photograph damage from safe positions. Protect suspected ordnance or fragments without handling them.

Issue preservation instructions ashore. Record every repair, test, movement and authority direction after the attack, because later losses may depend on the recovery sequence.

Resume routine logkeeping without rewriting emergency entries. Label late entries and corrections.

The ISM Code requires procedures for reporting, investigating and analysing non-conformities, accidents and hazardous situations, with corrective action. That learning process begins after stabilization but should not delay life safety.

Separate the safety review from attribution and liability. “Unknown projectile” remains appropriate until a competent investigation establishes more.

A controlled scenario

A tanker suffers a strike and engine-room fire. Flames are extinguished, all crew are accounted for and propulsion restarts. One navigation system remains failed, a boundary is hot and oily water continues entering a bilge.

The master reports that hostile activity is no longer observed and immediate fire is controlled, but does not close the emergency. Fire watch, pollution response and security lookout continue. Machinery receives staged tests, the bilge source is identified and authorities retain tug support. Only then does the ship shift to a controlled refuge under restrictions.

This is a hypothetical training scenario, not a report of a specific casualty or forecast.

Commercial conclusion

An attack is over only in the narrow security sense when hostile action ceases. The casualty ends later, through evidence that people, ship, navigation, cargo and environment are stable.

Owners should define staged stand-down criteria. Masters need authority to retain assistance and controls. Charterers and traders should receive precise milestones rather than demand “all clear.” Insurers need the transition chronology because damage can develop during recovery.

ZeaClub can track milestones, residual hazards, owners, evidence and approvals. It cannot declare an area secure, certify machinery, close a pollution response or release the master from command.

This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.

Sources