Do not infer motive from repetition

Two attacks on the same vessel can result from deliberate retargeting, route repetition, visibility, coincidence, mistaken identity or factors not publicly known.

Use careful categories:

- confirmed first incident; - confirmed second incident; - verified vessel identity; - observed similarities; - authority attribution; - analytical hypothesis; and - unknown.

IMO's list verifies the event sequence. UKMTO and JMIC reports add operational descriptions, often using “unknown projectile.” Neither wording should be expanded into a motive without evidence.

Commercial teams can change exposure controls without deciding motive. A repeated event shows that prior casualty or voyage history did not prevent another incident.

Do not publicly describe a vessel as “marked” or “targeted twice” unless a competent source supports the targeting claim.

The casualty position can become a hazard zone

After a strike, the ship may transmit distress, appear stationary on AIS, produce smoke or attract rescue traffic. Its position can become predictable and congested.

Create an incident-area ring based on the current threat, not a universal distance. Consider:

- weapon or craft type if verified; - last hostile contact; - debris and unexploded ordnance; - mines or suspicious objects; - fire, smoke and pollution; - drift and traffic; - communications interference; - military activity; and - line of sight or coastal proximity.

Warn nearby merchant ships through proper channels. Authorities should coordinate entry and holding points for responders.

A fixed ring can be misleading if the threat is mobile or long-range. Use time, bearing and behavior, not distance alone.

Update the casualty position and confidence frequently. GNSS interference can make the most widely circulated coordinate wrong.

Separate life rescue from property recovery

People in distress may require immediate rescue even when the area remains dangerous. Salvage, survey, evidence collection and cargo recovery can wait.

Prioritize:

1. distress alert and survivor location; 2. medical evacuation and firefighting for life safety; 3. ship stabilization and pollution prevention; 4. tow or refuge necessary to prevent greater harm; 5. property survey and commercial recovery; and 6. non-essential attendance.

This hierarchy does not make rescue crews expendable. The rescue coordination centre and security authorities should choose the safest available resources and tactics.

A merchant ship can assist from standoff by relaying, observing or searching down-current until a protected unit enters.

Do not send surveyors, lawyers, media or charterer representatives onboard while the follow-on threat remains unresolved.

Tugs and salvors need the security picture

A tug approaching a disabled tanker can become another predictable target. Its small size, exposed deck crew and need to work close aboard increase vulnerability.

Before dispatch, provide:

- verified incident and threat information; - exclusion or controlled areas; - authority and naval contacts; - ship position and drift confidence; - unexploded ordnance or mine concerns; - fire, cargo and pollution hazards; - communications and identification; - rendezvous and abort points; and - what protection, if any, is actually confirmed.

Do not advertise tug arrival or tow route broadly. Limit information to operational need.

The tug master and salvor must retain authority over their own safety. Commercial pressure from owner, cargo or insurer cannot turn an unprotected approach into a reasonable operation.

Include security delay and withdrawal in the salvage plan. A paused operation is not necessarily failed performance.

The ship should avoid becoming static if safely possible

If propulsion and steering remain reliable, movement can reduce predictability and clear a dangerous location. Yet a damaged ship may be unsafe at speed or unable to navigate through traffic.

The master should compare:

- machinery and steering condition; - fire and flooding; - route and sea room; - traffic and navigation interference; - crew capability; - threat direction; - authority instructions; and - destination or refuge.

“Proceed under own power” should include an operating envelope and fallback. A restarted engine is not proof of voyage fitness.

Anchoring can stop drift but expose crew forward and make the ship static. A tow can restore control while adding another vessel and connection team.

No tactic is universally correct. Record why the selected movement reduces total risk.

Responders need one access-control point

A casualty can generate requests from coastguard, navy, port, class, flag, insurers, salvors, cargo interests, investigators and technical contractors.

Appoint one operational coordinator with an access register. Every attendance request should state:

- purpose and urgency; - people and equipment; - authority; - security briefing; - ship hazards; - communications; - transfer method; - time window; and - abort criteria.

