UKMTO 194-26 records an Indian-crewed dhow attack outbound through Hormuz

The United Kingdom Maritime Trade Operations centre published Warning 194-26 as a numbered PDF on its product board, filename 20261103-ukmto_warning-194-26.pdf. The face of the product is titled 194-26 — ATTACK. The incident date is 2 November 2026. The incident time is 1105 UTC. The source line is Verified. UKMTO states that it is aware of a report by the Indian Government of an attack on an Indian crewed Dhow whilst sailing outbound through the Strait of Hormuz. The Omani Royal Navy have rescued the surviving crew. UKMTO is unaware of the status of the vessel. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. The location footer printed on the product is Lima, Oman. Emergency contacts printed on the product remain [email protected], +44 (0) 2392 222060, +44 (0) 7779 966976 and +44 (0) 7585 795608.

That is the working primary. Tuesday night’s product is the first numbered UKMTO Attack on a 2 November 1105 UTC Indian-government dhow clock, not a completed hull naming of this afternoon’s dedicated MSV Al Jusufi statements, not a rewrite of last night’s dedicated Warning 193-26, and not a conversion of last night’s dedicated NAVAREA IX 425/26 Selat Storm wreck onto a Lima dhow. It names an Indian crewed Dhow, an outbound Hormuz transit, an Omani Royal Navy rescue of the surviving crew, and an unknown vessel status. It does not name a merchant hull, an IMO number, a flag, a fatality, a crew count, an aerial object, a projectile, a fire, a sinking, a latitude/longitude, a nautical-mile offset beyond the Lima footer, or a keep-clear radius. This afternoon’s dedicated Indian file on this desk still told operators that UKMTO’s public board ended at 193-26. It no longer does. Masters who brief Tuesday night as UKMTO finally printing Al Jusufi on the PDF, as last night’s unnamed 9-nautical-mile Lima hole now carrying a fatality, as Selat Storm leaving Um Al Ghanam, or as tonight’s dedicated 195-26 tanker filed early will have merged four other series into a Verified Attack that still withholds the struck hull.

What the warning actually printed

The confirmed tape is the body of 194-26. UKMTO is aware of a report by the Indian Government of an attack on an Indian crewed Dhow whilst sailing outbound through the Strait of Hormuz. The Omani Royal Navy have rescued the surviving crew. UKMTO is unaware of the status of the vessel. Vessels are advised to transit with caution and report any suspicious activity to UKMTO, whilst authorities investigate. That is the product. Stay with that wording. Do not invent a hull. Do not invent Al Jusufi onto this PDF. Do not invent an IMO number, a call sign, a BDI number or a cargo grade. Do not invent a UAV, a mine, a small-boat device or a boarding. Do not invent a fatality count. “Surviving crew” is the rescue sentence UKMTO printed. It is not a named dead seafarer, not a 13-rescued / 1-dead split, and not a completed next-of-kin circular. Do not invent a lat/long on the UKMTO PDF. 194-26 does not print one. Do not invent a keep-clear radius around Lima, Limah, Khasab, Bukha or Fujairah. The PDF does not print one. Do not invent a fire-extinguished line, a sunk line, a continuing-to-next-port line, or a “vessel and crew safe” line. Those sentences sit on other products. They do not sit on 194-26. The status line on this PDF is that UKMTO is unaware of the status of the vessel. Hold that wording. The rescue line is the Omani Royal Navy, not the Omani Coast Guard. Hold that too.

The product type is the first briefing fact. 194-26 is Attack, the same family that ran dedicated 179-26 through 182-26, unused 186-26, dedicated 187-26, dedicated 188-26, dedicated 189-26, dedicated 191-26, dedicated 192-26, last night’s dedicated 193-26 and tonight’s dedicated 195-26, not the Suspicious Activity family that ran 183-26, 185-26 and 190-26, and not the Advisory family that ran 184-26. UKMTO says an Indian crewed Dhow was attacked outbound through the Strait of Hormuz and that the Omani Royal Navy rescued the surviving crew. It does not say a small boat attached devices. It does not say a mine in the water. It does not say a UAV. It does not say the ship is at anchor, NUC, under tow, sunk, on fire, or continuing to the next port of call. A DPA who briefs Tuesday night as “another Hormuz attached-device hit, crew safe” has borrowed 187-26’s method and Update 110’s Louise 1 all-clear and has dropped the unknown-status dhow that is the whole of this PDF. A DPA who briefs Tuesday night as a completed salvage because the Royal Navy rescued the surviving crew has under-read a numbered Attack that still withholds hull, fire, damage volume, and onward status of the vessel itself.

