35 Major Shipping Incidents in 2025
January 8, 2026
2025 did not have one single “headline disaster.” It had a steady drumbeat of shocks that hit every part of the system: port explosions, ferry tragedies, container ship fires, tanker blasts, piracy kidnappings, and kinetic attacks that turned routine transits into war-risk events. The common thread is not just danger at sea, it’s operational disruption on land: terminals shut down, voyages re-routed, salvage timelines stretched, and insurance and compliance teams forced to make decisions with incomplete early reporting. This master log is built to be a practical reference, so you can scan what happened, when it happened, and what details still need verification before anyone turns an incident into a conclusion.
ShipUniverse Weekly
Get the maritime stories operators are watching.
Stay ahead of vessel markets, port disruption, maritime technology, and more.
Subscribe to the NewsletterFree weekly maritime insights for owners, operators, brokers, suppliers, and decision makers.
Major Shipping Incidents — 2025 Master Log
Research-friendly fields for quick verification, comparison, and follow-on analysis.
How to use this table
This is a working index meant to make follow-on research faster. Treat any line item as a starting point:
confirm key facts (date, location, vessel ID, casualties, pollution) against multiple reputable sources before publishing or citing.
If a detail varies across reports, it is marked Reported.
Accuracy note
We strive for accuracy, but incident reporting can evolve (conflicting early reports, later investigations, revised casualty counts, and vessel status updates).
If you spot a discrepancy, verify with official statements, class/flag records, port authority notices, or multiple trusted outlets.
Tip: drag the top scrollbar to scan columns quickly.
| Incident | Date (local/UTC) | Area / nearest reference | Vessel(s) | Flag | IMO | Type / size | Voyage / cargo (reported) | What happened (1-line) | Casualties | Pollution / env. risk | Response actions | Status / follow-up |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
ASL Bauhinia — explosion & container fire (Red Sea)
Containership casualty
|
Jan 28, 2025
Time window: reported
|
Red Sea, approx. 122 nm NW of Hodeidah (Yemen) (reported) | ASL Bauhinia | Hong Kong (reported) | 9935868 | Containership (≈1,930 TEU; built 2022 reported) |
From: Jebel Ali (UAE) (reported) To: Aqaba / Jeddah (reported) Hazmat cargo mentioned in reporting |
Explosion/fire reported among containers; crew abandoned ship after unable to contain. | No injuries reported; crew rescued (reported) | No spill reported in early accounts; hazmat cargo noted | Abandon ship; rescue by nearby vessel(s); monitoring and investigation initiated | Cause under investigation; subsequent status updates varied by outlet (reported) |
|
An Yang 2 — grounding off Sakhalin (Sea of Okhotsk)
Bulk carrier grounding
|
Feb 8, 2025
Storm conditions (reported)
|
Off SW Sakhalin Island, Russia (Nevelsky district reported) | An Yang 2 | China (reported) | 9563421 | Bulk carrier (built 2010 reported) | Coal cargo reported; fuel oils mentioned in reporting | Ran aground after lifting anchor during heavy storm; hull/ballast damage reported. | No injuries reported; crew count reported ~20 | No fuel spill reported at time of early reports | Regional alert posture; response planning constrained by weather (reported) | Unloading/removal planning after weather improves (reported) |
|
USS Harry S. Truman / Besiktas-M — collision (Port Said area)
Naval / merchant collision
|
Feb 12, 2025
~11:46 pm local (reported)
|
Mediterranean Sea, vicinity of Port Said, Egypt |
USS Harry S. Truman (CVN-75) Besiktas-M |
US Navy / Panama (Besiktas-M reported) | CVN-75 / 9291365 | Aircraft carrier / Bulk carrier | Operational details limited; investigation opened | Collision while operating near Port Said; propulsion plants reportedly unaffected. | No injuries or flooding reported in early statements | No pollution reported in early statements | Investigation announced; inspections/damage assessment (reported) | Repairs/follow-up referenced in later reporting (reported) |
|
MSC Baltic III — grounding (Newfoundland, Canada)
Containership grounding
|
Feb 15, 2025
Severe weather (reported)
|
Near Wild Cove / Cedar Cove area, Newfoundland & Labrador (reported) | MSC Baltic III | Liberia (reported) | 9241475 | Containership (≈207 m reported) | Voyage: Montreal → Corner Brook (reported) | Lost power in storm conditions and grounded on rocky coastline. | All crew rescued by helicopter; no injuries reported | Fuel oils onboard; shoreline monitoring/cleanup referenced in later updates (reported) | Helicopter rescue; coast guard oversight; salvage + pollution prevention measures | Later 2025 updates described ongoing salvage constraints and hull deterioration (reported) |
|
Saytuun-2 — hijacked / piracy incident (Puntland, Somalia)
Security / piracy
|
Feb 17–22, 2025
Released confirmed Feb 24 (reported)
|
Off Garmaal near Eyl, Puntland (Somalia) | SAYTUUN-2 (Yemeni-flagged dhow / fishing vessel) | Yemen (reported) | Not stated in key public release | Dhow / fishing vessel | “Mothership” indicators referenced in reporting (reported) | Pirate boarding/hijack; vessel held for days; pirates later departed after theft. | Crew reported safe; no injuries reported | None reported | Naval monitoring/coordination; post-incident approach after release (reported) | Incident used in threat assessments as part of renewed piracy risk (reported) |
|
MSC Levante F / Super Sarkas — struck in Odesa (missile strike)
Port strike / vessel damage
|
Mar 1, 2025
Time window: reported
|
Odesa Sea Port, Ukraine (Black Sea) |
MSC Levante F Super Sarkas |
MSC Levante F: Panama Super Sarkas: Sierra Leone |
MSC Levante F: 9330264 Super Sarkas: 9221633 |
MSC Levante F: Container feeder (≈147 m LOA reported) Super Sarkas: Bulk carrier (≈170 m LOA reported) |
Port call context; cargo specifics not consistently stated publicly (Reported) | Ballistic/missile strike on port area damaged two merchant vessels. | Port workers injured (Reported) | No confirmed marine spill reported in initial accounts (Reported) | Port emergency response; damage assessment; operational checks before onward movement (Reported) | Subsequent reporting indicated limited damage to MSC Levante F and departure from Odesa (Reported) |
|
Solong / Stena Immaculate — collision & fire (North Sea)
Allision/collision; cargo tank breach
|
Mar 10, 2025
~09:47–10:00 UTC (Reported)
|
North Sea, off East Yorkshire (near Hull / Spurn Head area, UK) |
Solong Stena Immaculate |
Solong: Portugal (Madeira) Stena Immaculate: United States |
Solong: 9322554 Stena Immaculate: 9693018 |
Solong: Feeder containership (≈140 m; ≈800 TEU class reported) Stena Immaculate: Oil/product tanker |
Stena Immaculate: Jet A-1 aviation fuel cargo (Reported) Solong: General cargo; alcohol mentioned; early hazmat reports later disputed/clarified (Reported) |
Containership struck the anchored tanker; explosions/fire followed; both vessels abandoned. | 36 rescued; 1 Solong crewmember missing and later reported as fatality (Reported) | Jet fuel release reported; pollution monitoring/mitigation implemented (Reported) | Coastguard-led rescue; exclusion zones; firefighting support; tugs/escort; environmental surveillance (Reported) | Investigation opened; criminal case actions reported; vessels stabilized/towed/handled in follow-up operations (Reported) |
|
MJ Pinar — struck in Odesa while loading grain
Port strike; crew casualties
|
Mar 11, 2025
Reported next-day by media
|
Odesa Sea Port, Ukraine (Black Sea) | MJ Pinar | Barbados | 9406051 | Bulk carrier (Handysize class; ≈179 m LOA reported) | Loading wheat for Algeria (Reported) | Ballistic/missile strike damaged vessel and port infrastructure during cargo operations. | 4 killed; additional injuries reported (Reported) | No confirmed marine spill reported in initial accounts (Reported) | Emergency response at port; casualty assistance; damage assessment (Reported) | Incident fed into updated war-risk / port security posture and ongoing investigations (Reported) |
|
AL-HIDAYA — hijacked (Somali piracy)
Security incident; dhow seizure
|
Mar 16, 2025
Release confirmed later (Reported)
|
Off Durdura, vicinity of Eyl, Puntland (Somalia) | AL-HIDAYA (Yemeni-flagged fishing dhow) | Yemen (Reported) | N/A (traditional dhow; no IMO stated in public releases) | Fishing dhow | Local fishing activity / coastal transit (Reported) | Boarded and hijacked by suspected pirates; later abandoned by hijackers. | No casualties reported; crew reported safe (Reported) | None reported | Naval monitoring/coordination; post-release approach and evidence gathering (Reported) | Released after several days; incident cited in threat assessments for renewed piracy risk (Reported) |
|
Somali piracy — Yemeni fishing dhow hijacked (third recent attack)
Security incident; regional pattern marker
|
Mar 17, 2025
Some outlets date the incident as Mar 17 (Reported)
|
Off Eyl / Garmaal area, Puntland (Somalia) (Reported) | Yemeni-flagged fishing dhow (Name not consistently stated; may overlap with AL-HIDAYA depending on source date stamping) | Yemen (Reported) | N/A / not stated | Fishing dhow | Not consistently stated (Reported) | Suspected pirates seized a Yemeni-flagged dhow; described as the third such seizure/incident in recent weeks. | Crew reported safe in early accounts (Reported) | None reported | Naval monitoring; situational warnings to shipping; investigations ongoing (Reported) | Outcome described as release/abandonment in later updates (Reported) |
|
Sindbad tourist submarine disaster — sinking off Hurghada (Red Sea)
Tourist casualty / mass rescue
|
Mar 27, 2025
Morning hours local time (Reported)
|
Red Sea, off Hurghada, Egypt (near harbour area reported) | Sindbad (tourist viewing submarine) | Egypt (Reported) | N/A (tourist sub; no IMO) | Tourist submarine / underwater sightseeing craft | Passenger excursion; ~50 persons onboard reported | Tourist submarine sank during excursion/boarding; emergency response initiated. | 6 deaths reported; ~14 injured/hospitalised reported; survivors rescued (Reported) | No significant pollution angle reported (Reported) | Rescue by local authorities; medical response; investigation launched (Reported) | Operator excursions suspended in aftermath; investigation and safety scrutiny ongoing (Reported) |
|
Shahid Rajaee / Bandar Abbas — major port explosion (Iran)
Port disaster / industrial explosion
|
Apr 26, 2025
Time window: reported
|
Shahid Rajaee port area, Bandar Abbas, Iran (Strait of Hormuz region) | Port infrastructure event (no single vessel consistently identified as the primary casualty in early reporting) | N/A | N/A | Port / terminal infrastructure | Cargo specifics varied in early reporting; investigation-led updates expected (Reported) | Large explosion at/near a major Iranian container/industrial port complex with widespread damage. | Multiple fatalities and many injuries reported (Reported) | Air quality / hazardous materials concerns reported; marine spill not consistently confirmed (Reported) | Emergency services response; fire suppression; area closures; investigation launched (Reported) | Port operations disrupted; recovery and investigative findings evolved over time (Reported) |
|
ARM Cuauhtémoc / Brooklyn Bridge — allision (New York City)
Training ship allision / bridge strike
|
May 17, 2025
Evening local time (Reported)
|
East River, New York City, USA (Brooklyn Bridge) | ARM Cuauhtémoc (Mexican Navy sail training ship) | Mexico | N/A (naval vessel; public IMO listing not typically used) | Tall ship / sail training vessel | Training cruise / port visit (Reported) | Masts struck the Brooklyn Bridge during transit; structural and onboard damage reported. | Fatalities and multiple injuries reported (Reported) | No significant pollution reported (Reported) | Emergency response and medical triage; navigation restrictions; investigations by authorities (Reported) | Vessel secured for inspection/repairs; investigative findings pending (Reported) |
|
MSC Elsa 3 — capsize/sinking & oil spill response (Kerala, India)
Containership casualty / environmental response
|
May 25, 2025
Incident window: reported
|
Off Kochi / Kerala coast, India (Arabian Sea) | MSC Elsa 3 | Liberia (Reported) | — | Containership (feeder class; size varies by outlet) (Reported) | Coastal voyage; containerized cargo including some hazardous materials reported (Reported) | Vessel capsized/sank offshore; container loss and coastal impacts reported. | Crew evacuated; injuries not consistently reported (Reported) | Oil spill response initiated; shoreline contamination risk and container debris reported (Reported) | Coast Guard and state response; shoreline cleanup; hazard monitoring; container recovery efforts (Reported) | Extended response period with ongoing debris/pollution management and investigation (Reported) |
|
Orange Frost — crewmember abducted (Gulf of Guinea)
Security incident / kidnapping
|
May 30, 2025
Night-time boarding typical for region (Reported)
|
Gulf of Guinea (near Nigeria/Benin/Togo corridor reported) | Orange Frost | Not consistently stated in public summaries (Reported) | Not consistently stated (Reported) | Merchant vessel (type varies by outlet) (Reported) | Not consistently stated (Reported) | Armed boarding; one crewmember abducted in an offshore security incident. | 1 abducted; additional injuries not consistently reported (Reported) | None reported | Security alerts; incident reporting to maritime security centers; follow-on coordination (Reported) | Kidnap case typically transitions into negotiation / law enforcement tracking (Reported) |
|
Morning Midas — car carrier fire at sea
Vehicle carrier casualty
|
Jun 3, 2025
Initial reports: early June (Reported)
|
North Pacific Ocean (position varies by report; reported en route toward Mexico) | Morning Midas | Liberia (Reported) | — | Vehicle carrier / Ro-Ro (car carrier) | Car cargo; EVs mentioned in follow-on reporting (Reported) | Fire broke out onboard; firefighting efforts unsuccessful; crew evacuated. | No injuries reported; crew evacuated (Reported) | Fuel and cargo fire risk; pollution monitoring in follow-on coverage (Reported) | Distress response; crew evacuation; towing/salvage planning initiated (Reported) | Vessel later reported sunk (see Jun 23 entry) |
|
WAN HAI 503 — explosions & fire off Kerala (India)
Containership casualty / hazardous cargo concern
|
Jun 9, 2025
Daytime incident window (Reported)
|
Arabian Sea, off Kerala coast (near Kochi / Azhikkal corridor reported) | WAN HAI 503 | Singapore (Reported) | — | Containership | Containers; hazardous cargo concerns cited in early reporting (Reported) | Multiple explosions reported followed by sustained onboard fire; containers affected. | Injuries reported; crew evacuated/assisted (Reported) | Spill risk monitored; container loss/debris risk referenced in follow-on reports (Reported) | Indian Coast Guard/Navy response; firefighting support; tow/refuge planning (Reported) | Ports-of-refuge / grounding / salvage updates continued in subsequent reporting (Reported) |
|
Adalynn / Front Eagle — tanker collision & fire (Sea of Oman)
Tanker collision; regional navigation stress
|
Jun 17, 2025
Incident window: mid-June (Reported)
|
Sea of Oman (near Strait of Hormuz approaches reported) |
Adalynn Front Eagle |
Flags varied by outlet; confirm via registry (Reported) | Not consistently stated in short-form reporting (Reported) | Oil / product tankers | Crude/product cargo details not consistently stated in early reporting (Reported) | Collision followed by fire; firefighting and separation operations reported. | No injuries reported in initial accounts (Reported) | Fire-related pollution risk; monitoring referenced (Reported) | UAE/Oman-area response assets; tugs/support vessels; safety zones (Reported) | Investigation and traffic advisories followed; incident cited alongside regional interference concerns (Reported) |
|
Morning Midas — reported sinking after fire
Total loss following earlier casualty
|
Jun 23, 2025
Sinking date in follow-on reports (Reported)
|
North Pacific Ocean (location varies by report; confirm with follow-on notices) (Reported) | Morning Midas | Liberia (Reported) | — | Vehicle carrier / Ro-Ro (car carrier) | Residual fuel onboard; cargo loss total (Reported) | Vessel reported sank after prolonged fire and salvage efforts. | No casualties reported related to sinking (Reported) | Pollution monitoring and debris concerns referenced in coverage (Reported) | Monitoring/overflight/reporting; pollution response readiness in case of release (Reported) | Loss event concluded; investigations and insurance/claims processes expected (Reported) |
|
KMP Tunu Pratama Jaya — ferry sinking (Bali Strait)
Ro-Ro passenger ferry casualty
|
Jul 2, 2025
Late evening local time (Reported)
|
Bali Strait, Indonesia (Ketapang/Banyuwangi → Gilimanuk corridor) | KMP Tunu Pratama Jaya | Indonesia | Not consistently stated in public reporting (Reported) | Roll-on/roll-off passenger ferry |
Route: Ketapang (East Java) → Gilimanuk (Bali) Onboard: 65 people (53 passengers, 12 crew) reported; 22 vehicles reported |
Sank roughly ~30 minutes after departure; flooding/water ingress and power loss cited in early investigative reporting (Reported). | At least 18 confirmed dead; ~30 rescued; 16–17 missing reported during SAR updates (Reported) | No major spill confirmed in early reports; routine fuel pollution precautions assumed (Reported) | Multi-agency SAR with boats/air assets; wreck located during extended search; investigation initiated (Reported) | Search scaled down after weeks; formal cause investigation continued (Reported) |
|
Magic Seas — attacked (Red Sea)
Kinetic/security incident; bulk carrier
|
Jul 6, 2025
Afternoon/evening UTC window (Reported)
|
Southern Red Sea, off southwest Yemen (near Hodeidah area reported) | Magic Seas | Liberia | 9736169 | Bulk carrier (≈200 m LOA class reported) | Voyage details varied by outlet; northbound transit toward Suez corridor commonly reported (Reported) | Attacked by multiple small craft with gunfire/RPGs; follow-on strike by drones/USVs reported; crew abandoned ship. | No casualties reported; crew rescued by a passing merchant vessel (Reported) | Fire/pollution risk elevated due to hull damage and onboard fuel; monitoring expected (Reported) | Distress response; crew recovery; maritime security advisories; tugs/salvage planning referenced (Reported) | Houthis later claimed the vessel sank (see Jul 7 entry) (Reported) |
|
Magic Seas — reported sinking after attack
Total loss (reported) following Jul 6 strike
|
Jul 7, 2025
Claim/confirmation window differs by source (Reported)
|
Southern Red Sea, off Yemen (near Hodeidah area reported) | Magic Seas | Liberia | 9736169 | Bulk carrier (≈200 m LOA class reported) | Crew already off the vessel; rescue transfer to Djibouti referenced in reporting (Reported) | Vessel described as at risk of sinking and later claimed/treated as sunk in follow-on reporting (Reported). | No crew casualties reported; all crew rescued prior to loss (Reported) | Potential debris/fuel release risk; extent not consistently confirmed publicly (Reported) | Traffic advisories; security posture adjustments; monitoring for pollution/debris (Reported) | Event cited as first commercial ship sunk in the Red Sea corridor after a period of reduced attacks (Reported) |
|
Eternity C — attacked (Red Sea)
Kinetic/security incident; bulk carrier
|
Jul 7, 2025
Attacks reported across Jul 7–8 (Reported)
|
Southern Red Sea, off Yemen (near Hodeidah area reported) | Eternity C | Liberia | 9588249 | Bulk carrier (built 2012 reported) | Operational/cargo details reported but not fully consistent across early coverage (Reported) | Hit in sustained assaults involving small craft and explosive drones/USVs (methods reported vary by outlet); severe damage and abandonment reported. | Fatalities and missing persons reported; later tallies commonly cited ~3–4 dead with additional missing/captured claims (Reported) | High pollution risk due to sinking/fire scenarios; monitoring and response posture discussed (Reported) | Rescue coordination by regional/naval assets; survivor recovery over subsequent days reported (Reported) | Vessel later reported to have sunk (often dated Jul 9 in follow-on reporting) (Reported) |
|
Wonder Sea (Vinh Xanh 58) — capsize (Ha Long Bay)
Tourist boat casualty; storm-related capsize
|
Jul 19, 2025
~13:30 local time cited in reporting (Reported)
|
Hạ Long Bay, Quảng Ninh Province, Vietnam | Wonder Sea (also reported as Vinh Xanh 58, reg. QN-7105) | Vietnam | N/A (inland/tour craft; no IMO) | Tourist excursion vessel | Short sightseeing tour; passenger/crew counts reported around ~50+ total onboard (Reported) | Capsized during a sudden thunderstorm/squall with high winds; passengers trapped in/around overturned hull reported. | At least ~37–39 deaths reported; ~10–11 rescued; early missing figures reported and later updated (Reported) | No major pollution angle reported (Reported) | Large-scale rescue/search operation; medical response and recovery effort (Reported) | Investigation and safety scrutiny; memorial/recovery actions followed (Reported) |
|
KM Barcelona V-A — passenger ferry fire (North Sulawesi, Indonesia)
Passenger ferry fire; mass evacuation
|
Jul 20, 2025
Afternoon local time (Reported)
|
Celebes Sea, off North Sulawesi (near Talise / Manado approach area reported) | KM Barcelona V-A | Indonesia | No IMO shown on common AIS listings (Reported) | Passenger ferry |
Route: Talaud Islands → Manado (reported) Onboard: “Hundreds” reported; later rescue counts exceeded the manifest (Reported) |
Fire spread through upper decks/superstructure; passengers and crew abandoned ship into the sea. | At least 3 deaths reported (some early reports higher); 2 missing reported; ~575 rescued reported (Reported) | Localized fuel/fire pollution risk; no major spill confirmed in initial reporting (Reported) | Coast guard/navy response with local fishermen assistance; mass pickup from water; medical triage (Reported) | Cause investigation; passenger manifest discrepancies and overcrowding concerns highlighted (Reported) |
|
Marie Maersk — container fire on deck (off Liberia)
ULCV container fire
|
Aug 14, 2025
Smoke detected Aug 13 local (Reported)
|
Atlantic Ocean, off Liberia (West Africa) | MARIE MAERSK | Denmark | 9619933 |
Ultra-large containership (Triple-E class) ≈18,000–19,000 TEU class (Reported) • LOA ~399 m |
From: Rotterdam, Netherlands To: Tanjung Pelepas, Malaysia |
Smoke from containers escalated into a container fire; crew initiated firefighting and requested external assistance. | No injuries reported; crew remained safe (Reported) | Fuel/pollution risk monitored; no confirmed spill reported in initial updates (Reported) | Onboard firefighting; tugs/assisting assets dispatched; vessel stability and critical systems reported unaffected (Reported) | Fire reported brought under control over subsequent days; investigation and GA/claims processes typical (Reported) |
|
CMA CGM J. Madison — container ship fire (Straits of Malacca)
Hold fire; diversion/salvage support
|
Aug 18, 2025
Position reported near 04°18.8′N 099°23.0′E (Reported)
|
Straits of Malacca (Malaysia/Indonesia corridor) | CMA CGM J. MADISON | Malta | 9780897 |
Fully cellular containership ≈14,414 TEU class (Reported) |
From: Singapore To: Khalifa Port, UAE (Reported) |
Fire reported originating in cargo hold; suppression and external assistance reported. | No fatalities publicly confirmed in short-form updates; injuries not consistently reported (Reported) | Localized fire risk; no confirmed marine spill reported in initial summaries (Reported) | Firefighting and salvage support; diversion/anchorage actions reported; safety management measures initiated (Reported) | Fire later reported extinguished; post-incident inspections and cargo assessment typical (Reported) |
|
Kyparissia — container ship fire & explosion (Port of Tanjung Pelepas)
Berth fire; crew casualties
|
Nov 7, 2025
Midday during unloading (Reported)
|
Port of Tanjung Pelepas (PTP), Johor, Malaysia | KYPARISSIA | Malta | 9618599 |
Containership ≈4,957 TEU • LOA ~255.34 m • Beam ~37.41 m (Reported) |
Port stay / unloading operations; cargo specifics not consistently disclosed (Reported) | Fire reported in under-hatch area (Bay/Block 5) during discharge; explosion reported in follow-on accounts. | 3 dead; 3 seriously injured reported (Reported) | Primarily onboard fire risk; no major marine spill angle reported in initial coverage (Reported) | Port emergency response and firefighting; casualty response; terminal safety cordons (Reported) | Investigation and claims actions (incl. GA reports in later notices) typical after major casualty (Reported) |
|
ONE Henry Hudson — container ship fire (Port of Los Angeles)
Berth fire; hazmat container involvement
|
Nov 23, 2025
Fire began Nov 21 evening; response ongoing through Nov 23 (Reported)
|
Port of Los Angeles, USA (San Pedro) — Berth 218 | ONE HENRY HUDSON | Panama | 9302176 |
Containership LOA ~336 m (≈1,102 ft) • ONE-operated (Reported) |
Port call; mixed containerized cargo; hazardous materials identified in involved bays (Reported) | Below-deck fire escalated with an onboard explosion reported; multiple container bays involved; shelter-in-place issued then lifted. | No crew injuries reported; all crew accounted for (Reported) | Air quality/hazmat smoke concerns; environmental monitoring initiated (Reported) | Unified Command response (fireboats + shore crews); safety zone; ship towed to anchorage outside breakwater for continued suppression (Reported) | Fire substantially contained; dewatering and investigation actions reported in follow-on updates (Reported) |
|
Mersin — tanker hit by multiple explosions (off Dakar)
External blasts while at anchor
|
Nov 27, 2025
~23:45 UTC (Reported)
|
At anchor off Dakar, Senegal (Atlantic) | M/T Mersin | Panama (Reported) | 9428683 | Product/chemical tanker (MR class reported) | Cargo/voyage not consistently stated in official summaries (Reported) | Four external explosions reported; seawater ingress into engine room; vessel damaged while stationary. | No injuries or loss of life reported | No pollution reported; anti-pollution posture activated as precaution (Reported) | Distress response; tug/support deployment; stabilization and pollution-prevention measures (Reported) | Cause unclear in early reporting; investigation and commercial recovery actions followed (Reported) |
|
Kairos — blast & fire (Black Sea, off Turkey)
Sanctions-linked tanker casualty; rescue operation
|
Nov 28, 2025
~28 nm off Turkish shore cited (Reported)
|
Black Sea, off Turkey (near Bosphorus/Kocaeli approaches reported) | KAIROS | Gambia | 9236004 | Crude oil tanker (≈274 m LOA reported) |
From: Egypt (Reported) To: Novorossiysk, Russia (Reported) Sailing empty reported |
Explosion reported followed by onboard fire; rescue boats evacuated crew as firefighting/cooling continued. | 25 crew evacuated; no fatalities reported in initial official updates (Reported) | Fire/pollution risk managed; no confirmed spill in early official summaries (Reported) | Rescue evacuation; exclusion/safety management; firefighting and cooling operations (Reported) | Follow-on reporting described extended firefighting/towing outcomes and broader investigation into “external impact” (Reported) |
|
CGAS SATURN — crew abducted in piracy boarding (Gulf of Guinea)
Kidnap-for-ransom / offshore security incident
|
Dec 3, 2025
Night boarding typical (Reported)
|
Gulf of Guinea, off Equatorial Guinea / West Africa corridor (Reported) | CGAS SATURN | Portugal (Madeira) | 9261566 |
LPG tanker (small pressurised/handysize LPG class) ~75 m LOA • ~3,090 DWT class (Reported) |
Underway passage in West Africa; destination Malabo cited in reporting (Reported) | Pirates boarded and abducted crew members; personal effects reportedly taken. | 9 crew abducted reported; remaining crew reported safe (Reported) | None reported | Security alerts and reporting to regional maritime security centers; follow-on coordination and welfare support (Reported) | Kidnap cases typically move into negotiated release / law enforcement tracking; subsequent updates reported releases (Reported) |
|
Coral Adventurer — grounding on reef (Papua New Guinea)
Expedition cruise vessel grounding
|
Dec 28, 2025
Some reports date the grounding as Dec 27 local (Reported)
|
Solomon Sea, off Morobe Province, PNG — reef area near Dregerhafen / Dreghafen Point, northeast of Lae (Reported) | CORAL ADVENTURER | Australia | 9838644 |
Expedition cruise / passenger vessel ~93–94 m LOA (Reported) |
Voyage: Cairns → Papua New Guinea itinerary (Reported) Onboard: ~80 passengers + ~43 crew reported |
Ran aground on a reef while navigating PNG coastline; vessel stuck pending refloat efforts. | No injuries reported; passengers and crew reported safe | No spill reported; hull integrity checks reported (Reported) | Stability checks; refloat planning; passenger transfer to shore support and onward travel arrangements (Reported) | Refloat attempts and inspections continued after grounding; investigation and repair planning followed (Reported) |
|
Fitburg / Elisa — undersea telecom cable damaged (Gulf of Finland)
Critical infrastructure incident; suspected anchor drag
|
Dec 31, 2025
Disruption noted around 04:53 EET (Reported)
|
Gulf of Finland (Baltic Sea), in/near Estonia’s EEZ; cable link between Finland and Estonia (Reported) |
FITBURG Undersea telecom cable owned/operated by Elisa (Reported) |
St. Vincent & the Grenadines | 9250397 | General cargo vessel (~132 m LOA class reported) |
Route: St. Petersburg (Russia) → Haifa (Israel) reported Crew: 14 reported |
Cable outage detected; authorities alleged the vessel dragged anchor in the area and seized/boarded the ship for investigation. | No injuries reported | No spill reported | Vessel intercepted and brought to port; detentions/arrests and travel bans reported; criminal investigation opened (Reported) | Cable described as inoperable pending repairs; investigation ongoing (Reported) |
|
Migrant boat — capsize off Gambia (New Year’s Eve)
Overloaded migrant vessel disaster
|
Dec 31, 2025
Night hours (Reported)
|
Atlantic Ocean off the coast of The Gambia, near Jinack village (North Bank Region) (Reported) | Overloaded migrant boat (name not known) | N/A | N/A | Small migrant craft / open boat | >200 people reported onboard; Europe-bound route commonly cited (Reported) | Boat capsized near the coast; grounding on a sandbank and passenger movement cited in early accounts (Reported). | Large-scale casualty event; survivors rescued; fatalities and missing counts updated over time (Reported) | No pollution angle reported | Search-and-rescue by emergency services, local fishermen, and volunteers; medical triage for survivors (Reported) | Ongoing recovery/search in following days; formal investigation announced (Reported) |
Legend: Reported = detail varies across sources or is preliminary.
We welcome your feedback, suggestions, corrections, and ideas for enhancements. Please click here to get in touch.
