🔔 Subscribe to ShipUniverse Weekly →
ADNOC Logistics & Services confirmed on November 10, 2026, that one of its vessels was damaged in an attack inside the United Arab Emirates' territorial waters in the Arabian Gulf. The company said response operations were ongoing but did not identify the vessel, disclose the damage or provide information about its crew. In a separate maritime security warning, UK Maritime Trade Operations (UKMTO) reported that a tanker was struck by an unidentified projectile at 13:38 UTC, approximately 19 nautical miles northeast of Lima, Oman, near the Strait of Hormuz. UKMTO reported that the tanker's crew was safe, with no environmental impact reported, and that its master would assess the damage at first light. Neither authority identified an attacker, and it has not been established whether the two reports concern the same vessel.
ADNOC Confirms Ship Damage. UKMTO Warns of a Tanker Strike Near Hormuz.
One operator statement and one maritime-security warning establish attacks reported in the same region on Tuesday. Neither identifies the affected ship, and their relationship remains unresolved.
Two Reports That Must Be Kept Separate
A lack of vessel identification prevents an authoritative match. Each column below includes only the facts established by its own source.
ADNOC describes an attack in UAE territorial waters on the Arabian Gulf side. UKMTO describes a tanker strike northeast of Lima on Oman's Musandam coast. The UKMTO reference is an approximate location, not a published AIS position. Without a vessel name, IMO number, exact coordinates or matching incident report, the two notices cannot responsibly be counted as two independently confirmed vessel casualties or merged into a single attack.
November 10: The Public Evidence Timeline
Times below are associated with the primary records. The ADNOC publication timestamp must not be mistaken for the actual time its vessel was hit.
UKMTO warning 201-26 records the incident time supplied by the vessel's master near Lima, Oman.
The UAE's Emirates News Agency releases ADNOC's confirmation of damage inside UAE territorial waters.
UKMTO says the tanker's master intends to assess the damage at first light. No subsequent result is included in the initial warning.
Six Questions Still Awaiting Official Answers
Essential to establish ship type, operator, ownership and any link to the tanker off Oman.
The company has not yet reported the crew's condition. UKMTO's positive crew report cannot be transferred to another ship.
Hull integrity, propulsion, steering, cargo systems and pollution prevention are not yet assessed publicly.
UKMTO reports an unknown projectile. The weapon involved in the ADNOC incident has not been identified.
There is no confirmed return-to-service, towage, diversion or repair estimate for either report.
Requires independently matched vessel details, coordinates and timing.
The Hormuz Threat Is No Longer an Isolated Tanker Incident
UKMTO has issued a succession of alerts around the strait, while the IMO's wider incident registry records more than 130 confirmed incidents during the current Middle East conflict.
ADNOC Has Already Reported Fatal Tanker Strikes in 2026
The company was directly affected months before the November 10 announcement. Those earlier events are documented separately and do not identify Tuesday's damaged vessel.
ADNOC confirmed that these two VLCCs were struck by projectiles while transiting the Strait of Hormuz. One seafarer died, several were injured and both tankers sustained significant damage. ADNOC owned Al Bahyah and operated Mombasa B under a time-charter arrangement.
Reuters verified footage of the Singapore-flagged refined-products tanker on fire near Oman. The vessel is managed by Navig8, a company majority-owned by ADNOC Logistics & Services. That makes the operator's extended group exposure relevant to the regional attacks.
Six Commercial Exposures After a Vessel Strike
These categories explain how security events can translate into financial and operating consequences. No individual amount is yet confirmed for Tuesday's incidents.
Medical response, welfare, crew replacement and continuation of safe manning.
Damage surveys, temporary repairs, propulsion restrictions and class review.
Cargo integrity, contamination checks, transshipment and delivery obligations.
Unavailable earning days, missed delivery windows and recovery of the voyage schedule.
Coverage classification, deductibles, additional premiums and insurer notification requirements.
Potential containment, survey and cleanup obligations if damage affects cargo or bunkers.
Iran's Revolutionary Guard naval authorities have publicly attributed some recent tanker fires to naval mines and alleged use of unauthorized routes. Their November 10 claims did not provide independently confirmed vessel identities or establish a link to the ADNOC company announcement or UKMTO 201-26. A reported projectile strike should not be reclassified as a mine strike without evidence.
What Could a Damaged Tanker Cost Before It Returns to Service?
Separate vessel operating costs, foregone contribution, physical repairs and emergency services. Advanced mode adds cargo, salvage, war-risk and hypothetical insurance recovery scenarios. No output describes the actual ADNOC vessel.
Incident Cost Assumptions
Modeled Financial Exposure
Gross operating and casualty expense, less the model's assumed insurance recoveries. This is not a confirmed claim, payable amount or casualty estimate.
Expense & Recovery Breakdown
How Quickly Can Delay Costs Increase?
This sensitivity holds your physical damage, response and insurance assumptions constant and varies only the number of unavailable days. A higher daily cost does not imply worsening vessel damage.
| Unavailable Days | Time-Related Expense | Gross Exposure | Modeled Recoveries | Net Unrecovered Cost |
|---|
Incident Documentation Checklist
A planning aid for maritime operators, not an assessment of ADNOC's response. Marking an item means only that it has been checked by the user.
We welcome your feedback, suggestions, corrections, and ideas for enhancements.
Please click here to get in touch