Latest verified: 16 November 2026 · UKMTO source date; publication time unstated · JMIC ICOD 15 Nov, 17:00 SCT

Hourly source watch · 12-hour evidence reviewGet alertsUpdate policyMethodologySource desk

Maritime intelligence · history · policy

A regional view of Western Indian Ocean piracy.

Tracking piracy, armed robbery at sea and regional responses. With a current focus on Somalia and the Gulf of Aden, explore verified incidents, operating patterns, response mechanisms and lessons alongside a transparent risk outlook and operating-scenario explorer.

39landmark & current records indexed
9response mechanisms mapped
1→4source-verification hierarchy
Latest3 Nov · Indian Navy confirms all 20 AZINI crew rescued

Indian Ministry of Defence reporting identifies the Indian Navy response and says all 20 crew were safely rescued without casualties or injuries. MSCIO independently confirms liberation and closure; the earlier unnamed-source claim that 23 people were aboard remains unresolved.

Open sources

Current hostage picture

One held. Six released, recovered or liberated.

Indian Ministry of Defence reporting says all 20 AZINI crew were safely rescued without casualties or injuries during an Indian Navy operation completed on 2 November with Indian Air Force support; MSCIO independently confirms liberation and closure. An earlier Associated Press account citing an unnamed Puntland officer said 23 people were aboard, including two guards. No attributable Puntland release located resolves that conflict, so the Observatory does not infer the nationalities or status of any additional persons. ASANA remains the sole held merchant vessel and IMO's last published aggregate reports 22 seafarers captive aboard it; no combined total is inferred from the conflicting AZINI accounts. ATALANTA confirms HONOUR 25, SWARD, EUREKA and SIBU 1 closed. It reports SWARD safely arrived in Mombasa and says EUREKA's crew later flew from Mogadishu to their respective countries of origin; exact travel dates and individual welfare details are not published. An earlier observatory record attributed 87 captives to ATALANTA's 11 September release; the page retrieved on 2 October instead says more than 100. This historical discrepancy is unresolved, and the release predates the subsequent recoveries. IMO's 2 October release now supplies a revised current aggregate: 44 seafarers freed from HONOUR 25, SIBU 1/SEAMULL and EUREKA, with 22 remaining captive aboard ASANA. Pakistan's 1 October briefing confirms HONOUR 25's survivors safely transferred to Garowe for treatment. ATALANTA's new report gives two injured; Puntland Information Ministry reporting carried by Reuters and Pakistan's Foreign Office give four; ICC IMB's 15 October summary attributes five to Puntland authorities without identifying the fifth person or its underlying source. The complete injury total and casualty sequence remain unresolved. The final Pakistani crew reached Karachi on 7 October, and four Indonesian crew, including the master, arrived in Indonesia on 6 October. Other exact transfer times and individual medical findings remain unresolved.

01

Seized 29 Oct 2026

AZINI

Liberated / closed
20crew rescued
02

Seized 21 Apr 2026

HONOUR 25

Recovered
17crew at seizure
03

Seized 26 Apr 2026

SWARD

Released
15–17crew at seizure
04

Seized 02 May 2026

EUREKA

Released
12crew at seizure
05

Seized 17 Jul 2026

ASANA

Held
22crew at seizure
06

Seized 17 Aug 2026

LUTUF

Recovered
10crew at seizure
07

Seized 20 Aug 2026

SIBU 1

Recovered
20crew at seizure

Risk outlook & scenario explorer

Where should monitoring focus?

Explore incident patterns and declared operating assumptions alongside dated coastal-security, geopolitical, naval, cooperation and financing evidence. Useful for assessment preparation; predictive accuracy and safe-route selection are not established.

ASSESSMENT INPUTS · INITIALISING OPEN-DATA FEEDS
Predictive value has not been demonstrated.

In the 2023–26 prior-event diagnostic, the separate fixed score locates 5/17 events in its top zone versus 6/17 for the simple prior-frequency benchmark; top two: 8/17 versus 11/17. It does not outperform that benchmark in either comparison under the declared tie order. Inspect the diagnostics ↓

SCENARIO MODEL Incidents: verified layer Metocean: fallback AIS: declared baseline SAR: loadingMethod & limits ↓

Balances recent activity, exposed traffic, operating weather and plausible reach.

Selected satellite overlay has no available records. A footprint means imagery acquisition, not vessel detection; unmatched detections do not identify pirate craft. Check source availability below.

SCENARIO ZONESIndex 0–100 · not a probability
MIXED REACH SCENARIO ENVELOPEEAST AFRICAARABIAN PENINSULASOUTH ASIASOMALI BASINARABIAN SEAGULF OF ADENSOMALIA7901E. Gulf of Aden7402Puntland arc5903Eyl–Mogadishu5404W. Arabian Sea4505Southern basin
Guarded Moderate Elevated High Recent incident

Bands describe this configuration, not JMIC threat categories. The outlined zones depict the same declared radii used by route coverage. Dashed grey route portions lie outside them; their risk is unknown. Boundaries are analytical assumptions, not validated threat limits.

ASSESSMENT COVERAGE

Patterns, conditions and regional context

5/8 context reviews in date

The index combines incident recency and geography, traffic exposure, operating weather and action-group reach. Vessel speed, freeboard and protective measures affect the route scenario. The evidence below informs the wider assessment; qualitative factors have no invented numerical weights and are not counted twice.

Patterns and historical information

UKMTO 206-26 adds a suspicious tanker approach east of Socotra; its possible mothership remains unconfirmed, with no established piracy or link to Hobyo, so it is mapped but excluded from numerical piracy inputs. Alert 179/26 adds a fishing-vessel hijacking report near Hobyo, investigated as armed robbery. It is mapped at the exact latest-reported historical point but excluded from numerical inputs until the event date and attack location are established; vessel identity, crew welfare, current control and confirmed mothership use remain unknown. 39 curated records support incident review; 28 authority-linked piracy cases enter the scenario signal and prior-event ranking checks. Indian Ministry of Defence reporting says the Indian Navy, with Indian Air Force support, completed the AZINI operation on 2 November and safely rescued all 20 crew without casualties or injuries; MSCIO independently confirms liberation and closure. An earlier unnamed-source account said 23 people were aboard, so the manifest and any additional-person status remain unresolved. UKMTO 190 and MSCIO 161 remain one case: the UKMTO API marker stays visible at its historical 09°54′N, 53°03′E coordinate but excluded as a confirmed duplicate, while AZINI remains included as the dated incident at MSCIO Update 01's historical 09°47′N, 55°45′E position. Neither point is a current track. The outcome-only correction adds no incident and does not alter the prior-event ranking input. Potential mothership use was an operational warning, not confirmed subsequent use. Alert 160/26 and UKMTO record 184 remain excluded because no piracy attack is confirmed. The prior-frequency comparator is retained; no calibrated probability or predictive skill is claimed.

Index method and diagnostics

Dated monsoon assessment and weather inputs

JMIC's 25 October assessment records the southwest monsoon as withdrawn on 15 October and the inter-monsoon period as under way. It says farther-offshore skiff operations and possible use of dhows or hijacked fishing vessels as motherships are more feasible, while residual nearshore risk persists. This dated authority finding is not a forecast of present sea state and does not confirm an active mothership. Wind, waves, currents, visibility and daylight enter the index only with their feed labels. Missing weather remains an illustrative scenario.

JMIC seasonal assessment · 25 Oct 2026

2 context dimensions lack a verified current measure. Unknown does not mean no threat. Context review windows are conservative maintenance rules, not estimates of predictive accuracy.

Current incident pattern and vessel-protection warningReviewed evidence

Somali coast and basin · Gulf of Aden · Bab el-Mandeb · Indian Ocean Basin east of Socotra
Event: UKMTO 206-26: 16 Nov 2026 at 03:30 UTC. MSCIO 179/26 reported 13 Nov, exact event time unstated; earlier event dates/conflicts retained in the ledger.
Published: UKMTO public incident list dated 16 Nov; precise publication time unstated. API creation timestamp 04:25:24 UTC is not verified release time. evidenceThrough is date-only normalization. Earlier MSCIO/JMIC dates retained in the ledger.
Reviewed: 16 Nov, 14:13 UTC

UKMTO 206-26 reports a tanker approached by a possible mothership and skiff at 12°02′N 061°47′E, 430 NM east of Socotra; four armed persons and a ladder were sighted on the skiff. It remains Suspicious Activity, not confirmed piracy, and is excluded from numerical piracy inputs. No link to MSCIO 179/26 is established. The Hobyo fishing-vessel case remains under ATALANTA armed-robbery investigation with identity, crew welfare and outcome unknown. ASANA remains the sole verified held merchant vessel. AZINI remains liberated and closed; its crew-count and subsequent-custody questions, and possible IMB 057-26 overlap, remain unresolved.

Assessment implication: Apply UKMTO's caution and reporting warning for the reported offshore area; retain the separate MSCIO avoid-area warning near Hobyo. This extends the geographic watch to a new reported suspicious approach, not a verified PAG operating range or a calibrated escalation probability.

Unresolved: For UKMTO 206 the tanker identity, flag, crew total/welfare, craft identity, motive and subsequent outcome are unpublished. No boarding, firing, hijacking, confirmed mothership use, current position or connection to the Hobyo report is established. Older incident uncertainties remain unresolved; current naval coverage is unknown.

Reassess when: An MSCIO or ATALANTA update or correction; vessel or crew identification and welfare change; release, rescue, interception, transfer or prosecution; confirmed mothership use or follow-on attack; or a new warning or reclassification.

UKMTO Warning 206-26 · 16 Nov, publication time unstatedMSCIO Alert 179/26 · 13 Nov 2026, 14:34 displayed, timezone unstatedJMIC Update 114 · 15 Nov 2026, 13:00 UTC information cut-offMSCIO Alert 172/26 · 7 Nov 2026ICC IMB PRC · historical record 057-26, publication date unstatedUKMTO Overview No. 14 · 6 NovMSCIO–ATALANTA weekly report · 30 Oct–6 NovJMIC Update 110 · AZINI / UKMTO 190 linkage, 1 Nov 2026UKMTO Warning 190-26 · fishing-vessel boarding, 31 Oct 2026UKMTO official incident API · record 190MSCIO Alert 160/26 · armed-skiff approach, 30 Oct 2026MSCIO–ATALANTA weekly report · 23–30 Oct 2026MSCIO Alert 161/26 · AZINI hijacking, liberation and closure, 30 Oct–2 Nov 2026Indian Ministry of Defence via DD India · AZINI rescue, 3 Nov 2026Associated Press · earlier unnamed Puntland-source AZINI account, 1 Nov 2026JMIC Update 109 · 29 Oct 2026MSCIO Alert 156/26 · suspected PAG, 28 Oct 2026NAVAREA IX warning 416/26 · 28 Oct 2026UKMTO Advisory 184-26 · Gulf of Aden suspicious activity, 28 Oct 2026UKMTO official post · Advisory 184-26, 28 Oct 2026UKMTO official incident API · record 184Anadolu · UKMTO warning corroboration, 28 Oct 2026JMIC Update 108 · 25 Oct 2026UKMTO Weekly Overview No. 12 · 23 Oct 2026JMIC Update 106 · 18 Oct 2026MSCIO Alert 149/26 · Suspicious Activity, 17 Oct 2026NAVAREA IX warning 383/26 · attempted piracy, 17 Oct 2026UKMTO incident 176 · Attack, 17 Oct 2026UKMTO official incident API · incident 176 fieldsAnadolu · UKMTO incident 176 corroboration, 17 Oct 2026ICC International Maritime Bureau · January–September 2026 report, 15 OctICC IMB live piracy map · incident 053-26JMIC Update 104 · 11 Oct 2026MSCIO–ATALANTA · 2–9 Oct 2026NAVAREA IX warning 363/26 · 7 Oct 2026HYDROPAC warning 2914/26 · 7 Oct 2026NGA navigational warningsNAVAREA IX warning 361/26 · 7 Oct 2026NAVAREA IX active-warning list · 7 Oct 2026
Somali governance and coastal enforcementReview due

Somali coast · federal maritime-security authority · Puntland
Event: Federal Somali Navy and Coast Guard command handover in Mogadishu · 1 Nov 2026; IMO port-security coordination workshop in Bosaso · 14–17 Sep 2026; 25 and 29 Sep 2026 recoveries; SWARD release 11 Sep and later safe Mombasa arrival, date unstated; EUREKA crew return to countries of origin after 29 Sep recovery, dates incompletely stated; HONOUR 25 disembarkations 30 Sep and 4 Oct; ASANA still under pirate control as reported 16 Oct; EUCAP Somalia, ATALANTA and Puntland State Police cooperation meeting in Bossaso · 20 Oct
Published: Somali Ministry of Defence and Somali National News Agency posts dated 1 Nov 2026 by indexed source records, exact publication times unverified; Shabelle report dated 1 Nov 2026, exact publication time unstated; IMO Bosaso workshop release dated 17 Sep 2026, exact publication time unstated; EEAS / EUCAP Somalia release dated 27 Oct 2026, exact publication time unstated; ATALANTA release dated 16 Oct 2026 at 14:15, timezone unstated; JMIC dated 1 Oct; MSCIO reports ending 2 and 9 Oct; IMO welfare release dated 2 Oct; consular welfare reports dated 3–8 Oct
Reviewed: 05 Nov, 13:56 UTC

The Somali Ministry of Defence reports that Colonel Mohamed Abdiqadir ‘Sharif’ formally took over as Commander of the Navy and Coast Guard from Brigadier General Abdiwahab Abdullahi Omar on 1 November. The Somali National News Agency and Shabelle Media Network corroborate the handover; Shabelle places the ceremony in Mogadishu. The reviewed releases announce a leadership transition, not a new patrol, asset, funding decision or operational plan. EUNAVFOR ATALANTA confirms HONOUR 25, SWARD, EUREKA and SIBU 1 closed and ASANA still open. It reports SWARD safely arrived in Mombasa; EUREKA's crew later flew from Mogadishu to their countries of origin; and ASANA remains under pirate-action-group control inside Somali territorial waters. It confirms the three Puntland recoveries but reports two HONOUR 25 crew injured. Puntland Information Ministry reporting carried by Reuters and Pakistan's Foreign Office report four injured; ICC IMB's 15 October summary attributes five injuries to Puntland authorities without identifying the fifth person or its underlying Puntland source. The complete injury count remains unresolved. ATALANTA gives up to 21 SIBU 1 arrests without resolving conflicting custody counts or the later reported escape. The IMO aggregate remains 44 freed from HONOUR 25, SIBU 1 and EUREKA and 22 captive aboard ASANA. IMO records that a 14–17 September Bosaso workshop brought together twenty representatives of Puntland port, government, customs and security bodies to strengthen ISPS Code implementation, risk-based planning, information-sharing, incident reporting and coordinated response. Participants developed draft terms of reference and an indicative roadmap for a proposed multi-agency Port Security Advisory Committee. An EEAS / EUCAP Somalia release separately records a 20 October Bossaso meeting between EUCAP Somalia's Puntland field office, ATALANTA's liaison officer in Somalia and senior Puntland State Police officials focused on enhanced piracy liaison and operational cooperation.

Assessment implication: The federal command handover changes the named leadership of Somalia's Navy and Coast Guard but does not by itself demonstrate changed patrol coverage, readiness or anti-piracy effect. Completed recoveries demonstrate coastal intervention capacity. The IMO workshop documents concrete inter-agency port-security planning, while the later Bossaso meeting records an active EU–Puntland liaison pathway for piracy cooperation. The proposed committee remains a draft institutional arrangement; none of these records establishes that a coastal area is clear, that all suspects are in custody, that a new patrol or response asset has been delivered, or that recurrence is prevented.

