Identify what was actually observed
The first report should describe the object and behaviour without guessing its operator.
Useful observations include:
- UTC and independently verified ship position; - first and last bearing, elevation and approximate range; - direction of travel and relative movement; - number of objects; - size, shape, lights, sound and visible payload; - hovering, circling, following, diving or departure behaviour; - any simultaneous VHF call, electronic interference or small craft; - photographs or video obtained without exposing crew; and - radar or optical detection where available.
A small commercial quadcopter, fixed-wing system and loitering munition may present different signs, but visual identification from a moving ship can be unreliable. The log should distinguish “appeared to carry an object” from “armed.”
The team should also check whether the sighting could involve authorized military, coastal, port or survey activity. That check does not require delaying protective measures.
Move people away from exposed positions
The plan should identify protected muster or shelter positions before transit. When a suspicious UAV persists or behaves threateningly, nonessential crew should move inside and away from exposed decks, windows, flammable stores and likely fragmentation paths.
Bridge and engine personnel may need ballistic helmets or vests where the risk assessment and flag or company guidance support them. Protective equipment must not impair hearing, vision, movement or communication.
The bridge cannot normally be abandoned. Practical hardening can include anti-fragmentation measures at windows and controlled personnel positions, as described in the May Hormuz guidance.
Ventilation, watertight integrity, fire parties, medical kits and damage-control equipment should be readied according to the threat. Crew should know the difference between the security alarm, fire alarm and abandon-ship signal.
Shelter is not proof against a direct strike. It is a consequence-reduction measure.
Report early with the correct status
A persistent close overflight, circling contact, apparent targeting behaviour or UAV associated with electronic interference can justify a suspicious-activity report before any impact.
The report should state “unknown UAV observed” and describe behaviour. It should not name an operator without competent attribution.
UKMTO should receive the position, time, course, speed and brief description through the current incident process. The company security officer and applicable flag or naval coordination contacts should be informed under the ship security plan.
For US-flagged vessels, MARAD Advisory 2026-011 calls for immediate SSAS activation and contact with the Fifth Fleet Battle Watch and UKMTO following an attack, incident or suspicious activity. Other flags must follow their own requirements.
If the object dives, releases something, impacts or an explosion occurs, the status changes. The bridge should send an immediate update with casualties, fire, damage, pollution and assistance needs.
Early reporting can warn nearby ships even when the object’s purpose remains unknown.
Do not improvise electronic countermeasures
A crew may propose jamming control links, spoofing navigation, dazzling a camera or using a commercial anti-drone device. These actions can be unlawful, ineffective or hazardous.
Radio-frequency interference can disrupt the ship’s own navigation, communications and safety equipment or affect other users. Some drones operate autonomously and may continue, return or dive after losing a link. The ship may not know which frequency or system it is engaging.
High-powered lasers can injure people or affect aircraft. Projectile weapons can strike other ships or shore areas, damage the vessel and escalate contact with State forces.
Any counter-UAV equipment needs flag, coastal and port-State legal review, technical assurance, electromagnetic-compatibility assessment, training, rules for use and insurer acceptance. A vendor demonstration is not authority to operate it at sea.
Unless an approved system and procedure exist, the crew should not invent a defensive electronic or kinetic response during the incident.
Prepare for impact and secondary effects
The threat plan should assume the UAV may be a sensor for another weapon or part of a combined event. Lookouts should continue scanning the surface and air while the bridge monitors communications and navigation integrity.
Fire and damage-control parties should be ready but protected. Likely consequences include fragmentation, fire, blackout, steering loss, fuel or cargo release, damaged antennas and injured personnel.
After an impact, the ship should maintain safe movement if possible, assess watertight integrity, isolate fire or electrical damage and report. Crew should not rush onto an exposed deck while another object remains nearby.
A near miss can still produce fragments, blast damage or unexploded material. Suspected debris should not be handled casually. The area should be controlled and competent authorities consulted.
Assistance to another struck vessel requires a separate risk assessment because follow-on attack risk may remain.
Preserve evidence without turning crew into observers
Evidence can help authorities determine whether the object was commercial, military, hostile or unrelated. Relevant material includes original images, radar recordings, CCTV, VDR data, radio logs, GNSS anomalies, alarm histories, damage photographs and recovered fragments handled under authority advice.
The company should preserve original files with UTC, device and custodian data. Social-media uploads can remove metadata, expose location and spread unverified attribution.
Crew should not remain on deck to film a threatening object. A protected fixed camera is preferable to an exposed person where available.
Witness accounts should be recorded separately before they are harmonized through discussion. Different observations can help reconstruct altitude, direction and sequence.
The evidence file should preserve what was known when the master acted, not only the final authority conclusion.
Reassess the voyage and commercial exposure
A drone sighting can change the route risk even without a strike. The owner should check whether similar activity was reported, whether authorities revised the threat picture and whether the ship’s timing or public profile creates additional exposure.
Proceed, defer and abort criteria should be applied. A single distant transit may lead to monitoring; persistent following or an authority warning may justify a larger change. The response must remain vessel and time specific.
Insurers should receive notice where policy terms require it, especially after damage, diversion or use of protective measures. Charterers need a factual operational update without unsupported attribution.
Brokers and traders should not publish the ship’s live position or describe the sighting as a confirmed attack. A temporary pause does not prove damage.
ZeaClub can structure sightings by time, behaviour, evidence and verification status, link authority updates and flag possible duplicates. It cannot identify an operator from a low-quality image or authorize countermeasures.
Commercial conclusion
An unknown UAV is a developing security event, not automatically an attack and not automatically harmless.
The ship should track and describe it, preserve navigational control, shelter personnel, ready machinery and damage response, and report early through authorized channels. Any manoeuvre must account for traffic and route safety.
Electronic or armed countermeasures require prior lawful authority and technical integration. The strongest immediate defence is a drilled bridge team that acts on observable behaviour without claiming more certainty than the evidence provides.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- US Maritime Administration, Advisory 2026-011Accessed 2026-11-19
- Industry Guidance on the Safe Management of Vessel Transit through the Strait of Hormuz, May 2026Accessed 2026-11-19
- Joint Maritime Information Center, Information Note 128Accessed 2026-11-19
- UKMTO, recent incidentsAccessed 2026-11-19
- Joint Maritime Information Center, Advisory Update 007Accessed 2026-11-19