The United Kingdom Maritime Trade Operations published Warning 177-26 as an ATTACK product on Sunday. The working primary is the PDF. The incident date is 18 October 2026. The incident time is printed as TBC. The source line is Verified. UKMTO says it has received a report of an incident northeast of Khor Fakkan, United Arab Emirates. A tug travelling southbound has reported being struck by two unknown projectiles. The tug has sustained damage but is continuing on its route. One minor casualty has been reported. Vessels are advised to transit with caution and report any suspicious activity to UKMTO while authorities investigate. UKMTO printed neither a ship name, an IMO number, a flag, a tug class, a tow, a heading beyond southbound, a projectile type, a damage location, an environmental line, an attacker, nor a coordinate pair beyond the Khor Fakkan offset.
This is a United Arab Emirates east-coast / western Gulf of Oman file. It is not a Strait of Hormuz traffic-separation-scheme file. It is not an Arabian Gulf file northeast of Al Jubayl. It is not a Gulf of Aden LNG skiff file. It is not a rewrite of Saturday’s dedicated pieces on Warning 174-26 and Warning 175-26, both of which sit off Al Jubayl, and it is not a rewrite of this morning’s dedicated Warning 176-26, which sits 140 nautical miles southwest of Al Mukalla. As of this writing JMIC’s last numbered public note remains Update 105, JMIC# 001 26, information cut-off 151300 UTC 15 October. That note printed the Gulf of Oman at MODERATE and Hormuz at SEVERE. Warning 177-26 sits after that cut-off. The IMO highlighted-incidents board is still printed as 113 confirmed incidents as at 14 October. Do not brief Sunday’s tug product as Update 106, as an IMO-board move past 113, or as a Hormuz TSS increment.
Reuters, Arab News, Anadolu Agency and Middle East Eye carried the same numbered product on Sunday morning. Those wires reprint UKMTO: two unknown projectiles, damage, continuing on route, one minor casualty, time still to be confirmed. They do not name the hull. Do not import a flag, an operator, a tow, or an Iranian, Houthi or other attacker from colour that the PDF does not carry. Saturday’s IRNA / IRGC unnamed two-tanker mine claims remain unconfirmed colour; Update 105 already printed no substantiation for a 14 October IRGC mine-on-unauthorised-route claim. Do not merge those claims onto 177-26.
What UKMTO actually printed
The confirmed tape is short. ATTACK. 177-26. 18 OCT 2026. Time TBC. Source: Verified. Northeast of Khor Fakkan, UAE. Tug. Southbound. Struck by two unknown projectiles. Damage sustained. Continuing on its route. One minor casualty. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. The PDF filename is 20261018-ukmto_warning_177-26.pdf. UKMTO’s recent-incidents board lists the file under 17 October, which is the board’s grouping date, not a second incident date. Stay with the PDF’s 18 October incident line. Do not invent a hull, a flag, a tow, a citadel, a boarding, a fire, a pollution volume, or a second position.
The casualty line is the first briefing fact that is not on 174-26, 175-26 or 176-26. Sunday’s tug is damaged and still making way, with one minor casualty reported. UKMTO did not say who was hurt, whether the casualty remains aboard, or whether medical assistance was requested. It did not say the tug is not under command. It did not say the tug is drifting. Continuation of the route is a snapshot, not a completed damage assessment. A DPA who has a tug, a barge, an escort or an STS support craft on the Fujairah–Khor Fakkan–Kalba track has to treat two projectile strikes and a casualty as an engineering, medical and reporting problem before it is a naming exercise.
The platform type is the second briefing trap. UKMTO printed a tug, not a tanker and not a containership. Tugs on that coast work harbour assists, STS, wreck response, disabled-hull tows and coastal bunker moves. The PDF does not say whether Sunday’s hull was light, towing, or standing by. Do not brief a VLCC, an LNG cargo or a feeder just because the last three numbered warnings were tankers and an LNG tanker. Do not brief a named salvage tug against GFS Pride’s wreck caution unless UKMTO, a NAVAREA or the flag puts that hull on 177-26.
Operational implications
For a CSO with tonnage still using Fujairah, Khor Fakkan, Kalba, Sohar or the southern Omani corridor toward Musandam, Sunday is a projectile problem on the UAE east coast, not a small-boat RPG problem off Jubail and not a skiff-and-warning-shot problem off Mukalla. Update 105’s last numbered Gulf of Oman line was MODERATE, with attacks described as possible but not likely further east and south of Musandam / Jask. 177-26 does not automatically rewrite that assessment. It does tell a master that the 18 October tape now includes a numbered UKMTO attack on a southbound tug northeast of Khor Fakkan, with damage, continued passage and one minor casualty. Plan the next Fujairah or Khor Fakkan run on Update 105 plus Warning 177-26, not on a headline that the Gulf of Oman has moved to SEVERE or that Hormuz has reopened.
Geography on Update 105 already pointed at this coast. As of 15 October the note printed about 180 vessels at anchor in the vicinity of Fujairah / Khor Fakkan, 178 off Dubai / Jebel Ali to Ras Al Khaimah, and 74 in the vicinity of Musandam / Sohar. The 24–48 hour outlook said that if the Hormuz projectile pattern persisted, additional projectile or drone incidents could affect tankers and container ships at UAE anchorages — Ras Al Khaimah, Umm al Quwain, Sharjah and possibly Fujairah — and both outbound and inbound vessels in the southern Omani corridor. Sunday’s tug is not a tanker and not a containership. It is still a numbered hit on the same east-coast concentration. Stationary AIS-on hulls, tugs standing by disabled ships, and craft working wreck or STS jobs in that density are the units a master has to brief, not only shuttle tankers in the TSS.
Keep the wreck caution on a separate line. Update 105 and NAVAREA IX 373/26 caution mariners about the wreck of GFS Pride and floating containers in the vicinity of 26°16.8′N 056°08.6′E. That is a Hormuz debris object from the dedicated 15 October MPA / Update 105 Pride file. It is not a naming of Sunday’s tug. IMO’s highlighted-incidents board still lists WEDYAN, IMO 9524970, damaged with no pollution on 6 July, 16 nautical miles east of Khor Fakkan. That is a six-month-old board line. Do not collapse 177-26 onto Wedyan, Pride, Petro Dolphin or ST 3.
Do not recast Sunday as a Jubayl increment, as a rewrite of 174-26, 175-26 or 176-26, as an ST 3 numbering, as Update 106, as an IMO-board move, or as a confirmed IRGC mine strike. The confirmed facts are Warning 177-26, ATTACK, 18 October, time TBC, verified source, southbound tug, two unknown projectiles, damage, continuing on route, one minor casualty, northeast of Khor Fakkan, no hull name, JMIC still Update 105, IMO board still 113 as at 14 October.
What Operators Should Note
- Log a numbered UKMTO attack on a tug off Khor Fakkan, not a Hormuz TSS or Jubayl file. Warning 177-26. 18 October 2026. Time TBC. Source: Verified. Southbound tug northeast of Khor Fakkan, UAE, struck by two unknown projectiles. Damage sustained. Continuing on its route. One minor casualty. UKMTO printed neither hull, IMO, flag, tow, projectile type, pollution nor attacker.
- Treat “continuing on its route” as a snapshot, not a completed assessment. The public tape ends at damage, way on, and one unnamed minor casualty. UKMTO did not print NUC, a fire, a tow request, a medical evacuation or an environmental volume. Watch a PDF revision, a NAVAREA, or a flag/class circular before briefing the tug as clear.
- Keep Update 105 in the master’s pack. Gulf of Oman remains MODERATE on the 15 October JMIC note, ICOD 151300 UTC. About 180 vessels were at anchor IVO Fujairah / Khor Fakkan as of that cut-off. The outlook already flagged projectile or drone risk at UAE east-coast anchorages. Sunday does not print Update 106 and does not move the IMO board off 113 as at 14 October. Transit with caution. Report to UKMTO.
- Brief tugs, STS craft and hulls standing by in that density, not only shuttle tankers. 177-26 is a tug product. Harbour assists, wreck response and disabled-hull tows on the Fujairah–Khor Fakkan track now sit on the same numbered attack list as last week’s unnamed tankers and containerships. Do not assume a workboat is below the threat.
- Do not put a name on the hull and do not borrow a mine claim. Pride, Giselle, Al Saadiyat, Petro Dolphin, ST 3 and Wedyan remain their dedicated files. Saturday’s unnamed IRGC two-tanker mine colour is not a UKMTO naming of 177-26. Wait for UKMTO, JMIC, the flag or the operator.
- Leave 174-26, 175-26 and 176-26 on their dedicated pieces. 174-26 and 175-26 remain Saturday’s western-Gulf tanker numbers off Al Jubayl. 176-26 remains this morning’s Gulf of Aden LNG number. 177-26 is the new Khor Fakkan tug number. Watch the next numbered warning, a JMIC Update 106, or a named-hull primary — not a Jubayl or Mukalla rewrite.
Regulas Shipping will keep lining Warning 177-26 against Update 105’s still-MODERATE Gulf of Oman line and the Fujairah / Khor Fakkan anchorage density so operators can treat Sunday as a numbered tug attack with a minor casualty, not as a Hormuz rewrite or a named-hull finding.
