Security · HSSE Watch
IMO Seafarer Protection Update: Keep Essential Support Working
Published
IMO publication: 6 November 2026. Reported attack: 5 November 2026, Strait of Hormuz. Council session: 2–6 November. Article/source review: 7 November 2026.

Voyage disruption is also a people issue. When security conditions delay departure, relief or assistance, the essential support that keeps a crew safe must continue. A new IMO statement gives that responsibility renewed urgency.
The new confirmed development
IMO's statement published 6 November 2026 reports another seafarer death following an attack on M/T VELOS SAPPHIRE in the Strait of Hormuz on 5 November. The Council met from 2 to 6 November and called for protection of seafarers' safety, security, health and well-being.
The statement highlights threats to food, water, medical care and repatriation arising from conflict, including risks to people aboard ships unable to leave the Persian Gulf. This is not a new vessel-specific routing instruction or a finding about the cause, attacker or weapon in the VELOS SAPPHIRE incident. It does not establish that this attack is the event described in any particular UKMTO warning.
The practical angle: continuity of essential support
The following framework is our original application for ship and shore teams, not additional findings about the named vessel. Security planning often concentrates on a voyage decision or an immediate emergency. The supporting question is what happens to the people if disruption lasts longer than expected.
Use the Master's authority, company arrangements, responsible authorities and current official security advice for live decisions. This article does not recommend a route, an approach to a casualty or a change to a ship security plan. Do not circulate restricted security details in public comments or social posts.
Check needs against the people actually aboard
Review essential provisions, potable water, access to medical advice, necessary medication and arrangements for communication. Assign ownership to identified ship and shore roles. A request sent is not the same as a request received, accepted and fulfilled.
Record practical limitations early. For example, a planned delivery or relief can become uncertain if access changes. Make the contingency and the next escalation point clear instead of assuming yesterday's confirmation still applies. Personal health information should remain with authorised personnel and appropriate professionals.
Protect workload, rest and confidential support
Extended uncertainty can add workload, repeated calls and pressure to remain constantly available. Check how watchkeeping, emergency duties and communications affect the crew's real opportunities for recovery. A schedule on paper is not evidence that a person had uninterrupted rest.
Make confidential welfare support accessible and explain how a concern can be raised without stigma. Keep routine welfare information separate from operational status reports where appropriate. Do not require someone to disclose private medical or family circumstances to a whole watch team in order to seek help.
Make shore follow-through visible
- Name the owner: identify who coordinates provisions, medical support, communications and relief issues, with an after-hours backup.
- Track fulfilment: distinguish requested, confirmed, in progress and completed support. Record the last reliable update.
- Escalate a gap: use the agreed company, flag-state, port-state or other relevant assistance channels as applicable to the situation.
- Recheck after change: review arrangements when a vessel's movement, port access, staffing or assistance availability changes.
Questions for ship and shore leadership
- Which essential need would become difficult first if the disruption continued?
- Who checks that a support request reached the person able to act?
- Can the crew access medical advice and confidential welfare assistance?
- Are rest arrangements workable under the actual workload?
- What verified change would trigger the next review?
Video availability
No directly relevant authoritative embeddable video was verified for this new statement or incident. Unrelated conflict footage has not been inserted. Read the IMO publication for its exact scope and wording.
Key takeaway
Protecting a voyage includes protecting the people who must live and work through its disruption. Give essential support a named owner and verify that it reaches the crew.
Sources and dates
- IMO — Council calls for protection of seafarers ↗6 November 2026. Confirms another seafarer death following the 5 November attack; no attacker or weapon identified for that incident.
- IMO Secretary-General — closing remarks to Council 138 ↗Delivered 6 November 2026. Supporting primary statement; not a vessel-specific route instruction.
Sources checked 7 November 2026. Source statements and original practical applications are distinguished above. Always consult current official advice and applicable local requirements.
Share the lesson
Open the separate 9:16 Pinterest poster
Illustrative planning scene, not an actual incident or a technical procedure. HSSE TIPS branding appears only in the designed poster footer.
Your experience matters
Share your thoughts on this page
Have a question, a useful experience or a suggestion? Add your input below.
Comments are public. Keep them respectful and relevant. Do not share contact details, confidential information or emergency reports.
Comments on this page
Loading comments…