EUROPE / FOREIGN DRONE EVENTS

Explosion · Bulgaria

Drone attack off Bulgaria sinks ALFA WATAN and sets ABLE on fire

ALFA WATAN sank, crew missing; ABLE crew rescued, vessel still afloat in 9 October report

In the early hours of 6 October 2026 two merchant ships, the Togo-flagged ALFA WATAN and the Palau-flagged ABLE, were attacked about 70 nautical miles east of Byala, in Bulgaria’s exclusive economic zone outside its territorial waters. Bulgarian authorities reported aerial and maritime attack drones. ALFA WATAN sank, and the nearby ferry DIOSCURIA witnessed an explosion; ABLE caught fire.

Bulgaria has not attributed the attack. Rumen Radev said on 7 October that the circumstances suggested Russia but the evidence was insufficient for definitive attribution; Russia denied targeting the vessel. On 6 October Zelensky alleged a combined Russian attack, citing a joint investigation; that is a Ukrainian claim, not a Bulgarian finding. On 9 October Defence Minister Dimitar Stoyanov assessed ABLE’s damage as a surface-drone strike, without naming an operator.

ALFA WATAN’s crew are missing, not confirmed dead. Reuters reported twelve Syrians missing on 7 October, then ten missing, including nine Syrians, on 8 October; the discrepancy is unresolved. All eighteen ABLE crew were rescued, two of them injured. Bulgaria halted the search on 7 October, and on 8 October Syria sought an independent investigation. A 9 October inspection found no identifiable drone remnants aboard ABLE, which was still afloat.

Show on the interactive map →

Attribution and uncertainty

Origin / operator / attribution
Unresolved by Bulgaria. Rumen Radev said circumstances suggested Russia but evidence was insufficient for definitive attribution (7 October); Russia denied targeting the vessel. Zelensky separately alleged a Russian combined attack and claimed a joint investigation supported it (6 October). This Ukrainian claim is retained as attribution, not a published Bulgarian finding. On 9 October, Defence Minister Dimitar Stoyanov assessed ABLE’s damage as a surface-drone strike while declining to identify a Russian or Ukrainian operator.
Investigation / uncertainty
High confidence in the officially reported attack and vessel outcomes. Operator, precise weapons and exact positions remain unresolved. Conflicting ALFA WATAN crew totals remain source-dated; no reconciled death toll inferred. EEZ location is not a confirmed incursion into Bulgarian sovereign territory. No drone fragments identified aboard ABLE in the later inspection. Officials differed on flooding extent; the Navy commander said its eventual sinking could not yet be determined. The separately discovered Sinemorets UAV debris (N077) has no established connection.

Sources · 6

  1. Council of Ministers of Bulgaria ↗Rumen Radev: attack on two merchant ships in Bulgaria’s economic zone is unacceptable6 October 2026
  2. Bulgarian News Agency (BTA) ↗Drone Attack on Two Merchant Ships in Bulgaria’s Exclusive Economic Zone Prompts President to Convene Security Council6 October 2026, 21:57
  3. Reuters via MarketScreener ↗Drone sinks ship off Bulgaria, as fears grow about hybrid attacks by Russia6 October 2026; updated 22:08 UTC+03
  4. Reuters via MarketScreener ↗Bulgaria halts rescue operation for crew of sunken ship7 October 2026; updated 12:54 EDT
  5. Reuters via MarketScreener ↗Syria calls for independent probe into sinking of ship in Black Sea8 October 2026; updated 09:59 EDT
  6. Mediapool ↗Military found no drone remnants aboard ABLE; Bulgaria declines to attribute the ship attack9 October 2026, 15:26

Full record

Explosion

Red Explosion: the official account includes a witnessed explosion, alongside the two-ship drone attack, sinking and fire. No drone crash or shoot-down inferred; missing crew are not confirmed fatalities.

Rounded editorial estimate for the reported offshore area, not verified vessel coordinates or a point within territorial waters.

Map positions are approximate anchors for the named place, not verified incident coordinates.

