UKMTO explained

UKMTO — UK Maritime Trade Operations — is a Royal Navy maritime liaison cell based in Dubai. It is the primary 24/7 point of contact for merchant vessels transiting the high-risk area covering the Indian Ocean, Gulf of Oman, Persian Gulf, Red Sea, and Gulf of Aden. This page explains what UKMTO is, what it publishes, and how its advisories are structured.

What UKMTO is

UKMTO (UK Maritime Trade Operations) is a unit of the British Royal Navy headquartered in Dubai, United Arab Emirates. It functions as the primary maritime liaison between coalition naval forces and the commercial shipping community operating in the high-risk area (HRA). UKMTO's geographic mandate covers the Red Sea, Gulf of Aden, Gulf of Oman, Arabian Sea, Indian Ocean north of latitude 10°S, and the Persian Gulf — collectively the area where maritime security threats from piracy, state actors, and non-state armed groups have historically concentrated and where current Iranian interdiction risk is active.

UKMTO is not a command authority. It does not direct vessel movements, issue binding orders, or guarantee the safety of any vessel. Its function is liaison, information coordination, and early warning. UKMTO collects incident reports from masters and operators, correlates them with coalition naval intelligence, and redistributes threat advisories to the maritime community. It operates around the clock, every day of the year.

UKMTO's role within the coalition framework is described in Combined Maritime Forces publications. The authoritative description of UKMTO's mandate is on the UKMTO website.

What UKMTO publishes

UKMTO issues several categories of communication to the maritime community. The terminology used here reflects how UKMTO itself describes its outputs in its public-facing materials and as reported in trade press including gCaptain, Splash247, and The Maritime Executive.

Incident Reports

Factual records of a reported security incident affecting a specific vessel or location. Incident reports are issued after a reported event and typically include a reference number, position, UTC time, vessel type and flag (where known), nature of the incident, and current status. They are the most operationally specific category of UKMTO output. An incident report does not constitute a recommendation; it is a factual disclosure.

Advisories

Broader situational awareness communications covering a geographic area or threat category over a period of time. Advisories may aggregate multiple incidents, describe an evolving threat pattern, or provide general guidance on operating conditions in a defined area. They are typically broader in scope than an individual incident report.

Warnings

Urgent communications indicating a specific, imminent, or active threat in a defined area. Warnings carry higher urgency than advisories and are typically issued in response to a developing or recent kinetic event. Trade press coverage of UKMTO communications uses the term "Warning" consistently with this elevated-urgency sense.

UKMTO also maintains the Vessel Movement Reporting System, through which vessels transiting the HRA are expected to register their transits and check in at defined waypoints. Enrollment in the reporting system is the primary mechanism by which UKMTO tracks vessels and can initiate a response if a vessel fails to check in as expected. Details of the registration process are on the UKMTO website.

How to read a UKMTO advisory

UKMTO advisories and incident reports follow a broadly consistent structure. The fields listed below reflect what commonly appears in UKMTO communications as reported in trade press and as visible in UKMTO's own published examples; the exact format may vary by communication type and may be updated by UKMTO.

• Reference number. A unique identifier for the communication, typically in the format UKMTO/[YEAR]/[SEQUENTIAL NUMBER] or similar. Used to track a developing incident across multiple UKMTO communications.
• Date and time (UTC). All UKMTO communications use Coordinated Universal Time. The time given is the time of the report or observation, not the time of issue unless stated otherwise.
• Position. Geographic coordinates (latitude/longitude in decimal degrees or degrees-minutes-seconds) of the incident or area of concern.
• Vessel description. When a specific vessel is involved, UKMTO typically gives vessel type (tanker, container, bulk carrier), flag state, and a general size indication. IMO numbers and vessel names appear where UKMTO has been able to identify the vessel and where identification does not compromise ongoing operational response.
• Nature of incident. A brief factual description of what occurred or what threat is present. Examples from public UKMTO reports cited in trade press include: "vessel approached by small craft," "suspicious vessel in vicinity," "projectile impact reported," "vessel boarded by armed personnel."
• Current status. The last known state of the situation at the time of issue — for example, "vessel under way, crew safe," "vessel seized," "incident resolved," "situation ongoing."
• Action taken / recommended. Where UKMTO includes a guidance element, it typically takes the form of a factual description of coalition naval response action or a statement to vessels in the area to exercise caution and report any suspicious activity. UKMTO does not issue routing advice in the same way a flag state or P&I club does; its outputs are informational.

How vessels coordinate with UKMTO

Vessels transiting the HRA are expected to register with UKMTO prior to entering the area and to maintain contact at reporting waypoints throughout the transit. The specific contact details — telephone number (a 24/7 Royal Navy watch in Dubai), email format, and the registration form — are published on the UKMTO website. This page does not reproduce them here; UKMTO is the authoritative source and contact details are subject to change.

Masters and operators may also report suspicious incidents, approaches by unidentified craft, or receipt of suspicious communications (including any PGSA-related demands) directly to UKMTO. UKMTO's 24/7 watch operates continuously; there is no hour at which an incident report is too early or too late to submit.

UKMTO registration does not confer protection. It places the vessel in the awareness system of coalition naval forces, which is a precondition for any response if a vessel encounters a threat. Operators and flag states may have separate registration requirements; consult flag-state guidance and P&I club bulletins for the complete registration picture for a given transit.

Relationship to NAVCENT, CMF, and IMB PRC

UKMTO sits within a broader coalition maritime security architecture. The key relationships are:

• NAVCENT (U.S. Naval Forces Central Command). The U.S. naval command authority for the region. NAVCENT provides the command-level framework for military response. Project Freedom — the U.S.-led outbound transit umbrella — is coordinated through NAVCENT. UKMTO serves as the merchant-facing liaison layer; NAVCENT is the command-level authority above it. See Project Freedom explained for more on how that arrangement operates.
• CMF (Combined Maritime Forces). The multinational naval coalition whose task forces conduct maritime security operations in the region. CTF 152 within CMF holds the maritime security mandate for the Persian Gulf; CTF 153 covers the Red Sea and Bab-el-Mandeb. UKMTO's liaison role connects commercial shipping to this coalition framework.
• IMB PRC (International Maritime Bureau — Piracy Reporting Centre). The IMB's Piracy Reporting Centre in Kuala Lumpur (icc-ccs.org/imb) is the parallel reporting channel for piracy and armed robbery incidents globally. In the current Iran-related threat environment, UKMTO is the operationally relevant channel for the Gulf/Red Sea area; IMB PRC covers broader maritime piracy. Masters and operators with incidents involving piracy or armed robbery should report to both.

Limitations

UKMTO's website has consistently returned HTTP 403 responses to automated crawlers, including this site's build pipeline. This is a deliberate configuration using Cloudflare's bot-protection layer, not a transient fault. As a result, this site cannot programmatically ingest or mirror UKMTO advisories, incident reports, or vessel registration guidance. All UKMTO content on this site is described — not reproduced — based on what has appeared in public trade press coverage.

The practical consequence for users of this site: PGSA.IO's live feed does not include UKMTO advisory content sourced directly from UKMTO. Items in the feed that reference UKMTO incidents are sourced from trade press coverage of those incidents (gCaptain, Splash247, The Maritime Executive, CBS News) or from CENTCOM and CMF feeds where those bodies have independently reported the same incident. For the primary UKMTO advisory, always go to ukmto.org directly in a standard browser.

This page is also not a substitute for UKMTO registration, flag-state guidance, or P&I club bulletins. For questions about scam communications, see Scam watch. For questions about Project Freedom coordination, see Project Freedom explained.