• Sourcing2 transcripts collected, 0 new arrivals
  • New storyLyondellBasell misses third-quarter earnings and revenue estimates
  • New storyUSGS reports magnitude 4.7 earthquake near Sykiá, Greece
  • New storyVehicle fire shuts down eastbound Happy Valley Road in Barren County
  • New storyVehicle fire shuts eastbound I-24 lanes in Joelton, backing up Nashville traffic
  • New storyHong Kong security chief unveils joint task force to tackle bid-rigging
  • DevelopingSpringfield man killed in crash on I-57 near Effingham — 2 sources
  • DevelopingTwo hikers remain missing after searchers find collapsed tent near Lake Ann — 25 sources
  • Sourcing7 transcripts collected, 4 new arrivals
  • In productionNovaya Gazeta announces closure, citing pressure from Russian authorities

Conflict · Hormuz tanker attackContinuing story · report 6 of 6

Hormuz tanker resumes voyage after explosive attack; crew reported safe

Two devices attached to the hull caused an engine-room fire, according to reports relaying UKMTO. The crew were safe, but no confirmed link resolves the earlier burning-vessel sighting.

Aired Written 4 min read24 sourcesHeyDay News Desk · About usWatch report

Follow via RSS

Transcript · LOADING

Continuing storyDay 77

6 reports40 outlets60 sources4 videos

Full story

What changed since our last report

23 hours later

Then

Vessel reported on fire in Hormuz. Are the people aboard safe?

What we said was still open

  1. The vessel’s verified identity, crew condition, cause of the fire, damage, environmental consequences and final outcome remain unresolved.

    Still open

    The later tanker account reports safe crew, a fire caused by attached explosives, resumed passage and no reported environmental damage. Without an explicit same-vessel link, those outcomes do not conclusively resolve the earlier sighting; identity and full damage remain unverified. 123

  2. A dated authority or operator update identifying the ship and establishing what happened to the people aboard.

    Still open

    The new publications relay a UKMTO update, but an authenticated dated primary advisory or operator statement identifying the ship and documenting its outcome remains missing. 12

Now

Two devices attached to the hull caused an engine-room fire, according to reports relaying UKMTO. The crew were safe, but no confirmed link resolves the earlier burning-vessel sighting.

Two explosive devices attached to a tanker’s hull were enough to start an engine-room fire and temporarily stop the ship in the Strait of Hormuz. But the people aboard were reported safe, the fire was extinguished and the tanker resumed its voyage, according to United Kingdom Maritime Trade Operations updates relayed by Muslim Network TV and IranWire on October 30. 12

The reported recovery is the immediate good news. The attack itself remains unresolved: investigators have not identified the perpetrators, and the tanker has not been publicly identified in these accounts. Nor has it been explicitly linked to the burning vessel we reported near Khasab, Oman, a day earlier. 23

Key facts

  1. 2Explosive devices reportedly attached to the hull 12
  2. 25 nmReported attack position northeast of Khasab 12

IranWire dates the attack to Thursday evening, October 29, 2026, about 25 nautical miles northeast of Khasab. The account describes a small boat approaching the tanker’s port, or left, side. Two devices were attached above the waterline; the subsequent blasts caused the engine-room fire and temporarily disabled the vessel. It is a specific account of a deliberate attack, not simply an unexplained fire at sea. 2

Muslim Network TV reproduces the progression of UKMTO’s reporting: an initial third-party report of an outbound vessel on fire, with the cause unknown, followed by the account of attached explosives and the ship’s recovery. For this tanker, the later account supersedes that initial uncertainty about the cause. It does not establish the devices’ composition, how they were detonated or the precise technical damage. 1

The two publications relay the same maritime agency’s account; they are not two independent investigations of the attack. The original dated UKMTO advisory and an independent operator or authority confirmation have not been authenticated for this report. The attack sequence and outcomes therefore remain attributed to UKMTO through those published reports.

Two positions, no confirmed vessel link

In our October 29 broadcast, we reported a passing ship master’s sighting of a burning vessel roughly 9 nautical miles—about 17 kilometers—north of Khasab. Its identity, crew condition, cause of fire and eventual condition were unknown. IranWire’s report published that day likewise placed the sighting approximately 17 kilometers north of Khasab and said the ship’s identity, crew status, damage and environmental effects had not been disclosed. 3

The later tanker account gives a different position: 25 nautical miles northeast of Khasab. Those are two reported locations, not a verified track of one ship moving between them. Without a vessel name or an explicit connection from an authority or operator, the safe-crew update cannot conclusively settle what happened to the people aboard the earlier sighted vessel. 23