Reported date
2026-10-06 (early hours; 7–9 October follow-ups)
Record type
reported_offshore_drone_strike
Date basis
Attack in the early hours of 6 October. Search suspension on 7 October, investigation request on 8 October and ABLE inspection reported on 9 October update this same occurrence.
Location / jurisdiction
Black Sea, approximately 70 nautical miles east of Byala, in Bulgaria’s exclusive economic zone and outside its territorial waters.
Event categories
Aerial and maritime drone attack; reported explosion; ALFA WATAN sinking; ABLE fire; search and rescue
What was reported
Bulgarian government reported an aerial/maritime drone attack on two merchant ships. ALFA WATAN sank; nearby ferry DIOSCURIA witnessed an explosion and approached. ABLE caught fire and its crew was evacuated.
Aircraft / vessel / quantity
Two merchant vessels: Togo-flagged ALFA WATAN and Palau-flagged ABLE. Bulgarian authorities report aerial and maritime attack drones; models and number unestablished. Ship flags, crew nationality and attacker attribution are separate.
Origin / operator / attribution
Unresolved by Bulgaria. Rumen Radev said circumstances suggested Russia but evidence was insufficient for definitive attribution (7 October); Russia denied targeting the vessel. Zelensky separately alleged a Russian combined attack and claimed a joint investigation supported it (6 October). This Ukrainian claim is retained as attribution, not a published Bulgarian finding. On 9 October, Defence Minister Dimitar Stoyanov assessed ABLE’s damage as a surface-drone strike while declining to identify a Russian or Ukrainian operator.
Damage / casualties / disruption
ALFA WATAN crew missing: Reuters on 7 October reported twelve Syrians; its 8 October report gives ten missing, including nine Syrians. The discrepancy is unresolved; missing people are not recorded as confirmed dead. All eighteen ABLE crew were rescued, two injured; BTA reports eleven Turkish and seven Indian nationals aboard ABLE. ABLE remained afloat and drifting in the 9 October account, with severe hull damage and engine-room flooding; sinking was possible, not confirmed.
Response / outcome
DIOSCURIA assisted, with Bulgarian naval, air, border-police and maritime-rescue teams responding. Injured ABLE survivors were taken to Varna. Authorities halted the ALFA WATAN search on 7 October after finding a boat, three liferafts and equipment, but no sailors or drone wreckage. On 8 October Syria sought an independent investigation into the attack and termination of the search. A Cougar helicopter and frigate Verni inspected ABLE; two personnel boarded but found no identifiable drone remnants (9 October reporting).
Investigation / uncertainty
High confidence in the officially reported attack and vessel outcomes. Operator, precise weapons and exact positions remain unresolved. Conflicting ALFA WATAN crew totals remain source-dated; no reconciled death toll inferred. EEZ location is not a confirmed incursion into Bulgarian sovereign territory. No drone fragments identified aboard ABLE in the later inspection. Officials differed on flooding extent; the Navy commander said its eventual sinking could not yet be determined. The separately discovered Sinemorets UAV debris (N077) has no established connection.
Route / entry mechanism
Approximately 70 nautical miles east of Byala; no verified drone launch points or flight/surface tracks.
Explosive payload
Drone models, numbers and explosive payloads not established; no drone remains recovered in the 7 October report.
Counting / links
One dated record for the reported combined attack on ALFA WATAN and ABLE. Sinking, fire, rescue, search termination and investigation request remain together; no added rows for two ships, multiple drones or follow-ups. Separate from Royad Mammadov N072 off Romania on 5 October. The 9 October ABLE inspection is retained here; N077 is a distinct debris discovery with no proven link to this attack.
Research provenance
Added and reviewed 2026-10-09 against Bulgaria’s official 6 October statement, BTA and Reuters reports through 8 October (U037–U041). The Bulgarian attack was absent from the existing register. Original research snapshots unchanged. Updated 2026-10-12 with Mediapool’s 9 October inspection account (U046); attack date, anchor and existing casualty discrepancies retained.

Record N073 · reviewed 12 October 2026. Record fields keep the register’s original wording.