They named the miles. They did not name the ship.
WatchfulEye ยท
The conventional narrative is another Hormuz story, the 18 August outbound hit, or the named Greek-managed hulls. On Monday, UKMTO issued a new warning. It names the miles. It does not name the ship.
UKMTO Warning 120-26, 24 August 2026. Schematic of the reported 9 NM northeast of Ash Shishah. Not a satellite image. Ship not named.
## What changed
UKMTO issued Warning 120-26, labeled ATTACK, on 24 August 2026. Report time 2025UTC. Source: Master. This is not the 18 August outbound hit, and it does not name any of the hulls hit earlier in August. It is not Operation Economic Outcast.
The warning: "UKMTO has received a report of an incident 9NM northeast of Ash Shishah, Oman." The Master of an oil tanker reports the vessel struck by an unknown projectile, engine-room damage, vessel disabled. Crew reported safe. Environmental impact unknown at time of report. Vessels advised to transit with caution. Authorities investigating.
That is the official text. The ship's name is not on it. Who fired is not on it.
The War Zone published the same UKMTO wording and linked the official PDF. TWZ published 25 August 2026, 00:25 UTC. The same piece frames the strike as hours after Treasury Secretary Scott Bessent's sanctions announcement, and separates a parallel Houthi claim on the Saudi tanker Amzan off Yanbu in the Red Sea. That is a different waterway. Amzan is Red Sea / Yanbu.
## Sources
UKMTO Warning 120-26. Report date 24 August 2026. Report time 2025UTC. Issue date 24 August 2026. Source: Master.
The War Zone, 25 August 2026, 00:25 UTC. Same UKMTO wording. Bessent timing. Amzan / Yanbu separated as Red Sea.
## How it is being framed
Warning frame. 9NM northeast of Ash Shishah. Engine room. Disabled. Crew safe. That is the official warning.
Unnamed-ship frame. Oil tanker, no name. That is what the warning left blank.
Attribution frame. UKMTO assigned no blame. TWZ wrote that Iran is "extremely likely." That is TWZ inference, not the warning.
Sanctions-timing frame. Hours after Bessent. That is TWZ's headline job. The UKMTO warning does not mention Treasury.
Red Sea frame. Amzan, Yanbu, Houthi claim. Different waterway.
Those five jobs are not the same story. The warning frame can be checked against the PDF. The ship's name and the shooter cannot.
## Reporting versus inference
Reporting is: UKMTO Warning 120-26 exists; report time 2025UTC on 24 August 2026; 9NM northeast of Ash Shishah, Oman; oil tanker; unknown projectile; engine room; vessel disabled; crew reported safe; environment unknown; source Master; the 18 August outbound hit had one crew casualty, as Reuters and Al Jazeera reported, not crew safe; USNI News named Dignity, Pioneer, and Riyan Star on 21 August; this warning names none of them; Amzan is Red Sea / Yanbu.
Inference, labeled as such: a second unattributed projectile on the Hormuz eastern approach is consistent with a waterway that is still being hit. It is not proof of who fired, and it is not a named ship. TWZ's "extremely likely Iran" is a read, not a UKMTO finding.
## What may follow
Reasoning, not a forecast.
If the warning frame is right, the next fact to check is a ship name, or a second UKMTO warning on the same ship. If the unnamed-ship frame is right, the next USNI or Lloyd's report either matches Dignity / Pioneer / Riyan Star or it names a fourth ship. If the attribution frame is right, someone claims it, or UKMTO assigns blame. If the sanctions-timing frame is right, the next UKMTO warning mentions Treasury. We do not have that.
## What remains unresolved
The ship's name. Who fired. Whether the environmental impact is still unknown. Whether this is any of the hulls hit earlier in August. A second independent report on this strike. The sources here are TWZ and the official PDF.
## Corrections
If a source, a frame, or an inference on this page is wrong, we correct it here. contact@watchfuleye.us.
See how the story is framed, why it matters, and what happens next.