KHORYV drone-strike report: partially submerged wreck remains hazardous

Full record

Red Strike for a reported damaging drone attack. Capsize is established; later partial grounding is reported. No new attack or completed total sinking is inferred.

Rounded offshore editorial anchor retained. DHM ARN153 reports capsize at 44°06.59′N, 029°01.10′E at 10:06 local on 23 October. That is a capsize/navigation-hazard position, not necessarily the strike location. DHM ARN154 supersedes ARN153 and reports the still-afloat wreck at 43°57.42′N, 028°59.42′E at 11:03 local on 24 October. This later drifting/navigation-hazard position is not a strike coordinate. ARN155 supersedes ARN154: at 11:00 local on 25 October the inverted, partially submerged but still afloat vessel was reported at 43°55.25′N, 028°57.40′E. This drifting-wreck position is not the strike location. ARN156 supersedes ARN155: at 06:18 local on 27 October the partially submerged, inverted but still afloat vessel was reported at 43°51.24′N, 028°54.54′E. This later navigation-hazard observation does not establish the strike location or a new incursion. ARN158 supersedes ARN156: at 12:00 local on 27 October the inverted, partially submerged but still afloat vessel was reported at 43°49.50′N, 028°53.37′E. This is a later drifting-wreck observation, not a new strike position or established territorial incursion. Varna Radio NAVWARN 766/26 reports KHORYV at 43°30.60′N, 028°43.69′E at 18:00 UTC on 28 October, capsized, semi-submerged and drifting without crew or lights. This is a later wreck observation, not a strike coordinate.

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

Reported date

2026-10-23 (MRCC alerted around 10:00 local time)

Record type

reported_offshore_drone_strike

Date basis

The 10:00 time is the reported rescue alert, not an established strike time.

Location / jurisdiction

Black Sea, approximately 13 nautical miles east of Constanța; outside Romanian territorial waters according to the Romanian Naval Authority.

Event categories

Reported drone strike on merchant shipping; fire; capsize; search and rescue

What was reported

A reported drone attack and fire preceded capsize. The president said a vessel was hit by a drone outside territorial waters; AGERPRES links that statement to KHORYV. The 28 October NAVWARN766 describes a capsized, semi-submerged drifting wreck. Later reporting describes partial grounding; no new strike is established.

Aircraft / vessel / quantity

KHORYV, Comoros-flagged OBO carrier. Drone type and number unknown.

Origin / operator / attribution

Operator and drone origin unresolved. The president characterized the incident as Russian escalation, but the reviewed material supplies no technical attribution finding.

Damage / casualties / disruption

Romanian authorities reported thirteen crew: nine rescued, one dead and three missing. The wreck’s status has evolved since the earlier afloat notices; completed total sinking is not established. Ukraine’s MFA confirmed a Ukrainian fatality and four Ukrainians hospitalized, including the captain; two others did not require medical care. Its fourteen-crew figure conflicts with Romania’s thirteen; no reconciled manifest or final missing-person outcome was retrieved.

Response / outcome

A nearby merchant vessel recovered survivors before transfer to Romanian rescue services. MRCC coordinated ARSVOM and Interior Ministry assets. Weather prevented helicopter assistance; nine survivors subsequently reached Constanța for assessment. ARSVOM, as reported on 24 October, deployed SAR ARTEMIS at 14:24; MRCC suspended the search at 18:04 because of reduced visibility. This was not a final missing-person determination. ARN158 retains three missing and a recommended one-nautical-mile safety distance as of 27 October. Bulgaria’s transport ministry said on 27 October that institutions were monitoring the drifting wreck and would send a naval vessel for inspection. On 28 October BGNES quoted the defence minister saying it was entering Bulgarian territorial sea and that naval and transport authorities were ready to respond. Varna Radio NAVWARN 766/26 subsequently warns of the uncrewed, unlit drifting wreck at 18:00 UTC on 28 October and recommends five cables of clearance; this navigation description does not resolve the missing-person outcome. On 29 October bTV, citing information supplied by MoD, reported the vessel partly submerged and still hazardous, with Reshitelni on scene and operations temporarily suspended because of bad weather. Maritime.bg reported scuttling attempts and later partial grounding, with the bow still visible on the morning of 30 October. A 1 November Maritime.bg update reports the bow still protruding southeast of Shabla and continuing navigation warnings, supported by a photograph supplied that day by a merchant vessel.

Investigation / uncertainty

The latest retrieved primary navigation warning, NAVWARN766/26, describes the dated 28 October 18:00 UTC drift observation; it does not establish the wreck’s current movement. bTV’s 29 October MoD-attributed update supports partial submergence and continuing navigational danger. Maritime.bg reports the stern on the seabed and drift stopped, with the bow still visible in its 1 November update; these later details are attributed reporting, not a new primary hydrographic position. Completed total sinking, final missing-person outcome, operator, model and exact strike position remain unresolved. Crew totals still conflict (Romania: thirteen; Ukraine: fourteen). The uncrewed wreck description is not a missing-person determination. Later wreck drift or intervention in Bulgarian waters does not move the original offshore attack or establish another drone incursion.

Route / entry mechanism

Reported voyage: Ereğli, Turkey, departed 21 October, toward Sulina. Drone approach unknown. Offshore attack, not a confirmed sovereign-territory incursion.

Explosive payload

Unknown. Fire does not establish a separate explosion.

Counting / links

One new KHORYV occurrence, distinct from WINE TRADER, YARA J, Sea Destiny and the earlier offshore attacks. Strike, fire, sinking report and rescue are not separate rows. Later drift, partial grounding and attempts to remove the navigation hazard remain follow-ups to this same occurrence.

Research provenance

Added 23 October 2026 after reviewing the supplied Adevărul report. Original research snapshots unchanged. Reviewed 24 October against later Romanian official statements and Ukrainian MFA reporting; crew discrepancy retained. Current DHM ARN153 and MAI primary report reviewed 24 October; afloat/sinking conflict explicitly reconciled in favor of current competent navigation notice. Reviewed 25 October: DHM ARN154 later hazard position and 24 October ARSVOM-attributed search suspension; no new occurrence or territorial crossing inferred. Reviewed 26 October against ARN155; later wreck position is a follow-up to the same occurrence. Reviewed 27 October against current DHM ARN156; the 06:18 local observation updates the drifting-wreck position, not the occurrence date, attribution or original offshore classification. Reviewed 28 October against DHM ARN158, published 27 October: the 12:00 local drifting-wreck observation supersedes ARN156, without changing the occurrence date or original offshore classification. Reviewed 28 October against Bulgarian transport-ministry monitoring statement and the minister’s later territorial-sea wording; original attack classification and anchor retained. Reviewed 29 October against Varna Radio NAVWARN 766/26: later dated drift position and navigation precautions added; original strike anchor and casualty uncertainty retained. Reviewed 30 October against the dated NAVWARN766 listing, bTV’s MoD-attributed 29 October status and Maritime.bg’s 29–30 October live follow-ups. Historical drift coordinates retained, newer partial-submergence/grounding reporting attributed, and the offshore attack classification unchanged. Reviewed 2 November against Maritime.bg’s 1 November observation; no completed total sinking inferred.

Record N112 · reviewed 2 November 2026. Record fields keep the register’s original wording.