{"id":917,"date":"2026-10-06T03:32:43","date_gmt":"2026-10-06T03:32:43","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-an-irgc-tanker-turn-back-after-advisory-152-26\/"},"modified":"2026-10-06T03:33:43","modified_gmt":"2026-10-06T03:33:43","slug":"ukmto-logs-an-irgc-tanker-turn-back-after-advisory-152-26","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-logs-an-irgc-tanker-turn-back-after-advisory-152-26\/","title":{"rendered":"UKMTO logs an IRGC tanker turn-back after Advisory 152-26"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre issued Advisory 152-26 on Monday, 5 October. Sourced to a master, with a report time of 0827 UTC, it said a tanker transiting the Strait of Hormuz inbound had been hailed by Iran\u2019s Islamic Revolutionary Guard Corps 11 nautical miles north of Khasab, Oman, and instructed to turn back or the vessel would be targeted. The master confirmed that the tanker had complied. Authorities were investigating. Vessels were advised to transit with caution and report suspicious activity to UKMTO. The official product named neither hull, flag, cargo nor the exact wording of the hail beyond that instruction.<\/p>\n

Anadolu Agency, Al Arabiya carrying Reuters, Mehr News and gCaptain carried the same unnamed master report on Monday. That is the working primary. 152-26 is an Advisory classified as Suspicious Activity, not an Attack warning. It is a new named-location hail-and-turn-back product, not a reprint of JMIC\u2019s generic \u201coccasional VHF hailing\u201d line, not a projectile hit, and not a rewrite of Monday evening\u2019s Warning 156-26. The useful facts for a DPA and a Gulf master are the IRGC as the hailing party on a UKMTO product, the 11-nautical-mile fix north of Khasab, the inbound transit, the explicit \u201cturn back or be targeted\u201d instruction, and the master\u2019s confirmation of compliance. Do not invent a hull to fill the UKMTO gap, and do not treat a complied-with hail as a completed attack.<\/p>\n

What UKMTO published, and where the ship was<\/h2>\n

152-26 is the first Monday product in the 152\u2013156 sequence. The report time is 0827 UTC on 5 October; the issue date is the same day. Anadolu\u2019s copy said the encounter was on Sunday. Stay with the official product: a Monday advisory, master-sourced, 0827 UTC. Do not move the hail onto Sunday\u2019s 150-26 engine-room file or onto Mokha\u2019s 151-26 explosions note.<\/p>\n

The position is the operational content. Eleven nautical miles north of Khasab puts the hail in the Musandam approaches, on the inbound lane toward the Arabian Gulf, not in the Gulf of Oman STS cluster and not on a Fujairah-bound outbound. UKMTO did not publish a latitude and longitude, a TSS designation, or a finding on whether the ship was inside Omani territorial sea, Omani contiguous zone, or waters Iran treats as its own. Do not write that finding. What the product does say is that an inbound tanker was told to reverse course under threat of being targeted, and that it did so. gCaptain\u2019s first Monday read called that \u201canother form of pressure\u201d that did not result in an attack. Hold that distinction. A hail that produces a U-turn is a routing outcome. It is not a projectile, a boarding, or a detention.<\/p>\n

Mehr News restated the UKMTO sentence and did not add a hull. Al Arabiya\u2019s Reuters copy was the same unnamed inbound tanker. TradeWinds, behind a paywall headline, framed the U-turn as a sign that vessel flow may be falling after a wave of attacks. Use that only as market colour. It is not a UKMTO traffic count, and it is not a finding that this particular ship was carrying a named cargo.<\/p>\n

How the hail sits against Update 102<\/h2>\n

The last public numbered Joint Maritime Information Center regional note is Update 102, information cut-off 041500 UTC on Sunday, 4 October, still SEVERE in the Strait of Hormuz. In the 72-hour operational summary it already recorded that IRGC attacks, attempted attacks and harassment had persisted, including UAV overflight, targeted surveillance of merchant shipping, and occasional VHF hailing, \u201cto assert presence along key transit lanes and maintain pressure on transiting vessels.\u201d The outlook section is more specific: vessels transiting with AIS-on can expect elevated targeting risk \u201cand receive directed hails instructing them to divert toward the northern Iranian-controlled route.\u201d Monday\u2019s 152-26 is the first UKMTO master report in this run that puts a clock, a distance off Khasab, and a complied-with turn-back on that generic line. It is not a rewrite of Update 102, and Update 102 does not name this tanker.<\/p>\n

The same note is the working traffic picture. Independent tracking showed single-digit Strait of Hormuz transits in each direction. U.S. NCAGS data put flows at about 32 vessel transits a day over the previous 72 hours, against a 2025 baseline of about 138 a day. U.S.-facilitated transits for 1\u20133 October were given as 95. Mining watch in and adjacent to the TSS remained in the outlook. A 30-nautical-mile standoff from U.S. units remained the published hygiene. Neutral transit is permitted; unauthorized entry or departure from Iranian ports is not.<\/p>\n

U.S. Central Command, in a 5 October Tampa release, said its forces had redirected the 130th commercial vessel the same day under the naval blockade of ships attempting to enter or depart Iranian ports, resumed on 14 July. Three non-compliant ships had been disabled. Over 12 weeks CENTCOM said it had destroyed 13 commercial vessels it described as blockade violators or part of an IRGC shadow network. Mariners were told to monitor Notices to Mariners and to call U.S. naval forces on VHF Channel 16 in the Gulf of Oman and Strait of Hormuz approaches. That is a separate enforcement channel from an IRGC hail. A master answering an IRGC turn-back instruction 11 nautical miles north of Khasab is not the same event as a CENTCOM redirect of a ship bound to or from an Iranian port. Do not merge the two on the bridge log. Do not treat compliance with the hail as a blockade violation, and do not treat a CENTCOM redirect as an IRGC product.<\/p>\n

Operational implications<\/h2>\n

A hail that orders an inbound tanker to turn back is a routing and charter problem before it is a kinetic one. The ship has already committed to the strait. A U-turn off Khasab puts her across or back into the traffic flow, possibly AIS-on, possibly with a projectile watch already standing, and now with a changed destination. Charterers stemming Gulf load ports need a written decision tree for a hail of this type: whether the master complies, whether the company security officer is on the call, whether the hail is logged and reported to UKMTO and the flag, and whether the ship then holds south of Musandam, proceeds under NCAGS advice, or aborts the inbound entirely. 152-26 records one master\u2019s choice. It is not a standing order for the next inbound.<\/p>\n

JMIC\u2019s Update 102 outlook already told AIS-on ships to expect directed hails toward the northern Iranian-controlled route. Monday\u2019s product is harsher than a suggested divert: turn back or be targeted. That is a threat of force used to reverse an inbound, not a routing recommendation toward Iranian waters. Operators who have been briefing the southern Omani corridor as the working lane should not read 152-26 as a requirement to take the northern route, and they should not read it as a coastal-state pilotage instruction. It is an unnamed IRGC hail at a named distance off Khasab.<\/p>\n

Oman\u2019s Article 10 AIS-on rule inside territorial waters was not withdrawn. The two instructions do not cancel. A ship that goes AIS-off to reduce projectile and hail risk, then finds herself 11 nautical miles north of Khasab, may still have an Omani compliance problem if she is inside 12 nautical miles. UKMTO did not say which side of that line this tanker was on. Passage plans should carry both the hail risk and the AIS-on statutory risk, not one as a waiver of the other.<\/p>\n

The rest of Monday\u2019s UKMTO tape is kinetic and should stay on its own desk: time-late Attack warnings 153-26 (inbound LPG, 1716 UTC 4 October), 154-26 (crude, 1907 UTC 4 October, unknown projectiles) and 155-26 (crude, 3 October, above the waterline, time TBC, possible overlap with an earlier 3 October file), then Warning 156-26 at 1637 UTC, a live engine-room fire. 152-26 is the only Suspicious Activity advisory in that sequence. Do not brief the Khasab U-turn as the cause of the evening fire, and do not brief the evening fire as proof that this inbound was later hit. UKMTO named no hull on either product.<\/p>\n

Do not fold 152-26 into Yanbu loadings, the UAE MPCI container-filing mandate, the Premier Alliance FE1 Suez return, Japan\u2019s 35-ship vessel-level permit, Warning 151-26 south of Mokha, or Iran\u2019s Persian Gulf Strait Authority declaration channel. Those are crude-export, documentation, liner, sanctions, Red Sea and coastal-state products. Monday morning\u2019s file is an unnamed inbound tanker that turned around after an IRGC hail 11 nautical miles north of Khasab.<\/p>\n

What Operators Should Note<\/h2>\n