Verified, Indian Government and Dhow is the second briefing fact. The report sits on a Verified source that is aware of an Indian Government report, not on a Master, not on a CSO, and not on a third-party Channel 16 relay. That is a different reporting path from last night’s dedicated 193-26, whose source line was Master, and from tonight’s dedicated 195-26, whose source line is Company Security Officer. Indian crewed Dhow is also a different type from 193-26’s vessel, 195-26’s Tanker, 192-26’s tanker and 425/26’s tug boat. Do not treat “Indian Government” as a hull naming. Do not treat “Dhow” as a confirmed MSV name, a confirmed tanker recast, or a confirmed IMO row. Do not treat “outbound through the Strait of Hormuz” as a confirmed TSS plot, a confirmed Limah tag, or a confirmed 9-nautical-mile northeast-of-Lima offset. The public PDF does not say whether the dhow is still afloat, whether it sank, whether a wreck buoy was laid, or where the rescued crew were landed after 1105 UTC.

The geography is the third briefing fact. 194-26 prints outbound through the Strait of Hormuz. The location footer is Lima, Oman. That is Musandam’s reporting, on the eastern approach, not this afternoon’s dedicated 72-nautical-mile east-of-Khafji offset, not 0.6 nautical miles west of Jazirat Um Al Ghanam, and not a printed nautical-mile offset off Lima. Last night’s dedicated 193-26 remains a Master Attack 9 nautical miles northeast of Lima with a hole on the starboard side and vessel and crew safe. Tonight’s dedicated 195-26 remains a CSO Attack on a tanker 14 nautical miles northeast of Lima with two unknown projectiles into the engine room. 194-26 is neither of those two Lima offsets. A passage plan that only carried last night’s 9-nautical-mile hole, or that treated Tuesday afternoon as empty because 193-26 was the last UKMTO number at 11:30 UTC, has not budgeted a 1105 UTC outbound dhow on a Lima footer whose vessel status UKMTO does not know.

The numbering is the fourth briefing fact. 194-26 is numbered after 193-26 on the product board. The incident clock is not on last night’s 1 November 2020 UTC hole. 1105 UTC on 2 November sits about 15 hours after 193-26’s 2020 UTC Master report and about 32 hours before tonight’s dedicated 195-26 1900 UTC tanker clock. Monitor the Situation first tracked the public 194-26 product at 13:13 UTC on 3 November, after this afternoon’s dedicated Al Jusufi and NAVAREA III 0168/26 files. Do not brief Tuesday night as “194 after 193 on the water.” Brief Tuesday night as a later-issued Attack on a 2 November Indian-government dhow clock. Do not invent a 196-26 because 195 now sits after 194 on the board.

Industry colour of the same clock, held separately: Monitor the Situation first tracked the public product at 13:13 UTC on 3 November and tagged Strait of Hormuz. Seatrade-Maritime restated the MEA’s MSV Al Jusufi naming against the UKMTO Royal Navy rescue sentence. Xinhua, later on 3 November, restated 194-26 as an Indian government report of an attack on a dhow with Indian crew outbound through Hormuz on Monday, Royal Navy of Oman rescue, vessel status unknown, 1105 GMT. Those reprints are not a PDF naming. Treat them as industry colour of the public PDF and of this afternoon’s dedicated Indian statements. Do not collapse them onto 194-26 as a completed identification on the UKMTO instrument. Do not promote a Seatrade merge of Al Jusufi onto a PDF that still prints Indian crewed Dhow.

Official Indian wrap of the same 2 November clock, held separately: this afternoon’s dedicated Minister of Ports, Shipping and Waterways and Ministry of External Affairs statements remain the named MSV Al Jusufi file — unidentified aerial object, near the coast of Oman / near Limah, 14 Indian seafarers, 13 rescued by the Omani Coast Guard, Gandhar Nahim Ajij from Gujarat dead from injuries, embassy coordinating repatriation. DMA colour on that file added a liferaft abandonment, a Khasab hospital outcome and a Hamriyah-to-Porbandar voyage. Those products name a hull. 194-26 does not. The rescue-service wording splits: the Indian statements print Omani Coast Guard; 194-26 prints Omani Royal Navy. The clock wording splits: the MEA printed “yesterday evening”; 194-26 prints 1105 UTC. Do not promote Al Jusufi, the named fatality, Limah, the Coast Guard line, the aerial-object class, the 14-crew count or the DMA extras onto this PDF. Do not treat 194-26 as a withdrawal of this afternoon’s dedicated Indian file. Keep both in the master’s pack until a later UKMTO PDF, flag circular, JMIC note, IMO row or NAVAREA prints Al Jusufi against the 1105 UTC clock.

