Strike · Bulgaria
CONTSHIP JET struck by surface drones offshore; crew rescued, ship later sank
· CONTSHIP JET off Cape Kaliakra · Reported maritime-drone strike
Surface-drone strike reported by authorities; all 18 crew rescued; subsequent sinking confirmed by Varna Radio
Bulgarian defence authorities say Navy surveillance and a French patrol aircraft observed a surface-drone attack on CONTSHIP JET at 12:00 local (10:00 UTC) on 28 October, with three hits observed. Varna Radio gives the strike position as 43°15′N, 028°48′E off Cape Kaliakra. This is one offshore merchant-shipping occurrence, not a confirmed Bulgarian territorial incursion.
Defence and transport authorities confirm all 18 crew were rescued. Varna Radio NAVWARN 768/26 confirms the ship subsequently sank at 20:30 UTC on 28 October at 43°07.80′N, 028°45.36′E, with more than 20 containers drifting, including dangerous goods. This supersedes the earlier unofficial sinking report.
The drone operator, launch origin and motive remain unknown. Reuters reports Ambrey’s provisional video-based assessment of a likely Murena-300S-derived design; this is not a confirmed model or operator identification. Three reported drones and three observed hits are not separate incidents. The later sinking position does not replace the original strike coordinate.
Navigation warnings on 1 November reported drifting containers near Burgas Bay. BNR linked four of them to CONTSHIP JET only provisionally; the official notices do not name their source vessel. These are hazard follow-ups, not new attacks or a cumulative container count. On 2 November the transport ministry said a container near Tsarevo was secured, with origin and condition under investigation. Cargo was labelled Christmas decorations, not independently verified contents; BNT later reported that water samples were taken, with results pending. Its association with CONTSHIP JET remains unconfirmed.
Attribution and uncertainty
- Origin / operator / attribution
- Drone operator, launch origin and motive remain unresolved. Reuters on 29 October reported Ambrey analyst Tomas Alexa’s provisional assessment that the filmed surface drone likely derives from the Russian Murena-300S design; this is not a confirmed model or operator attribution.
- Investigation / uncertainty
- The official observation account and navigation warning support the attack, location and rescue, not a technical model or operator identification. Ambrey’s video-based design assessment reported by Reuters remains provisional. The minister reported three maritime drones, while the defence ministry describes three observed hits; neither creates separate occurrences. Operator, launch point and motive remain unknown. The sinking is confirmed by NAVWARN 768/26, but its later position is not the strike location. Neither the wreck nor cargo drift establishes a new drone incursion. The Burgas sightings are not a unique additive container total; vessel association remains provisional and no new pollution finding is established. The Tsarevo container is a provisional cargo-hazard follow-up, not a confirmed CONTSHIP JET container, drone recovery or pollution finding.
Sources · 14
- BGNES / Bulgarian Defence Minister ↗Minister reports three maritime drones struck a container ship28 October 2026, 12:51
- The Sofia Globe ↗Drone attack on container ship off Bulgaria’s Cape Kaliakra28 October 2026, 12:58
- Chernomore / Maritime.bg and defence minister ↗CONTSHIP JET identified in Cape Kaliakra attack report28 October 2026, 13:15
- Maritime.bg / Contship management spokesperson ↗Ship manager says all 18 CONTSHIP JET crew are safe28 October 2026, 13:56; updated 13:57
- Replica Online / BNT and Bulgarian Defence Minister ↗CONTSHIP JET bound for Constanța struck by three drones off Bulgaria28 October 2026, 14:16
- Varna Radio / Bulgarian VTMIS ↗Varna Radio navigation warnings: CONTSHIP JET strike, sinking and hazardous containers; KHORYV wreck position
- Bulgarian Ministry of Defence ↗Navy and French patrol aircraft observed CONTSHIP JET strike; all 18 crew rescued, 28 October
- Bulgarian Ministry of Transport and Communications ↗18-member crew of CONTSHIP JET rescued — 28 October 2026
- Maritime.bg ↗CONTSHIP JET live updates; overnight sinking reported but not officially confirmed
- bTV / Admiral Emil Eftimov interview ↗Admiral Eftimov: drones that struck CONTSHIP JET approached from the east29 October 2026, 10:29
- Reuters / Ambrey interview (StreetInsider syndication) ↗Greek container ship sinks after drone attack off Bulgaria — provisional Ambrey design assessment29 October 2026, 06:55 EDT (10:55 UTC); strike occurred 28 October
- Bulgarian National Radio (BNR Burgas) ↗Four drifting containers reported east of Burgas Bay1 November 2026, 16:00 local
- Bulgarian Ministry of Transport and Communications ↗Container washed ashore near Tsarevo secured2 November 2026
- BNT ↗Timing of Tsarevo container recovery remains unclear2 November 2026, 18:23 local
Full record
Red Strike for reported damaging maritime-drone attack. Offshore context explicitly separated from confirmed territorial incursions.
Anchor updated to the reported strike coordinate in Varna Radio NAVWARN 759/26 (43°15′N, 028°48′E), replacing the preliminary editorial anchor. Earlier reports gave about 16 nautical miles from Kaliakra or 21 nautical miles from Shabla. Offshore coverage is not a confirmed sovereign-territory incursion; later drift or sinking positions are not strike coordinates. NAVWARN 768/26 places the subsequent sinking at 43°07.80′N, 028°45.36′E; this does not replace the original strike anchor.
Map positions are approximate anchors for the named place, not verified incident coordinates.
- Reported date
- 28 October 2026, 10:00 UTC (12:00 Bulgarian local time)
- Record type
- reported_offshore_drone_strike
- Date basis
- Varna Radio NAVWARN 759/26 dates the surface-drone hit to 10:00 UTC on 28 October; the defence ministry gives 12:00 local. These are the reported strike time, not publication timestamps.
- Location / jurisdiction
- Black Sea southeast of Cape Kaliakra in Varna Radio’s warning. Varna Radio NAVWARN 759/26 reports the strike at 43°15′N, 028°48′E; the defence ministry describes 17 miles east of the cape.
- Event categories
- Reported maritime-drone strike on merchant shipping; crew abandonment
- What was reported
- The Bulgarian defence ministry says the Navy surveillance system and a French patrol aircraft observed the surface-drone attack at 12:00 local on 28 October and three hits were observed. Varna Radio NAVWARN 759/26 identifies CONTSHIP JET and reports a surface-drone hit at 10:00 UTC. Included under the register’s existing offshore merchant-shipping treatment, not as a confirmed Bulgarian territorial incursion.
- Aircraft / vessel / quantity
- Liberian-flagged container ship CONTSHIP JET, IMO 9348625. Bulgarian defence minister reports three maritime drones; precise platform type/model unestablished.
- Origin / operator / attribution
- Drone operator, launch origin and motive remain unresolved. Reuters on 29 October reported Ambrey analyst Tomas Alexa’s provisional assessment that the filmed surface drone likely derives from the Russian Murena-300S design; this is not a confirmed model or operator attribution.
- Damage / casualties / disruption
- All 18 crew were rescued according to Bulgarian defence and transport authorities, corroborating the earlier manager account. Varna Radio NAVWARN 768/26 confirms CONTSHIP JET sank at 20:30 UTC on 28 October at 43°07.80′N, 028°45.36′E. More than 20 containers were adrift, with flammable gases and liquids and other dangerous goods among the lost cargo. This official warning supersedes the earlier explicitly unconfirmed sinking report.
- Response / outcome
- The transport ministry reports an alert at 12:01 local and abandonment at 12:13 on 28 October; at 12:53 eight crew were aboard a Navy cutter and ten in a lifeboat. The defence ministry says three naval ships deployed immediately and all 18 crew were rescued by 13:45 local. These official accounts supersede reliance on the manager-only safety statement. Eftimov told bTV that the Navy had warned ships in the area roughly half an hour before the attack. On 1 November NAVWARN779 reported four containers east of Burgas Bay at 08:55 UTC; NAVWARN780 reported a container at 12:20 UTC. BNR described the four as probably from CONTSHIP JET, but the notices themselves do not identify a vessel. On 2 November the Bulgarian transport ministry reported a container washed ashore near Tsarevo; border police secured the area and the military prosecutor was notified. The cargo was labelled Christmas decorations, but actual contents were not verified. Origin and condition remained under investigation; the ministry initially announced planned environmental sampling. BNT later reported that water samples had been taken on 2 November, with results expected within five days; no pollution result was reported.
- Investigation / uncertainty
- The official observation account and navigation warning support the attack, location and rescue, not a technical model or operator identification. Ambrey’s video-based design assessment reported by Reuters remains provisional. The minister reported three maritime drones, while the defence ministry describes three observed hits; neither creates separate occurrences. Operator, launch point and motive remain unknown. The sinking is confirmed by NAVWARN 768/26, but its later position is not the strike location. Neither the wreck nor cargo drift establishes a new drone incursion. The Burgas sightings are not a unique additive container total; vessel association remains provisional and no new pollution finding is established. The Tsarevo container is a provisional cargo-hazard follow-up, not a confirmed CONTSHIP JET container, drone recovery or pollution finding.
- Route / entry mechanism
- Reported voyage from Haifa, Israel, toward Constanța, Romania. Admiral Emil Eftimov told bTV on 29 October that the drones approached from the east over the sea; precise track and launch point remain unknown.
- Explosive payload
- Unknown; no separately established explosion count.
- Counting / links
- One CONTSHIP JET occurrence, distinct from KHORYV, CHELSEA 3 and earlier ship attacks. Three reported drones, impacts and abandonment are not separate event records.
- Research provenance
- Added 28 October after direct BGNES and Sofia Globe browser reads and Chernomore body review. Original research snapshots unchanged. Reviewed 29 October against Bulgarian defence and transport ministries and Varna Radio navigation warnings; official rescue and reported strike position incorporated. Overnight sinking reporting retained as unconfirmed. Reviewed 30 October against Varna Radio NAVWARN 768/26: sinking confirmed for 28 October 20:30 UTC; original strike anchor and offshore classification retained. Reviewed 31 October against Reuters’ 29 October interview reporting via its StreetInsider syndication; provisional technical assessment added without changing operator certainty, occurrence date or geography. Reviewed 2 November against current Varna Radio NAVWARN779/780 and BNR’s provisional vessel association. Reviewed 3 November against the transport ministry’s 2 November Tsarevo notice; unconfirmed vessel association and labelled-versus-verified cargo distinction retained. Later BNT reporting confirms sampling took place on 2 November, with results pending.
Record N124 · reviewed 3 November 2026. Record fields keep the register’s original wording.