The United Kingdom Maritime Trade Operations published Warning 174-26 on Saturday as an ATTACK product. The working primary is the PDF. The incident date is 16 October 2026. The incident time is 0900 UTC. The source line is Company Security Officer. UKMTO says it received a time-late report of an incident 68 nautical miles northeast of Al Jubayl, Saudi Arabia, of a tanker struck by an unknown projectile. The PDF prints “stuck”; that is the product’s wording for the strike. All crew are reported safe and have been evacuated. There is no reported environmental impact at the time of the report. Vessels are advised to transit with caution and report any suspicious activity to UKMTO while authorities are investigating. UKMTO printed neither a ship name, an IMO number, a flag, a cargo, a heading, a damage survey, a fire line, an attacker, nor a coordinate pair beyond the Al Jubayl offset.
This is an Arabian Gulf file. It is not a Strait of Hormuz file. It is not a rewrite of Friday night’s dedicated India-ministry piece on MT ST 3. It is not a rewrite of Thursday’s dedicated JMIC Update 105. 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 Arabian Gulf at MODERATE and said no confirmed attacks or disruptions had been reported in the Arabian Gulf in that period. Warning 174-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 Saturday as Update 106, as an IMO-board move past 113, or as a Hormuz reopen.
UKMTO later published a second Saturday product, Warning 175-26, for a tanker attacked by a rocket-propelled grenade from a small boat 78 nautical miles northeast of Al Jubayl at 1922 UTC. Reuters, in an Arab News read updated at 11:20 on 17 October, reported both Saturday products and said it could not immediately establish whether the two reports referred to the same incident. Keep the two PDFs as two numbered files. They have different clocks, different sources, different weapons language, and different crew outcomes. 174-26 is the 0900 UTC time-late CSO projectile file with an evacuation. 175-26 is the later master-reported small-boat RPG file and has its own dedicated piece on this desk.
What UKMTO actually printed
The confirmed tape is short. ATTACK. 174-26. 16/10/2026. 0900 UTC. Company Security Officer. Time-late. 68 nautical miles northeast of Al Jubayl, Saudi Arabia. Tanker. Unknown projectile. All crew safe. Evacuated. No reported environmental impact at time of report. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. Al Arabiya, Gulf Today and a Reuters/Arab News write-through carried the same Saturday English read. None of those outlets added a UKMTO hull name, a JMIC listing, or a flag-state casualty report.
Industry colour arrived beside the PDF, not inside it. Vanguard, as reprinted by Al Arabiya and Gulf Today, identified the ship as the Marshall Islands-flagged crude-oil tanker Safeen Principal and said it lost power and suffered an engine-room fire. UKMTO printed none of those words. Open-register colour on the name Safeen Principal points the other way: IMO 9799927, MMSI 470305000, call sign A6E2079, United Arab Emirates, 2017 feeder containership of about 143 metres, not a Marshall Islands VLCC, with recent AIS colour toward Dammam. Do not collapse Vanguard’s tanker naming onto that container-ship file, and do not brief either sentence as a UKMTO naming. Treat “Safeen Principal” as unresolved industry colour until UKMTO, JMIC, the flag or the operator put a hull on 174-26.
Iranian messaging is a competing colour file, not an attribution. Monitor-style aggregators and Iranian-facing accounts circulated Armed Forces video of a burning tanker and, in some headlines, an Iran-strike line. UKMTO did not name an attacker. Update 105 already told masters that IRGC activity, UAV overflight and hail pressure persist in the wider theatre; that is the last numbered JMIC assessment, not a Saturday finding that 174-26 was an IRGC shot. Do not brief the video as the product.
Operational implications
For a CSO with tankers still working the western Arabian Gulf — Jubail, Ras Tanura, King Fahd Industrial Port, Dammam and the approaches to those terminals — Saturday is the first numbered UKMTO attack west of the Hormuz cluster since Update 105 closed the Arabian Gulf period with a blank kinetic line. Update 105’s Arabian Gulf outlook was MODERATE: residual kinetic risk, GNSS interference, and elevated targeting risk for AIS-on ships sitting still. 174-26 does not automatically rewrite that assessment. It does tell a master that the 16 October tape now includes a projectile strike and a full crew evacuation about 68 nautical miles off the Saudi Gulf coast, not inside the Strait traffic-separation scheme. Plan the next Jubail or Ras Tanura run on Update 105 plus the new numbered warning, not on a headline that the war has “moved to Saudi waters” as a legal finding.
Evacuation is the other operational fact. 166-26 through 173-26, on the dedicated Update 105 tape, were mostly continue-passage or NUC files inside Hormuz. Petro Dolphin remains the dedicated 165-26 Sohar evacuation and missing-crew file. GFS Pride remains the dedicated 170-26 fire, drift and sink. 174-26 is a third evacuation geometry, this time in the western Gulf, with no wreck product, no NAVAREA, no pollution volume and no named salvage tug on the public tape. A DPA should log a possible not-under-command or abandoned tanker northeast of Jubail until the flag, the coastal state or a later UKMTO revision says the crew went back aboard or the hull was taken in tow. Do not treat “no reported environmental impact at time of report” as a completed survey. UKMTO dated that sentence to the time of the CSO report.
Do not assign ST 3 to this PDF. Friday’s dedicated piece is a Union-minister crew-safety naming: crude-oil tanker MT ST 3, projectile, Strait of Hormuz, 15 Indian seafarers safe. Sonowal printed no UKMTO number. Saturday’s 174-26 prints no hull and no Hormuz. The clocks can sit on the same calendar day without being the same casualty. 171-26 remains the dedicated 13 October unnamed outbound Hormuz tanker. 160-26 / GEM NO.2 remains the dedicated UAE-anchorage Arabian Gulf extension on Update 104. None of those files is 174-26.
Charterers will ask whether a western-Gulf projectile day changes additional war-risk, waiting-at-anchor instructions, or the decision to keep AIS on while drifting off Jubail. Saturday’s primary does not reprint a Joint War Committee amendment, a class circular, a Saudi Ports Authority notice, or a pollution figure. It reprints a time-late CSO report and an evacuation. Keep GNSS-interference and AIS-risk drills from Update 105 in the master’s pack. Report to UKMTO. Do not invent a 176-26, an Update 106, or a Safeen Principal flag circular to hold the file.
Do not recast Saturday as a Hormuz increment, as a rewrite of Update 105, as an ST 3 numbering, as a Pride or Giselle wrap, or as a single-incident merge with 175-26. The confirmed facts are Warning 174-26, ATTACK, 16 October 0900 UTC, time-late CSO, tanker, unknown projectile, 68 nautical miles northeast of Al Jubayl, crew safe and evacuated, no reported environmental impact at time of report, no hull name, JMIC still Update 105, IMO board still 113 as at 14 October.
What Operators Should Note
- Log a numbered UKMTO attack, not a Hormuz file. Warning 174-26. 16 October 2026, 0900 UTC. Time-late Company Security Officer report. Tanker struck by an unknown projectile 68 nautical miles northeast of Al Jubayl, Saudi Arabia. All crew safe and evacuated. No reported environmental impact at time of report. UKMTO printed neither hull, IMO, flag, cargo, heading, fire nor attacker.
- Keep Update 105 in the master’s pack. Arabian Gulf remains MODERATE on the 15 October JMIC note, ICOD 151300 UTC. Saturday does not print Update 106 and does not move the IMO board off 113 as at 14 October. Transit with caution. Report to UKMTO. Do not treat an AG projectile day as a Hormuz downgrade or as a new regional threat scale.
- Treat the evacuation as an open NUC/salvage watch. The crew left the ship. UKMTO has not printed a return-aboard, a tow, a wreck, a NAVAREA or a pollution volume. Do not brief “no environmental impact at time of report” as a completed survey. Watch the next numbered warning, a Saudi coastal-state notice, or a flag/class circular.
- Do not put a name on the hull. Vanguard’s Safeen Principal / Marshall Islands / engine-room-fire line is industry colour. Open-register Safeen Principal IMO 9799927 is a UAE feeder containership, not that tanker. Iranian burning-tanker video is messaging, not a UKMTO attribution. Wait for UKMTO, JMIC, the flag or the operator.
- Do not assign ST 3 or 171-26 to this PDF. ST 3 remains Friday’s dedicated India-ministry Hormuz naming. 171-26 remains the dedicated 13 October unnamed outbound tanker. 173-26 remains Al Saadiyat. GEM NO.2 remains the earlier UAE-anchorage AG file. 174-26 is the new western-Gulf number.
- Keep 175-26 on its own product. Reuters could not say whether the two Saturday reports were one casualty. The PDFs differ on time, source, weapon and whether the crew left the ship. Brief them as two files until UKMTO collapses them.
Regulas Shipping will keep lining Warning 174-26 against Update 105’s still-MODERATE Arabian Gulf line so operators can treat Saturday as a numbered western-Gulf projectile evacuation, not as a Hormuz rewrite or a named-hull finding.