Unresolved: The command-handover releases publish no operational priorities, workplan, budget, asset allocation, patrol boundaries, coverage measure, response-time commitment or readiness effect; current federal and regional policing coverage therefore remains unknown. IMO does not confirm that the proposed Port Security Advisory Committee, draft terms of reference or indicative roadmap have been formally adopted, funded or implemented, and publishes no readiness metric or measured security effect. The 27 October EUCAP release gives no agreed workplan, funding, assets, patrol boundaries, coverage measure, response-time commitment, follow-up delivery or measured operational effect. ATALANTA confirms group-level EUREKA repatriation but does not give travel dates, flight details or individual medical findings. Exact SWARD Mombasa-arrival time, HONOUR 25 casualty chronology and complete injury count, SIBU 1 custody outcome, current ASANA coordinate and pirate-network reconstitution remain unresolved. The published HONOUR 25 injury totals are two (ATALANTA), four (Puntland Information Ministry/Reuters and Pakistan's Foreign Office) and five (ICC IMB attributing Puntland authorities); no reviewed source reconciles them or identifies a fifth injured person. Four injured Pakistani crew and three Pakistani remains reached Karachi on 4 October; the other three surviving Pakistani crew completed their return on 7 October. Four Indonesian crew reached Indonesia on 6 October, but diagnosis and present condition for the crew member reported hospitalised remain unpublished. These welfare developments do not alter the operating-risk scores.

Reassess when: Verified changes in coastal policing, security authority, arrests, escapees, prosecutions, pirate operating bases, formal adoption or implementation of the proposed Bosaso Port Security Advisory Committee, or implementation of the announced EU–Puntland cooperation.

Somali Ministry of Defence · Navy and Coast Guard command handover, 1 Nov 2026Somali National News Agency · Navy and Coast Guard command handover, 1 Nov 2026Shabelle Media Network · Navy and Coast Guard command handover, 1 Nov 2026IMO · Bosaso port-security coordination workshop, 17 Sep 2026EEAS / EUCAP Somalia · ATALANTA–Puntland cooperation, 27 Oct 2026EUNAVFOR ATALANTA · northern Somalia piracy-case update, 16 Oct 2026ICC International Maritime Bureau · January–September 2026 report, 15 OctIMO welfare aggregate · 2 Oct 2026JMIC Update 101 · 1 Oct 2026MSCIO–ATALANTA · 2–9 Oct 2026MSCIO–ATALANTA · 25 Sep–2 OctMSCIO Alert 41/26 · EUREKA closed, 6 Oct 2026Ahram Online · EUREKA Egyptian crew return, 5 Oct 2026KP2MI · HONOUR 25 onward return and welfare, 8 Oct 2026Indonesian Foreign Ministry · HONOUR 25 crew return, 7 Oct 2026ANTARA · HONOUR 25 Indonesian crew return, 6 Oct 2026Geo News · HONOUR 25 final Pakistani crew arrival, 7 Oct 2026ARY News · HONOUR 25 Karachi arrival corroboration, 7 Oct 2026Dawn · HONOUR 25 Karachi arrival detail, 7 Oct 2026Pakistan DPM/FM · HONOUR 25 onward repatriation, 7 Oct 2026Associated Press of Pakistan · HONOUR 25 onward repatriation, 7 Oct 2026Pakistan DPM/FM · HONOUR 25 crew transfer, 5 Oct 2026Egyptian MFA · 3 Oct welfareRadio Pakistan · 3 Oct repatriationRadio Pakistan · 4 Oct departureAaj English TV · 4 Oct arrivalHUM News English · 4 Oct arrival
Regional geopolitics and route disruptionCurrent measure unknown

Somali coast and basin · Gulf of Aden · Indian Ocean Basin east of Socotra
Event: UKMTO suspicious approach 430 NM east of Socotra · 16 Nov at 03:30 UTC; JMIC outlook snapshot 15 Nov at 13:00 UTC; southwest monsoon subsided 15 Oct
Published: UKMTO public record dated 16 Nov, exact publication time unstated; date-only evidenceThrough normalization. JMIC Update 114 dated 15 Nov, ICOD 13:00 UTC, not publication time.
Reviewed: 16 Nov, 14:13 UTC

The new UKMTO suspicious approach east of Socotra is geographically relevant to JMIC's earlier qualified offshore-PAG outlook, but does not confirm piracy, a PAG position or a link to the Hobyo seizure. A possible mothership remains possible, not identified or verified. JMIC's 15 November substantial Gulf of Aden and moderate Somali coast/basin ratings are unchanged; they are not extrapolated as a new rating for this offshore point. The southwest monsoon was assessed as subsided on 15 October. The 12 November numerical weather outlook is expired; no live sea-state value or new numerical weight is inferred.

Assessment implication: Retain offshore caution and regional reporting awareness without expanding a confirmed pirate operating range from one suspicious encounter. Qualitative context does not alter numerical piracy inputs or establish a conflict-to-piracy causal link.

Unresolved: Current local sea state, present patrol coverage, PAG positions and a quantitative conflict-to-piracy relationship remain unknown. The short weather outlook expires with its stated horizon; it must not be treated as continuing measurements. Competing coastal-control claims are not settled attribution or an implemented piracy-response capability.

Reassess when: A replacement sea-state or operational outlook, confirmed coastal-control change with a documented shipping/piracy pathway, deployment change, warning or incident-status revision.

Operational communications integrityReviewed evidence

Gulf of Aden · Yemen approaches · regional WIO operator guidance
Event: HOCC communications and transit-service claims assessed by JMIC at 12 Nov 2026, 13:00 UTC; individual contact dates unstated; separate false-authority emails reported before 22 Oct
Published: JMIC Update 113 dated 12 Nov 2026, exact publication time unstated; earlier MSCIO Advisory 10-2026 dated 22 Oct
Reviewed: 13 Nov, 14:03 UTC

JMIC reports an advertised voluntary HOCC transit-request service but says merchant use is independently unconfirmed. It warns that disclosing voyage information in response to those communications may increase targeting risk, and cites MARAD 2026-013 guidance for U.S.-flagged commercial vessels to disregard Houthi instructions to activate AIS or submit voyage information and report contacts. This is separate from MSCIO's 22 October warning against false Yemeni Coast Guard information-request emails; the two sources do not establish a common sender or piracy connection.

Assessment implication: Verify operational communications through established official channels and follow applicable flag-state guidance. An advertised transit service is not independently verified safe passage. No new coastal-state reporting obligation, guaranteed protection or piracy attribution is inferred.

Unresolved: No verified service-use count, targeting consequence, sender linkage or related piracy case is established. U.S.-flag guidance is not automatically a requirement for all flags. Current naval coverage remains unknown.

Reassess when: An MSCIO correction or closure; a competent authority identifying additional addresses, confirmed compromise, operational consequence or related incident; or replacement reporting guidance.

Flag-state vessel-protection requirementsReview due

Norwegian vessels · Red Sea · Bab el-Mandeb · Gulf of Aden · western Arabian Sea · Somali waters · western Indian Ocean
Event: Security levels effective from 26 Oct 2026 until further notice, explicitly stated on both pages; guidance published 29 and 30 Oct; exact effective hour unstated
Published: Norwegian Maritime Authority pages published 29 and 30 Oct 2026; exact publication times unstated
Reviewed: 05 Nov, 13:56 UTC

The Norwegian Maritime Authority extends ISPS Security Level 2 to the entire Gulf of Aden for Norwegian vessels and retains Level 2 in the western Arabian Sea, Somali waters and the western Indian Ocean out to 600 nautical miles from the Somali coast. Its 30 October guidance keeps Level 3 in force in the Bab el-Mandeb Strait, sets Level 2 for the southern Red Sea and northern Gulf of Aden, and extends the northern Red Sea Level 2 area to waters north of Yanbu. The authority cites continued exposure in Bab el-Mandeb to missile, drone and small-boat attacks and requires vessel-specific Ship Security Assessments and Ship Security Plans, with BMP Maritime Security, voyage and port-call risk assessment, training and drills, review of UKMTO/EUNAVFOR information and reporting to UKMTO and MSCIO.

Assessment implication: The 30 October page materially extends the Norwegian Level 2 area northward to waters north of Yanbu while retaining, rather than newly imposing, Level 3 in Bab el-Mandeb. Read with the 29 October page, it supports heightened preparedness for Norwegian vessels throughout the stated corridor. This is flag-administration guidance, not a new JMIC regional threat rating, a requirement for other flags, an incident report, a patrol deployment or evidence of present naval coverage. It changes qualitative vessel-protection context only; the incident ledger, ASANA status, map positions and numerical diagnostics remain unchanged.

Unresolved: The authority gives no exact publication times, separate effective hours, review dates or geographic boundary coordinates. Its 29 October statement that a number of vessels are held does not enumerate vessels or distinguish merchant from other craft and therefore does not supersede JMIC and ATALANTA reporting that ASANA is the sole verified held merchant vessel. Current naval coverage remains unknown.

Reassess when: A Norwegian Maritime Authority revision or withdrawal; another flag administration changing requirements; or competent operational guidance that changes the applicable area or protective measures.

Public counter-piracy posture and responsesReviewed evidence

Gulf of Aden · ATALANTA, CTF 151 and independent deployers
Event: Fishing-vessel seizure reported to MSCIO 13 Nov 2026; ATALANTA investigation ongoing as reported by JMIC at 15 Nov information cut-off; exact incident time unstated. Earlier completed responses and exercises retain their dates.
Published: MSCIO 179/26 displays 13 Nov at 14:34, timezone unstated; JMIC Update 114 dated 15 Nov with 13:00 UTC information cut-off, exact publication time unstated. Earlier source publication dates retained.
Reviewed: 16 Nov, 02:10 UTC

MSCIO and JMIC report that ATALANTA is investigating the fishing-vessel hijacking report near Hobyo as armed robbery. No interception, rescue, arrest, transfer, prosecution or release is announced in these reports. Earlier AZINI rescue and detention, ATALANTA coordination, CTF 151 Operation Tidal Wave and the completed 5 November Seychelles–Russia boarding exercise remain separate dated responses or exercises.

Assessment implication: The investigation is a verified public response-status update, not confirmation of present assets, readiness, patrol coverage or response availability. No additional Seychelles participation or current naval position is established; numerical diagnostics are unchanged.

Unresolved: Alert 179/26 vessel and crew identity, welfare, current control, investigative findings, response outcome and legal custody remain unknown. Current naval coverage is unknown. The earlier AZINI crew-count conflict and subsequent custody/legal outcome remain unresolved.

Reassess when: A cleared official deployment, withdrawal, patrol-coverage change, completed response or public readiness update.

MSCIO Alert 179/26 · 13 Nov 2026, 14:34 displayed, timezone unstatedJMIC Update 114 · 15 Nov 2026, 13:00 UTC information cut-offRussian Defence Ministry · completed Seychelles anti-piracy exerciseSDF spokesperson via Seychelles News Agency · exercise completed 5 Nov, published 7 NovTürkiye Ministry of National Defence · Somalia rotation, 5 NovUKMTO Overview No. 14 · 6 NovTürkiye Grand National Assembly · Somalia mandate extension, 21 JulEUNAVFOR ATALANTA · statistics updated 5 Nov 2026EUNAVFOR ATALANTA · PSC flagship visit and counter-piracy exercise, 4 Nov 2026MSCIO Alert 160/26 · armed-skiff approach, 30 Oct 2026MSCIO–ATALANTA weekly report · 23–30 Oct 2026MSCIO Alert 161/26 · AZINI hijacking, liberation and closure, 30 Oct–2 Nov 2026Indian Ministry of Defence via DD India · AZINI rescue, 3 Nov 2026Associated Press · earlier unnamed Puntland-source AZINI account, 1 Nov 2026EEAS / EUCAP Somalia · ATALANTA–Puntland cooperation, 27 Oct 2026CMF / CTF 151 · Operation Tidal Wave concluded, published 20 Oct 2026CMF / CTF 151 · Djibouti partnership visit, published 19 Oct 2026EUNAVFOR ATALANTA · northern Somalia piracy-case update, 16 Oct 2026Pakistan DPM/FM · HONOUR 25 crew transfer, 5 Oct 2026EUNAVFOR ATALANTA · 54th Force Headquarters rotation, 11 Oct 2026EUNAVFOR ATALANTA · September 2026 newsletterMSCIO–ATALANTA · 2–9 Oct 2026MSCIO–ATALANTA · 25 Sep–2 OctATALANTA · 11 Sep 2026CMF · 11 Sep 2026
Diplomacy, cooperation and legal capacityDated context

Regional and multinational maritime enforcement
Event: DCoC/JA lexicon workshop in Addis Ababa · 27–30 Oct 2026; regional strategy workshop in Mombasa · 2–6 Nov 2026; IMO Council · 2–6 Nov; earlier cooperation and legal events retained in the operational feed
Published: IMO lexicon release dated 9 Nov 2026; IMO Council release dated 6 Nov; CMF published 12 Nov, article dateline 10 Nov. Exact release times unstated. evidenceThrough retains the latest dated source, not this review time.
Reviewed: 14 Nov, 14:07 UTC

CMF confirms CTF 154 joined experts from 13 countries at the 2–6 November Mombasa workshop. Participants produced a regional risk register and proposals for a shared vessel registry to support detection of piracy and smuggling. Kenya's fleet commander is slated to take CTF 154 command in January 2027; this is prospective, not a completed handover. The DCoC Secretariat corroborates the workshop dates. No verified 11–13 November High-Level Meeting adoption outcome was located; the earlier information-sharing framework remains a draft in this record.

Assessment implication: Completed strategy work and documented outputs strengthen the regional cooperation record. IMO separately confirms that Seychelles, Somalia, RCOC and RMIFC participated in finalising an expanded draft Common Maritime Security Lexicon at the 27–30 October Addis Ababa workshop. A shared vocabulary supports consistent incident reporting and legal-authority interpretation, but the 9 November release only proposes High-Level Meeting consideration, not adoption. This is distinct from the Mombasa workshop, whose Seychelles participation is not established. A registry proposal is not an operational registry. Neither workshop establishes new patrols, feed authorisation or a measured piracy effect; CTF 151 remains the counter-piracy task force.

Unresolved: The full risk register, registry adoption, implementation timetable, resources, Mombasa participating-country list and Seychelles participation there are unpublished. Lexicon adoption, implementation and assessed operational effect remain unverified. The High-Level Meeting's scheduled end date does not establish its decisions. Current patrol coverage remains unknown.

Reassess when: Verified High-Level Meeting outcomes; risk-register publication; registry adoption or implementation; completed CTF 154 handover; funded capacity or prosecution outcomes.

Piracy financing and reinvestmentReview due

Somalia · Horn of Africa financial networks
Event: Historical evidence · Apr 2005–Dec 2012; UN Monitoring Team reporting period · 23 Jun–15 Dec 2025
Published: 2013 study; UN S/2026/44 published 4 Feb 2026
Reviewed: 05 Nov, 13:56 UTC

The World Bank, UNODC and INTERPOL Pirate Trails study documents historical recycling of ransom proceeds into further piracy and other crime. In paragraph 108 of S/2026/44, the UN Analytical Support and Sanctions Monitoring Team records Member State reporting that AQAP received a share of revenue from payments made by vessels for safe passage through high-risk waters linked to Al-Shabaab piracy.

Assessment implication: The UN report documents a piracy-related extremist-financing pathway that merits monitoring. It does not establish a current ransom payment, quantify pirate resources or connect the reported revenue to any 2026 Observatory incident, so no numerical uplift is added.

Unresolved: The UN report identifies no vessels, payment amounts, transaction dates, intermediaries or 2026 operational link. No current verified ransom amount or reinvestment dataset is available to this model. Financing remains unknown, not zero.

Reassess when: Responsibly publishable authority-confirmed payments, financial seizures, sanctions or demonstrated changes in pirate financing capacity.

Verified evidence revisions are published through the observatory's ongoing watch. Open feeds refresh separately; a feed refresh does not verify political, diplomatic or financing claims. More inputs improve coverage only when reliable, relevant and validated; they do not by themselves establish forecasting skill.

DATA PROVENANCE

Freshness, latency and coverage

Open feeds are checked every 15 minutes while this page is visible and when you return. Shared snapshots last up to 15 minutes, or two minutes during a weather outage. Retrieval time is not the provider’s model issue time.

Verified source layer16 Nov 2026 · UKMTO source date; publication time unstated · JMIC ICOD 15 Nov, 13:00 UTC

Evidence cutoff for the official and reconciled source layer. Incident inputs retain their own event and publication dates; approximate positions remain explicitly labelled.

Metocean retrieved atLoading

Requesting seven-day marine and atmospheric fields.

Traffic presenceDeclared baseline

Declared corridor exposure is active while the source status loads.

Sentinel-1 coverageLoading

0 recent theatre footprints in the public catalogue.

Unmatched SAR contextLoading

Awaiting source status.

SCENARIO LAB

Change the operating assumptions

Active layers use these assumptions
Traffic diverted awayBaselineTraffic concentrated
Recent incident pulseResidual temporal weight

The model weights mothership-labelled cases more strongly. Incident signals decay with age and exclude events older than two years.

ROUTE COVERAGE + TRANSIT SCENARIO

Inspect coverage and vessel assumptions

Scenario only · UTC

Waypoints are analytical corridor approximations, not navigational routes. Departure changes weather valid times only; today's incident and context scenario is reused, not reconstructed for past dates or predicted for future ones. No named vessel or live position is retained. Official reporting and voyage-assessment resources ↓

MODEL DIAGNOSTICS

Historical ranking tests and spatial drift

Rolling time splits17each event tested only on prior incidents
Top-two hit rate8/1747% broad-zone ranking
Top-zone miss rate71%top zone misses event zone
Top-zone hits5/17curated location checks
Baseline difference-6 ppversus fixed-order prior frequency
Spatial sample difference169 older / 17 modern locations; descriptive
Prior-frequency baselinesame earlier-event splits
Benchmark sensitivity · retrospective hit rates
Frequency benchmarkTop zoneTop two
All prior · fixed tie order35%65%
All prior · tie-neutral32%62%
Prior 730 days · tie-neutral24%45%

The original all-history benchmark remains above. Equal counts use Gulf of Aden, Puntland, Eyl–Mogadishu, Arabian Sea, then southern basin order; 5/17 folds tie for first. Tie-neutral rates give fractional expected credit across equally ranked zones; they are not attack probabilities.

The incident kernel uses only the previous 730 days; 1/17 folds have no cases in that window. Benchmark choice and tie handling affect the comparison.

7/17 targets lie outside every assessment circle. Diagnostics assign all locations to their nearest centre; this does not demonstrate route coverage.

39 curated records · 28 included in the piracy-pattern model · 15 reported coordinates · remaining positions approximate. Changing declared assumptions tests robustness, not statistical confidence.

Prior-event spatial ranking checks, not predictive validation.

This separate diagnostic uses fixed 44/24/13/19% incident/traffic/weather/reach weights, unlike the current horizon model. Tests require four earlier-day cases, exclude the target day and give earlier incidents unit weight, avoiding today’s release or casualty labels. Both model and comparator use today’s geography, including approximate holding/recovery references; first-publication timestamps and original location versions are unavailable. Spatial sample difference is total-variation distance between curated period proportions, not a statistical significance test. The sample is not a complete event census. These checks do not estimate attack probabilities or false-alert rates, and do not validate the live model. This retrospective comparison cannot establish predictive skill.

Assessment method

Evidence, assumptions and the limits of inference.

01

Incident signal

Current status, vessel-type labels, event age and recorded location form a decaying signal. Event classifications are retained in the ledger but are not independently weighted predictors. Mothership labels do not establish present intent.

02

Exposure

Aggregated AIS vessel-hours or a declared corridor baseline estimate opportunity. Individual tracks and vulnerable vessels are excluded.

03

Operating access

Wave height, current, wind, visibility and daylight feed an assumed small-craft access function. This relationship has not been fitted to piracy outcomes.

04

Reach + vulnerability

Coastal, mixed-reach and mothership assumptions are separated. Selecting one confirms no current action group. Vessel inputs affect only the route scenario; numerical protection effects are unvalidated.

05

Satellite context

A limited selection of Sentinel-1 footprints shows dated acquisitions, not exhaustive surveillance. Unmatched detections are contextual indicators; they neither identify pirate craft nor change the index.

06

Historical diagnostics

A prior-event spatial ranking check reports hits, misses, a prior-frequency benchmark and spatial drift. It cannot validate attack occurrence, non-event periods or the live scenario model.

07

Regional context

Coastal governance, geopolitics, public counter-piracy posture, diplomacy and financing are reviewed with dated evidence, uncertainty and revision triggers. Their numerical effects are unestimated; they inform judgement alongside the index.

Inspect the numerical assumptions

All weights, boundaries and thresholds below are declared modelling choices, not fitted coefficients. Enabled components are renormalised to sum to one; scores from different layer configurations or horizons are not directly comparable.

Component weights before renormalisation
HorizonIncidentsTrafficWeather accessReach
24h42%22%20%16%
72h34%27%17%22%
7d25%31%16%28%
Declared zone constants · inputs scaled 0–1, radius in NM
ZoneRadiusTraffic baselineWeather substituteOpportunity priorCoastal reachMothership reach
E. Gulf of Aden1250.940.640.820.820.95
Puntland arc1050.690.760.880.990.91
Eyl–Mogadishu1500.790.570.760.690.92
W. Arabian Sea2050.860.430.710.240.83
Southern basin1850.730.510.680.310.72

Traffic and reach: authorised AIS sums 21-day vessel-hours within 260 NM of each point, then scales each sum relative to the largest zone sum as 0.42 + 0.56 × relative hours. This imposed floor and normalisation do not estimate attack rates. The exposure slider multiplies traffic by 1 ± up to 30%, bounded 0–1. Mixed reach is 52% coastal + 48% mothership; it confirms no present action group.

Incident term: 80% decaying case signal + 20% fixed opportunity prior. Standard half-lives are 38/62/92 days and distance scales 250/330/430 NM. Fast decay multiplies half-life by 0.65; persistent by 1.45. Status weights held/monitoring/released/disrupted/attempted are 1/0.72/0.64/0.82/0.7; mothership-labelled cases multiply by 1.12 and dhow/fishing labels by 0.86. The summed case kernel is divided by 2.25 and capped at one. None of these weights establishes recurrence or current capability.

Scenario bands and sensitivity: boundaries are 40, 56 and 72 out of 100, with no probability or authority-category meaning. The nine-setting range varies decay and reach only; fixed priors, caps and omitted input uncertainty can conceal instability. Low indices and uncovered areas do not establish safety.

Weather access: wave/wind/current/visibility/daylight weights are 42/27/13/7/11%. Assumed wave, wind and current terms decline to zero at 3.6 m, 30 kn and 4.8 km/h; visibility scales from 1.5 to 13.5 km. Day/night terms are 1/0.72. These are not operational safety limits. Missing weather uses fixed zone assumptions.

Vessel scenario: type factors tanker/bulk/cargo/container/ro-ro are 1.11/1.06/1/0.88/0.96; freeboard low/medium/high 1.16/1/0.87; posture limited/standard/enhanced 1.12/1/0.82. The speed term is 1.2 − (knots − 8) × 0.035, bounded 0.7–1.25. Their product is bounded 0.62–1.42 and the final index 0–100. Caps can hide differences; none of these values measures a vessel's actual attack probability or the efficacy of its protection.

What would establish more value: a complete incident and non-event record, exposure denominators, archived information as it was available before each event, route-local weather and prospective comparisons against simple benchmarks. Test missed events, false alerts and uncertainty before claiming predictive skill.

Research decision-support only.

This transparent scenario tool uses open metocean forecasts and Sentinel-1 acquisition metadata when available. Global Fishing Watch AIS presence is normally available to roughly 96 hours ago and SAR detections to roughly five days ago; both require provider authorisation. Missing fields use declared illustrative assumptions or corridor exposure baselines. Input coverage reports availability, not calibrated confidence. The model excludes confidential UKMTO vessel reports, individual vulnerability targeting and live naval positions. Use UKMTO, MSCIO, flag-State and company guidance for operational decisions.

AIS/SAR availability requires provider authorisation and completed report retrieval. Slow or rate-limited requests can leave inputs unavailable; the baseline remains explicit. Satellite plots contain at most six recent acquisition footprints and 24 aggregate unmatched cells, not complete spatial or temporal coverage.

Verified incident picture

One theatre. Multiple operating geometries.

Explore a curated verification layer of landmark and current events. Positions marked ‘approximate’ are derived from official distance or coastal-location descriptions—not represented as exact coordinates.

Event locations only; current vessel positions are unknown. Pins refer to seizure, holding or recovery areas as described in each record; they do not track released vessels. Response areas describe institutional scope, not current patrol coverage.

Pins may overlap where reported areas coincide. This selector opens every record without displacing its coordinates.

VERIFIED INCIDENT LAYER
MSCIO published IRTC lane boundaryMSCIO published IRTC lane boundaryATALANTA · SCHEMATIC FOCUSCTF 151 · SCHEMATIC FOCUSIRTCEAST AFRICAARABIAN PENINSULASOUTH ASIASOMALI BASINARABIAN SEAGULF OF ADENSOMALIABosasoHobyoMogadishuMombasa
HeldUnder investigationReleased / recoveredAttack disruptedApproach / boarding

Map scope: selected verified incidents that explain the evolution of the Somali theatre. Uniformly fitted Mercator projection; IRTC lanes follow MSCIO's published coordinates. Response areas and hotspot halos are schematic, not exact boundaries or guarantees of patrol coverage. It is not a navigation chart and does not replace operational reporting services.

Open IMB global live map IRTC geometry source

Incident index

Vessels, people and outcomes—not just dots.

Search the observatory's verified case layer by vessel, flag, location, date, outcome or response. Each record preserves the status of the crew and the response that followed.

39 records
Date / vesselType & flagLocationCrewOutcomeSource
16 Nov 2026Incident 16 Nov 2026 at 03:30 UTC in UKMTO Warning 206-26 and its official API. Public incident list dated 16 Nov; exact publication time unstated. API creation 04:25:24 UTC is not treated as verified publication time.Unnamed tanker · UKMTO 206-26Suspicious Activity — possible mothership and armed-skiff approachTankerUnknown
430 NM east of Socotra, Yemen · Indian Ocean Basin · 12°02′N 061°47′E
—not confirmed Under investigation
13 Nov 2026MSCIO report date, not a verified event clock. Page displays 13 Nov 2026 at 14:34, timezone unstated; JMIC Update 114 dated 15 Nov has a 13:00 UTC information cut-off, not a publication time. Incident date/time and position-fix time are not independently stated.Unidentified fishing vessel · MSCIO 179/26Armed robbery — reported fishing-vessel hijacking under ATALANTA investigationFishing vesselUnknown
Somali territorial waters · approx. 67 NM northeast of Hobyo · 06°19′N 049°13′E
—not confirmed Under investigation
29 Oct 2026IMB gives 03:30 UTC; source publication date/time unstated; observed in the public map during the 14 November reviewUnnamed fishing vessel · IMB 057-26Hijacked — IMB report; possible overlap with another recorded case unresolvedFishing vesselUnknown
Around 37 NM SE of Xaafun, Somalia · 09°51.54′N 051°30.73′E
—not confirmed Released / recovered
06 Nov 2026Approximately 22:45 UTC; MSCIO publication displays 7 November 2026 at 19:47, timezone unstatedUnidentified radar target · merchant observer unnamedSuspicious Activity — unidentified target and explosion; piracy link not establishedTarget unidentified; observing vessel described only as a merchant vesselUnknown
Bab el-Mandeb Strait · 12°46.4′N 043°18.0′E
—not confirmed Under investigation
30 Oct 2026Warning 190-26 states 14:19 UTC on 30 October; the official API instead states 18:48 UTC on 31 October — conflict unresolvedAZINI · confirmed duplicate UKMTO recordHijack — confirmed duplicate of MSCIO Alert 161/26's AZINI case; event clocks unresolvedLarge fishing vessel; official API separately labels the record ‘Dhow’Iran · UKMTO Overview No. 14
09°54′N, 53°03′E · UKMTO API record 190
—not confirmed Confirmed duplicate of AZINI hijack
30 Oct 2026MSCIO Alert 160/26 reports the approach at approximately 02:25 UTC on 30 OctoberMerchant vessel not identifiedSuspicious activity — armed-skiff approach; no shots or boarding attempt reportedNot publishedNot published
11°57.4′N, 45°04.5′E · Gulf of Aden
—not confirmed Approach aborted; vessel continued
29 Oct 2026Hijacking reported at approximately 09:00 UTC on 29 October; initial last-reported position timestamped 04:00 UTC on 30 October. The MSCIO–ATALANTA weekly report dates the issue of AZINI Update 01 to 2 November, while the alert page displays 31 October at 09:24, timezone unstated. Neither source timestamps the position fix.AZINIPiracy — hijacking; vessel liberated and incident closedFishing vesselIran
09°47′N, 55°45′E · latest reported AZINI position
20 rescuedaffected Released / recovered
28 Oct 2026Advisory PDF states 10:30 UTC; official API utcDateOfIncident field states 12:02 UTC — conflict unresolved. MSCIO does not state the observation time.Merchant vessels not identifiedAdvisory — suspicious activity potentially indicative of pirate-action-group activity; no attack confirmedNot publishedNot published
12°42′N, 47°35′E · Gulf of AdenApprox. position
—not confirmed Under investigation
17 Oct 2026JMIC Update 106 explicitly links the warning to UKMTO incident 176 at 10:30 UTC; warning issued at 17:00 UTCName withheldAttempt of piracy reported — NAVAREA IX warning 383/26LNG tankerBahamas
12°54′N, 47°55′E · Gulf of Aden north of Somalia
—not confirmed Confirmed duplicate; vessel continued safely

Observatory analysis · 3 November 2026

The resurgence is real. It is not yet the 2011 model.

Indian Ministry of Defence reporting says the Indian Navy, with Indian Air Force support, completed the AZINI response on 2 November and safely rescued all 20 crew without casualties or injuries; MSCIO independently confirms liberation and closure. An earlier unnamed-source account said 23 people were aboard, so the manifest and any additional-person status remain unresolved. UKMTO 190 remains visible at its historical API coordinate as a confirmed duplicate and excluded from numerical pattern calculations; AZINI remains included as the dated incident, so this outcome-only correction does not alter the prior-event ranking input. Historical positions are not a live track. Alert 160/26 remains a separate armed-skiff approach with no shots or boarding attempt. No calibrated probability, predictive skill or present naval coverage is claimed.

01

Net assessment

Persistent capability; uncertain operating opportunity

Repeated hijackings are consistent with retained coastal access and hostage-taking capability. This is an inference from documented cases; it does not establish current network size, available craft or the identity of organisers. Regional conflict and competing maritime tasks may affect response capacity, but a piracy-specific effect and current naval coverage are not measured.

Assessment basisMixed evidenceDocumented cases; causal effects unmeasured

Operating range

Documented coastal and offshore settings

Documented cases
ALWASEEMI · 2026
400 NM east of Mogadishu
SAVINA CAYLYN · 2011
About 800 NM east of Somalia · historical

Current status: MSCIO Update 02 says ATALANTA confirms AZINI was liberated and closes the incident. Its historical positions remain evidence of the case's documented reach, not a current track; the outcome change does not alter the prior-event ranking input.

UKMTO's API maps Warning 190 at 09°54′N, 53°03′E, while its PDF prints no coordinate and conflicts on the event date and time. UKMTO has now reclassified record 190 as a hijack, and JMIC explicitly links it to MSCIO Alert 161/26's AZINI case. The marker is retained as a historical source-reported duplicate, not a current track or necessarily the hijacking location, and remains excluded from numerical counts to prevent double counting. MSCIO Update 01 gives AZINI's latest reported position as 09°47′N, 55°45′E and says it is approaching the maritime traffic lane, but supplies no fix time. That marker is also historical, not a current track; the preceding 09°42′N, 53°55′E fix was timestamped 04:00 UTC on 30 October. JMIC assesses that the hijack indicates possible pirate-action-group reach across the northern Somali Basin toward routes east and south of Socotra, but this is a qualified outlook, not a measured range limit or calibrated probability. The 7 October MSCIO attack has an ICC IMB-reported event time and position: 05:50 UTC at 12°58.77′N, 43°12.54′E. IMB reports suspected pirates, while the MSCIO record itself does not attribute the attack. That event remains excluded from the Somalia-focused scenario calculation. HONOUR 25, SWARD and LUTUF reflect close-to-coast opportunity; SIBU shows an underway tanker was seized offshore in the Gulf of Aden. ATALANTA assessed ALWASEEMI's March 2026 seizure as highly likely preparation for mothership use. SAVINA CAYLYN is a historical example from the 2011 peak. These dated examples use different geographic reference points; they do not measure present operating limits or confirm an active mothership. A single coastal buffer cannot describe all the documented event locations. ATALANTA's ALWASEEMI account

Seasonality

A dated seasonal assessment

JMIC · 15 Nov

JMIC's 15 November update retains the assessment that the southwest monsoon subsided on 15 October. Its new fishing-vessel report near Hobyo illustrates retained coastal seizure capability; the event is being investigated as armed robbery. JMIC assesses possible offshore use of seized fishing vessels or dhows and PAG reach east and south of Socotra, not confirmed mothership use by this vessel or a current group position. Update 114 supplies no replacement numerical wave/wind forecast; the 12 November 24–48-hour weather outlook is expired. JMIC retains moderate threat on the Somali coast and basin and substantial threat in the Gulf of Aden. ASANA is the sole merchant vessel still reported held, while the fishing-vessel case has an unresolved outcome. This is dated authority evidence and a qualified outlook, not a measured seasonal attack rate or a forecast of present sea state. Check current feeds and official advisories before passage. JMIC Update 114 · 15 Nov, 13:00 UTC cut-off

Target profile

The six merchant seizures: four tankers

Documented mix
Oil / product tankers4 / 6
General / cargo2 / 6

ASANA, the sole merchant vessel still reported held, is an oil or product tanker. Among the six documented merchant seizures from April to August 2026, four were tankers and two were general or cargo vessels. At least four cases involved reported routes to Mogadishu, Bosaso or Mombasa. The ledger also includes dhow and fishing-vessel incidents, including suspected mothership use; these are outside the six-merchant-vessel denominator. IMB's January–September release attributes eight vessel hijackings to Somali pirates, but its public summary does not list the eight cases or separate merchant ships from dhows and fishing craft. The Observatory therefore preserves both figures with their different scopes instead of adding unnamed cases or changing the documented 4/6 mix. Without vessel traffic and protection denominators, the seizure mix does not establish a higher attack rate for regional traders or quantify the effect of their defences. IMB January–September 2026 release

Response evidence

Delay creates response opportunities

Case-based lessons
01Detect

Lookout / radar / reporting

02Deter

Speed / barriers / manoeuvre

03Delay

Citadel / access control

04Coordinate

UKMTO / MSCIO / naval

05Secure

Boarding / evidence / legal

GLAMOR and GOLDEN ARSENAL provide complementary 2026 evidence: prompt reporting, systems denial, a functioning citadel and coordinated naval pressure can prevent a boarding from becoming a hostage case. These cases document actions and outcomes; they do not estimate the numerical protective effect of any measure. For GLAMOR, CTF 151 reports that it directed a patrol aircraft within two hours. PMPF's reported SIBU 1 recovery adds evidence that coastal-State enforcement can end a hostage case. EFE's PMPF account reports no casualties while AFP reports one alleged pirate killed and five people wounded; the conflict, detainee count and prosecution outcomes remain unresolved. If AFP's report that 28 detainees escaped during transfer is confirmed, with only partial recapture, it would weaken judicial follow-through and create an opportunity for suspects to return to pirate networks. Puntland has not publicly confirmed the escape or alleged police assistance. CTF 151's six-day Operation Tidal Wave, concluded on 20 October, adds a separate current example of coordinated warship, maritime-patrol-aircraft and regional-coastguard activity. CMF confirms that Seychelles aircraft and ships worked together farther east than before, but publishes no asset identities, patrol boundaries, incident outcomes, current positions or measured deterrent effect; the completed operation does not establish current coverage or a guaranteed response. Puntland's 29 September announcement that five HONOUR 25 crew were killed before the tanker was recovered turns the earlier armed threats into a fatal outcome and sharply raises the hostage-protection and deconfliction priority for ASANA, now the sole merchant vessel still reported held after EUREKA's 29 September recovery. JMIC Update 101 confirms both recoveries, five HONOUR 25 crew casualties and all EUREKA crew safe, but does not resolve the casualty sequence. PMPF places the operation off Dharin-Bar in Bandar Beyla district. Its initial report of 21 apprehensions was later revised to 16; AP reports at least 11 other suspects escaped the operation and remained at large. The casualty sequence and any ransom outcome remain unconfirmed. Pakistan's Foreign Office says the surviving crew were safely transferred to Garowe by its 1 October briefing, where the injured were being treated. ATALANTA's 16 October account confirms its flagship moved to the HONOUR 25 area ready to provide medical assistance and evacuation if needed. It reports five crew killed and two injured; Puntland Information Ministry reporting carried by Reuters and Pakistan's Foreign Office report four injured; ICC IMB's 15 October summary attributes five injuries to Puntland authorities without identifying the fifth person or its underlying source. The complete injury total and fatality sequence remain unresolved. Geo News and ARY News confirm the final three Pakistanis' 7 October Karachi arrival; Dawn fixes it at 16:40 PKT (11:40 UTC) aboard an Ethiopian Airways flight from Addis Ababa. ANTARA and AFP confirm that four Indonesian crew, including the master, arrived in Indonesia on 6 October. Other exact transfer times and individual medical findings remain unconfirmed. The CTF 151 command-post exercise reported on 25 September separately rehearsed multinational response, medical support, evidence seizure and legal approval, but did not announce any additional patrol assets or coverage.

Scenario watchlist

Indicators that would change the assessment

Monitoring scenario

Contained coastal persistence

Alert 179/26 reports a fishing-vessel hijacking near Hobyo under ATALANTA armed-robbery investigation. Identity, crew welfare, present control and any offshore use remain unknown; no event probability is estimated.

Watch: authority-confirmed vessel control, crew welfare and follow-on activity
Plausible escalation

Multiple active motherships

UKMTO 206-26 reports a possible mothership and armed skiff 430 NM east of Socotra. This is suspicious activity under investigation, not a confirmed pirate group, mothership identity or link to the Hobyo fishing vessel.

Watch: replacement PAG warnings, missing dhows and skiff sightings
High impact

Authority-confirmed financing

A UN report published in February 2026 records Member State reporting of a piracy-linked safe-passage revenue share reaching AQAP during its June–December 2025 reporting period. It gives no vessels, amounts or 2026 incident link; the current measure remains unknown.

Watch: confirmed payments or financial disruption
Positive inflection

Coordinated coastal disruption

Somali authorities deny anchorages while naval forces disrupt motherships offshore.

Watch: arrests, evidence and prosecutions

Evidence check

Four claims that distort the debate

Each finding separates a real contributing factor from a conclusion the evidence does not support.

“Piracy began only because of illegal fishing.”

Coastal predation and grievances mattered to early legitimacy. The ransom economy, however, became an organised profit-seeking system with financiers taking the largest share.

“Navies solved piracy.”

Naval presence was indispensable, but the decline required BMP, armed security, citadels, regional prosecutions, Somali action ashore and lower ransom profitability together.

“No attacks means no capability.”

The 2017 and 2023 returns show that skills, networks and launch geography can survive below the threshold of frequent reported attacks.

“Every incident off Somalia is piracy in law.”

UNCLOS piracy occurs outside State jurisdiction. Attacks inside territorial waters are generally classified as armed robbery at sea, with the coastal State holding primary jurisdiction.

Response network

No single mechanism owns the problem.

Deterrence at sea, awareness, prosecution, capacity and political coordination are separate functions. The architecture succeeds when each hands the case to the next without losing time, evidence or authority.

Naval response Regional ownership Legal finish Industry interface
Primary role

Protects vulnerable shipping; deters, disrupts and represses piracy; coordinates response through MSCIO; gathers evidence for prosecution.

Evidence of delivery

Portuguese Commodore José João Rodrigues Pedra assumed command of the 54th Force Headquarters rotation on 10 October 2026, embarked aboard the new flagship ESPS SANTA MARÍA. The mandate runs to 28 February 2027. ATALANTA and the Seychelles Armed Forces also completed ALDABRA V phase 2 in Seychelles from 26 to 29 September, using a real-life piracy scenario with assets and special-operations teams from both forces.

Persistent gap

The rotation and exercise records give no complete force composition, patrol-area change, coverage measure, readiness metric or demonstrated deterrent effect; a vast operating area and competing regional demands limit persistent coverage.

Official source

The operational handoff

01

Report

Ship → UKMTO / MSCIO

02

Fuse

MSCIO / RMIFC / JMIC

03

Respond

ATALANTA / CTF 151 / national

04

Secure evidence

Boarding team → investigators

05

Transfer

Flag / coastal / regional State

06

Finish

Prosecute → imprison → repatriate

History of the modern cycle

How a coastal grievance became a transnational ransom industry.

Modern Somali piracy did not move in a straight line. It grew through adaptation, collapsed under layered pressure, then re-emerged when opportunity again exceeded risk.

1
1991–2004
Formation

State collapse and coastal predation

The fall of Somalia's central government removed effective maritime policing. Illegal fishing and coastal grievances helped legitimise early armed self-defence narratives, but the activity evolved into organised criminal enterprise.

2
2005–2007
Acceleration

The ransom model proves scalable

Merchant-vessel hijackings produced far larger returns than coastal robbery. Investors, negotiators, guards, suppliers and local brokers formed an onshore business ecosystem.

3
2008–2011
Peak

Industrial-scale piracy

Captured dhows and ships became motherships, pushing attacks far into the Arabian Sea and Indian Ocean. IMB recorded 237 Somalia-related incidents in 2011; success rates nevertheless began to fall.

4
2012–2016
Collapse

Layered suppression works

Naval patrols, BMP, armed guards, citadels, stronger regional prosecutions and action ashore combined. Reported incidents fell from 237 in 2011 to 75 in 2012 and 15 in 2013.

5
2017–2022
Residual risk

Dormant, not dismantled

ARIS 13 showed retained capability, but the cost and probability of failure kept most groups inactive. The Indian Ocean High Risk Area designation was removed from 1 January 2023.

6
2023–2025
Resurgence

Mothership-enabled return

MV RUEN's capture in December 2023 marked the return of large-vessel hijacking. A cluster of dhow, fishing-vessel and merchant incidents followed through 2024–2025.

7
2026
Active cycle

A renewed hostage economy

Six merchant vessels were seized between 21 April and 20 August. ATALANTA's 16 October status update confirms HONOUR 25, SWARD, EUREKA and SIBU 1 closed and ASANA still open. It reports SWARD safely arrived in Mombasa and says EUREKA's crew later flew from Mogadishu to their respective countries of origin, without supplying those travel dates. JMIC and IMO reporting already established the September recoveries and current aggregate: 44 seafarers freed from SIBU 1/SEAMULL, HONOUR 25 and EUREKA, with 22 remaining captive aboard ASANA. ATALANTA confirms five HONOUR 25 crew killed but reports two injured; Puntland Information Ministry reporting carried by Reuters and Pakistan's Foreign Office report four, while ICC IMB's 15 October summary attributes five injuries to Puntland authorities without identifying the fifth person or the underlying Puntland source. The injury total and fatality sequence remain unresolved. ATALANTA also reports up to 21 SIBU 1 suspects arrested, which does not reconcile earlier counts or the later reported custody escape. Exact transfer times, current ASANA position, individual medical findings and final custody outcomes remain outstanding. On 10 September, a seventh piracy case began with the boarding of GLAMOR in the Gulf of Aden, but citadel use and a coordinated ATALANTA-CMF response prevented another seizure. On 17 September, a suspicious skiff pursued and attempted to intercept an unnamed tanker east of Aden; the vessel refused to stop and the crew was reported safe, although later contact was lost. MSCIO and JMIC differ by 54 minutes on the initial event time, which remains unresolved. On 17 October at 10:30 UTC, UKMTO classified a separate encounter at 12°54′N, 47°55′E as an attack after a seven-person skiff fired two shots at an LNG tanker 140 NM southwest of Al Mukalla; the tanker's armed security team fired warning shots and the skiff altered course. UKMTO's 23 October overview identifies a Bahamas-flagged LNG tanker of about 110,000 DWT, says the vessel continued its voyage and reports no injuries, damage or pollution. No boarding or piracy attribution is reported. JMIC Update 106 explicitly links NAVAREA IX warning 383/26 to UKMTO incident 176, so the warning remains visible but excluded as a confirmed duplicate. MSCIO Alert 149/26 sits one minute east and closely matches the narrative, but that linkage remains inferential. UKMTO says southwest of Al Mukalla while JMIC says southeast; the exact coordinate is preserved and the directional conflict remains unresolved. JMIC also assesses the southwest monsoon is ending and published forecast wave heights within skiff-operating limits in the Gulf of Aden and Somali Basin, while retaining substantial Gulf of Aden and moderate Somali-coast/basin threat levels. The vessel name, IMO number, crew count and nationalities remain unpublished. An earlier observatory record attributed 87 captives to ATALANTA's 11 September release; the source page retrieved on 2 October instead says more than 100. This historical aggregate discrepancy remains unresolved and predates the subsequent vessel releases and recoveries.

The ransom enterprise

Capability is an onshore system expressed at sea.

A skiff is only the visible edge. Sustainable piracy requires finance, intelligence, fuel, weapons, crews, a captured mothership, safe anchorage, guards, negotiators, local suppliers and a way to distribute or launder proceeds.

01

Finance

Investors underwrite fuel, weapons and supplies

02

Acquire

Dhow or fishing vessel becomes a mothership

03

Hunt

Skiffs search, approach and test vulnerability

04

Hold

Ship is anchored close to a permissive coast

05

Monetise

Negotiators, guards and brokers sustain captivity

06

Recycle

Proceeds reward actors and finance the next cycle

Law and legal finish

Stopping the attack is only half the operation.

A successful maritime intervention must end in a lawful transfer, admissible evidence, fair trial, safe detention and—where applicable—repatriation. Every gap creates a release risk.

UNCLOS Article 101

Piracy

Illegal acts of violence, detention or depredation committed for private ends by the crew or passengers of a private ship, directed against another ship on the high seas or outside the jurisdiction of any State.

Universal jurisdiction may apply on the high seas.
IMO Code of Practice

Armed robbery at sea

Comparable violence, detention or depredation against a ship within a State’s internal waters, archipelagic waters or territorial sea.

The coastal State has primary enforcement jurisdiction.
Why it matters now

The 2026 cases cross legal zones.

LUTUF was reported only four nautical miles from the Somali coast, EUREKA was taken at a Yemeni anchorage, and SIBU was reported 136 nautical miles east of Al Mukalla. Precise location changes the competent authority, offence, consent needed for action and transfer pathway.

Somali legislative status

Both chambers approved the revision; enactment remains unverified.

SONNA reported on 19 September that the House of the People approved the bill revising Somalia's piracy and kidnapping law on 10 November 2025, and that the Upper House approved it on 9 September 2026. The official account does not establish presidential assent, promulgation or entry into force, so the Observatory records parliamentary approval only.

Open official account

For masters, CSOs and operators

Prepare before the bridge team sees the skiff.

This quick reference points to authoritative operational resources. It is not a substitute for a company voyage risk assessment, BMP-MS, flag-State requirements or live UKMTO / MSCIO direction.

01

Before entering the VRA

Register the voyage, confirm reporting schedules, review the latest warnings and test emergency communications.

02

Harden the vessel

Identify low freeboard and access points; rig barriers, lighting, hoses and alarms proportionate to the risk assessment.

03

Brief and drill

Define the alarm, mustering, citadel, SSAS, evasive-manoeuvre and evidence-preservation actions.

04

Detect and report early

Maintain an effective lookout, question unusual dhow–skiff patterns and contact UKMTO before uncertainty becomes boarding.

05

If boarded

Follow the master and company plan; protect life; do not emerge from the citadel until cleared by authorised forces.

06

After the event

Preserve CCTV, VDR, AIS, communications and physical evidence; record crew welfare and witness accounts.

Update operations

Continuously monitored. Deliberately published.

The observatory uses a tiered evidence review cycle. High-consequence changes are checked several times a day; slower-moving evidence is reviewed on a proportionate schedule. No-change runs do not manufacture updates or alter the public record.

Source monitoring active

Verification controls the publish decision.

A new report is assessed against the source hierarchy, event and publication dates, geography, vessel identity, crew status and any conflicting accounts. Preliminary or single-source claims remain outside the verified layer unless the reporting authority itself is the competent operational source.

Primary source firstCorroborate where practicableUncertainty stays visibleNo material change, no deployment
01Hourly

Operational condition watch

New attacks, boardings, hijackings, warnings, vessel or crew status changes, releases, rescues and counter-piracy interceptions.

Publish only when a material change is authoritatively confirmed.
02Every 12 hours

Evidence and analysis refresh

Incident map and index, operational feed, hotspot assessment, response activity, source links and emerging operating patterns.

Reconcile the full current picture and issue a concise change log.
03First Monday monthly

Statistics and mechanism audit

Official totals, mandates, patrol and reporting arrangements, legal developments, prosecutions, guidance and emergency contacts.

Correct superseded records and flag unresolved discrepancies.
04Quarterly

Full observatory review

Historical chronology, trend calculations, case studies, regional architecture, methodology and source-hierarchy performance.

Revalidate the evidence base and preserve an auditable revision trail.

Device alerts

Receive new verified releases

Opt in for browser notifications after a verified incident or material status change is published. No sign-in is required. This stores a private browser delivery endpoint; no email or personal profile is collected. Disable alerts here at any time.

Alerts require your permission on this device.

Checking for published revisions… · The open page checks for published revisions every minute.

Detection uses an hourly authority-source watch; publication follows verification. A direct event feed from authorities is not connected. Push alerts can reach supported devices when the page is closed, but immediate delivery is not guaranteed. For an emergency, use the official reporting contacts.

Information received

New documents, official communications or credible leads supplied for review enter the same verification queue. Receipt alone never changes the published record; restricted, personal or uncleared material is not published.

See the evidence hierarchy

Operational feed

What changed—and why it matters.

A curated feed prioritising operational authorities over headlines. Every item carries a verification date, source type and direct route to the underlying record.

MSCIO / JMIC armed-robbery warning

Fishing-vessel hijacking reported near Hobyo; ATALANTA investigates armed robbery

MSCIO Alert 179/26, published 13 November at 14:34 with timezone unstated, reports a fishing-vessel hijacking. JMIC Update 114 dated 15 November corroborates the report. The latest-reported point is 06°19′N 049°13′E in Somali territorial waters, approximately 67 NM northeast of Hobyo, not a current track or verified attack point. Exact event date/time, vessel identity, flag, crew number, welfare, current control and outcome are unpublished. MSCIO strongly advises vessels in the vicinity to avoid the area, maintain enhanced vigilance and immediately report suspicious activity. No confirmed piracy classification, offshore mothership use, rescue or arrest is inferred. ASANA remains the sole verified held merchant vessel; the fishing-vessel case is separately unresolved.

Open record
IMO · implemented regional drafting cooperation

Seychelles, RCOC and RMIFC contribute to draft maritime-security lexicon

IMO confirms that the expanded draft was finalised at the 27–30 October Addis Ababa workshop, with Seychelles, Somalia, RCOC and RMIFC among participants. It is intended to clarify terminology used across agencies and jurisdictions for incident reporting and coordinated responses. Submission to the 11–13 November High-Level Meeting was planned; adoption and implementation remain unverified. Seychelles participation here must not be inferred for the separate Mombasa workshop.

Open record
IMO Council · separate regional statistical denominator

IMO notes 17 regional piracy and armed-robbery instances

The 2–6 November Council session noted 17 attempted or actual piracy and armed-robbery instances in the Western Indian Ocean and Gulf of Aden since the year's start. Its 6 November release supplies no case table or precise statistical cut-off. This is not a hijacking count and is not directly interchangeable with the Observatory ledger, UKMTO's wider piracy-related series or IMB's totals. No unnamed cases, crew outcome, map position or numerical-model change is inferred.

Open record
CMF / DCoC regional cooperation output

Mombasa workshop produces regional risk register and vessel-registry proposals

CMF confirms that CTF 154 joined experts from 13 countries on 2–6 November to develop a regional risk register and proposals for a shared vessel registry relevant to piracy and smuggling. The article is datelined 10 November and published 12 November, with no exact release time. It does not establish registry implementation, additional patrols or Seychelles participation. A Kenyan CTF 154 command transition is planned for January 2027, not completed. No verified DCoC High-Level Meeting adoption outcome is established.

Open record
Historical IMB source reconciliation

IMB 057-26: unnamed fishing vessel rescued; case overlap unresolved

IMB records a 03:30 UTC fishing-vessel hijacking at 09°51.54′N 051°30.73′E, around 37 NM southeast of Xaafun, Somalia, and says a naval asset rescued all crew. The vessel is unnamed; its identity and any AZINI linkage are unconfirmed. The historical point is mapped separately but excluded from numerical counts to avoid potentially double-counting a case. Crew total, rescue timing and force, custody and later welfare remain unpublished. This is not treated as a newly occurring incident or urgent alert.

Open record
JMIC dated outlook and communications warning

Somali Basin sea-state outlook changes; vessel status unchanged

JMIC Update 113 forecasts moderate Somali Basin seas of 1.4–1.8 metres and winds of 15–19 knots for its reporting period, still assessed as permitting offshore skiff and mothership activity. Gulf of Aden seas are forecast slight. This is a dated 24–48-hour outlook, not live conditions. ASANA remains the sole reported held merchant vessel, with no new welfare information; regional ratings are unchanged. JMIC also warns that disclosing voyage details in response to HOCC communications may increase targeting risk and cites MARAD's U.S.-flag guidance. Use of the advertised transit service is independently unconfirmed.

Open record
Named SDF spokesperson · corroborated completed training

Seychelles and Russia complete anti-piracy boarding exercise

Seychelles Defence Forces spokesperson Lieutenant Colonel Archil Mondon tells Seychelles News Agency that joint boarding teams trained on 5 November using a Seychelles Coast Guard vessel as a simulated pirate-held target, with helicopter support, during MARSHAL SHAPOSHNIKOV's visit. The Russian Defence Ministry separately confirms completion. This records practical regional cooperation, not a real interception, present ship position, new patrol coverage or measured readiness effect. Exact exercise times and evaluated outcomes are unpublished.

Open record
MSCIO suspicious-activity report · event 6 Nov

Bab el-Mandeb: unidentified target explosion, piracy link unknown

MSCIO Alert 172/26 reports an unidentified northbound radar target followed by an explosion and prolonged surface fire at approximately 22:45 UTC on 6 November at 12°46.4′N 043°18.0′E. No distress calls were reported. Identity, cause and welfare remain unknown; no attack on the observing merchant vessel or piracy connection is established. The historical reported point is mapped but excluded from numerical piracy diagnostics. Publication displays 7 November at 19:47 with timezone unstated.

Open record
UKMTO recovery and enforcement update

AZINI recovery: detention reported; later custody unknown

UKMTO’s 6 November Overview No. 14 says the Indian Navy recovered AZINI on 2 November, detained unauthorised persons aboard and rescued the original crew. Its warning summary reports 10–12 armed boarders, but it does not state how many people were detained or establish subsequent custody, transfer, release or prosecution. The overview table places record 190 at 09°54′N, 53°04′E on 30 October, while its narrative says 1 November. The official API instead gives 09°54′N, 53°03′E and 31 October; MSCIO reports hijacking on 29 October. These unresolved source differences do not change the historical markers or the confirmed duplicate treatment. The overview reports 44 piracy-related reports in its wider year-to-date series (11 boardings/hijackings, five attacks, 28 suspicious-activity reports), not 44 confirmed pirate attacks. These totals are kept separate from the Observatory index. No extra incident, current ship position, crew outcome or numerical model change is inferred.

Open record
MSCIO–ATALANTA weekly report

ASANA remains under monitoring; AZINI update dates differ

The report covers 30 October–6 November; its directory displays 6 November at 11:23, time zone unstated. ATALANTA continues monitoring ASANA. The report confirms AZINI’s closure and repeats the separate 30 October armed-skiff approach without reporting shots. The MSCIO–ATALANTA weekly report dates the issue of AZINI Update 01 to 2 November, while the alert page displays 31 October at 09:24, timezone unstated. Neither source timestamps the position fix. No new crew welfare information, piracy case or map position is established.

Open record
Official independent-deployer update

Türkiye reports Somalia naval rotation and resupply

Türkiye’s defence ministry said on 5 November that two frigates began a Somalia-bound rotation and maritime resupply mission on 30 October. Parliament had approved a two-year extension from 27 July 2026 of the wider Somalia security mandate, which includes counter-piracy. Arrival, transfer of duties, patrol coverage and any connection to a specific incident are not established.

Open record
JMIC operational advisory

Gulf of Aden warning reaches end date; no replacement identified

JMIC Update 111 says NAVAREA IX warning 416/26 reached its stated 3 November end date and identifies no replacement as of 5 November at 13:00 UTC. That does not establish that the suspected group dispersed or that conditions are safe. JMIC reports no confirmed attack or disruption in the Gulf of Aden or Somali coast and basin in the preceding 96 hours. It reconfirms AZINI’s closure and lists ASANA as the sole merchant vessel still held, without new welfare details. The Bab el-Mandeb floating-object report (MSCIO 168/26) is classified as suspicious activity, with no reported attack on a merchant vessel and no established piracy link.

Open record
ATALANTA operational-posture and statistics update

Djibouti exercise recorded; WFP-vessel total advances to 2,519

Operation ATALANTA published on 4 November at 15:21, timezone unstated, that its flagship ESPS SANTA MARÍA hosted an EU Political and Security Committee visit in Djibouti on 3 November. The visit included a counter-piracy coordination exercise linked to the Operation Headquarters in Rota and a static capability display. The release identifies the embarked SH-60B helicopter and ScanEagle system, D-4 ORION personnel associated with a CASA CN-235 VIGMA maritime-patrol aircraft, and Special Operations Maritime Task Unit capabilities. These are historical, publicly cleared event details—not present ship or aircraft positions, a patrol boundary, a readiness measure or evidence of current coverage. ATALANTA also reports 79 pirate-related events since November 2023, with one still ongoing in the Somalia Basin, and 177 pirates transferred. Its statistics page, updated 5 November with no stated time, now gives 2,519 WFP vessels protected, 3,311,078 tonnes of food or aid delivered, 177 pirate transfers and 145 convictions. The press release's less precise ‘more than 2,515’ wording is compatible with the current statistics page. No incident, crew, hostage, map or numerical risk diagnostic changes are made; ASANA remains the sole verified ongoing merchant-vessel case.

Open record
Indian Ministry of Defence crew-welfare and response update

Indian Navy says all 20 AZINI crew safely rescued

Indian Ministry of Defence reporting says the Indian Navy, with Indian Air Force support, completed a more-than-48-hour operation on 2 November, secured AZINI and safely rescued all 20 crew members without casualties or injuries. MSCIO had already confirmed liberation and closure. The official Indian report resolves the participating force and the welfare of the 20 people it describes, but an earlier Associated Press account citing an unnamed Puntland Maritime Police Force officer said 21 Iranian crew and two Somali guards were aboard. No attributable Puntland release located resolves the 20-versus-23 discrepancy, so nationalities or additional persons are not inferred. The exact interception coordinate and completion time, pirate number and identity, arrests or custody, vessel condition and destination, and any ransom or negotiation detail remain unpublished. Historical coordinates are not a current track. The outcome-only correction adds no incident and does not alter the prior-event ranking input.

Open record
MSCIO operational status update

AZINI liberated; incident closed

MSCIO Alert 161/26 Update 02 says Operation ATALANTA confirms that anti-piracy military forces liberated the Iranian fishing vessel AZINI and closes the incident. The authority does not publish the liberation date or time, location, participating force or forces, crew number, nationalities or welfare, casualties, arrests or custody, vessel condition or destination, or ransom or negotiation detail. Historical AZINI and UKMTO 190 coordinates remain source-reported points, not a current track. The linked UKMTO record remains visible as a confirmed duplicate and excluded from numerical counts. The outcome change does not add an incident or alter the prior-event ranking input.

Open record
Monthly operational-contact audit

UKMTO backup lines and IMB 24-hour reporting contact added

The first-Monday audit confirms UKMTO's primary 24/7 number and email, MSCIO's two telephone lines and email, and adds UKMTO's two published 24/7 secondary numbers plus the ICC IMB Piracy Reporting Centre's 24-hour anti-piracy helpline and reporting email. The audit also rechecked ATALANTA's mandate and cumulative statistics, current UKMTO/JMIC and MSCIO incident records, CMF/CTF 151 arrangements, IMB January–September statistics, regional mechanisms and reporting links. No new in-scope incident, vessel or crew-status change, prosecution outcome, patrol-coverage measure, threat reclassification or numerical-assessment change was verified. The incident evidence cut-off therefore remains unchanged and no urgent visitor notice is created.

Open record
UKMTO reclassification · JMIC case linkage

Warning 190 reclassified as hijack and linked to AZINI

UKMTO Update 001 reclassifies incident 190 from suspicious activity to hijack. JMIC Update 110 explicitly groups UKMTO 190-26 and MSCIO 161/26 as the same AZINI fishing-vessel case. The UKMTO API record remains visible at its historical 09°54′N, 53°03′E coordinate but is now labelled a confirmed duplicate and excluded from numerical counts; AZINI remains the counted hijacking record. Source clocks conflict: MSCIO and JMIC report approximately 09:00 UTC on 29 October, the initial UKMTO PDF states 14:19 UTC on 30 October, and the API states 18:48 UTC on 31 October. JMIC's table retains a suspicious-activity label while its narrative says AZINI was hijacked and UKMTO later reclassified record 190. Crew number and welfare, current position, ransom or negotiation status, response assets and confirmed subsequent mothership use remain unpublished.

Open record
Official Somali maritime-security governance update

New Somali Navy and Coast Guard commander assumes office

The Somali Ministry of Defence reports that Colonel Mohamed Abdiqadir ‘Sharif’ formally took over as Commander of the Navy and Coast Guard from Brigadier General Abdiwahab Abdullahi Omar on 1 November. The Somali National News Agency and Shabelle Media Network corroborate the handover; Shabelle places the ceremony in Mogadishu. This is a verified leadership transition, not evidence of a new patrol, asset, funding decision or changed anti-piracy capability. The reviewed releases publish no operational priorities, workplan, patrol boundaries, coverage measure, response-time commitment or readiness effect. Current naval and coastal-policing coverage therefore remains unknown; incident records, map positions, vessel and crew statuses, threat ratings and numerical diagnostics are unchanged.

Open record
UKMTO initial suspicious-activity warning · superseded

Fishing vessel boarded; possible PAG activity

The initial UKMTO Warning 190-26 reported that a large fishing vessel was boarded by unauthorised personnel and retained a suspicious-activity classification. At that publication point, the reviewed authorities had not linked the record to AZINI. UKMTO later reclassified incident 190 as a hijack, and JMIC Update 110 linked it to MSCIO Alert 161/26's AZINI case; see the newer correction above. The initial PDF states 14:19 UTC on 30 October and prints no coordinate, while the API states 18:48 UTC on 31 October and maps record 190 at 09°54′N, 53°03′E. Those conflicts and the unpublished crew welfare remain unresolved.

Open record
MSCIO operational piracy update

AZINI latest reported position moves toward traffic lane

MSCIO Alert 161/26 Update 01 gives AZINI's latest reported position as 09°47′N, 55°45′E and says the hijacked fishing vessel is approaching the maritime traffic lane. The authority does not state the time of this fix, so the coordinate is preserved as a historical reported position rather than a current track. Crew number, nationalities and safety remain unpublished. Potential mothership use remains a warning, not confirmed subsequent use, and Operation ATALANTA continues to investigate. Exact hijacking position, current position or course, pirate number and identity, ransom or negotiation status and response assets remain unpublished. No second competent-authority report was located at publication time.

Open record
MSCIO suspicious-activity alert

Armed skiff aborts Gulf of Aden approach

MSCIO Alert 160/26 reports that at approximately 02:25 UTC on 30 October near 11°57.4′N, 45°04.5′E, two suspicious craft approached an unidentified merchant vessel in the Gulf of Aden. One greenish fast skiff carried four persons and reportedly a mounted machine gun. It closed to approximately 300 metres astern, then aborted after the vessel's armed security team displayed their weapons. No shots were fired and no boarding attempt was reported; the vessel continued its voyage. Operation ATALANTA is investigating. Vessel identity, flag, type, crew particulars and welfare, damage status, the second craft's details, piracy attribution and present positions remain unpublished. The event coordinate is historical, not a current track. No authority source reviewed links this encounter to Alert 156/26, AZINI or another case.

Open record
MSCIO operational piracy alert

Iranian fishing vessel AZINI reported hijacked

MSCIO Alert 161/26 reports that armed pirates hijacked the Iranian fishing vessel AZINI off northeastern Somalia at approximately 09:00 UTC on 29 October. Its last reported position was 09°42′N, 53°55′E at 04:00 UTC on 30 October; this is a historical fix, not a current track or necessarily the hijacking location. Crew number, nationalities and safety are not published, and MSCIO says crew safety remains unknown. The vessel could potentially be used as a mothership, but no subsequent use is confirmed. Operation ATALANTA is investigating. Exact hijacking position, present position or course, pirate number and identity, welfare detail, ransom or negotiation status and response assets remain unpublished. No second competent-authority report was located at publication time.

Open record
National flag-administration security guidance

Norway retains Level 3 in Bab el-Mandeb; widens Level 2 north

The Norwegian Maritime Authority keeps ISPS Security Level 3 in force in the Bab el-Mandeb Strait for Norwegian vessels. It sets Level 2 for the southern Red Sea and northern Gulf of Aden and extends the northern Red Sea Level 2 area to waters north of Yanbu. The authority cites continuing missile, drone and small-boat exposure in Bab el-Mandeb and recommends BMP Maritime Security, vessel-specific security planning, voyage and port-call risk assessment, training and reporting to UKMTO and MSCIO. Level 3 is retained rather than newly imposed; the stated material change is the northward Level 2 extension. This is Norwegian flag-state guidance, not a JMIC regional threat reclassification, a new piracy incident, a patrol deployment or evidence of present naval coverage. Exact publication time, effective hour, review date and boundary coordinates are unstated. Incident records, map positions, ASANA status and numerical diagnostics remain unchanged.

Open record
National flag-administration security guidance

Norway extends ISPS Level 2 across the full Gulf of Aden

The Norwegian Maritime Authority has extended ISPS Security Level 2 to the entire Gulf of Aden for Norwegian vessels. Level 2 remains in force in the western Arabian Sea, Somali waters and the western Indian Ocean out to 600 nautical miles from the Somali coast. The authority requires vessel-specific security assessment and planning and recommends BMP Maritime Security, training and drills, review of EUNAVFOR threat assessments through MSCIO, and reporting to UKMTO and MSCIO. This is Norwegian flag-state guidance, not a new JMIC regional threat rating, incident report, patrol deployment or evidence of present naval coverage. Its unenumerated reference to vessels held by pirates does not change the Observatory's verified ASANA-only merchant-vessel count. Exact publication time, effective hour, review date and map coordinates are unstated; incident counts, positions and numerical diagnostics remain unchanged.

Open record
JMIC operational status and threat update

No Gulf of Aden attack confirmed; ASANA remains sole held merchant vessel

JMIC Update 109, with an information cut-off of 13:00 UTC on 29 October, records UKMTO 184-26 as an advisory concerning multiple suspicious small-craft sightings near merchant vessels in the Gulf of Aden. It describes suspected pirate-action-group activity but reports no damage and no confirmed Gulf of Aden attack in the preceding 96 hours. JMIC retains substantial threat in the Gulf of Aden and moderate threat on the Somali coast and basin. It also confirms ASANA as the sole merchant vessel still hijacked, describing it as a Tanzanian-flagged product/chemical tanker carrying oil products. The update does not identify the vessels or crews involved in the 28 October sightings, resolve their welfare, publish a current ASANA position or establish present naval coverage. Incident counts, the map and numerical diagnostics are unchanged.

Open record
Official coastal-security cooperation update

EUCAP, ATALANTA and Puntland police strengthen piracy liaison

An EEAS / EUCAP Somalia release records a 20 October meeting in Bossaso between EUCAP Somalia's Puntland field office, Operation ATALANTA's liaison officer in Somalia and senior Puntland State Police officials. Discussions focused on enhanced information-sharing, liaison and operational cooperation against piracy and other illicit maritime activity; ATALANTA outlined its maritime operations and future engagement opportunities. The release documents an active cooperation channel but gives no agreed workplan, funding, assets, patrol boundaries, coverage measure, response-time commitment, follow-up delivery or measured operational effect. It therefore does not establish a new patrol, present naval coverage, a completed response or Seychelles participation. Incident records, vessel and crew status, map positions and numerical diagnostics remain unchanged.

Open record
ICC IMB case-level incident clarification

7 October container-vessel attack: time, position and response added

ICC IMB incident 053-26 records a container vessel approached and fired upon by suspected pirates at 05:50 UTC on 7 October at 12°58.77′N, 43°12.54′E in the Red Sea. The alarm was raised, crew retreated to the citadel, the vessel increased speed and manoeuvred evasively, and the onboard armed security team returned fire, aborting the approach. MSCIO Alert 132/26 separately reports a container vessel fired on by two people aboard a fishing boat in the Bab el-Mandeb, damage to a bridge-wing porthole and lifeboat, and all crew safe. The matching date, vessel type, area and gunfire make a common event highly likely, but neither authority cross-references the other. NAVAREA IX warning 363/26 is less than one nautical mile from the IMB position; JMIC later assessed the warning activity as likely fishermen firing into the air over a close approach, so the conflicting interpretations remain explicit and the warning is not treated as a confirmed duplicate.

Open record
MSCIO operational alert · NAVAREA IX warning

Possible pirate action group: position corroborated

MSCIO Alert 156/26 reports a suspected pirate action group operating approximately at 12°42′N, 47°35′E in the Gulf of Aden. It describes a green-blue craft with nine persons, two ladders and one hook, observed travelling south at an estimated 10–18 knots; Operation ATALANTA is investigating. NAVAREA IX warning 416/26, issued at 15:00 UTC, independently reports a possible pirate action group at the same approximate position and advises mariners to keep clear and exercise extreme caution. No attack, boarding or hijacking is reported. The observation time, merchant-vessel identities, crew details and outcome remain unpublished; the reported course and speed are not a current position. The advisory remains excluded from numerical incident-pattern calculations.

Open record
UKMTO Advisory 184-26 · official-source discrepancy

Gulf of Aden advisory: position added; time conflict preserved

UKMTO Advisory 184-26 records suspicious small-craft activity near merchant vessels at 10:30 UTC on 28 October, sourced to military authorities and labelled Aden, Yemen. UKMTO's official incident API maps record 184 at 12°42′N, 47°35′E but gives 12:02 UTC in its incident-time field. The Observatory preserves both times because the authority sources conflict. One reported green-and-blue craft carried nine people, two ladders and a hook. The coordinate is mapped as an advisory location, not a confirmed attack or current craft position. Merchant-vessel identities, crew details and outcome remain unpublished; no attack, boarding, hijacking, mothership or confirmed attribution is established. The advisory is excluded from incident-pattern calculations and does not change the numerical forecast.

Open record
JMIC seasonal operating-context update

Southwest monsoon withdrawn; farther-offshore skiff feasibility increases

JMIC Update 108, with an information cut-off of 13:00 UTC on 25 October, records the southwest monsoon as withdrawn on 15 October and says the inter-monsoon period is under way. It retains substantial threat in the Gulf of Aden and moderate threat on the Somali coast and basin, assesses residual opportunistic piracy risk in nearshore Somali waters and the Gulf of Aden, and says farther-offshore skiff operations and possible use of dhows or hijacked fishing vessels as motherships are more feasible. JMIC labels the regional piracy outlook unchanged and reports no Gulf of Aden incident after UKMTO 176. This is a qualitative operating-context update: it does not establish an active mothership, a current pirate position, increased naval coverage or a numerical forecast change.

Open record
UKMTO vessel and outcome clarification

LNG-tanker attack: Bahamas flag and no damage reported

UKMTO Weekly Overview No. 12 identifies incident 176's vessel as a Bahamas-flagged LNG tanker of approximately 110,000 DWT. The authority reports that the vessel continued its voyage and that no injuries, damage or pollution were reported. The vessel name, IMO number, crew count and nationalities, assailants, motive and piracy attribution remain unpublished. UKMTO continues to say 140 NM southwest of Al Mukalla while JMIC Update 106 says southeast; the exact 12°54′N, 47°55′E coordinate is unchanged. MSCIO Alert 149/26 remains a high-confidence but inferential match.

Open record
MSCIO operational communications advisory

False Yemeni Coast Guard emails seek vessel and port details

MSCIO Advisory 10-2026 warns that several shipping companies received emails claiming to originate from the Yemeni Coast Guard and requesting vessel movements, port calls and operational details, particularly information concerning Saudi Arabian ports. MSCIO identifies ycgyemen.sanaa@gmail.com and info@ycg-yemen.com as neither official nor verified Yemeni Coast Guard addresses; some messages reportedly included documents presented as official correspondence. MSCIO instructs companies, operators and vessels not to reply or provide information and to report further communications to MSCIO. This is a communications-security advisory, not a new Yemeni reporting channel, route or port restriction, piracy incident, or evidence of changed pirate capability.

Open record
Official multinational counter-piracy operation update

CTF 151 concludes six-day Operation Tidal Wave

Combined Maritime Forces reports that CTF 151 concluded the six-day Operation Tidal Wave in the Gulf of Aden and Indian Ocean on 20 October. Fifteen organisations from ten nations participated through coalition warships, maritime-patrol aircraft and regional coastguards, combining day-and-night presence, merchant-shipping warnings, coordinated offshore patrols, regional inshore coverage and training. CMF says an Indian warship joined a focused operation for the first time, Kenya widened the waters it patrolled, and Seychelles aircraft and ships worked together farther east than before. The release confirms an implemented regional operation and Seychelles contribution, but gives no precise start date or times, complete participant or asset list, patrol boundaries, incident outcomes, current positions or quantitative coverage or deterrence measure. The operation has ended; intended continuing cooperation does not establish present asset availability or guaranteed response.

Open record
Official counter-piracy coordination update

CTF 151 strengthens Djibouti partnerships ahead of focused operation

Combined Maritime Forces reports that CTF 151 visited Djibouti from 8–13 October and held senior-level talks ahead of a focused Gulf of Aden counter-piracy operation. Discussions with the Djibouti Navy and Coast Guard covered coastal surveillance, maritime-interdiction procedures and information-sharing; meetings with ATALANTA reaffirmed patrol coordination, information-sharing and mutual support, while talks with Japanese and Spanish maritime-patrol-aircraft detachments addressed use of limited airborne surveillance assets and avoiding duplicated coverage. Personnel also rehearsed a coalition piracy response in a tabletop exercise. CMF does not disclose the operation date, participating assets, patrol area or coverage, current ship or aircraft positions, measured readiness or operational effect, or Seychelles participation; current naval coverage therefore remains unknown.

Open record
JMIC operational correction and seasonal outlook

JMIC links piracy warning to UKMTO 176; monsoon limits ease

JMIC Update 106, with an information cut-off of 13:00 UTC on 18 October, explicitly states that NAVAREA IX warning 383/26 reported UKMTO incident 176. The warning is therefore retained as a visible but excluded duplicate rather than an unresolved separate event. JMIC keeps the Gulf of Aden threat substantial and the Somali coast/basin threat moderate, and assesses that ending southwest-monsoon conditions and forecast wave heights make skiff operations increasingly feasible, including possible use of dhows or hijacked fishing vessels as motherships. JMIC says 140 NM southeast of Al Mukalla while UKMTO says southwest; the exact 12°54′N, 47°55′E coordinate is preserved. MSCIO Alert 149/26 remains a high-confidence but inferential match. The vessel flag and outcome were not published in that update; UKMTO's 23 October overview later identifies the Bahamas flag and reports no injuries, damage or pollution. Piracy attribution remains unknown; no numerical forecast changes.

Open record
UKMTO official incident-record clarification

LNG-tanker attack: exact time and position now recorded

UKMTO's official incident API records incident 176 at 10:30 UTC on 17 October at 12°54′N, 47°55′E. JMIC Update 106 now explicitly links NAVAREA IX warning 383/26 to this event, while MSCIO Alert 149/26 remains a closely matching but not cross-referenced report one minute of longitude east. The warning remains a separate excluded duplicate to prevent double counting. UKMTO says southwest of Al Mukalla while JMIC says southeast; the exact coordinate is preserved. The API did not publish the vessel flag or damage outcome; UKMTO's 23 October overview later identifies the Bahamas flag and reports no injuries, damage or pollution. The vessel name, IMO number, crew count and nationalities, assailant identity, motive and piracy attribution remain unpublished.

Open record
MSCIO operational classification and welfare update

Gulf of Aden encounter: vessel and crew safe

MSCIO Alert 149/26 reports a suspicious-activity incident involving a merchant vessel at approximately 12°54′N, 47°56′E on 17 October. A small craft carrying seven people reportedly armed with rifles approached to about 100 metres off the vessel's starboard quarter and opened fire. The embarked armed security team fired warning shots; no ladders or hooks were observed, the craft moved away, and the vessel and crew were reported safe. JMIC Update 106 explicitly links NAVAREA IX warning 383/26 to UKMTO incident 176, but does not cross-reference MSCIO. The one-minute position difference and matching narrative support a high-confidence inferential MSCIO linkage.

Open record
Official navigational warning · attempted piracy

Attempted piracy reported north of Somalia

NAVAREA IX warning 383/26, issued at 17:00 UTC on 17 October, reports an attempt of piracy at 12°54′N, 47°55′E in the Gulf of Aden north of Somalia and advises mariners to keep clear and exercise extreme caution. JMIC Update 106 explicitly states that the warning reported UKMTO incident 176, resolving the prior linkage uncertainty. The warning remains a separate display record but is excluded from numerical calculations as a confirmed duplicate. MSCIO Alert 149/26 remains a closely matching but not explicitly linked report approximately one minute east.

Open record
UKMTO operational attack report

LNG tanker fired upon southwest of Al Mukalla

UKMTO incident 176 records that at 10:30 UTC a small skiff carrying seven persons approached an LNG tanker at 12°54′N, 47°55′E, 140 NM southwest of Al Mukalla, and fired two shots. The tanker's armed security team fired two warning shots, after which the skiff altered course. JMIC Update 106 explicitly identifies NAVAREA IX warning 383/26 as reporting this event. MSCIO Alert 149/26 closely matches the encounter and reports no ladders or hooks and the vessel and crew safe, but that linkage remains inferential. UKMTO's 23 October overview later identifies a Bahamas-flagged LNG tanker of about 110,000 DWT, says it continued its voyage and reports no injuries, damage or pollution. The vessel name, IMO number, crew count and nationalities, assailants, motive and piracy attribution remain unknown. JMIC says southeast while UKMTO says southwest; the exact coordinate is preserved.

Open record
EUNAVFOR ATALANTA operational case update

Four piracy cases closed; ASANA remains under pirate control

Operation ATALANTA confirms HONOUR 25, SWARD, EUREKA and SIBU 1 closed and ASANA still open. It reports SWARD safely arrived in Mombasa; EUREKA's crew later flew from Mogadishu to their respective countries of origin; and ASANA remains under pirate-action-group control inside Somali territorial waters. ATALANTA also confirms the Puntland recoveries, five HONOUR 25 fatalities and all SIBU 1 crew safe. Its two-injured HONOUR 25 figure conflicts with four injured reported by Puntland Information Ministry/Reuters and Pakistan's Foreign Office, and with ICC IMB's five-injured attribution to Puntland authorities. The complete injury count remains unresolved. ATALANTA's up-to-21 SIBU 1 arrests do not resolve other custody totals or the later reported escape. Exact travel dates, individual medical findings and current ASANA coordinates remain unpublished.

Open record
Official multinational training-command update

CMF headquarters assumes command of training-focused CTF 154

Combined Maritime Forces reports that its headquarters assumed command of CTF 154 from the Indian Navy at a 14 October ceremony. During the India-led tenure beginning 11 February, CTF 154 trained more than 1,100 people from 39 countries, delivered more than 7,800 professional-development hours and held more than 20 specialist exchanges and engagements. This is a capacity-building command handover: CMF separately identifies CTF 151 as the regional counter-piracy lead, and the release announces no additional patrol assets, coverage or response availability. CMF does not identify a Seychelles role in the handover.

Open record
Official IMB January–September statistics and casualty account

IMB records eight Somali-attributed vessel hijackings; HONOUR 25 injury count conflicts

The ICC International Maritime Bureau reports 51 piracy and armed-robbery incidents worldwide in January–September 2026, the lowest nine-month total since 1992: 36 vessels boarded, eight hijacked, four fired upon and three attempted boardings. IMB attributes eight vessel hijackings to Somali pirates and says Somali piracy accounted for 94% of all crew taken hostage globally. Its public summary does not provide a case-by-case Somali table. The Observatory therefore preserves its separate six-merchant-vessel seizure denominator and does not create two unnamed ledger records; the difference may reflect dhows, fishing vessels, reporting geography or classification, but the source does not supply enough detail to reconcile those possibilities. IMB also attributes five HONOUR 25 injuries to Puntland authorities. That conflicts with ATALANTA's two-injured account and the four injured reported by Puntland Information Ministry/Reuters and Pakistan's Foreign Office; IMB does not identify the fifth person or its underlying Puntland source. The injury total remains unresolved.

Open record
Official multinational counter-piracy capacity update

CMF convenes inaugural SPAR exchange on piracy and armed robbery

Combined Maritime Forces reports that India-led CTF 154 brought together 135 participants from 25 countries and 19 organisations for the inaugural Subject Matter Expert Exchange on Piracy and Armed Robbery on 5–6 October. Sessions covered recent operations, information-sharing, maritime law enforcement, evidence and prosecution, port response and surveillance technology; CMF says feedback will inform future CTF 154 training and engagement. The release is dated 14 October but gives no publication time, participant list, agreed action plan, funding, delivery timetable, new asset allocation or patrol-coverage change. It therefore does not establish Seychelles participation or a current operational capability increase.

Open record
JMIC operational clarification / qualified assessment

Bab al-Mandab warning: JMIC says activity was likely fishermen warning over close approach

JMIC Update 104 records NAVAREA IX warning 363/26 at 12°58′N, 43°12′E but says the activity was likely local fishermen firing shots in the air to warn of a small closest point of approach. JMIC's wording is explicitly qualified, and it continues to advise a sharp lookout and prompt reporting. ICC IMB incident 053-26 separately records a container vessel fired upon by suspected pirates at 05:50 UTC at 12°58.77′N, 43°12.54′E; MSCIO reports damage and all crew safe. The IMB point is less than one nautical mile from the warning coordinate, but no authority cross-references the products and the interpretations conflict. The warning therefore remains a separate excluded record rather than a confirmed duplicate.

Open record
EUNAVFOR ATALANTA force-posture update

Portugal assumes ATALANTA force command; SANTA MARÍA becomes flagship

Operation ATALANTA reports that Portuguese Commodore José João Rodrigues Pedra assumed command of its 54th Force Headquarters rotation on 10 October, succeeding Spanish Rear Admiral Francisco Javier Vázquez Sanz. The Spanish frigate ESPS SANTA MARÍA is the new flagship and hosts the forward tactical headquarters. The announcement confirms command continuity but gives no complete force composition, patrol-area change, coverage measure or new response-time commitment; current naval coverage therefore remains unknown.

Open record
MSCIO–ATALANTA operational attack report

Bab el-Mandeb: gunfire damages container vessel; crew safe

MSCIO–ATALANTA's weekly report records Alert 132/26: on 7 October, two individuals aboard a fishing boat reportedly opened fire on a container vessel in the Bab el-Mandeb, damaging the starboard bridge-wing porthole and lifeboat; all crew were safe. ICC IMB incident 053-26 reports a likely common event at 05:50 UTC at 12°58.77′N, 43°12.54′E and says the alarm, citadel, increased speed, evasive manoeuvres and armed-team return fire aborted the approach. Vessel name, flag and crew count remain unpublished. The IMB–MSCIO linkage is high-confidence but inferential.

Open record
Primary national-authority crew-welfare update

HONOUR 25: two Indonesian crew reach home regions; one receives hospital care

Indonesia's migrant-worker protection ministry reports that two of the four returned HONOUR 25 crew reached Makassar at about 17:45 WITA on 7 October and were accompanied home to their families. It also reports that one of the other two required hospital treatment after reaching Indonesia. The Indonesian Foreign Ministry had confirmed all four arrived at Soekarno-Hatta Airport on 6 October and were transferred to family representatives for onward return. The official sources do not publish the hospitalised crew member's diagnosis, treatment, current condition or discharge status, or confirm completed onward travel for the fourth crew member.

Open record
Corroborated navigational-warning correction / classification pending

Bab al-Mandab: parallel warnings carry corrected piracy position

NAVAREA IX warning 363/26, issued at 19:00 UTC on 7 October, reports piracy activity at 12°58′N, 43°12′E and cancels warning 361/26, which had reported a different Gulf of Aden coordinate. HYDROPAC warning 2914/26 independently carries the corrected position. ICC IMB incident 053-26 now reports a container-vessel attack at 05:50 UTC at 12°58.77′N, 43°12.54′E, less than one nautical mile away. However, no authority explicitly cross-references the products and JMIC later assessed the warning activity as likely fishermen firing into the air over a close approach. The warning and attack therefore remain separate records with the conflicting interpretations preserved.

Open record
Corroborated crew-repatriation completion

HONOUR 25: final three Pakistani crew reach Karachi

Geo News and ARY News report that the final three Pakistani HONOUR 25 crew arrived at Karachi's Jinnah International Airport on 7 October. Dawn's updated report fixes their arrival at 16:40 PKT (11:40 UTC) aboard an Ethiopian Airways flight from Addis Ababa, attributing the detail to the Ansar Burney Trust's vice chairperson; Geo reports that they were medically examined at the airport. Pakistan's Deputy Prime Minister and Foreign Minister had earlier reported them en route. The exact flight number, individual medical findings and the return status of any other surviving crew are not published.

Open record
Primary national-authority onward-repatriation update

HONOUR 25: final Pakistani crew en route to Karachi

Pakistan's Deputy Prime Minister and Foreign Minister reports that the final three Pakistani HONOUR 25 crew are en route from Addis Ababa to Karachi for reunion with their families on 7 October. Associated Press of Pakistan, Express Tribune and Dawn publish the statement. The wording does not establish an actual take-off time or flight identity, and completed Karachi arrival remains unconfirmed. Individual medical findings and the return status of any other surviving crew are also unpublished.

Open record
MSCIO–ATALANTA operational closure

EUREKA: incident formally classified closed

MSCIO Alert 41/26 states that Operation ATALANTA has confirmed through different sources that EUREKA is no longer under pirate control and formally classifies the incident closed. The page is dated 6 October at 14:46, with timezone unstated. This operational closure corroborates the already recorded 29 September recovery; it does not add a recovery time or coordinate, vessel or cargo condition, individual medical findings, the four Indian crew members' repatriation status, or ransom information.

Open record
Corroborated national crew-repatriation update

HONOUR 25: four Indonesian crew return home

ANTARA reports from Soekarno-Hatta Airport that four Indonesian HONOUR 25 crew members, including the vessel's master, arrived in Indonesia on 6 October at approximately 18:42 WIB. Indonesian ministers received them, and the government says medical and psychological care will continue. AFP independently witnessed the arrival. Individual medical findings, the final three Pakistani crew's planned 7 October Karachi journey and the return status of any other surviving crew remain unresolved.

Open record
Corroborated crew-repatriation update

EUREKA: eight Egyptian crew return to Cairo

Ahram Online reports that all eight Egyptian EUREKA seafarers reached Cairo from Mogadishu late on 4 October and reunited with their families. The Egyptian Foreign Ministry had confirmed their reception and accommodation in Mogadishu on 3 October after identifying the eight-person EUREKA group in its 30 September release statement. Exact flight and landing time, individual medical findings and the four Indian crew members' repatriation remain unpublished. No ransom payment is confirmed.

Open record
Primary national-authority crew-welfare update

HONOUR 25: three remaining Pakistani crew reach Addis Ababa

Pakistan's Deputy Prime Minister and Foreign Minister reports that the three Pakistani crew who had remained aboard HONOUR 25 were successfully removed and flown to Addis Ababa with a Pakistan Embassy team. He thanked Somalia and EUNAVFOR Operation ATALANTA for assistance and said ATALANTA had been in the vicinity; ATALANTA has not yet published its own account. Onward Karachi travel is expected on 7 October and is not complete. Exact transfer times, the captain's separate identity and status, individual medical findings and non-Pakistani survivor repatriation remain unpublished.

Open record
Corroborated crew-welfare and repatriation update

HONOUR 25: four injured crew and three remains arrive in Karachi

Aaj English TV and HUM News report that four injured Pakistani crew members and the remains of three deceased Pakistani crew members arrived at Karachi's Jinnah International Airport aboard Ethiopian Airlines flight ET-694. Aaj's report was published at 19:39 PKT; neither report states the exact landing time or individual medical findings. The status of the other surviving crew remains unresolved.

Open record
Official broadcaster / Foreign Office welfare update

HONOUR 25: four injured crew and three remains depart Addis Ababa

Radio Pakistan reports that four injured Pakistani crew members and the remains of three deceased Pakistani crew members departed Addis Ababa for Karachi aboard Ethiopian Airlines flight ET-694. Dawn independently reports the same departure from Pakistan's Foreign Office account. Radio Pakistan also states that the flight was scheduled to land at 16:40 PKT; the landing was still prospective at the time of that update and was confirmed later on 4 October. Exact departure and publication times, individual medical findings and the status of the other surviving crew remain unresolved.

Open record
Primary national-authority consular welfare update

EUREKA Egyptians received in Mogadishu; Cairo return pending

Egypt's Foreign Ministry confirms reception and embassy accommodation in Mogadishu. The group's eight/EUREKA identity is established by its 30 September statement. Arrival was completed by the 3 October publication; exact event date/time and Cairo arrival are unspecified. The four Indian crew's repatriation remains unconfirmed.

Open record
Official broadcaster repatriation update

HONOUR 25: remains reached Addis Ababa; Karachi transit pending

Radio Pakistan confirms the three Pakistani remains reached Addis Ababa pending onward clearance. The report is dated 3 October; exact event/publication times and completed Karachi arrival are unspecified. No completed survivor return is confirmed.

Open record
Official regional-cooperation record

IOC and AP-IOC formalise parliamentary cooperation after maritime-security seminar

The Indian Ocean Commission reports that 27 parliamentarians and national-assembly officials attended a regional maritime-security seminar and the AP-IOC plenary in Mauritius from 30 September to 2 October. The IOC and AP-IOC signed a memorandum formalising their cooperation on 2 October. The record establishes institutional cooperation; it does not announce a counter-piracy deployment, operational task force, extra patrol coverage or measured deterrent effect.

Open record
Primary national-government bereaved-family support

Pakistan announces support for families of three HONOUR 25 fatalities

Pakistan's Prime Minister announced PKR 12.5 million for each of the three bereaved Pakistani families, plus a house and free education and healthcare for the deceased seafarers' children. He also directed the Foreign Ministry and embassy to expedite repatriation of the remains, maintain contact with the families, support treatment for the injured and pursue the safe return of the remaining Pakistani personnel. The package is announced; payment, housing delivery and repatriation completion are not confirmed.

Open record
IMO authoritative welfare aggregate

IMO confirms 44 freed; 22 remain captive aboard ASANA

The International Maritime Organization reports that 44 seafarers were freed from HONOUR 25, SEAMULL/SIBU 1 and EUREKA, while 22 remain captive aboard ASANA. This resolves the current aggregate after the three September recoveries. It does not resolve the disputed HONOUR 25 fatality chronology, individual medical findings, completed repatriation, current vessel positions or enforcement-custody outcomes.

Open record
MSCIO–ATALANTA operational corroboration / map evidence

ATALANTA corroborates vessel outcomes; SIBU 1 hijacking fix now reported

MSCIO’s weekly report for 25 September–2 October confirms the releases of HONOUR 25, SWARD, LUTUF and SIBU 1. Its tables record HONOUR 25 released on 29 September, five crew dead and others injured; EUREKA abandoned at Comanche Beach on 29 September with all crew safe ashore; and SIBU 1 released on 25 September with crew safe. ASANA remains its sole active merchant case. The SIBU 1 table supplies the 20 August 06:00 UTC hijacking fix of 14°41′N, 51°27′E; the map uses that historical reported position. Exact recovery coordinates, casualty chronology, individual medical findings, custody outcomes and completed repatriation remain unresolved. The report also gives a conflicting LUTUF locality, Maraya in Eyl district rather than UKMTO’s Mareeyo; no new exact location is inferred. Publication time is unconfirmed. Its mapped substantial Gulf of Aden/coastal corridor and moderate outer-basin areas must not be collapsed into JMIC’s broad labels. Maintain heightened vigilance, BMP-MS and immediate reporting to MSCIO/UKMTO; the report specifically highlights the area within 150 NM of the Somali coast between Mogadishu and Hafun.

Open record
Attributed national-authority repatriation update

HONOUR 25: four Pakistani survivors scheduled to return on 3 October

Foreign Minister Ishaq Dar said on 2 October that four Pakistani survivors had been safely retrieved and were scheduled to arrive in Karachi on 3 October. Three Pakistani remains were being repatriated; three Pakistani crew remained aboard with the captain, with return coordination continuing. Anadolu and Express Tribune corroborate the statement; direct primary-post retrieval was unavailable. The aboard account differs from the 1 October general survivor-transfer account, and any subsequent return aboard is unspecified. This is a planned return, not completed repatriation. Exact retrieval and publication times, current vessel position and individual medical findings are not supplied.

Open record
JMIC operational-authority confirmation

JMIC confirms both 29 September recoveries; ASANA remains the sole active hijacking

JMIC Update 101, dated 1 October and available by 2 October, with an information cut-off of 15:00 UTC on 1 October, confirms that Puntland Maritime Police Forces recovered HONOUR 25 and EUREKA on 29 September. It reports five HONOUR 25 crew casualties and all EUREKA crew safe, and lists ASANA as the sole merchant vessel still hijacked. JMIC does not resolve when the HONOUR 25 deaths occurred, identify the casualties, address injuries or arrests, or provide exact recovery coordinates. Gulf of Aden threat remains substantial; Somali coast and basin threat remains moderate.

Open record
Primary national-authority welfare update

HONOUR 25 survivors transferred to Garowe; treatment and return arrangements continue

Pakistan's Foreign Office briefing published on 1 October confirms surviving crew safely transferred from Bandar Beyla to Garowe, where the injured are receiving treatment. It confirms four injured, including three Pakistanis; the Trust's earlier all-Pakistani injury account remains a conflicting record. Repatriation is pending. The briefing describes deaths during recovery, whereas PMPF says before the operation; the sequence is unresolved. Precise transfer time, briefing publication time and individual medical findings are not supplied.

Open record
National-authority welfare and repatriation update

HONOUR 25 survivors ashore; injured receiving hospital care

Pakistan's Foreign Office confirmed on 30 September that HONOUR 25's injured crew had been taken to a nearby hospital and were receiving medical care, while surviving crew members had been brought safely ashore at Bandar Beyla. Pakistani officials from the embassy in Djibouti were proceeding there to assist their nationals and support medical care, the return of surviving Pakistani crew and transport of the deceased. The statement establishes the survivors' basic welfare at that time but does not provide individual medical findings or a completed repatriation date. The UAE Foreign Ministry separately condemned the killing and wounding on 1 October and called for stronger regional and international maritime-security cooperation.

Open record
PMPF operational clarification / custody correction

PMPF details EUREKA recovery; HONOUR 25 arrest count revised

PMPF's late-29 September statement, reported by Reuters and AP on 30 September, says EUREKA's hijackers grounded and abandoned the tanker, then fled ashore and inland as Puntland forces approached. The 12 crew disembarked and were subsequently confirmed safe. For HONOUR 25, PMPF's initial report of 21 apprehensions was revised to 16; AP reports that at least 11 other suspected pirates escaped the operation and remained at large. This is distinct from the earlier SIBU 1 detainee escape during road transfer. JMIC Update 101 has since confirmed both 29 September recoveries, five HONOUR 25 crew casualties and all EUREKA crew safe. The exact EUREKA recovery time and coordinate, vessel and cargo condition, individual medical findings and repatriation completion remain unpublished. MSCIO–ATALANTA’s report for 25 September–2 October now corroborates EUREKA’s abandonment on 29 September and all crew safe ashore. No ransom payment is confirmed.

Open record
National-authority crew confirmation / vessel release

EUREKA crew released; ASANA is sole vessel still reported held

MT EUREKA was released on 29 September after being held since 2 May. JMIC Update 101 now confirms the recovery and reports all crew safe. Egypt's Foreign Ministry confirmed on 30 September that all eight Egyptian sailors were freed and instructed its embassy in Mogadishu to receive them, check their welfare and arrange their return. India's High Commission in Nairobi separately reported that the four Indian seafarers aboard EUREKA were safe. PMPF says the hijackers grounded and abandoned the tanker, then fled ashore and inland as its forces approached. The established crew total remains 12; one secondary account's reference to 22 is not adopted. The exact recovery time and coordinate, vessel and cargo condition, individual medical findings and repatriation completion remain unpublished. MSCIO–ATALANTA’s report for 25 September–2 October now corroborates EUREKA’s abandonment on 29 September and all crew safe ashore. No ransom payment is confirmed.

Open record
Regional operational-authority clarification / conflicting counts

PMPF fixes HONOUR 25 recovery area; arrest count revised

A Puntland Maritime Police Force statement places the 29 September HONOUR 25 operation off Dharin-Bar in Bandar Beyla district and says the vessel is safe under Puntland control. JMIC Update 101 now confirms the recovery and five crew casualties but does not resolve their timing or address arrests. PMPF initially reported 21 suspected pirates apprehended but later revised the figure to 16; AP reports at least 11 other suspects escaped the operation and remained at large. PMPF says the five crew deaths occurred before its operation, while surviving crew accounts relayed by the Ansar Burney Trust say pirates opened fire as forces closed in. Pakistan's Foreign Office later reported the surviving crew safely ashore and the injured receiving hospital care. Exact operation timing, coordinates and individual medical findings remain unpublished; MSCIO–ATALANTA’s report for 25 September–2 October now confirms the 29 September release, five crew dead and others injured; chronology and custody remain unresolved.

Open record
Official Seychelles–ATALANTA exercise and coordination record

Seychelles and ATALANTA complete ALDABRA V phase 2

Operation ATALANTA's September newsletter records that ATALANTA and the Seychelles Armed Forces conducted ALDABRA V phase 2 in Seychelles from 26 to 29 September. The exercise used a real-life piracy scenario and brought together assets and special-operations teams from both forces to practise tactics, techniques and procedures introduced during phase 1. The newsletter also records a 29 September Port Victoria meeting between the ATALANTA Force Commander and Seychelles Chief of Defence Forces, and states that the 54th SHADE Indian Ocean is scheduled for 25–26 November in Port Victoria. The source gives no exact newsletter publication date or time, participant or asset list, readiness metric, patrol-coverage change or measured operational effect; SHADE remains scheduled rather than completed.

Open record
Fatal crew outcome / regional-government recovery

Puntland recovers HONOUR 25; five crew killed

Puntland's Information Ministry announced on 29 September that security forces recovered the Palau-flagged petroleum-products tanker HONOUR 25 and captured 16 alleged pirates. It said the pirates killed five of the 17 crew before the operation began—three Pakistanis, one Myanmar national and one Indian—and injured four, described as three Pakistanis and one Indian. JMIC Update 101 now confirms the recovery and five crew casualties but does not identify them, address injuries or arrests, or resolve when the deaths occurred. The Ansar Burney Trust separately confirmed the five fatalities but described all four injured as Pakistanis, leaving the injury-nationality breakdown unresolved. Pakistan's Foreign Office later reported the surviving crew safely ashore at Bandar Beyla and the injured receiving hospital care. Exact recovery timing and coordinates, individual medical findings and detainee arrangements remain unpublished; MSCIO–ATALANTA’s report for 25 September–2 October now confirms the 29 September release, five crew dead and others injured; chronology and custody remain unresolved.

Open record
Crew-welfare escalation / corroborated report

HONOUR 25 master reports armed death threats; families lose contact

Arab News Pakistan reported on 27 September that HONOUR 25's master sent a message on 25 September saying pirates repeatedly threatened the crew with firearms and warned they would kill them if a military operation targeted the vessel. Families of the 10 Pakistani seafarers subsequently reported losing contact. The Ansar Burney Trust said all 17 crew were alive and no serious illness was known at that last contact. This entry preserves the pre-recovery warning; Puntland's 29 September announcement now supersedes its welfare snapshot with a reported five fatalities, four injuries and vessel recovery. No ransom agreement or payment has been confirmed.

Open record
JMIC operational-authority confirmation

JMIC confirms SIBU 1 recovery and three-vessel active list

JMIC Update 100, issued on 27 September with an information cut-off of 15:00 UTC, independently confirms that Puntland forces recovered MT SEAMULL (also known as SIBU 1) on 25 September and that the crew was reported safe. It lists HONOUR 25, EUREKA and ASANA as the three merchant vessels still hijacked, reports no new confirmed attack or disruption during the preceding 72 hours, and keeps the Gulf of Aden threat substantial and the Somali coast and basin threat moderate. JMIC labels SIBU 1 Eritrea-flagged, while Reuters removed a reported flag state because the registry could not be verified; the Observatory therefore preserves the flag as unresolved. JMIC gives no current positions, revised captive total, individual medical assessment or new HONOUR 25 welfare information.

Open record
Custody failure / attributed security report

AFP reports 28 SIBU 1 detainees escaped during transfer

AFP reported on 27 September, citing four local security sources, that 28 of the 41 suspected pirates escaped during a road transfer from Garacad to Garowe on the night of 25 September. The sources said the transport vehicle suffered a burst tyre and its door was unlocked; later reporting says 13 were recaptured and one escapee was fatally shot. Puntland has not publicly confirmed the escape, the number still at large, or suspicions that police facilitated it. Those allegations remain unproven, and the original arrest and casualty totals remain disputed.

Open record
PMPF detention update / conflicting counts

Later PMPF statement reports 41 detained after SIBU 1 recovery

Dawan Africa reports that a later written Puntland Maritime Police Force statement put 41 suspected pirates in custody, superseding Puntland Television's initial report of 15 arrests. The statement also reports one alleged pirate killed and five wounded. This remains an attributed PMPF claim: AFP reported one killed, four wounded, 15 detained and one police officer injured, while EFE's PMPF-sourced account reported no casualties and did not give a detainee total. The exact arrest and casualty figures therefore remain unresolved; the vessel and all 20 crew remain reported safe.

Open record
Status integrity repair / attributed movement

SIBU 1 flag withdrawn; officials report three active cases moved toward Hobyo

Reuters corrected its 25 September report to remove SIBU 1's flag state because it was unverified; the incident record now treats the current flag as unresolved. Separately, Puntland officials told AFP that HONOUR 25, EUREKA and ASANA had moved south toward Hobyo in Galmudug. No JMIC, UKMTO or ATALANTA publication has yet confirmed that movement or supplied current positions, so the Observatory records it as an attributed directional update rather than an exact location.

Open record
Regional operational-authority cross-check

PMPF account fixes SIBU 1 recovery time; casualty reports conflict

PMPF commander Colonel Mohamed Jama told EFE that the 48-hour operation ended at 06:30 UTC on 25 September near Garacad, with SIBU 1 / SEAMULL, its 20-person crew and cargo secured and all alleged pirates aboard detained. EFE reports no casualties on either side. AFP separately reports 15 detainees, one alleged pirate killed, four wounded and one police officer injured; a later written PMPF statement reported by Dawan Africa puts 41 suspected pirates in custody, one killed and five wounded. The casualty outcome and detainee count remain unresolved. EFE gives the crew as 16 Indian, two Syrian, one Iraqi and one Sudanese; AP's earlier account listed one Syrian and left one nationality unpublished. Three merchant vessels remain reported held: HONOUR 25, EUREKA and ASANA. JMIC Update 099 predates the recovery.

Open record
CMF counter-piracy readiness

CTF 151 rehearses Gulf of Aden incident response

CMF’s 25 September release says Republic of Korea-led CTF 151 recently held a command-post exercise in Bahrain. Its 16 September dateline does not establish the exact exercise date. Multinational staff rehearsed coordinating ships, aircraft, regional authorities, maritime-security partners and medical support during boarding and suspicious-skiff scenarios, then worked through evidence seizure, command approval and legal considerations. CMF says CTF 151 will continue training with regional partners; the release does not announce additional ships, aircraft or patrol coverage.

Open record
MSCIO / JMIC cross-check

Official sources differ on pursuit time; crew reported safe

The incident occurred on 17 September. MSCIO Alert 111/26, issued that day, places the pursuit at approximately 13:59 UTC and reports the tanker and crew safe, with Operation ATALANTA investigating. JMIC Update 098, published on 20 September, records the pursuit at 14:53 UTC at 13°07′N, 46°18′E, reported as 75 NM east of Aden. JMIC says the vessel refused to stop and the master reported all well at 16:08 UTC, after which further contact could not be established. The 54-minute timing difference is unresolved. Both authorities classify the event as suspicious activity, not a completed attack or boarding. The vessel's name, flag and crew count were not published. Four merchant vessels remain hijacked; Gulf of Aden threat remains substantial and Somali coast and basin threat remains moderate.

Open record
IMO port-security governance update

Bosaso agencies draft port-security committee framework

IMO reports that its EU-funded Red Sea Project convened twenty representatives of Puntland port, government, customs, police and maritime-security bodies in Bosaso from 14 to 17 September. The workshop addressed ISPS Code and SOLAS XI-2 implementation, risk-based security planning, information-sharing, incident reporting and coordinated response. Participants developed draft terms of reference and an indicative roadmap for a proposed multi-agency Port Security Advisory Committee. This is a substantive institutional-planning outcome, not confirmation that the committee has been formally adopted, funded or implemented; it establishes no new patrol, response asset, coverage measure, readiness metric or demonstrated security effect.

Open record
JMIC operational assessment

Monsoon restrictions begin to lift; pirate capability persists

JMIC Update 097, issued on 17 September with an information cut-off of 15:00 UTC, reports no confirmed piracy attack or disruption during the preceding 96 hours and retains four hijacked merchant vessels: HONOUR 25, EUREKA, ASANA and SEAMULL/SIBU 1. The Gulf of Aden threat remains substantial and the Somali coast and basin threat remains moderate. JMIC assesses that southwest-monsoon restrictions are beginning to ease and warns that pirate action groups retain the capability to board and divert merchant vessels along the Somali coast, IRTC approaches and adjacent Gulf of Aden lanes. It gives no new crew-welfare, release, ransom or aggregate-captive figure.

Open record
Operational-authority confirmation

JMIC confirms SWARD released on 11 September

JMIC Update 096, issued on 13 September with an information cut-off of 15:00 UTC, confirms that the Saint Kitts and Nevis-flagged general cargo ship was released on 11 September and is free of pirates. JMIC reports the crew well and says a naval welfare check remained pending. It lists four merchant vessels still hijacked and leaves the Gulf of Aden threat substantial and the Somali coast and basin threat moderate. JMIC gives no crew number or release mechanism, so the 15-versus-17 count discrepancy and Puntland sources' ransom claim remain unresolved.

Open record
Reported vessel and crew release

SWARD and its crew reported released near Garacad

AFP reporting published on 13 September, citing Puntland security sources and authorities, says the Saint Kitts and Nevis-flagged MV SWARD was released near Garacad with its crew still aboard. Reports place the release on either Friday 11 or Saturday 12 September. AFP gives 17 crew, while ATALANTA's earlier case record gave up to 15; the discrepancy is unresolved and no individual welfare assessment is public. Puntland sources say a ransom was paid, but no amount or independently verifiable payment evidence has been disclosed. Four vessels remain reported held; no revised authoritative aggregate captive-seafarer figure was available at AFP's publication time.

Open record
CMF response confirmation

CTF 151 details multi-agency GLAMOR response

The incident occurred on 10 September; Combined Maritime Forces published its account on 11 September. Republic of Korea-led CTF 151 says it directed Japanese maritime patrol aircraft JN41 to intervene within two hours of the initial report and coordinated information and response activity with ATALANTA, the Indian Navy and regional maritime centres. The master and company security officer later confirmed the vessel clear, all crew safe and accounted for, and GLAMOR resumed its planned transit. CMF did not publish the crew number.

Open record
Piracy incident resolved

GLAMOR boarding ends without a seventh active hijacking

The incident occurred on 10 September. UKMTO's initial warning records a 09:00 UTC report of an unidentified skiff approaching a cargo vessel 98 NM southwest of Al Mukalla. JMIC later records the approach and boarding at 10:00 UTC, leaving the exact sequence unresolved. ATALANTA, publishing at 14:19 on 11 September, identifies the Saint Vincent and the Grenadines-flagged MV GLAMOR, a six-person pirate action group and a location 38 NM southwest of Balhaf. The crew stopped the vessel, shut down its systems and entered the citadel. ATALANTA redirected assets and coordinated a Japanese reconnaissance-aircraft show of force through CMF; the pirates abandoned the vessel, which resumed transit. All crew were reported safe and well. The crew count was not published.

Open record
JMIC operational assessment

JMIC records GLAMOR boarding; five earlier vessels remain held

JMIC Update 095, with an information cut-off of 15:00 UTC on 10 September, records GLAMOR as a Gulf of Aden suspicious-activity case and says the unauthorized personnel boarded but failed to seize control. It separately reports no confirmed attack or disruption on the Somali coast or basin and retains the five-vessel captivity list: HONOUR 25, SWARD, EUREKA, ASANA and SEAMULL/SIBU 1. The Gulf of Aden threat remains substantial and the Somali coast/basin threat moderate.

Open record
JMIC status confirmation

JMIC confirms LUTUF release and five vessels still held

JMIC Update 091, with an information cut-off of 15:00 UTC on 30 August, confirms that the Cameroon-flagged LUTUF (IMO 9109134) was released on 29 August after 12 days. It lists HONOUR 25, SWARD, EUREKA, ASANA and SEAMULL/SIBU 1 as the five merchant vessels still held. JMIC reports no new confirmed incident during the preceding 72 hours and does not attribute LUTUF's release to either military action or ransom. Gulf of Aden risk remains substantial and Somali coast/basin risk moderate.

Open record
Conflicting official accounts

Puntland disputes federal account of LUTUF's release

Puntland's Security Ministry confirms that LUTUF and its crew are free but denies that a Somali-Turkish rescue operation secured the release. It alleges that federal and Turkish actors facilitated a ransom payment. Puntland disclosed no amount or independently verifiable payment evidence; Somalia's federal government and Türkiye had not publicly answered the allegation at the source cut-off. Mogadishu's separate account attributes the release to sustained military pressure and claims four pirate boats were destroyed and 14 alleged pirates killed. The release is confirmed, but the mechanism, alleged ransom, casualties and attribution remain unresolved.

Open record
Verified vessel recovery

Somali and Turkish forces recover MV LUTUF

Somalia's Defence Ministry announced on 29 August that Somali and Turkish forces had recovered the Cameroon-flagged cargo vessel following a joint operation. AP published the announcement at 16:56 UTC and separately reported that a local elder said the vessel and crew were freed. The ministry did not provide the exact recovery time or an individual crew-welfare assessment. It also said four pirate boats were destroyed and 14 alleged pirates killed; those casualty and attribution claims have not been independently confirmed. Puntland previously described victims of earlier coastal strikes as civilians, and public reporting does not establish whether those strikes formed part of this operation.

Open record
JMIC operational assessment

Gulf of Aden threat remains substantial; Somali coast and basin moderate

JMIC Update 090 assesses a strong possibility of a maritime-security incident in Gulf of Aden coastal approaches, transit corridors and established small-craft areas. It says pirate action groups retain the ability to board and divert merchant vessels despite the southwest monsoon, while offshore skiff range remains constrained. The Somali coast and basin remain moderate because nearshore opportunism persists. JMIC reports no new piracy attack in the preceding 48 hours and lists the same six merchant vessels as held.

Open record
Coalition command update

Republic of Korea assumes command of CTF 151

CMF says Republic of Korea Navy Capt. Yoon Hyun-woo assumed command from Royal Navy Capt. Jason Eacock at a ceremony in Manama on 23 August; the release was published 25 August. During the UK command from February, CTF 151 coordinated 17 contributing units, conducted 69 intelligence, surveillance and reconnaissance patrols, and responded to 25 active piracy-related incidents. No new asset allocation, patrol boundary or incident outcome was announced.

Open record
Official threat assessment

IMO says more than 90 seafarers are captive across six vessels

Following the 20 August SEAMULL hijacking, the IMO Secretary-General described six vessels and more than 90 seafarers as held, demanded their immediate and unconditional release, and called for sustained international naval cooperation and DCoC-led regional action. The figure is an official aggregate lower bound; it does not resolve vessel-level count discrepancies or confirm any change in individual welfare status.

Open record
Evidence reconciliation

ATALANTA's aggregate and vessel-level crew figures do not reconcile

ATALANTA reports 67 people held across HONOUR 25, SWARD, EUREKA and ASANA, but its stated vessel figures—up to 17, up to 15, 12 and up to 22—sum to no more than 66. The Observatory preserves both official records and does not infer the unidentified difference.

Open record
Official crew response

Pakistan asks the IMO for urgent intervention on HONOUR 25

Pakistan says Deputy Prime Minister Ishaq Dar met IMO Secretary-General Arsenio Dominguez in London on 24 August, thanked him for supporting efforts to release the ten Pakistani seafarers aboard HONOUR 25 and called for urgent institutional intervention for all seafarers. The meeting is confirmed; no agreement, change in welfare status or release was announced.

Open record
Verified response update

Puntland says coastal security forces have been deployed

A Puntland Security Ministry statement dated 21 August says security agencies and coastal-district officials were activated against pirate groups. AP reported the deployment at 08:18 UTC on 22 August. The area, assets, tasking and operational effect remain undisclosed; other claims in the statement remain outside the verified layer.

Open record
Vessel verification

Official record strengthens the SIBU–SEAMULL identity chain

AP identifies SIBU 1 as managed by UAE-based Qatrat Alnada Almasi Ship Management, while vessel databases associate SIBU 1 with IMO 9204776. A U.S. Treasury record independently links that manager and IMO to SEAMULL and listed it as Palau-flagged in December 2025. Reuters removed a later reported flag state from its 25 September account because it was unverified, so the Observatory now leaves the current flag unresolved rather than carrying forward a registry claim.

Open record
Official crew update

India reports 22 Indian seafarers aboard SIBU and LUTUF safe

The High Commission of India in Kenya says 16 Indian seafarers are aboard MT SIBU and six aboard MV LUTUF. The welfare of the eight other reported crew members has not been separately confirmed by that statement.

Open record
UKMTO warning

Six armed persons seize a tanker and redirect it towards Somalia

UKMTO published its warning at 09:48 UTC and Update 001 at 10:12 UTC; its public documents do not give a separate event time. UKMTO places the incident 136 NM east of Al Mukalla, while later Indian reporting said about 30 NM off Yemen. The map follows UKMTO and marks the position approximate.

Open record
Assessment

Six held cases now span coastal, anchorage and offshore operating patterns

The SIBU seizure well east of Al Mukalla broadens the current geometry, while LUTUF's monsoon-season capture shows that near-coast opportunity persists.

Read assessment
UKMTO warning

Cargo vessel boarded by eight armed persons south of Mareero

The vessel was subsequently identified as the Cameroon-flagged LUTUF. Later Indian reporting puts the crew at 10 and reports its six Indian seafarers safe; four other welfare statuses remain unresolved.

Open record
Regional mechanism

DCoC states advance a proposed regional counter-piracy task force

DCoC national focal points endorsed development of a Combined DCoC Counter-Piracy Task Force under Working Group 3. The proposal includes coastal-State sea-riders and a legal-transfer framework, but it is not yet operational: assets, geography, resources and final adoption remain unresolved.

Open record
Official regional information-sharing update

DCoC/JA states validate a draft information-sharing framework

IMO reports that DCoC/JA delegates meeting in Dar es Salaam from 15 to 17 September validated a draft Framework of Cooperation and Coordination and an interoperability gap analysis for national maritime information-sharing centres, the Seychelles-based RCOC and Madagascar-based RMIFC. Seychelles and Somalia were among the participating states. The documents are scheduled for review and possible adoption at the ninth DCoC/JA High-Level Meeting in Antananarivo from 11 to 13 November; adoption, implementation, resources, operating procedures and any capability effect remain unresolved.

Open record
Operational data

ATALANTA records 177 pirate transfers and 145 convictions since 2009

At its 14 October snapshot, ATALANTA’s statistics page reported 2,518 WFP vessels protected and 3,311,078 tonnes of food or aid delivered to Somali ports under protection. The current 5 November statistics are recorded in the newer update above. These cumulative outputs do not establish current patrol coverage or quantify deterrence.

Open record
Situation update

Four vessels and 67 crew confirmed held near the northern Somali coast

HONOUR 25, SWARD, EUREKA and ASANA were reported anchored inside territorial waters and close to one another.

Open record
Official statistics

IMB records a concentrated Somali hostage threat despite low global totals

IMB recorded 38 global incidents and 67 crew taken hostage in the first half of 2026; Somali pirates accounted for 94% of those hostages. The reporting period ended before ASANA, LUTUF and SIBU and must not be treated as the current captivity total.

Open record

Source desk

Know what is known, estimated and still unconfirmed.

The observatory uses a source hierarchy. Operational alerts lead; official confirmations stabilise the record; intergovernmental and research sources provide legal, historical and structural context.

01

Primary competent operational authority · master's report

UKMTO Warning 206-26 · 16 November

Suspicious Activity at 03:30 UTC, 430 NM east of Socotra at 12°02′N 061°47′E. A tanker reported a possible mothership and skiff with four armed persons and a ladder. Publication date 16 Nov; precise publication time unstated. No confirmed piracy, boarding, crew welfare, perpetrator identity or link to the Hobyo fishing-vessel report is established.
02

Primary competent operational authority

MSCIO Alert 179/26 · armed robbery under investigation

Published 13 November 2026 at 14:34, displayed timezone unstated. Reports a fishing-vessel hijacking investigated by ATALANTA as armed robbery, latest reported point 0619N 04913E in Somali territorial waters, approx. 67 NM northeast of Hobyo, and an avoid-area/vigilance/reporting warning. Identity, crew, event clock, current control and outcome are unpublished.
03

Primary joint operational assessment

JMIC Update 114 · 15 November 2026

Information cut-off 15 November at 13:00 UTC, not publication time. Corroborates MSCIO 179/26; ASANA remains the sole held merchant vessel. Coastal seizure capability and possible offshore PAG range remain qualitative assessments, not confirmed use of the fishing vessel as a mothership. Threat categories unchanged; no replacement numerical sea-state forecast.
04

Primary intergovernmental cooperation record

IMO · expanded draft maritime-security lexicon, 9 Nov 2026

Workshop 27–30 October in Addis Ababa; confirms Seychelles, Somalia, RCOC and RMIFC participation. Draft finalised for High-Level Meeting consideration, not verified adoption or implementation. Exact publication time unstated.
05

Primary intergovernmental statistical and policy account

IMO Council 138 · regional aggregate, published 6 Nov 2026

Council met 2–6 November and noted 17 attempted or actual piracy and armed-robbery instances in the Western Indian Ocean and Gulf of Aden since the year's start. No case table or exact statistical cut-off supplied. This wider aggregate is not 17 hijackings and cannot be equated to the Observatory's unique cases, UKMTO piracy-related reports or IMB totals. No additional unnamed incidents or numerical model changes are inferred.
06

Primary industry piracy-reporting centre

ICC IMB PRC · incident 057-26

Historical fishing-vessel hijacking and crew-rescue report; publication date unstated. Exact point preserved; vessel identity and possible AZINI overlap unresolved. Excluded from unique-event numerical counts pending reconciliation.
07

Primary competent multinational authority

CMF / CTF 154 · Mombasa regional strategy workshop, published 12 Nov

Workshop held 2–6 November; article dateline 10 November, publication 12 November, exact time unstated. Confirms risk-register output and vessel-registry proposals, not implementation or a new patrol. Does not establish Seychelles participation.
08

Competent national defence-authority accounts; named SDF interview carried by Seychelles News Agency

Seychelles–Russia boarding exercise · SDF spokesperson and Russian Defence Ministry

Completed exercise on 5 November, SNA publication 7 November at 10:10 with timezone unstated. Russian Defence Ministry corroborates completion at https://t.me/s/mod_russia_en?before=30475. Training is not present patrol coverage or measured operational capability.
09

Primary competent operational authority

MSCIO Alert 172/26 · 7 Nov 2026

Suspicious target/explosion in Bab el-Mandeb on 6 November at approximately 22:45 UTC. Exact reported coordinate retained; target identity, cause and piracy connection unknown. Displayed publication clock 19:47 has no stated timezone.
10

Primary multinational operational assessment

JMIC Update 113 · 12 Nov 2026

Information cut-off 12 November at 13:00 UTC, not exact publication time. Revised dated Somali Basin sea-state outlook and voyage-information warning; ASANA and regional threat categories unchanged. Qualitative context, not live weather or a calibrated piracy forecast.
11

Primary competent operational-authority contact register

UKMTO Contact Us · operational contacts checked 2 Nov

Lists UKMTO's primary 24/7 Operations Centre number +44 (0) 2392 222060, two 24/7 secondary numbers +44 (0) 7779 966976 and +44 (0) 7585 795608, and watchkeepers@ukmto.org. It also cross-lists MSCIO and ICC IMB reporting contacts. The page does not state when individual contact fields last changed; the 2 November date records the Observatory's verification, not source publication.
12

Primary industry piracy-reporting contact register

ICC IMB Piracy Reporting Centre · 24-hour contact checked 2 Nov

Lists the 24-hour anti-piracy helpline +60 3 2031 0014 and piracy@icc-ccs.org for reporting piracy, armed robbery and suspicious sightings. The page does not state when individual contact fields last changed; the 2 November date records the Observatory's verification, not source publication.
13

Primary official federal maritime-security governance statement, corroborated by the Somali National News Agency and independent reporting

Somali Ministry of Defence · Navy and Coast Guard command handover, 1 Nov

The Ministry reports that Colonel Mohamed Abdiqadir ‘Sharif’ formally took over as Commander of the Somali Navy and Coast Guard from Brigadier General Abdiwahab Abdullahi Omar on 1 November 2026. The Somali National News Agency and Shabelle Media Network corroborate the handover; Shabelle places the ceremony in Mogadishu. Exact publication times are unverified. The releases announce a leadership transition but no new patrol, asset, funding decision, operational plan, patrol boundary, coverage measure, response-time commitment or readiness effect. Current naval and coastal-policing coverage remains unknown.
14

Independent Somali reporting corroborating the official federal announcement

Shabelle Media Network · Navy and Coast Guard command handover, 1 Nov

Reports that the newly appointed commander formally assumed office in Mogadishu on 1 November 2026, succeeding Brigadier General Abdiwahab Abdullahi Omar. The report describes a command ceremony and headquarters inspection but publishes no implemented operational change, patrol coverage, new asset, funding or measured security effect.
15

Primary UN maritime-security capacity-building release

IMO · Bosaso port-security coordination workshop, 17 Sep

Reports that IMO's EU-funded Red Sea Project held a Port Security Inter-Agency Coordination Workshop in Bosaso, Puntland, from 14 to 17 September 2026. Twenty participants from Puntland government, port, customs, police and maritime-security bodies worked on ISPS Code and SOLAS XI-2 implementation, risk-based planning, information-sharing, incident reporting and coordinated response. Participants developed draft terms of reference and an indicative roadmap for a proposed multi-agency Port Security Advisory Committee. The release is dated 17 September 2026; exact publication time is unstated. It does not confirm formal adoption, funding or implementation of the proposed committee, a new patrol, response asset, coverage change, readiness metric or measured operational effect.
16

Primary official coastal-security cooperation release

EEAS / EUCAP Somalia · ATALANTA–Puntland cooperation, 27 Oct

Published 27 October 2026, exact time unstated. Records a 20 October meeting in Bossaso between EUCAP Somalia's Puntland field office, Operation ATALANTA's liaison officer in Somalia and senior Puntland State Police officials. The parties discussed enhanced information-sharing, liaison and operational cooperation against piracy and other illicit maritime activity; ATALANTA outlined its maritime operations and future engagement opportunities. The release gives no agreed workplan, funding, assets, patrol boundaries, coverage measure, response-time commitment, follow-up delivery or measured operational effect. It does not establish a new patrol, present naval coverage, a completed response or Seychelles participation.
17

Primary competent operational-authority overview

UKMTO Overview No. 14 · 6 Nov

Produced 6 November, reporting range through 4 November; exact publication time unstated. UKMTO’s 6 November Overview No. 14 says the Indian Navy recovered AZINI on 2 November, detained unauthorised persons aboard and rescued the original crew. Its warning summary reports 10–12 armed boarders, but it does not state how many people were detained or establish subsequent custody, transfer, release or prosecution. The overview table places record 190 at 09°54′N, 53°04′E on 30 October, while its narrative says 1 November. The official API instead gives 09°54′N, 53°03′E and 31 October; MSCIO reports hijacking on 29 October. These unresolved source differences do not change the historical markers or the confirmed duplicate treatment. UKMTO reports 44 piracy-related reports: 11 boardings/hijackings, five attacks and 28 suspicious-activity reports. This wider authority series is not a count of confirmed pirate attacks or the Observatory’s case index.
18

Primary joint operational weekly assessment

MSCIO–ATALANTA weekly report · 30 Oct–6 Nov

Report period 30 October–6 November; directory displays 6 November at 11:23, time zone unstated. Confirms ongoing ASANA monitoring and AZINI closure and reprises Alert 160/26. The MSCIO–ATALANTA weekly report dates the issue of AZINI Update 01 to 2 November, while the alert page displays 31 October at 09:24, timezone unstated. Neither source timestamps the position fix. No new captive count, welfare assessment or confirmed piracy link for the floating-object sighting in Bab el-Mandeb is provided.
19

Primary national defence release

Türkiye Ministry of National Defence · Somalia naval rotation, 5 Nov

Türkiye’s defence ministry said on 5 November that two frigates began a Somalia-bound rotation and maritime resupply mission on 30 October. Parliament had approved a two-year extension from 27 July 2026 of the wider Somalia security mandate, which includes counter-piracy. Arrival, transfer of duties, patrol coverage and any connection to a specific incident are not established.
20

Primary parliamentary record

Türkiye Grand National Assembly · Somalia mandate extension, 21 Jul

Records parliamentary approval on 21 July of a two-year extension effective 27 July 2026. Authority to support Somalia against piracy and other threats does not establish present patrol coverage.
21

Primary joint operational incident and threat assessment

JMIC Update 111 · 5 Nov

Information cut-off 5 November 2026 at 13:00 UTC; exact public release time unstated. Records the end date of NAVAREA IX warning 416/26 with no replacement identified, confirms ASANA still held and notes AZINI closure. Retains regional threat ratings. MSCIO Alert 168/26 concerns an unexplained floating object in Bab el-Mandeb, with no merchant-vessel attack or piracy link reported.
22

Primary competent operational-authority joint advisory

JMIC Update 110 · AZINI / UKMTO 190 linkage, 1 Nov

Dated 1 November 2026 with a 13:00 UTC information cut-off. JMIC explicitly groups MSCIO Alert 161/26 and UKMTO Warning 190-26 as the same AZINI fishing-vessel case and reports that MSCIO and UKMTO received accounts of a large fishing vessel boarded and taken by armed persons east-southeast of Socotra. The narrative says MSCIO reports AZINI hijacked by armed pirates and potentially usable as a mothership. JMIC retains a suspicious-activity label in its incident table, while UKMTO subsequently reclassified record 190 as a hijack; the temporal inconsistency is preserved. JMIC retains moderate threat on the Somali coast and basin and assesses that the case indicates possible pirate-action-group reach across the northern Somali Basin toward routes east and south of Socotra. This is a qualified outlook, not a live track, calibrated probability or confirmation of subsequent mothership use. Exact crew status, ransom or negotiation status, present position and current naval coverage remain unknown.
23

Primary competent operational-authority initial warning, subsequently reclassified

UKMTO Warning 190-26 · fishing-vessel boarding, 31 Oct

The initial Warning 190-26 reports that a large fishing vessel was boarded by unauthorised personnel and says authorities are concerned the activity will form part of a Pirate Action Group. It originally classified the report as suspicious activity, gave the source as verified and advised caution, BMP measures and reporting. UKMTO Update 001 subsequently reclassified incident 190 as a hijack, and JMIC Update 110 links it to MSCIO Alert 161/26's AZINI case. The PDF states 30 October 2026 at 14:19 UTC but prints no vessel name, flag, coordinate, crew detail or outcome; those conflicts remain unresolved.
24

Primary competent operational-authority structured incident record

UKMTO official incident API · record 190

The official API's Update 001 says UKMTO reclassified incident 190 as a hijack to reflect the incident information. It maps record 190 at 09°54′N, 53°03′E in the Indian Ocean Basin and labels the vessel type ‘Dhow’, but its incident field states 31 October 2026 at 18:48 UTC, conflicting with Warning 190-26's 30 October at 14:19 UTC and MSCIO/JMIC's approximately 09:00 UTC on 29 October for AZINI. The coordinate is a historical structured-record position, not a current track or necessarily the hijacking location. The API fields crewHeld: 0 and vesselUnderPirateControl: false were not used to infer release or crew safety; MSCIO supplies the liberation status and the later Indian Ministry of Defence report supplies the safe outcome for the 20 crew it describes.
25

Primary competent operational-authority suspicious-activity alert

MSCIO Alert 160/26 · armed-skiff approach, 30 Oct

Reports that at approximately 02:25 UTC on 30 October 2026, near 11°57.4′N, 45°04.5′E in the Gulf of Aden, two suspicious craft approached a merchant vessel. One greenish fast skiff carried four persons and reportedly had a mounted machine gun. It closed to approximately 300 metres astern, then aborted after the vessel's armed security team displayed their weapons. No shots or boarding attempt were reported, the vessel continued its voyage and Operation ATALANTA is investigating. The page displays 30 October at 09:10, timezone unstated. Vessel identity, flag, type, crew particulars and welfare, damage status, the second craft's details, piracy attribution and present positions are unpublished. No linkage to Alert 156/26, AZINI or another case is inferred.
26

Primary joint operational weekly assessment

MSCIO–ATALANTA weekly report · 23–30 Oct

The report folder displays creation on 30 October 2026 at 15:21, timezone unstated. It independently preserves MSCIO's own summary of Alert 160/26: two suspicious craft approached a merchant vessel in the Gulf of Aden; one fast skiff carried four persons and reportedly a mounted machine gun, closed to about 300 metres, then aborted after the armed security team displayed weapons. It reports no shots or boarding attempt and says the vessel continued its voyage. This is corroboration within the same operational authority chain, not an independent second-source account. The weekly report ends before Alert 161/26 and therefore does not update AZINI.
27

Primary national defence-authority reporting

Indian Ministry of Defence via DD India · AZINI rescue, 3 Nov

DD India published the Ministry of Defence report on 3 November 2026 at 09:51 IST. It says the Indian Navy, with Indian Air Force support, completed a more-than-48-hour operation on 2 November, secured AZINI and safely rescued all 20 crew members without casualties or injuries. It does not publish the precise completion time or interception coordinate, pirate number or identity, arrests or custody, vessel condition or destination, or ransom or negotiation detail. An earlier Associated Press account citing an unnamed Puntland Maritime Police Force officer said 23 people were aboard; no attributable Puntland release located resolves that discrepancy, so nationalities and any additional persons are not inferred.
28

Reputable wire report used only to preserve an unresolved conflict

Associated Press · earlier AZINI crew account, 1 Nov

Published 1 November 2026. Cites an unnamed Puntland Maritime Police Force officer who said 21 Iranian crew and two Somali security guards were aboard AZINI. This account is not treated as a competent-authority release and conflicts with the later Indian Ministry of Defence report that all 20 crew were rescued. It is retained to make the discrepancy explicit; the Observatory does not infer the manifest, nationalities or status of any additional persons.
29

Primary competent operational-authority piracy alert

MSCIO Alert 161/26 · AZINI hijacking, liberation and closure, 30 Oct–2 Nov

Reports that armed pirates hijacked the Iranian fishing vessel AZINI off northeastern Somalia at approximately 09:00 UTC on 29 October 2026. The initial alert gave a last reported position of 09°42′N, 53°55′E at 04:00 UTC on 30 October. Update 01 gave 09°47′N, 55°45′E without a fix time. Update 02 says Operation ATALANTA confirms that anti-piracy military forces liberated AZINI and closes the incident. The page displays 2 November 2026 at 20:52, timezone unstated. It does not publish the liberation date or time, location, participating force or forces, crew number, nationalities or welfare, casualties, arrests or custody, vessel condition or destination, or ransom or negotiation detail. Potential mothership use was a warning; no subsequent use was confirmed. Historical coordinates are not a current track, and no second competent-authority release was located at release preparation time.
30

Primary national flag-administration security guidance

Norwegian Maritime Authority · southern Red Sea, Bab el-Mandeb and northern Gulf of Aden, 30 Oct

Published 30 October 2026, exact time unstated. Keeps ISPS Security Level 3 in force in the Bab el-Mandeb Strait for Norwegian vessels; sets Level 2 in the southern Red Sea and northern Gulf of Aden; and extends the northern Red Sea Level 2 area to waters north of Yanbu. The authority cites continued missile, drone and small-boat exposure in Bab el-Mandeb and recommends BMP Maritime Security, vessel-specific planning, risk assessment, training and reporting to UKMTO and MSCIO. Level 3 is retained rather than newly imposed, and the stated material change is the northward Level 2 extension. This is flag-state guidance, not a JMIC regional threat reclassification, piracy incident or present naval-coverage measure. No effective hour, review date or boundary coordinates are published.
31

Primary national flag-administration security guidance

Norwegian Maritime Authority · Gulf of Aden and WIO security level, 29 Oct

Published 29 October 2026, exact time unstated. Extends ISPS Security Level 2 to the entire Gulf of Aden for Norwegian vessels and retains Level 2 in the western Arabian Sea, Somali waters and the western Indian Ocean out to 600 nautical miles from the Somali coast. Requires vessel-specific Ship Security Assessments and Plans and recommends BMP Maritime Security, drills, review of EUNAVFOR assessments through MSCIO, and reporting to UKMTO and MSCIO. This does not replace JMIC regional threat ratings or establish a new incident, patrol deployment, current position or present naval coverage. The page gives no effective hour, review date or map coordinates. Its unenumerated reference to vessels held by pirates is not used to change the Observatory's ASANA-only verified merchant-vessel count.
32

Primary joint operational incident and threat assessment

JMIC Update 109 · 29 Oct

Information cut-off 29 October 2026 at 13:00 UTC; the product is dated 29 October and its exact public release time is unstated. JMIC records UKMTO 184-26 as an advisory concerning multiple suspicious small-craft sightings near merchant vessels in the Gulf of Aden, describes suspected pirate-action-group activity and reports no damage. It reports no confirmed Gulf of Aden attack in the preceding 96 hours, retains substantial threat in the Gulf of Aden and moderate threat on the Somali coast and basin, and confirms ASANA as the sole merchant vessel still hijacked: a Tanzanian-flagged product/chemical tanker carrying oil products. It supplies no merchant-vessel identity, crew number or welfare update for the 28 October sightings, no current ASANA coordinate and no present naval-coverage measure.
33

Primary competent operational-authority alert

MSCIO Alert 156/26 · suspected pirate action group, 28 Oct

Reports a suspected pirate action group operating in the Gulf of Aden approximately at 12°42′N, 47°35′E. It describes a green-blue small craft with nine persons, two ladders and one hook travelling south at an estimated 10–18 knots and states that Operation ATALANTA is investigating. The page displays 28 October 2026 at 11:47, timezone unstated. It does not identify a merchant vessel, flag, crew or welfare status, give the observation time, report an attack or boarding, or establish the craft's current position or confirmed pirate attribution.
34

Primary official navigational warning

NAVAREA IX warning 416/26 · possible pirate action group, 28 Oct

Issued at 15:00 UTC on 28 October 2026, it reports a possible pirate action group approximately at 12°42′N, 47°35′E in the Gulf of Aden off Somalia and advises mariners to keep clear, exercise extreme caution and report incidents. Its 3 November cancellation time is an administrative validity limit, not an incident outcome. The warning does not identify a vessel, crew, attack, boarding or current craft position.
35

Primary competent operational-authority advisory, corroborated by a same-day wire report

UKMTO Advisory 184-26 · Gulf of Aden suspicious activity, 28 Oct

Records the incident at 10:30 UTC on 28 October, attributes the report to military authorities and labels the area Aden, Yemen. Reports several sightings of suspicious small craft near merchant vessels that may indicate pirate-action-group activity. One green-and-blue craft reportedly carried nine people, two ladders and a hook. Authorities are investigating and UKMTO advises caution and reporting. The PDF publishes no coordinate, merchant-vessel identities or flags, crew numbers or welfare, individual sighting sequence, weapons, approach distances, damage, outcome or confirmed attribution. The advisory does not confirm an attack, boarding, hijacking, mothership or connection to an existing case.
36

Primary competent operational-authority structured incident record

UKMTO official incident API · record 184

Publishes record 184 at 12°42′N, 47°35′E with a utcDateOfIncident field of 12:02 UTC and a record-creation timestamp of 12:04:47 UTC on 28 October. The 12:02 field conflicts with Advisory 184-26's 10:30 UTC incident time. The API does not explain whether the coordinate represents one sighting, all sightings or an administrative map position, and its creation timestamp is not treated as verified publication time.
37

Reputable wire corroboration quoting the competent operational authority

Anadolu · UKMTO warning corroboration, 28 Oct

Quotes UKMTO's 28 October public statement and reproduces the reported Gulf of Aden suspicious-activity warning and green-and-blue craft description. The article supplies no additional event time, coordinate, vessel identity, crew status or confirmed piracy outcome.
38

Primary competent operational-authority weekly incident and outcome summary

UKMTO Weekly Overview No. 12 · 23 Oct

Produced 23 October 2026 for the reporting period through 21 October. Identifies incident 176's vessel as a Bahamas-flagged LNG tanker of approximately 110,000 DWT, reports that it continued its voyage, and records no reported injuries, damage or pollution. The overview does not publish the vessel name, IMO number, crew count or nationalities and does not establish piracy attribution. Its southwest-of-Al-Mukalla wording remains in conflict with JMIC Update 106's southeast wording; the exact reported coordinate is unchanged.
39

Primary competent operational-authority communications advisory

MSCIO Advisory 10-2026 · false Yemeni Coast Guard emails, 22 Oct

Reports that several shipping companies received emails falsely claiming to originate from the Yemeni Coast Guard and requesting vessel movements, port calls and operational details, particularly information concerning Saudi Arabian ports. MSCIO identifies ycgyemen.sanaa@gmail.com and info@ycg-yemen.com as neither official nor verified Yemeni Coast Guard addresses and instructs operators not to reply or provide information, and to report further communications to MSCIO. The advisory does not establish the recipients, sender identity, intent, any disclosure, system compromise, a related piracy case or a new Yemeni reporting requirement.
40

Primary official multinational counter-piracy operation record

CMF / CTF 151 · Operation Tidal Wave concluded, 20 Oct

Reports that CTF 151 concluded a six-day operation in the Gulf of Aden and Indian Ocean involving 15 organisations from ten nations, coalition warships, maritime-patrol aircraft and regional coastguards. CMF describes day-and-night presence, warnings to merchant shipping, coordinated offshore patrols, inshore regional coverage and training. It says an Indian warship joined a focused operation for the first time, Kenya widened its patrol waters, and Seychelles aircraft and ships worked together farther east than before. The release gives no precise start date or times, complete participant or asset list, patrol boundaries, incident outcomes, current positions or quantitative coverage or deterrence measure.
41

Primary official multinational counter-piracy coordination record

CMF / CTF 151 · Djibouti partnership visit, 19 Oct

Reports that CTF 151 visited Djibouti from 8 to 13 October ahead of a focused Gulf of Aden counter-piracy operation. Talks with the Djibouti Navy and Coast Guard covered coastal surveillance, interdiction procedures and information-sharing; discussions with ATALANTA reaffirmed patrol coordination, information-sharing and mutual support; and meetings with Japanese and Spanish maritime-patrol-aircraft detachments addressed use of limited airborne surveillance assets, avoiding duplicated coverage and rapid information exchange. A tabletop exercise rehearsed a coalition piracy response. CMF does not disclose the operation date, participating assets, patrol area, coverage, current positions, measured readiness or operational effect, or Seychelles participation.
42

Primary joint operational threat and seasonal assessment

JMIC Update 108 · 25 Oct

Information cut-off 25 October 2026 at 13:00 UTC; the UKMTO archive lists an issue date of 25 October and a 17:40 time with timezone unstated. JMIC retains substantial threat in the Gulf of Aden and moderate threat on the Somali coast and basin. It records the southwest monsoon as withdrawn on 15 October, assesses residual opportunistic piracy risk in nearshore Somali waters and the Gulf of Aden, and says farther-offshore skiff operations and dhow or hijacked-fishing-vessel mothership use are more feasible during the inter-monsoon period. It reports no incident after UKMTO 176 in the Gulf of Aden and labels the regional piracy outlook unchanged; the assessment does not establish an active mothership, a current pirate position, increased naval coverage or a calibrated probability change.
43

Primary joint operational assessment and explicit incident cross-reference

JMIC Update 106 · 18 Oct

Information cut-off 18 October 2026 at 13:00 UTC. JMIC explicitly states that NAVAREA IX warning 383/26 reported UKMTO incident 176, resolving the prior uncertainty over whether those two products describe one encounter. It retains the Gulf of Aden threat at substantial and the Somali coast/basin at moderate, reports ASANA as the sole merchant vessel still hijacked, and assesses that ending southwest-monsoon conditions and forecast wave heights make skiff operations increasingly feasible. It says 140 NM southeast of Al Mukalla, conflicting with UKMTO's southwest wording while reproducing the same incident number; the exact UKMTO coordinate remains controlling. JMIC does not cross-reference MSCIO Alert 149/26 and does not establish piracy attribution.
44

Primary competent operational-authority incident update

MSCIO Alert 149/26 · Suspicious Activity, 17 Oct

Reports a 17 October suspicious-activity incident involving a merchant vessel at approximately 12°54′N, 47°56′E. A small craft carrying seven people reportedly armed with rifles approached to about 100 metres off the vessel's starboard quarter and opened fire. The embarked armed security team fired warning shots; no ladders or hooks were observed, the craft moved away, and the vessel and crew were reported safe. JMIC Update 106 explicitly links NAVAREA IX warning 383/26 to UKMTO incident 176, but does not cross-reference MSCIO; the matching position and encounter details make the MSCIO linkage high-confidence but inferential.
45

Primary official navigational warning

NAVAREA IX warning 383/26 · attempted piracy, 17 Oct

Reports an attempt of piracy at 12°54′N, 47°55′E in the Gulf of Aden north of Somalia and advises mariners to keep clear and exercise extreme caution. Issued 17 October 2026 at 17:00 UTC. JMIC Update 106 explicitly states that the warning reported UKMTO incident 176, resolving the prior linkage uncertainty. The Observatory preserves the warning as a separate display record and excludes it from numerical pattern calculations as a confirmed duplicate. MSCIO Alert 149/26 remains a closely matching but not explicitly cross-referenced report.
46

Primary competent operational-authority incident report

UKMTO incident 176 · Attack, 17 Oct

Reports that at 10:30 UTC a small skiff with seven persons approached an LNG tanker at 12°54′N, 47°55′E, 140 NM southwest of Al Mukalla, and fired two shots. The tanker's armed security team fired two warning shots and the skiff altered course. UKMTO's 23 October weekly overview subsequently identifies the vessel as Bahamas-flagged and approximately 110,000 DWT, says it continued its voyage, and reports no injuries, damage or pollution. JMIC Update 106 explicitly links NAVAREA IX warning 383/26 to this event. MSCIO Alert 149/26 remains inferential. Vessel name, IMO number, crew count and nationalities, motive and piracy attribution remain unpublished. JMIC says southeast while UKMTO says southwest, so the directional conflict is preserved.
47

Primary competent operational-authority structured incident record

UKMTO official incident API · incident 176 fields

The official UKMTO incident API records incident 176 at 10:30 UTC on 17 October 2026 and 12°54′N, 47°55′E. It also records a 13:19:07 UTC record-creation timestamp, which the Observatory does not treat as a verified public publication time. JMIC Update 106 explicitly links NAVAREA IX warning 383/26 to incident 176. MSCIO Alert 149/26 remains one minute east and closely matching but is not explicitly cross-referenced. The warning remains visible and excluded as a confirmed duplicate.
48

Primary operational-authority vessel, crew and response-status update

EUNAVFOR ATALANTA · northern Somalia piracy-case update, 16 Oct

Confirms HONOUR 25, SWARD, EUREKA and SIBU 1 closed and ASANA still open. Reports SWARD safely arrived in Mombasa; EUREKA's crew later flew from Mogadishu to their countries of origin; ASANA remains under pirate-action-group control inside Somali territorial waters; and adds operational details for the three Puntland recoveries. Exact SWARD arrival and EUREKA repatriation dates, current ASANA coordinates, individual welfare, final custody counts and the HONOUR 25 fatality sequence remain unresolved.
49

Primary official multinational training-command record

CMF / CTF 154 · command handover, 16 Oct

Reports that CMF headquarters assumed command of training-focused CTF 154 from the Indian Navy at a 14 October ceremony. During the India-led tenure beginning 11 February, CTF 154 trained more than 1,100 people from 39 countries, delivered more than 7,800 professional-development hours and held more than 20 specialist exchanges and engagements. CMF separately identifies CTF 151 as the regional counter-piracy lead. The release does not establish added patrol coverage, asset availability, response times, Seychelles participation or measured operational effect.
50

Primary official piracy-statistics and guidance release

ICC International Maritime Bureau · January–September 2026 report, 15 Oct

Reports 51 global piracy and armed-robbery incidents in January–September 2026: 36 vessels boarded, eight hijacked, four fired upon and three attempted boardings. IMB attributes eight vessel hijackings to Somali pirates and 94% of all crew taken hostage globally to Somali piracy. It also attributes five HONOUR 25 injuries to Puntland authorities, conflicting with the two reported by ATALANTA and the four reported by Puntland Information Ministry/Reuters and Pakistan's Foreign Office. The public summary gives no case-by-case Somali incident table, so its aggregate is not used to invent missing ledger records or overwrite the Observatory's separate six-merchant-vessel denominator.
51

Primary official piracy-incident record

ICC IMB live piracy map · incident 053-26

Records a container vessel approached and fired upon by suspected pirates at 05:50 UTC on 7 October 2026 at 12°58.77′N, 43°12.54′E in the Red Sea. The alarm was raised, crew retreated to the citadel, the vessel increased speed and manoeuvred evasively, and the onboard armed security team returned fire, aborting the approach. The matching date, vessel type, area and gunfire make a common event with MSCIO Alert 132/26 highly likely, but no authority cross-references the records. The IMB map says estimated positions are shown when exact coordinates are unavailable, so the reported precision is preserved without claiming independent survey accuracy.
52

Primary official multinational capacity-building record

CMF / CTF 154 · inaugural SPAR 2026, 14 Oct

Reports that 135 participants from 25 countries and 19 organisations attended the inaugural Subject Matter Expert Exchange on Piracy and Armed Robbery on 5–6 October. Sessions covered operations, information-sharing, law enforcement, evidence and prosecution, port response and surveillance technology. CMF says feedback will inform future CTF 154 training and engagement, but announces no participant list, agreed action plan, funded delivery, new asset allocation, patrol-coverage change or measured operational effect.
53

Competent operational multi-source assessment

JMIC Update 104 · 11 Oct

With an information cut-off of 15:00 UTC on 11 October, JMIC records NAVAREA IX warning 363/26 at 12°58′N, 43°12′E but says the activity was likely local fishermen firing shots in the air to warn of a small closest point of approach. The wording is explicitly qualified. JMIC retains substantial threat in the Gulf of Aden and Bab el-Mandeb, moderate threat on the Somali coast and basin, and lists ASANA as the sole merchant vessel still held.
54

Primary operational-authority deployment and command record

EUNAVFOR ATALANTA · 54th Force Headquarters rotation, 11 Oct

Reports that Portuguese Commodore José João Rodrigues Pedra assumed command of ATALANTA's 54th Force Headquarters rotation on 10 October and that ESPS SANTA MARÍA became the operation's flagship. The release establishes command and flagship continuity but does not announce a mandate, patrol-area, force-level, coverage or response-time change.
55

Primary operational-authority exercise and Seychelles-cooperation record

EUNAVFOR ATALANTA · September 2026 newsletter

Records the 26–29 September ALDABRA V phase 2 counter-piracy exercise between Operation ATALANTA and the Seychelles Armed Forces, including a real-life piracy scenario using assets and special-operations teams from both forces. It also records the 29 September meeting between the ATALANTA Force Commander and Seychelles Chief of Defence Forces in Port Victoria and schedules the 54th SHADE Indian Ocean for 25–26 November in Port Victoria. The newsletter gives no exact publication date or time, participant or asset list, readiness metric, patrol-coverage change or measured operational effect.
56

Primary operational-authority incident report and threat assessment

MSCIO–ATALANTA · weekly report, 2–9 Oct

Published on the MSCIO document listing on 9 October at 20:03, with timezone unstated. Records Alert 132/26: two individuals aboard a fishing boat reportedly fired on a container vessel in the Bab el-Mandeb on 7 October, damaging a starboard bridge-wing porthole and lifeboat; all crew were reported safe. Vessel identity, flag, crew count, exact position, event time and attribution remain unpublished. The report retains substantial piracy threat in the IRTC and Bab el-Mandeb and moderate threat on the Somali coast and basin.
57

Competent navigational-warning corroboration; exact message relayed from HYDROPAC

HYDROPAC warning 2914/26 · 7 Oct

Received at 19:07 UTC, independently reports piracy activity at the same 12°58′N, 43°12′E position as NAVAREA IX 363/26, advises vessels to keep clear and exercise extreme caution, and cancels HYDROPAC 2912/26. The relay preserves the warning text and metadata; the official NGA navigational-warning query is linked separately.
58

Official issuing-system reference

NGA navigational warnings

Official U.S. National Geospatial-Intelligence Agency navigational-warning query for HYDROPAC and other warning series. The public query is JavaScript-driven and was used as the issuing-system reference rather than as a directly addressable message record.
59

Primary official navigational warning / correction

NAVAREA IX warning 363/26 · 7 Oct

Reports piracy activity at 12°58′N, 43°12′E in the Bab al-Mandab Strait, advises mariners to keep clear and exercise extreme caution, and explicitly cancels warning 361/26. It gives no underlying event time, vessel identity, incident classification, crew information or outcome; the scheduled cancellation is not an incident-duration estimate.
60

Superseded primary official navigational warning

NAVAREA IX warning 361/26 · 7 Oct

Originally reported piracy activity at 12°00′N, 47°00′E and advised mariners to keep clear and exercise extreme caution. NAVAREA IX warning 363/26 later cancelled it and supplied a different Bab al-Mandab coordinate. The original coordinate is retained only as superseded publication history, not as an active warning position.
61

Independent domestic-news airport confirmation

Geo News · 7 Oct

Reports that the final three Pakistani HONOUR 25 crew arrived at Karachi's Jinnah International Airport on 7 October and were medically examined there. The exact flight number, landing time and individual findings are not published.
62

Independent domestic-news arrival corroboration

ARY News · 7 Oct

Independently reports that the final three Pakistani HONOUR 25 crew reached Karachi via Ethiopian Airlines on 7 October. The report supplies no exact landing time or individual medical findings.
63

Primary national-authority onward-repatriation statement

Pakistan Deputy Prime Minister / Foreign Minister · 7 Oct

Reports that the final three Pakistani HONOUR 25 crew are en route from Addis Ababa to Karachi for reunion with their families on 7 October. The wording does not establish an actual take-off time, flight identity or completed arrival.
64

Official state-news publication of the ministerial statement

Associated Press of Pakistan · 7 Oct

Publishes Pakistan's Deputy Prime Minister and Foreign Minister's 7 October onward-repatriation update and embassy welfare support. Exact publication, departure and arrival times are not stated.
65

Independent domestic-news corroboration quoting the ministerial statement

Express Tribune · 7 Oct

Corroborates that the final three Pakistani crew were described as en route from Addis Ababa to Karachi later on 7 October. It does not independently confirm actual take-off or arrival.
66

Independent domestic-news arrival-detail reporting

Dawn · 7 Oct

Its updated report says the final three Pakistani HONOUR 25 crew arrived in Karachi at 16:40 PKT (11:40 UTC) aboard an Ethiopian Airways flight from Addis Ababa, attributing the detail to the Ansar Burney Trust's vice chairperson. The exact flight number and individual medical findings remain unpublished.
67

Primary operational-authority incident closure

MSCIO Alert 41/26 · 6 Oct

Operation ATALANTA confirms through different sources that EUREKA is no longer under pirate control, and MSCIO formally classifies the incident closed. The page is dated 6 October at 14:46, with timezone unstated; it adds no recovery coordinate, crew-welfare detail or ransom information.
68

Established Egyptian national newspaper / completed-return reporting

Ahram Online · 5 Oct

Reports that all eight Egyptian EUREKA seafarers reached Cairo from Mogadishu late on 4 October and reunited with their families. The exact flight and landing time and individual medical findings are not published; the Egyptian MFA's 3 October statement supplies the official Mogadishu reception link.
69

Primary Indonesian migrant-worker protection authority

KP2MI · 8 Oct

Reports that two HONOUR 25 crew reached Makassar at about 17:45 WITA on 7 October and were accompanied home to their families. It also reports that one of the other two returned Indonesian crew required hospital treatment after arrival; diagnosis, treatment and current status are not published, and the fourth crew member's completed onward travel is not confirmed.
70

Primary national-authority repatriation statement

Indonesian Foreign Ministry · 7 Oct

Confirms all four Indonesian HONOUR 25 crew reached Soekarno-Hatta Airport on 6 October and were formally transferred to family representatives, with onward travel to their home regions planned and follow-up health care to continue.
71

Indonesian state news agency / airport reporting

ANTARA · 6 Oct

Reports that four Indonesian HONOUR 25 crew, including the master, arrived at Soekarno-Hatta Airport on 6 October at approximately 18:42 WIB and were received by Indonesian ministers. The government says medical and psychological care will continue; individual findings are not published.
72

Independent international-wire eyewitness corroboration

AFP · 6 Oct

Independently corroborates the completed airport arrival of the four Indonesian HONOUR 25 seafarers and official reception on 6 October.
73

Primary national-authority welfare and transfer statement

Pakistan Deputy Prime Minister / Foreign Minister · 5 Oct

Reports the three Pakistani crew who had remained aboard HONOUR 25 were successfully removed and flown to Addis Ababa with a Pakistan Embassy team. The statement thanks Somalia and ATALANTA for assistance. ATALANTA's later 16 October case update confirms operational contact and readiness to assist around HONOUR 25 but does not detail this transfer.
74

Reputable corroboration quoting the ministerial statement

Dawn · 5 Oct

Corroborates Addis Ababa transfer of the three remaining Pakistani crew and the prospective 7 October Karachi flight. Published 5 October and updated at 17:21 PKT; exact transfer times and individual medical findings are not stated.
75

Independent domestic-news corroboration

Express Tribune · 5 Oct

Corroborates the Pakistan Foreign Minister's welfare and transfer statement, including the attributed Somalia and ATALANTA assistance. It supplies no independent operational detail or completed Karachi arrival.
76

Reputable domestic broadcaster arrival confirmation

Aaj English TV · 4 Oct

Reports that four injured HONOUR 25 Pakistani crew members and the three Pakistani remains arrived at Karachi's Jinnah International Airport. Published 4 October at 19:39 PKT; exact landing time and individual medical findings are not stated.
77

Independent domestic-news arrival corroboration

HUM News English · 4 Oct

Corroborates completed Karachi arrival and reports airport reception. Exact publication and landing times are not retained.
78

Official national broadcaster departure confirmation

Radio Pakistan · 4 Oct

Reports that four injured HONOUR 25 Pakistani crew members and three Pakistani remains departed Addis Ababa aboard ET-694 for Karachi. Its scheduled 16:40 PKT landing was prospective in that report; later airport reporting separately confirms arrival.
79

Reputable corroboration quoting Pakistan Foreign Office

Dawn · 4 Oct

Corroborates the Addis Ababa departure and expected Karachi arrival from the Foreign Office account; unrelated ransom and chronology claims are not adopted.
80

Primary national-authority consular reception confirmation

Egyptian Ministry of Foreign Affairs · 3 Oct

Confirms Mogadishu reception and embassy accommodation pending Cairo travel; exact event time and completed return unspecified. Official index dates publication 3 October.
81

Primary publication-date evidence

Egyptian MFA · dated missions index

Dates the Mogadishu reception statement 3 October 2026, without an exact publication time.
82

Primary vessel and Egyptian crew-count confirmation

Egyptian Ministry of Foreign Affairs · 30 Sep

Names eight freed Egyptians aboard M/T EUREKA; identifies the group covered by the later reception statement.
83

Official national broadcaster repatriation confirmation

Radio Pakistan · 3 Oct

Three Pakistani remains reached Addis Ababa; onward Karachi clearance pending. Exact arrival/publication times and completed return unspecified.
84

Primary regional-cooperation record

Indian Ocean Commission · 2 Oct

Confirms the 30 September–2 October maritime-security seminar and the 2 October IOC–AP-IOC memorandum formalising parliamentary cooperation. No operational deployment, new patrol coverage or quantified piracy effect is announced.
85

Primary national-government bereaved-family support announcement

Radio Pakistan · 2 Oct

Records the announced PKR 12.5 million, housing, education and healthcare support for each of the three bereaved Pakistani families, and directives on treatment, repatriation and remaining personnel. Delivery and repatriation completion are unconfirmed.
86

Official national news-agency corroboration

Associated Press of Pakistan · 2 Oct

Corroborates the Prime Minister's announced family-support package and directives; it does not establish that funds, housing or repatriation have been completed.
87

Primary intergovernmental welfare confirmation

International Maritime Organization · 2 Oct

Confirms 44 seafarers freed from HONOUR 25, SIBU 1/SEAMULL and EUREKA, and 22 still captive aboard ASANA. It does not resolve casualty chronology, individual medical findings, repatriation completion or current vessel positions.
88

Primary operational-authority report

MSCIO–ATALANTA · weekly report, 25 Sep–2 Oct

Report period 25 September–2 October; retrieved 2 October, exact publication time unconfirmed. Corroborates the vessel outcomes, five HONOUR 25 fatalities and other injuries; reports EUREKA crew safe ashore and SIBU 1’s historical hijacking fix. Its mapped threat areas differ from JMIC’s broad regional labels; no current ship positions, completed repatriation or reconciled captive aggregate is supplied.
89

Attributed competent-government statement, corroborated reporting

Pakistan Foreign Minister via Anadolu · 2 Oct

Four HONOUR 25 Pakistani survivors scheduled Karachi 3 October; three Pakistani remains being repatriated; three Pakistani crew still aboard with the captain. Event and publication times unspecified; return not confirmed complete. Direct minister-post retrieval unavailable.
90

Corroboration with embedded government-post link

Express Tribune · Dar statement corroboration

Corroborates the 2 October planned return and remaining-aboard account. Link to the minister's statement is embedded; unrelated flag, ransom and casualty-sequence claims are not adopted.
91

Primary operational-authority confirmation

JMIC / UKMTO · Update 101

Information cut-off 1 October at 15:00 UTC: confirms the 29 September PMPF recoveries of HONOUR 25 and EUREKA, five HONOUR 25 crew casualties, all EUREKA crew safe and ASANA as the sole merchant vessel still hijacked; retains substantial Gulf of Aden and moderate Somali coast/basin threat levels
92

Primary national-authority welfare confirmation

Pakistan Ministry of Foreign Affairs

1 October briefing: HONOUR 25 survivors transferred to Garowe, injured receiving treatment and repatriation pending; casualty-sequence discrepancy retained
93

National-government crew-welfare and repatriation confirmation

Pakistan Foreign Office via Dawn

30 September confirmation that HONOUR 25's injured crew were receiving hospital care, surviving crew were safely ashore at Bandar Beyla, and Pakistani consular and repatriation assistance was being mobilised
94

Official regional-government response

United Arab Emirates Ministry of Foreign Affairs

1 October condemnation of the killing and wounding aboard HONOUR 25 and call for stronger regional and international cooperation to protect commercial vessels and crews
95

Regional operational-authority statement with wire verification

Puntland Maritime Police Force via Associated Press

EUREKA grounding and abandonment, pirate flight as forces approached, crew disembarkation and safety; HONOUR 25's revised 16-apprehension figure and at least 11 other suspects reported at large
96

National-government crew-welfare confirmation

Egyptian Foreign Ministry via Egypt Today

30 September confirmation that all eight Egyptian sailors from EUREKA were released, with embassy reception, welfare checks and return arrangements pending
97

National diplomatic-mission crew-welfare confirmation

High Commission of India in Kenya via Press Trust of India

Confirmation that the four Indian seafarers aboard EUREKA were safe and that the Togo-flagged tanker had been released on 29 September
98

Regional operational-authority statement reported by international wire

Puntland Maritime Police Force via Reuters

Corroboration that EUREKA's hijackers fled ashore and inland as PMPF approached, with pursuit continuing after the 29 September recovery
99

Regional operational-authority statement with independent caveats

Puntland Maritime Police Force via Arab News

Dharin-Bar recovery area, vessel control and the initial 21-apprehension claim, subsequently revised by PMPF to 16; preserves survivor accounts that conflict with PMPF on the casualty sequence
100

Regional-government statement reported by international wire

Puntland Information Ministry via Reuters

29 September HONOUR 25 recovery, five crew fatalities, four injuries and the reported capture of 16 alleged pirates; later Pakistan Foreign Office reporting supersedes its initial lack of survivor-welfare detail
101

Independent crew-welfare corroboration

Ansar Burney Trust via Geo News / Reuters

Separate confirmation of five HONOUR 25 fatalities and four injured crew, with an unresolved discrepancy over the injured crew's nationalities
102

Direct crew-welfare reporting and corroborated family account

Arab News Pakistan / Ansar Burney Trust

Pre-recovery record of the master's 25 September death-threat warning, families' loss of contact and the last report that all crew were alive; superseded by Puntland's 29 September fatality and recovery announcement
103

Specialist maritime corroboration

Riviera Maritime Media

Independent reporting of the HONOUR 25 captain's 24–25 September warning; retained as a pre-recovery record and superseded by Puntland's 29 September fatality announcement
104

Wire report citing four local security sources

AFP via News Central

Reported that 28 detainees escaped during the 25 September transfer, 13 were recaptured and one suspect was fatally wounded; official confirmation remains outstanding
105

Wire report citing four local security sources

AFP via The Daily Tribune

Reported escape of 28 SIBU 1 detainees during the 25 September transfer from Garacad to Garowe; Puntland confirmation and the number still at large remain outstanding
106

Regional operational-authority statement reported by local media

Puntland Maritime Police Force via Dawan Africa

Later written PMPF statement reporting 41 people in custody, one alleged pirate killed and five wounded; retained as attributed because AFP and EFE give conflicting figures
107

Regional operational-authority account

Puntland Maritime Police Force via EFE

Exact SIBU 1 recovery time and location, crew and cargo safety, arrests, and the no-casualty account that conflicts with AFP
108

Regional operational-authority statement

Puntland Maritime Police Force via Eastleigh Voice

PMPF attribution, reported 48-hour SIBU 1 recovery operation, crew and property safety, and arrests aboard
109

Wire report of regional-government statement

AFP via Bangladesh Sangbad Sangstha

Puntland's 25 September announcement that SIBU 1 was recovered and all 20 crew were safe; enforcement and casualty figures remain attributed
110

Official counter-piracy readiness record

Combined Maritime Forces / CTF 151

Gulf of Aden response exercise reported 25 September; exact exercise date unspecified; medical support, evidence seizure and legal approval
111

Primary operational statistics

EUNAVFOR ATALANTA · statistics updated 5 Nov

Cumulative official figures: 177 suspected pirates transferred, 145 convicted, 2,519 WFP vessels protected and 3,311,078 tonnes of food or aid delivered. The page gives the update date but no publication time; these totals do not establish current asset availability, patrol coverage or deterrent effect.
112

Primary operational-posture record

EUNAVFOR ATALANTA · PSC flagship visit and counter-piracy exercise, 4 Nov

Publicly cleared 3 November Djibouti counter-piracy coordination exercise and capability display; 79 pirate-related events since November 2023, one ongoing in the Somalia Basin, and 177 transfers. The dated port call and display are not present positions or a current coverage measure.
113

Operational warning

JMIC / UKMTO

Update 100 independently confirms SIBU 1's 25 September recovery, crew safety and the three-vessel active list; it also preserves current threat levels and supplies no present positions or new HONOUR 25 welfare assessment
114

Operational confirmation

MSCIO / EU NAVFOR ATALANTA

Alert 111/26 corroboration, crew safety, ATALANTA investigation and regional incident reporting
115

Crew-welfare confirmation

High Commission of India in Kenya

Official Indian seafarer numbers and reported welfare aboard SIBU and LUTUF
116

Official vessel record

U.S. Treasury / OFAC

SEAMULL identity, IMO number, December 2025 manager and sanctions record
117

Wire corroboration

Associated Press

Independent vessel identity, management and 20-person crew reporting for SIBU 1; crew-nationality lead
118

Wire corroboration and correction

Reuters

PMPF commander confirmation of the SIBU 1 recovery and correction removing an unverified flag state
119

Wire report citing Puntland officials

AFP via The Daily Tribune

Attributed report that HONOUR 25, EUREKA and ASANA moved south toward Hobyo; exact positions remain unconfirmed
120

Regional-government account

Puntland Security Ministry

Official competing account of LUTUF's release, reported with the ransom allegation explicitly unverified
121

Incident registry

IMB Piracy Reporting Centre

Global incident classification, annual reporting and current-year live map
122

Intergovernmental record

IMO / DCoC-JA

Official captive-seafarer assessment, guidance, legal definitions and regional architecture
123

Regional operational framework

DCoC/JA Secretariat

Proposed regional counter-piracy task force, sea-rider model and legal-transfer work
124

Intergovernmental regional-mechanism record

IMO · DCoC/JA information-sharing framework · 21 Sep

Records the 15–17 September validation of a draft information-sharing framework and gap analysis, Seychelles and Somalia participation, and the planned 11–13 November High-Level Meeting in Antananarivo
125

Primary official parliamentary-status account

Somali National News Agency · 19 Sep

Records House of the People approval of the piracy and kidnapping law revision on 10 November 2025 and Upper House approval on 9 September 2026. Presidential assent, promulgation and entry into force remain unconfirmed.
126

Coalition operations

Combined Maritime Forces

CTF 151 activity, GLAMOR response coordination, focused operations and partner contributions
127

Research baseline

World Bank · UNODC · INTERPOL

Ransom flows, network structure, economic impact and criminal-finance analysis
128

Primary intergovernmental monitoring report

UN Security Council Monitoring Team · S/2026/44

Paragraph 108 records Member State reporting that AQAP received a share of revenue from vessel payments for safe passage linked to Al-Shabaab piracy. The report covers 23 June–15 December 2025 and does not identify vessels, amounts, transaction dates or a connection to the Observatory's 2026 incidents.
129

Regional mechanism

Seychelles MFA / IOC

CGIMA chairmanship, roadmap and regional coordination
130

Cartographic base

Natural Earth

Public-domain 1:50m land and coastline geometry for map-position validation

Methodology & caveats

Verification before velocity.

Cut-off. Current-status claims were checked against public sources available at 16 November 2026 · UKMTO source date; publication time unstated · JMIC ICOD 15 Nov, 17:00 SCT. Source reviews run hourly, but a missing later update does not prove that a situation remains unchanged.

Coordinates. Many authorities deliberately publish a broad location or distance rather than exact coordinates. Approximate map positions are analytical aids and are labelled as such. The base uses Natural Earth 1:50m geometry; a broad reference that resolves on land is displaced only to the nearest plausible offshore water and carries an incident-level cartographic note. Exact reported coordinates are not moved.

Counting. IMB, IMO, UKMTO and naval operations may use different geography, reporting windows and legal classifications. The site does not combine unlike totals as if they were directly comparable.

Attribution. “Suspected Somali piracy” describes a reported operating pattern or authority assessment; it does not establish criminal guilt, sponsorship or affiliation without due process.

Review policy. Monitoring is not confirmation. The system deploys only substantive, verified changes; slower-moving statistics, mandates, law and analysis are reviewed every 12 hours, monthly or quarterly according to volatility.