That distinction matters because the newer account supplies much of what was missing before—but only for the tanker it describes. It establishes a reported cause, extinguishment and return to movement. It does not provide a verified name, IMO identification number, flag, owner, operator, crew count or next destination.

Recovery does not mean no damage

All crew members were reported safe. Neither account establishes how many people were aboard, a rescue or evacuation, or a detailed medical assessment. The vessel continued toward its next port after the fire was put out, but movement is not the same thing as an undamaged ship: an engine-room fire severe enough to disable a tanker is already a consequential result. The full damage and repair cost remain unclear. 12

IranWire says no environmental damage or oil spill had been reported; Muslim Network TV relays UKMTO’s statement of no environmental impact. That is the reported outcome, not an independently inspected environmental assessment. 12

The attached-device account should also be kept separate from other allegations in the strait. IranWire’s October 29 report relayed an IRGC Navy claim that three tankers had struck sea mines during the preceding 24 hours. It also reported that CENTCOM had rejected commercial-vessel mine-strike claims on October 28 and said recognized shipping lanes remained clear. The Iranian claim was unverified, and CENTCOM’s earlier statement cannot adjudicate an attack reported on the following evening. Neither establishes a connection to this tanker. 3

UKMTO advised vessels to transit cautiously and report suspicious activity while authorities investigated. That guidance does not establish a new closure, exclusion zone, mandatory diversion or specific delay to another ship. Likewise, this tanker’s resumed voyage tells us about its own recovery of movement—not the operating status or safety of the entire Strait of Hormuz. 1

The immediate human outcome is reassuring. The remaining questions concern accountability and identification: who reached the tanker’s hull, who directed them, how much damage they caused—and whether a named ship and a documented authority update will finally connect this attack account to the earlier fire sighting.

As aired 12 lines
  1. A tanker disabled by explosive blasts has resumed its voyage, with everyone aboard reported safe. On October 29, we reported a burning vessel near Khasab whose crew's condition was unknown. The tanker update now describes a deliberate attack that reached the ship's hull. Who carried it out, and was this the vessel seen burning earlier?
  2. A passing ship's master supplied the earlier fire sighting. The United Kingdom Maritime Trade Operations agency now describes a tanker attacked with explosives. Its account gives that tanker's crew a safe outcome and says the ship continued toward its next port.
  3. The tanker attack happened on Thursday evening, October 29. A small boat approached the ship before the explosions. The location given for that attack differs from the position of the earlier burning-vessel sighting.
  4. The attack happened about 25 nautical miles northeast of Khasab, Oman, in the Strait of Hormuz. The earlier sighting was roughly 9 nautical miles north of Khasab, or about 17 kilometers. Those positions describe two separate reports of a vessel in trouble.
  5. The location difference leaves a basic identification problem. Nobody has named the tanker publicly in this account. Without an explicit link, its safe crew and resumed voyage can't settle what happened to the vessel in the earlier sighting.
  6. Two explosive devices were attached to the tanker, the maritime agency says. The small boat approached its port side, meaning the left side. The devices were fixed to the hull above the waterline, and the subsequent blasts started an engine-room fire.
  7. The fire temporarily disabled the tanker. For this ship, the later attack account replaces the initial unknown cause with a specific sequence of attached devices and explosions. The account doesn't identify who was in the small boat or who directed them.
  8. Vessels were advised to travel cautiously and report suspicious activity while authorities investigated. Khasab is the port used to locate both reports. The surrounding Strait of Hormuz is a key route for global energy and commodity supplies.
  9. The tanker's return to movement answers what happened to that ship after it was disabled. Its recovery tells us little about other vessels' journeys. The maritime agency's instruction was to proceed cautiously and report anything suspicious.
  10. All crew members were reported safe, and the fire was extinguished before the tanker continued toward its next port. No environmental damage or oil spill had been reported. The ship had nevertheless suffered an engine-room fire severe enough to stop it temporarily.
  11. The full damage and repair cost are still unclear. Investigators also haven't identified the attackers. The known sequence ends with the tanker moving again, while responsibility for the small-boat attack remains unresolved.
  12. The tanker described in the attack account continued its voyage with its crew safe. The earlier fire sighting still has a separate unanswered question. Nobody has confirmed that the vessel seen burning north of Khasab was this tanker.

Sources

24 sources19 outlets

Source map

Follow the evidence behind this report. The map shows its connections; the links below open the sources cited in this article.

Source map loads as you read.

Explore the full newsroom map ↗

Revision log

  1. r1First published.