The United Kingdom Maritime Trade Operations published Warning 180-26 as an ATTACK product. The working primary is the numbered text on UKMTO’s recent-incidents board. The incident date is 20 October 2026. The incident time is 1830 UTC. The source line is Master. UKMTO says it has received a time-late report of an incident 30 nautical miles southeast of Al Faw, Iraq. The master of a tanker reports being struck by an unknown projectile. The crew are reported as safe. There is no reported damage or environmental impact. 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 cargo grade, a heading, a projectile type, a fire line, an attacker, an STS note, nor a coordinate pair beyond the Al Faw offset.
This is a northern Arabian Gulf file. It is not a Strait of Hormuz traffic-separation-scheme file. It is not a Musandam / Bukha file. It is not an Arabian Gulf file northeast of Al Jubayl. It is not a rewrite of the dedicated 9 September New Andros / Hercules Star Al Faw piece, which sat at about 28 nautical miles south-east of Al Faw on the IMO sheet. As of this writing the IMO highlighted-incidents board, as at 21 October, prints 119 confirmed incidents and does not name an 20 October Al Faw tanker. AL DASMA on that board is a Strait of Hormuz second-attack row, not this product. JMIC’s last numbered public note remains Update 106, JMIC# 001 26, information cut-off 181300 UTC 18 October, Hormuz SEVERE, Arabian Gulf SUBSTANTIAL. Warning 180-26 sits after that cut-off. Do not brief Tuesday’s Al Faw product as Update 107, as an IMO-board move past 119, as a Hormuz TSS increment, or as a second naming of New Andros.
What UKMTO actually printed
The confirmed tape is short. ATTACK. 180-26. 20 October 2026. 1830 UTC. Source: Master. Time-late. 30 nautical miles southeast of Al Faw, Iraq. Tanker. Unknown projectile. Crew reported safe. No reported damage. No reported environmental impact. Transit with caution. Report suspicious activity to UKMTO. Authorities investigating. That is the product. UKMTO’s recent-incidents board groups the file under 20 October. Stay with the board’s 20 October 1830 UTC incident line. The product sequence on that board now runs Advisory 178-26, then this Attack. A 179-26 Attack or Advisory does not appear on the same listing. Do not invent 179-26, and do not treat the jump as a suppressed Al Dasma number. Al Dasma is a different sea.
Arab Times timestamped a Basra dateline on 21 October and reprinted Warning 180-26: tanker, unknown projectile, about 30 nautical miles southeast of Al Faw, approximately 1830 GMT on Tuesday, delayed report from the master, crew safe, no damage, no environmental impact, vessels to transit with caution, authorities investigating. Iran International timestamped its English read at 10:33 UTC the same day and used “30 nautical miles from Al Faw”; stay with UKMTO’s southeast offset, not the shortened wire range. Reuters, as carried by Devdiscourse, printed the same Tuesday Al Faw projectile line. Those wires do not name the hull. They do not name a cargo. They do not print an STS. They do not print a fire. Do not import a named Iraqi, Iranian or other service, a precision munition, or a completed damage survey from colour that the numbered product does not carry.
The product type is the first briefing fact. 180-26 is an Attack, the same family as 174-26 through 177-26, not the Advisory family that ran 178-26 and 163-26. UKMTO says the ship was struck. It also says there is no reported damage. Those two lines sit together on the same product. They are not a finding that the projectile missed, and they are not a completed class survey. The missing hull, cargo and attacker lines are omissions, not a completed identification. A DPA who has a tanker in the northern Gulf approaches to Al Faw, Umm Qasr, Khor Al Zubair or the Basrah holding ground has to treat a numbered time-late Attack as a reporting and war-risk problem before it is a naming exercise.
Geography is the second briefing trap
Al Faw sits at the head of the Arabian Gulf, on the Iraqi side of the Shatt al-Arab approaches. Thirty nautical miles southeast of that point is a northern-Gulf offset, not a Hormuz TSS mile, not 11 nautical miles west of Bukha, and not 68 or 78 nautical miles northeast of Al Jubayl. JMIC Update 106’s central-Arabian-Gulf Jubayl paragraph and its Fujairah / Khor Fakkan density count do not automatically cover this water. The IMO board’s 9 September NEW ANDROS row — IMO 9294252, 28 NM south-east of Al-Faw, damaged, no pollution — is a different date, a different named hull, and a different offset. Do not move New Andros onto 180-26 because both files use Al Faw. Do not move AL DASMA onto 180-26 because both files are 20 October tanker events on neighbouring desks. Al Dasma’s NAVAREA IX 393/26 coordinate is 26-09.02N 055-56.1E, about 11 nautical miles west of Bukha in the Strait of Hormuz. That is several hundred nautical miles from Al Faw.
Riviera carried an Ambrey note of a separate merchant ship targeted by four projectiles during an STS operation in Basrah Anchorage, all reported to have impacted the water, with no damage and no injuries. That is industry colour. It is not Warning 180-26. The numbered product says a tanker was struck, names no STS, and prints no four-round miss. Do not merge the STS splash onto the Master Attack, and do not brief 180-26 as a confirmed miss because Ambrey printed water impacts. Keep them as two tapes until UKMTO, a flag or a coastal-state notice collapses them.
Operational implications
For a CSO with tonnage still using the northern Gulf for Iraqi barrels, STS, floating storage or a wait at Al Faw / Umm Qasr, Tuesday night is a projectile problem in the approaches, not a Hormuz TSS problem and not a Duqm military-interaction problem. Update 106 remains the last numbered JMIC note. It does not list 180-26. The IMO 119-count as at 21 October does not list 180-26. Plan the next Al Faw, Basrah or Khor Al Zubair run on Update 106 plus Warning 180-26 plus the dedicated 119-count piece, not on a headline that the northern Gulf has been added to the IMO sheet or that Hormuz has reopened.
Time-late is the practical watch. UKMTO says the master reported after the event. A ship that was struck at 1830 UTC on Tuesday and only appears as a numbered Attack when the centre publishes the product is a reporting-gap problem for the next hull in the same holding ground. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders while the ship is stopped. The dedicated 9 September Hercules Star / New Andros piece already treated “waiting orders” off Al Faw and off Port Rashid as inside the projectile envelope. 180-26 does not change that briefing. It adds a new numbered Attack on the same coast, with a safer public outcome — crew safe, no reported damage, no reported environmental impact — and with no hull name.
Keep the dedicated files on their own lines. New Andros remains the dedicated 9 September Al Faw IMO row. Hercules Star remains the dedicated Port Rashid fatality file. 174-26 and ST3 remain Saturday’s 68 NM Jubayl file. 175-26 / Loyalty remain the 78 NM Jubayl RPG file, now named on the IMO 119-count. 176-26 remains the Mukalla LNG number. 177-26 / Jif Barracuda remain the Khor Fakkan tug number, now named on the same IMO sheet. 178-26 remains the Duqm Advisory. Al Dasma remains the Hormuz second-attack / NAVAREA IX 393/26 fire. Do not collapse Tuesday’s unnamed tanker onto any of them.
Do not recast 20 October 1830 UTC as a Jubayl increment, as a rewrite of 174-26 through 178-26, as an ST3 numbering, as Update 107, as an IMO-board move, as a confirmed Basrah STS miss, or as an IRGC boarding. The confirmed facts are Warning 180-26, 20 October, 1830 UTC, Master, time-late, tanker, unknown projectile, 30 nautical miles southeast of Al Faw, crew safe, no reported damage, no reported environmental impact, no hull name, JMIC still Update 106, IMO board still 119 as at 21 October without this file.
What Operators Should Note
- Log a numbered UKMTO Attack off Al Faw, not a Hormuz or Jubayl file. Warning 180-26. 20 October 2026. 1830 UTC. Source: Master. Time-late. Tanker struck by an unknown projectile approximately 30 nautical miles southeast of Al Faw, Iraq. Crew reported safe. No reported damage. No reported environmental impact. UKMTO printed neither hull, IMO, flag, cargo, projectile type, fire, STS nor attacker. Arab Times, Iran International and Reuters reprint the same numbered product without a name.
- Treat “struck” and “no reported damage” as two open lines, not a completed miss. The public tape does not say the projectile impacted the water. It does not say the ship continued, went NUC, or went to refuge. It does not say the crew were evacuated. Watch a PDF revision, a flag or class note, a NAVAREA, or a JMIC Update 107 before briefing the tanker as clear, holed, or mistaken identity.
- Do not merge 180-26 onto New Andros, Al Dasma or the Ambrey STS splash. New Andros remains the dedicated 9 September named Al Faw row, 28 NM south-east, damaged, no pollution. Al Dasma remains the dedicated IMO 119 / NAVAREA IX 393/26 Hormuz fire at 26-09.02N 055-56.1E. Ambrey’s four-projectile Basrah STS water impacts remain industry colour. 180-26 is a new numbered Attack on a new clock.
- Keep Update 106 and the 119-count in the master’s pack, and do not stretch them to this product. Hormuz remains SEVERE and the Arabian Gulf SUBSTANTIAL on the 18 October JMIC note. The IMO board as at 21 October is 119 confirmed / 24 dead and does not print an Al Faw 20 October row. 180-26 sits after both cut-offs. Transit with caution. Report to UKMTO.
- Put the Al Faw / Umm Qasr / Basrah holding ground back on the night orders as a projectile envelope. Time-late means the next ship in the same roadstead may only hear the Attack after it is over. Answer UKMTO and the DPA while the event is happening. Do not treat “waiting orders,” STS or floating storage as a risk-reducing phrase on this coast.
- Leave 174-26 through 178-26 on their dedicated pieces. 174-26 / ST3 and 175-26 / Loyalty remain Saturday’s Jubayl numbers. 176-26 remains Mukalla. 177-26 / Jif Barracuda remains Khor Fakkan. 178-26 remains the Duqm Advisory. 180-26 is the new Al Faw Attack number. Watch the next numbered warning, a JMIC Update 107, or a named-hull primary — not an Al Dasma or New Andros rewrite.
Regulas Shipping will keep lining Warning 180-26 against Update 106’s still-current Arabian Gulf level and against Wednesday’s IMO 119-count so operators can treat Tuesday’s Al Faw tape as a numbered unnamed tanker Attack in the northern Gulf, not as a Hormuz rewrite or a named-hull finding.