What this is not

This is not a completed Al Jusufi naming on the UKMTO instrument. This afternoon’s dedicated Indian statements remain the named MSV Al Jusufi fatality file. 194-26 is the first numbered UKMTO Attack that is aware of an Indian Government report of an Indian crewed Dhow. It still does not print Al Jusufi, a fatality, Limah, an aerial object, a 14-crew count or a Coast Guard line. A passage plan that treats Tuesday night as “UKMTO has now named Al Jusufi” has over-read a Verified dhow Attack. A passage plan that drops this afternoon’s dedicated Indian file because 194-26 exists has deleted a named hull and a named dead seafarer that the PDF still withholds.

This is not Warning 193-26, and it is not last night’s unnamed Lima hole. Last night’s dedicated Warning 193-26 remains an Attack, incident 1 November 2026, 2020 UTC, source Master, filename 20261102-ukmto_warning_193.pdf: vessel struck by an unknown projectile causing a hole on the starboard side, 9 nautical miles northeast of Lima, Oman; vessel and crew safe; no environmental impact reported. 194-26 is 2 November, 1105 UTC, source Verified, Indian crewed Dhow, outbound Hormuz, surviving crew rescued, vessel status unknown. Fifteen hours, a type change and a crew-status conflict separate the two clocks. A Master Attack that prints vessel and crew safe is not a Verified Attack that prints surviving crew and unknown vessel status. Do not collapse Al Jusufi, or this dhow, onto 193-26 because both sit off Lima. Official MSCIO Alert 166/26 remains wrap on dedicated 193-26. Do not promote MSCIO’s Strait of Hormuz tag onto 194-26 beyond the outbound-Hormuz sentence UKMTO itself printed.

This is not Warning 195-26, and it is not tonight’s tanker. Tonight’s dedicated Warning 195-26 remains an Attack, incident 3 November 2026, 1900 UTC, source Company Security Officer, filename 20261103-ukmto_warning_195_26.pdf: tanker struck by two unknown projectiles into the engine room, 14 nautical miles northeast of Lima, Oman; no casualties or environmental impact reported as this time. 194-26 is a 2 November 1105 UTC dhow with a Royal Navy rescue and unknown vessel status. Thirty-two hours and a ship type separate the two clocks. Do not convert tonight’s tanker onto Monday’s dhow. Do not convert Monday’s dhow onto tonight’s unnamed tanker casualty.

This is not NAVAREA IX 425/26, and it is not a Selat Storm naming. Last night’s dedicated 425/26 remains a named hydrographic wreck: tug boat Selat Storm reported involved in a security incident and sunk in 26-22.55N 056-20.47E, approximately 0.6 nautical miles west of Jazirat Um Al Ghanam. 194-26 prints Dhow, outbound Hormuz, Lima. It does not print tug, Selat Storm, sunk, or Um Al Ghanam. IMO’s highlighted-incidents board, as at 3 November, now prints SELAT STORM (IMO 9266657), 1 November, Strait of Hormuz, Damaged, pollution unknown — wrap on dedicated 425/26, not a 194-26 hull and not tonight’s dedicated file. Do not collapse 425/26 onto 194-26 as a UKMTO naming.

This is not Warning 191-26, 192-26 or an IMO LARGO ATOM row, and it is not Leonora Kosan. Sunday night’s dedicated 191-26 remains a Strait of Hormuz Mayday-relay Attack at 1509 UTC 1 November. Monday morning’s dedicated 192-26 remains a tanker Attack at 2347 UTC 1 November, 72 nautical miles east of Ras Al Khafji. IMO, as at 3 November, now prints LARGO ATOM (IMO 1034747) against that 72-nautical-mile Khafji offset — wrap on dedicated 192-26, unused as a second Khafji piece. Dedicated 181-26 / IMO’s Leonora Kosan row remains 9390953, 23 October, 6 nautical miles northeast of Limah. 194-26 is a 2 November dhow on a Lima footer. Do not convert those earlier files onto this number because they share Musandam reporting.