The master controls safe access onboard subject to lawful authority. Security plans should not block emergency or public-authority access without justification, but access still needs coordination.

Issue identity and approach instructions to prevent misidentification. An unannounced launch heading toward a recently attacked ship can trigger defensive action.

Commercial visits should use remote data until the security gate opens.

Follow-on risk changes evidence collection

Evidence can degrade, but the effort to preserve it must not create another casualty.

Save VDR data, logs, electronic messages and remote images without sending crew into exposed or damaged areas. Mark suspected ordnance and establish an exclusion zone. Do not move fragments.

Authorities may use aerial or standoff imagery before boarding. Record who collected each file and its time and location basis.

If the ship must move, fight fire or jettison material for immediate safety, document the reason and change where practicable. Evidence preservation never outranks life and pollution prevention.

A second incident needs its own timeline. Do not merge the two attacks into one chronology or assume damage from the later event belongs to the first.

Insurers and investigators require causation by event where evidence permits.

Fleet and voyage history need a new risk field

After any attack, add the vessel's incident history to future voyage approval. This is not a claim that the ship will be attacked again.

Review:

- public identification and media exposure; - visible repair or damage; - repeated route and timing; - flag, ownership, management and cargo changes; - AIS and commercial databases; - crew trauma and confidence; - residual technical limits; and - insurer or authority conditions.

A change of charterer or cargo does not erase the ship's identity. A name or flag change should not be treated as a security control.

Decide whether the next route, timing, escort or waiting plan needs modification. Consider another vessel only after comparing its own crew, capability and exposure.

Maintain privacy and avoid unsupported threat labels that can follow the ship commercially.

Incident clusters need deconfliction

Several attacks in one area can produce multiple casualty zones, tugs, patrol units and diverted merchant ships. Radio and radar pictures become crowded.

Authorities should assign clear coordinators, working channels and approach routes. Ships should report capability and avoid converging without tasking.

Company emergency teams also need deconfliction. One security officer cannot manage several masters, insurers and authorities through separate calls indefinitely. Assign ship-specific leads and a fleet-level common picture.

Track responder availability. The tug or medical asset planned for one ship may be diverted to another.

Charterers and cargo interests should receive scheduled verified updates. Repeated ad hoc calls increase workload and can leak sensitive movement information.

A follow-on incident should trigger the company's surge plan, not simply add another line to the first conference call.

Insurance and contracts require event boundaries

A second attack can raise questions about separate occurrences, deductibles, aggregation, causation, mitigation, deviation and notice.

Notify insurers promptly under the policy. Preserve the ship's condition before each event, repair status, voyage decision and authority information.

Do not admit fault or characterize the occurrence structure in an operational report. State facts and obtain qualified insurance and legal advice.

Charterers may question why the vessel returned to the area or continued. The contemporaneous risk assessment, approvals and master judgment are central evidence.

A prior attack does not automatically make every later voyage unreasonable. It does make unsupported repetition harder to defend.

Cargo claims should distinguish damage timing where surveys and records permit.

A controlled scenario

A tanker is struck, loses speed and waits for a tug near the reported position. Smoke and AIS make the casualty easy to locate. An unidentified aerial contact appears while two commercial launches approach.

The master warns authorities and clears non-essential launches. The rescue coordinator establishes a holding area, while a protected unit checks the contact. The tug receives a secure rendezvous and abort route. VDR and remote evidence are preserved, but survey attendance waits. The ship moves at limited power once technical and navigational conditions permit.

This is a hypothetical scenario, not an account of AL DASMA or a prediction.

Commercial conclusion

The first attack is not a safe endpoint. It can make the ship and everyone approaching it more predictable.

Owners should include follow-on threat in casualty plans and future voyage gates. Salvors and tugs need security integration, not only technical data. Authorities should control the casualty area. Charterers and insurers should respect staged access and preserve event boundaries.

ZeaClub can track incident areas, responders, access, threat updates, evidence and separate event timelines. It cannot secure the scene, attribute repetition or authorize an approach.

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

Sources