{"id":1159,"date":"2026-10-31T23:34:14","date_gmt":"2026-10-31T23:34:14","guid":{"rendered":"https:\/\/regulasshipping.com\/blog\/ukmto-190-26-records-a-fishing-vessel-boarding-as-possible-pag-activity\/"},"modified":"2026-10-31T23:35:14","modified_gmt":"2026-10-31T23:35:14","slug":"ukmto-190-26-records-a-fishing-vessel-boarding-as-possible-pag-activity","status":"publish","type":"post","link":"https:\/\/regulasshipping.com\/blog\/ukmto-190-26-records-a-fishing-vessel-boarding-as-possible-pag-activity\/","title":{"rendered":"UKMTO 190-26 records a fishing-vessel boarding as possible PAG activity"},"content":{"rendered":"

The United Kingdom Maritime Trade Operations centre published Warning 190-26 as a numbered PDF on its product board, filename 20261031-ukmto_warning_190.pdf<\/code>. The face of the product is titled 190-26 \u2014 SUSPICIOUS ACTIVITY. The incident date is 30 October 2026. The incident time is 1419 UTC. The source line is Verified. UKMTO states that it has received information that a large fishing vessel has been boarded by unauthorised personnel. Authorities are concerned that this activity will form part of a PAG (Pirate Action Group). Vessels are advised to transit with caution and adopt all BMP measures. Any suspicious activity is to be reported to UKMTO, whilst authorities investigate. Emergency contacts printed on the product remain watchkeepers@ukmto.org and +44 (0)2392222060.<\/p>\n

That is the working primary. Saturday night\u2019s product is a Warning in the Suspicious Activity family, not an Attack and not an Advisory. It does not name a merchant hull, an IMO number, a flag, a fishing-vessel name, a mothership, a merchant target, a lat\/long, a keep-clear radius, or a location footer on the public PDF as retrieved. It does not convert the boarding into a confirmed hijack of a merchant ship. This afternoon\u2019s dedicated IMO 122-count piece on this desk, published about 11:35 UTC, still told operators that UKMTO ended at Warning 189-26. 190-26 was not on that board when that note was written. Masters who brief Saturday night as a Hormuz projectile, as a rewrite of Wednesday\u2019s Gulf of Aden Advisory, as unused 186-26 finally named, or as Update 110 will have merged a fishing-vessel boarding into four other series.<\/p>\n

What the warning actually printed<\/h2>\n

The confirmed tape is the body of 190-26. UKMTO has received information that a large fishing vessel has been boarded by unauthorised personnel. Authorities are concerned that this activity will form part of a PAG (Pirate Action Group). Vessels are advised to transit with caution and adopt all BMP measures. Any suspicious activity to be reported to UKMTO, whilst authorities investigate. That is the product. Stay with that wording. Do not invent a merchant hull. Do not invent a flag. Do not invent a skiff colour, a ladder count, a hook, or a person count. Those details sit on Wednesday night\u2019s dedicated Advisory 184-26. They do not sit on 190-26. Do not invent a lat\/long on the UKMTO PDF. 190-26 does not print one. Do not invent a keep-clear radius around Aden, Bosaso, Khasab or Fujairah. The PDF does not print one. Do not invent a crew-safe line, a fire line, or an environmental-impact line. Those sentences sit on other late-October products. They do not sit on 190-26.<\/p>\n

The product type is the first briefing fact. 190-26 is Suspicious Activity, the same family that ran 183-26 and Thursday morning\u2019s dedicated 185-26, not the Attack family that ran 174-26 through 177-26, 179-26, 180-26, 181-26, 182-26, Thursday afternoon\u2019s unused 186-26, Friday morning\u2019s dedicated 187-26, Friday evening\u2019s dedicated 188-26 and Saturday morning\u2019s dedicated 189-26, and not the Advisory family that ran 184-26 and 178-26. UKMTO says a large fishing vessel has been boarded by unauthorised personnel and that authorities are concerned the activity will form part of a Pirate Action Group. It does not say a merchant vessel was boarded. It does not say a projectile struck a tanker. It does not say a small boat attached devices. It does not say the fishing vessel is at anchor, NUC, under tow, sunk, on fire, or proceeding as a mothership. A DPA who briefs Saturday night as \u201canother Hormuz Attack, crew safe\u201d has borrowed 187-26\u2019s all-clear lines and has dropped the fishing-vessel boarding that is the whole of this PDF. A DPA who briefs Saturday night as a completed PAG disruption because 184-26 already printed ladders and a hook has under-read a numbered Warning that still withholds geography, a merchant target and a disruption line.<\/p>\n

Verified, 1419 UTC and 30 October is the second briefing fact. The report sits on a Friday afternoon clock published on a Saturday product, not on Wednesday\u2019s 1030 UTC Aden Advisory and not on Saturday morning\u2019s time-late 28 October Hormuz Attack. Channel 16, the UKMTO emergency line and the company duty officer still have to be on the night orders for any hull working the Voluntary Reporting Area, the Internationally Recommended Transit Corridor, the Somali Basin, or the Gulf of Oman and Hormuz approaches. Do not treat \u201cVerified\u201d as a hull naming. Do not treat \u201cboarded\u201d as a confirmed merchant hijack. Do not treat the missing location footer as a closed geographic file. The public PDF as retrieved does not say where the fishing vessel was when it was boarded, whether it is still under the boarders\u2019 control, or where it went after 1419 UTC.<\/p>\n

BMP on the action line is Best Management Practices for Maritime Security, the current industry booklet, not a new circular. 190-26 tells transiting ships to adopt all BMP measures and to report. It does not reprint citadel, hardening, AIS or Voluntary Reporting Area procedures. It does not order an armed team. UKMTO emergency reporting remains the watchkeepers mailbox and +44 (0)2392222060. MSCIO\u2019s standing registration mailbox remains postmaster@mscio.eu. Those are different desks. 190-26 does not merge them.<\/p>\n

Industry colour of the same clock, held separately: Monitor the Situation restated the UKMTO fishing-vessel boarding and PAG-concern sentences and tagged the event Gulf of Oman. That reprint is not a naming and is not a location footer. Treat it as industry colour of the public PDF. Do not collapse it onto 190-26 as a completed identification, a Khasab or Fujairah plot, or a territorial-sea finding. The public PDF as retrieved does not print Gulf of Oman, Gulf of Aden, Strait of Hormuz or a port name.<\/p>\n

What this is not<\/h2>\n

This is not a rewrite of 184-26, and it is not a second Aden Advisory. Wednesday night\u2019s dedicated Advisory 184-26 remains an unnamed PAG watch, 1030 UTC 28 October, source Military authorities, location footer Aden, Yemen: reports from various sources of suspicious activity within the Gulf of Aden, potentially indicative of Pirate Action Group Activity; several sightings of suspicious small craft near merchant vessels; one report a green and blue boat with two ladders and one hook with nine persons onboard; transit with caution; follow BMP MS; report to UKMTO. 184-26 is Advisory. 190-26 is Warning \/ Suspicious Activity. 184-26 is 28 October, 1030 UTC. 190-26 is 30 October, 1419 UTC. 184-26 prints small-craft sightings. 190-26 prints a boarded fishing vessel. 184-26 prints Aden, Yemen. 190-26 prints no location footer on the public PDF as retrieved. Do not merge Wednesday\u2019s sighting watch onto Friday\u2019s boarding because both print PAG. Do not convert 190-26\u2019s fishing vessel into 184-26\u2019s green-and-blue nine-person boat.<\/p>\n

This is not a rewrite of NAVAREA IX 416\/26, and it is not a move of 12-42N 047-35E. 416\/26, issued 281500 UTC 28 October and wrapped on Wednesday night\u2019s 184-26, remains the working keep-clear: Gulf of Aden \/ Somalia, possible pirate action group approximately 12-42N 047-35E, keep clear of this position, extreme caution, report incidents, cancel 032359 UTC 3 November 2026. That NAVAREA is still in force tonight. 190-26 does not reprint 12-42N 047-35E. It does not extend the cancel. It does not add a radius. Hold 416\/26 as wrap on the earlier Aden watch, not as a 190-26 plot. A DPA who briefs Saturday night as \u201cthe Aden keep-clear moved\u201d has invented a coordinator revision the Pakistan Saturday table does not print. NAVAREA IX still ends, on that table, at 423\/26 as an in-force list.<\/p>\n

This is not a rewrite of 189-26, 188-26, 187-26 or unused 186-26. Saturday morning\u2019s dedicated Warning 189-26 remains a time-late Attack: crude oil tanker, unknown projectile, outbound Strait of Hormuz, 28 October, time TBC, source Verified. Friday evening\u2019s dedicated Warning 188-26 remains an unnamed vessel Attack, 1800 UTC 30 October, 40 nautical miles south of Lavan Island, port-side projectile, fire, crew reported safe. Friday morning\u2019s dedicated Warning 187-26 Update 001 remains an unnamed outbound tanker Attack, 2212 UTC 29 October, 25 nautical miles northeast of Khasab, two explosive devices attached above the waterline, engine-room fire extinguished, continuing. Thursday afternoon\u2019s unused Warning 186-26 remains a CSO Attack: tanker struck by an unknown projectile at 1600 UTC 29 October whilst completing an outbound Hormuz transit, no reported injuries, no environmental impact report, location footer Khasab, Oman. 190-26 prints a large fishing vessel, boarded, Suspicious Activity, PAG concern. A projectile, a fire, a crude-oil tanker and a Lavan offset are not a fishing-vessel boarding. Do not convert 190-26 onto those Attacks as a late naming.<\/p>\n

This is not 185-26, and it is not Friday morning\u2019s companion dhow wreck. Thursday late-morning\u2019s dedicated Warning 185-26 remains a Suspicious Activity fire sighting 9 nautical miles north of Khasab at 0300 UTC, Third Party, unnamed vessel. Friday morning\u2019s dedicated NAVAREA IX 417\/26 remains the working wreck instrument on dhow MSV Quba, reported sunk in 26-19.95N 056-16.82E. Last night\u2019s dedicated NAVAREA IX 420\/26 remains oil tanker RITI, security incident causing fire onboard, anchored in 26-24.07N 056-24.72E. 190-26 prints a boarded fishing vessel and a PAG concern. A Hormuz fire, a dhow wreck and a named tanker at Ra\u2019s Tahir are not this product. Do not merge them because they sit on a late-October board.<\/p>\n

This is not Update 110, and it is not an International Maritime Organization 123-count. JMIC Update 109, JMIC# 001 26, ICOD 291300 UTC 29 October, remains the last numbered public periodic note, with Hormuz SEVERE, the Arabian Gulf SUBSTANTIAL, the Gulf of Oman MODERATE, the Gulf of Aden SUBSTANTIAL and 160 incidents since 1 March. Update 109\u2019s last 96-hour list ends at 185-26. 186-26, 187-26, 188-26, 189-26, 420\/26 and now 190-26 all sit off that list as published. They are not a completed Update 110. Wednesday afternoon\u2019s dedicated JMIC Advisory Note 016-26 remains the blockade visit-and-search document pack. This afternoon\u2019s dedicated IMO highlighted-incidents board remains 122 confirmed \/ 24 seafarer fatalities as at 30 October, with Ghana Prosperity\u2019s second Strait row as the newest named line. 190-26 does not fill those slots and does not belong on that Middle East highlighted-incidents table. This is not Thursday\u2019s dedicated Contship Jet or Khoryv Black Sea files, and it is not this afternoon\u2019s dedicated NAVWARN 776\/26 Galata diving box. Those are Kaliakra, Shabla and Varna products. They do not belong on a PAG boarding Warning.<\/p>\n

This is not a confirmed merchant hijack, a named mothership, or a corridor closure. 190-26 prints a large fishing vessel boarded by unauthorised personnel and a concern that the activity will form part of a Pirate Action Group. It does not print Asana. Update 108 still carried Asana as hijacked on the unused periodic note that Update 109 later replaced; 190-26 does not move that hull and does not close that case. It does not print a IRTC deviation, a daylight-only order, or an armed-team instruction. Do not promote a PAG-concern sentence to a completed disruption or to a named merchant target.<\/p>\n

Operational implications<\/h2>\n

For a master already in the Internationally Recommended Transit Corridor, shaping the Voluntary Reporting Area overnight, or holding on a Gulf of Oman or Hormuz approach, Saturday night is a bridge-and-lookout problem before it is a policy problem. UKMTO printed a large fishing vessel boarded by unauthorised personnel and then printed the authority concern that the activity will form part of a Pirate Action Group. A boarded fishing vessel is a classic mothership watch: the hull itself may loiter, may close a merchant track, or may launch or recover small craft. The product still stops at \u201cconcerned that this activity will form part of a PAG.\u201d The working instruction is transit with caution, adopt all BMP measures, and an immediate report, not a deviation around a published circle. 416\/26 still gives the earlier Aden watch a plot to keep clear of through 032359 UTC 3 November: 12-42N 047-35E. That plot is not 190-26\u2019s plot. A passage plan that only carried Wednesday\u2019s Advisory, or that treated the corridor as quiet because 184-26 printed sightings rather than a boarding, has not budgeted a Friday 1419 UTC fishing-vessel boarding published on Saturday.<\/p>\n

For a DPA and an operator with ships in the Gulf of Aden, the Red Sea approaches, the Somali Basin, the Gulf of Oman or the Strait this week, the reporting split is the operational content. Sightings of a large fishing vessel under unauthorised control, of small craft working from such a hull, of ladders, hooks or a close CPA go to UKMTO on the 190-26 action line and to the company security officer. MSCIO remains the EU ATALANTA registration and alert desk. Registering with one mailbox is not a substitute for the other. NAVCENT NCAGS remains the 016-26 blockade mailbox for hulls that still need the Strait. 190-26 does not order a daylight-only transit, a deviation around 12-42N 047-35E beyond the existing 416\/26 keep-clear, or a halt to visit-and-search compliance. It also does not authorise a master to treat every fishing vessel in the Voluntary Reporting Area as a confirmed PAG after the fact. Log the Warning number, the 30 October date, the 1419 UTC clock, the Verified source line, the large-fishing-vessel type, the boarded-by-unauthorised-personnel method, the PAG-concern sentence, and the BMP action line. Do not log Aden, 12-42N 047-35E, a green-and-blue nine-person skiff, RITI, Louise 1, Ghana Prosperity, a Hormuz projectile, or a Gulf of Oman territorial-sea finding that the PDF does not print.<\/p>\n

BMP hardening, citadel drills, AIS and lighting policy, and the decision to keep or drop a privately contracted armed security team stay company and flag business. 190-26 does not order a team on, a team off, a speed change, or a corridor closure. Charterers, P&I and war-risk underwriters will now ask whether the ship was in the Voluntary Reporting Area after 1419 UTC Friday, whether it reported, and whether it was following BMP MS. They will not be answered by Saturday morning\u2019s 189-26 Hormuz Attack, by Friday night\u2019s 188-26 Lavan Attack, by this afternoon\u2019s IMO 122-count, or by Wednesday\u2019s 184-26 small-craft Advisory. Off-hire and deviation conversations that treat 190-26 as a Hormuz fixture problem have misread the product type.<\/p>\n

The missing geography, mothership-status and merchant-target lines are the practical watch, not a completed all-clear. The public PDF says none of those things. It does not say whether the fishing vessel is making way, whether it is still boarded, whether small craft have left it, or whether a merchant ship was approached after 1419 UTC. Those missing lines are omissions. They are not a completed \u201call well,\u201d and they are not a confirmed hijack. Next-port authorities will want a written account that 190-26 does not contain. Keep Update 109\u2019s Gulf of Aden SUBSTANTIAL \/ Gulf of Oman MODERATE \/ Hormuz SEVERE lines and 016-26 visit-and-search in the master\u2019s pack. Watch a PDF revision that names a hull, prints a location footer, a lat\/long, a mothership status or a merchant approach; a NAVAREA that plots this fishing vessel rather than 12-42N 047-35E; a flag or class note; a JMIC Update 110; or an official MSCIO alert retrieved from mscio.eu \u2014 not a headline that Saturday night closed Wednesday\u2019s Aden file or completed a PAG disruption.<\/p>\n

Keep the dedicated files on their own lines. 189-26 remains this morning\u2019s unnamed time-late Hormuz crude-oil-tanker Attack. 188-26 remains last night\u2019s unnamed vessel Attack 40 nautical miles south of Lavan Island. 187-26 remains Friday morning\u2019s unnamed outbound-tanker Attack 25 nautical miles northeast of Khasab. 186-26 remains the unused 1600 UTC unknown-projectile Attack. 185-26 remains Thursday\u2019s 9-nautical-mile north-of-Khasab fire sighting. 184-26 \/ 416\/26 remains the Gulf of Aden PAG keep-clear through 3 November. 183-26 remains the 26 October Al-Faw fire. 182-26 remains the 23 October outbound-Hormuz disablement, named Ghana Prosperity on Update 109 and on this afternoon\u2019s IMO 122-count as wrap, not as a 190-26 hull. 181-26 \/ Leonora Kosan remains Limah. 420\/26 remains last night\u2019s dedicated RITI fire-and-anchor. 417\/26 remains Friday morning\u2019s dedicated MSV Quba wreck. Update 109 remains the last periodic threat note. 016-26 remains Wednesday afternoon\u2019s blockade document pack. This afternoon\u2019s dedicated 776\/26 remains the Galata diving box. 775\/26 remains this morning\u2019s two-hour Bulgarian territorial-sea e-mail. Thursday\u2019s 768\/26 and 766\/26 remain the Kaliakra and Shabla Black Sea files. Do not recast 31 October night as a Hormuz Attack, as a named Aden boarding, as unused 186-26 finally published, as Update 110, as an IMO 123-count, or as a corridor closure.<\/p>\n

What Operators Should Note<\/h2>\n
    \n
  • Log 190-26 as a Suspicious Activity fishing-vessel boarding with a PAG concern, not as an Attack and not as a rewrite of 184-26.<\/strong> UKMTO Warning 190-26, incident 30 October 2026, 1419 UTC, source Verified. Filename 20261031-ukmto_warning_190.pdf<\/code>. Large fishing vessel boarded by unauthorised personnel. Authorities concerned the activity will form part of a Pirate Action Group. Transit with caution. Adopt all BMP measures. Report suspicious activity to UKMTO, watchkeepers@ukmto.org \/ +44 (0)2392222060. Authorities are investigating. UKMTO printed neither hull, IMO, flag, mothership status, merchant target, attacker, lat\/long, keep-clear radius, nor a location footer on the public PDF as retrieved. This is not 189-26, not 188-26, not 187-26, not 186-26, not 184-26, and not Update 109.<\/li>\n
  • Hold the clock, the product type and the method.<\/strong> 190-26 is Suspicious Activity, not Attack and not Advisory. The working date is 30 October. The working time is 1419 UTC. The working source is Verified, not Military authorities and not Master. The working hull type is a large fishing vessel, not a crude-oil tanker and not a green-and-blue skiff. The working method is boarded by unauthorised personnel, not an unknown projectile and not two attached devices. Do not brief Saturday night as \u201cWednesday\u2019s Aden watch, upgraded.\u201d Do not brief Saturday night as quiet because the PDF withholds a location footer.<\/li>\n
  • Hold 184-26 \/ 416\/26 on their own line through 3 November.<\/strong> Advisory 184-26 remains the dedicated 1030 UTC 28 October Gulf of Aden small-craft PAG watch, location footer Aden, Yemen. NAVAREA IX 416\/26 remains the keep-clear at 12-42N 047-35E until 032359 UTC 3 November. 190-26 does not reprint that plot, does not extend the cancel, and does not add a radius. Do not move 12-42N 047-35E onto Friday\u2019s fishing vessel. Do not convert the fishing vessel onto the nine-person green-and-blue boat.<\/li>\n
  • Hold Monitor the Situation colour separately.<\/strong> That reprint restated the PDF and tagged Gulf of Oman. The public product does not print Gulf of Oman, Gulf of Aden or a port name. Do not promote a tracker tag to a 190-26 location footer, a Khasab plot, or a territorial-sea finding.<\/li>\n
  • Do not collapse 189-26, 188-26, 187-26, 186-26 or 420\/26 onto this number.<\/strong> 189-26 remains the dedicated time-late outbound-Hormuz crude-oil-tanker Attack. 188-26 remains the dedicated 1800 UTC unnamed vessel Attack 40 nautical miles south of Lavan Island. 187-26 remains the dedicated 2212 UTC attached-device Attack 25 nautical miles northeast of Khasab. 186-26 remains the unused 1600 UTC 29 October CSO unknown-projectile Attack, Khasab footer. 420\/26 remains last night\u2019s dedicated RITI fire-and-anchor at 26-24.07N 056-24.72E. Five late-October products are five products. Do not make them one hull.<\/li>\n
  • Treat the missing geography and mothership-status lines as open watch lines.<\/strong> The public tape does not print a location footer, a lat\/long, a keep-clear, a mothership confirmation, a merchant approach, a crew line or a disruption. Keep Update 109 Gulf of Aden SUBSTANTIAL \/ Gulf of Oman MODERATE \/ Hormuz SEVERE and 016-26 visit-and-search in the master\u2019s pack. Report to UKMTO and keep MSCIO registration current. Watch a PDF revision that names a hull or prints a location; a NAVAREA that plots this fishing vessel; a flag or class note; a JMIC Update 110; or an official MSCIO alert \u2014 not a headline that Saturday night closed Wednesday\u2019s Aden file or completed a PAG disruption.<\/li>\n<\/ul>\n

    Regulas Shipping will keep lining Warning 190-26 against Wednesday night\u2019s dedicated Advisory 184-26 and against NAVAREA IX 416\/26\u2019s 3 November keep-clear so operators can treat Saturday night\u2019s tape as a numbered Suspicious Activity fishing-vessel boarding with a Pirate Action Group concern, not as a Hormuz Attack, a named Aden boarding, or a completed disruption.<\/p>\n","protected":false},"excerpt":{"rendered":"

    The United Kingdom Maritime Trade Operations centre published Warning 190-26 as a numbered PDF on its product board, filename 20261031-ukmto_warning_190.pdf. The face of the product is titled 190-26 \u2014 SUSPICIOUS ACTIVITY. The incident date is 30 October 2026. The incident time is 1419 UTC. The source line is Verified. UKMTO states that it has received […]<\/p>\n","protected":false},"author":1,"featured_media":1157,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[26,18,4],"tags":[],"class_list":["post-1159","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-highlights","category-maritime-industry","category-maritime-security"],"_links":{"self":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1159","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/comments?post=1159"}],"version-history":[{"count":1,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1159\/revisions"}],"predecessor-version":[{"id":1160,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/posts\/1159\/revisions\/1160"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media\/1157"}],"wp:attachment":[{"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/media?parent=1159"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/categories?post=1159"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/regulasshipping.com\/blog\/wp-json\/wp\/v2\/tags?post=1159"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}