This is not Update 110, not Update 111, not a 129th IMO row, and not NAVAREA IX 427/26. Sunday afternoon’s dedicated Update 110, ICOD 011300 UTC 1 November, remains the last numbered public periodic note. There is no Update 111 this run. IMO’s highlighted-incidents board now prints 128 confirmed incidents and 24 confirmed seafarer fatalities as at 3 November, with new top rows LARGO ATOM, SELAT STORM and ARZANAH (IMO 9928023, 28 October, Strait of Hormuz, Damaged, no pollution). That increment is wrap, not tonight’s dedicated file. IMO has not named 194-26, 195-26, 193-26, 191-26, Al Jusufi, Quba or AZINI. The fatality line is still 24. Do not invent a 25th IMO fatality from “surviving crew.” NAVAREA IX 427/26 and 428/26, both 031500 UTC 3 November, remain Red Sea seaplane-landing boxes off Shura Island and Amaala Triple Bay — wrap, unused as dedicated. 416/26, the Gulf of Aden PAG keep-clear, self-cancelled at 032359 UTC 3 November.

Operational implications

For a master already shaping a Gulf of Oman or southern Hormuz transit, or holding at Fujairah, Khor Fakkan, Sohar, Lima, Limah, Khasab or the Musandam TSS tonight, Tuesday night is a later-issued Attack on a 2 November 1105 UTC Indian-government dhow clock, on top of tonight’s dedicated 195-26 tanker, on top of last night’s dedicated 193-26 hole, on top of this afternoon’s dedicated named Al Jusufi fatality, and on top of last night’s dedicated Selat Storm wreck. Update 110 remains the last numbered JMIC note and still prints Hormuz SEVERE. 016-26 remains the working blockade document pack for hulls that still need the Strait. 194-26 adds an outbound dhow whose surviving crew the Omani Royal Navy rescued and whose vessel status UKMTO does not know. A passage plan that only carried this afternoon’s Indian statements, or that treated Tuesday as closed because 193-26 was the last UKMTO number at 11:30 UTC, has not budgeted a numbered UKMTO Attack on that dhow clock.

An Indian crewed Dhow, learned from a Verified reading of an Indian Government report, is a small-craft lookout problem, a SAR-and-welfare problem and a missing-wreck problem at the same time. 194-26 is not 187-26’s alongside, slow-speed, above-waterline device problem, and it is not 193-26’s starboard-hole, crew-safe problem. It is a lookout, CPA, AIS-on/AIS-off, citadel and possible-unlit-hull problem at the same time as it is a missing-plot problem. BMP MS projectile and citadel guidance remains the working industry pack; 194-26 does not reprint it and does not order an armed team. It also does not authorise a master to treat every radar contact off Lima as this dhow, or to treat every AIS-off wooden hull as Al Jusufi after the fact. Log the Warning number, the 2 November date, the 1105 UTC clock, the Verified source line, the Indian Government report, the Indian crewed Dhow type, the outbound Hormuz sentence, the Omani Royal Navy surviving-crew rescue, the unknown vessel status, and the Lima, Oman footer. Do not log Al Jusufi, a named fatality, Limah, an aerial object, a 14-crew count, a Coast Guard line, a fire, a sinking, a dates cargo, a 9-nautical-mile offset, a 14-nautical-mile offset, or an IRGC attribution that the PDF does not print.

The missing hull, plot and vessel-status lines are the practical damage watch, not a completed all-clear. The public PDF says the Omani Royal Navy rescued the surviving crew and that UKMTO is unaware of the status of the vessel. It does not say whether the dhow is making way, whether it is still afloat, whether it sank, whether a wreck buoy was laid, whether a fire started, or where the rescued crew were landed. Those missing lines are omissions. They are not a completed “all well,” and they are not a NAVAREA wreck symbol. “Unaware of the status of the vessel” is a status sentence. It is not a class survey and it is not a five-cable keep-clear. Next-port authorities will want a written account that 194-26 does not contain. Charterers, manning agents and P&I will now ask whether the ship was outbound through Hormuz after 1105 UTC on 2 November, whether it reported, and whether it was following Update 110 and 016-26. They will not be answered by last night’s 193-26 “crew safe” sentence, by tonight’s 195-26 “no casualties” sentence, by this afternoon’s dedicated Indian fatality file, or by a headline that UKMTO has now named Al Jusufi.

For a DPA and an operator with any merchant hull still using Fujairah, Khor Fakkan, Sohar or the southern Hormuz corridor, the reporting split is the operational content. Sightings of an unlit dhow, wreckage, a Mayday on Channel 16, fire, smoke or pollution go to UKMTO on the 194-26 action line and to the company security officer. NAVCENT NCAGS remains the 016-26 blockade mailbox for hulls that still need the Strait. MSCIO remains the EU ATALANTA registration and alert desk; no numbered MSCIO wrap against the 1105 UTC dhow clock was retrieved this run. Registering with one mailbox is not a substitute for the others. 194-26 does not order a daylight-only transit, a deviation around a published circle, or a halt to visit-and-search compliance. Keep Update 110 Hormuz SEVERE / Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master’s pack. Watch a PDF revision that names a hull, prints a fatality, a lat/long, a NUC, a tow, a fire, a sunk line or a next-port line; a NAVAREA that plots this dhow rather than Selat Storm, RITI or Quba; a flag or class note; a JMIC Update 111; or an IMO-board row that prints this dhow — not a headline that this afternoon’s Indian naming closed last night’s Lima hole or completed a salvage.

Keep the dedicated files on their own lines. 195-26 remains tonight’s dedicated tanker Attack, 1900 UTC, 14 nautical miles northeast of Lima. 193-26 remains last night’s dedicated unnamed Lima hole, 2020 UTC 1 November, vessel and crew safe; MSCIO 166/26 is wrap. This afternoon’s dedicated Al Jusufi file remains the named Indian MSV fatality, Omani Coast Guard rescue, Limah on the MEA tape. 192-26 remains Monday morning’s dedicated Arabian Gulf tanker Attack; IMO’s new LARGO ATOM row is wrap. 191-26 remains Sunday night’s dedicated Channel 16 Mayday-relay Attack. 425/26 remains last night’s dedicated named tug wreck; IMO’s new SELAT STORM row is wrap. 189-26 remains Saturday morning’s unnamed time-late Hormuz Attack; Arzanah on Update 110 and now on IMO’s 128-count is wrap. 188-26 / Al Mayeda, 187-26 / Louise 1 and 186-26 / RITI remain earlier dedicated or unused files. 417/26 remains Quba. 420/26 remains RITI’s fire-and-anchor. Update 110 remains ICOD 011300 UTC, 167 incidents. 016-26 remains the blockade document pack. 424/26 remains the dedicated 3–4 November Pakistan firing box through 040700 UTC 4 November. 427/26 and 428/26 remain wrap. Do not recast 3 November night as a completed Al Jusufi PDF naming, as a 193-26 rewrite, as a 195-26 dhow conversion, as Update 111, or as IMO moving the fatality line to 25.

What Operators Should Note

  • Log 194-26 as a 2 November outbound-dhow Attack on a Verified Indian-government clock, not as an Al Jusufi PDF naming and not as a 193-26 rewrite. UKMTO Warning 194-26, incident 2 November 2026, 1105 UTC, source Verified. Filename 20261103-ukmto_warning-194-26.pdf. Indian Government report of an attack on an Indian crewed Dhow whilst sailing outbound through the Strait of Hormuz. Omani Royal Navy rescued the surviving crew. UKMTO unaware of the status of the vessel. Transit with caution. Report suspicious activity to UKMTO, [email protected] / +44 (0) 2392 222060. Authorities are investigating. Location footer Lima, Oman. UKMTO printed neither hull, IMO, flag, fatality, crew count, aerial object, projectile, fire, sinking, lat/long, nautical-mile offset, anchorage, NUC, tow, next port, nor a keep-clear radius. This is not a completed Al Jusufi naming, not 193-26, not 195-26, not 425/26, and not Leonora Kosan.
  • Hold the clock, the water and the type. 194-26 is Attack, not Suspicious Activity. The working date is 2 November. The working time is 1105 UTC. The working source is Verified, not Master, not Merchant Vessel, and not CSO. The working type is Indian crewed Dhow. The working water is outbound through the Strait of Hormuz with a Lima, Oman footer. The working rescue line is Omani Royal Navy, surviving crew. The working vessel line is status unknown. The product number is 194. The incident clock sits after 193-26’s 2020 UTC 1 November hole and before 195-26’s 1900 UTC 3 November tanker. Do not brief Tuesday night as “193-26’s Lima hole, now with a fatality.” Do not brief Tuesday night as quiet because the PDF withholds hull and plot.
  • Hold this afternoon’s dedicated Al Jusufi file as wrap, not as a 194-26 hull. Minister / MEA: MSV Al Jusufi, unidentified aerial object, near the coast of Oman / near Limah, 14 Indian seafarers, 13 rescued by the Omani Coast Guard, Gandhar Nahim Ajij dead from injuries. DMA colour: liferaft, Khasab hospital, Hamriyah to Porbandar. Those products name a hull. 194-26 does not. Rescue-service wording splits (Coast Guard vs Royal Navy). Clock wording splits (MEA “evening” vs 1105 UTC). Do not promote Al Jusufi, the named fatality, Limah, the aerial-object class or the DMA extras onto this PDF. Seatrade’s merge of the two tapes is industry colour.
  • Do not collapse 193-26, 195-26, 425/26 or IMO’s new 128-count rows onto this number. 193-26 remains last night’s dedicated unnamed Lima hole, 9 nautical miles northeast, vessel and crew safe; MSCIO 166/26 is wrap. 195-26 remains tonight’s dedicated tanker Attack, 14 nautical miles northeast of Lima, two projectiles into the engine room, no casualties. 425/26 remains last night’s dedicated Selat Storm wreck; IMO’s new SELAT STORM row is wrap. IMO now prints 128 confirmed / 24 dead as at 3 November, with LARGO ATOM, SELAT STORM and ARZANAH as the new named rows — wrap, not tonight’s dedicated file. IMO has not named this dhow, Al Jusufi, 193-26, 195-26, 191-26, Quba or AZINI. Fatality still 24. Do not invent a 25th IMO fatality from “surviving crew.”
  • Do not merge this watch onto Leonora Kosan, Quba, AZINI, Aden or the expired 416/26 box. 181-26 / Leonora Kosan remains the 23 October 6-nautical-mile northeast-of-Limah row. 417/26 remains the dedicated MSV Quba sunk file. 190-26 / 161/26 remains the dedicated fishing-vessel hijack, AZINI; MSCIO Update 02 on that page now prints the vessel liberated and the incident closed — wrap, unused as dedicated. 184-26 / 416/26 remains the Gulf of Aden PAG keep-clear and is now self-cancelled at 032359 UTC 3 November. 424/26 remains the dedicated 3–4 November Pakistan firing box through 040700 UTC 4 November. 427/26 and 428/26 remain Red Sea seaplane-landing wrap. 016-26 remains the blockade document pack. Update 110 remains the last numbered public periodic note. No Update 111, no numbered MSCIO wrap against the 1105 UTC clock, no ARN 163 this run.
  • Treat the missing hull, plot and vessel-status lines as open damage lines. The public tape prints Indian crewed Dhow, outbound Hormuz, Omani Royal Navy surviving-crew rescue, vessel status unknown, Lima footer. It does not print a hull, a fatality, a lat/long, a wreck buoy, a fire, a survey, a NUC interval, a tug, a next-port name or a class note. Keep Update 110 Hormuz SEVERE / Arabian Gulf SUBSTANTIAL and 016-26 visit-and-search in the master’s pack. Sightings go to UKMTO, MSCIO, the Omani authorities and the CSO. Watch a PDF revision that names a hull or prints a lat/long; a NAVAREA that plots this dhow rather than Selat Storm; a flag or class note; a JMIC Update 111; or an IMO-board row — not a headline that this afternoon’s Indian naming closed last night’s Lima hole or that 194-26 completed a salvage.

Regulas Shipping will keep lining Warning 194-26 against this afternoon’s dedicated MSV Al Jusufi statements and against last night’s dedicated Warning 193-26 so operators can treat Tuesday night’s tape as a numbered Verified Attack on an Indian crewed Dhow outbound through Hormuz, not as a completed Al Jusufi PDF naming, a 193-26 rewrite, or a silent IMO fatality-count move.

Don’t miss future updates!

We don’t spam! Read our privacy policy for more info.

More From Author

NAVAREA III 0168-26 is the 3 November in-force list

UKMTO 195-26 records a tanker engine-room hit 14 NM northeast of Lima