# EU foreign-drone events in 2026 — consolidated research register

**Coverage cutoff:** 24 September 2026. **Export compiled:** 24 September 2026. **Format:** UTF-8 Markdown.

## What this file contains

This is the consolidated, source-linked table of the incident material available from the research conversation, including the detailed research report, the subsequent corrections, and additional incidents identified while checking the export. It contains **84 incident, discovery, cluster, alert or related-object records**, plus **4 non-additive aggregate/context records**, with **93 source references**.

**These are record counts, not a count of 84 proven foreign attacks, unique drones, or independently verified incursions.** Some records describe several vehicles, potentially linked discoveries, unknown-origin sightings, objects not confirmed as drones, or events in an adjacent exclusive economic zone (EEZ). Their status is explicit in the table. Ordinary domestic hobby-drone activity is not silently relabeled as foreign; the Przasnysz and Tyulenovo cases, for example, remain unresolved/related objects.

The four specific correction records — **Neptun Deep (20 August), Tuzla (22 August), Olimp (26 August), and the Viișoara shepherd discovery (1 September)** — are included, not excluded. The separate **11 August Neptun Deep recovery of two aerial drones** is also included. See the lookup below.

**Completeness boundary:** the full second research report and correction text were available for this consolidation. The first report was not separately available as a complete event-by-event file, so a fully audited union with any entries unique to that unseen version cannot be claimed. This file is a consolidated research inventory, **not a claim that every 2026 incident in all 27 EU countries has been found**. 28 records were added during export checks rather than being present as entries in the earlier visible chronology; their provenance says so.

**Verification boundary:** source references were preserved from the earlier research; many relevant pages were checked again, but not every imported factual claim received a fresh forensic/source audit. The provenance column and source-register notes distinguish imported findings from rechecked sources. Reopening a source is not independent corroboration, and a source containing an official claim does not make that claim undisputed fact. Investigative status is the status in the cited reporting, not a promise that the investigation remained unchanged through the cutoff.

## Requested-incident lookup

This lookup points into the master table; it does **not** add incidents to the count.

| Requested / easily confused case | Record | Date | Counting treatment |
| --- | --- | --- | --- |
| Neptun Deep — explosive maritime drone engaged by F-16, then Navy EOD | E047 | 20 August 2026 | **One USV**, despite the initial two-drone account; two response stages. |
| Neptun Deep — earlier drifting aerial drones | E043 | 11 August 2026 | **Two aerial UAVs plus a wing**, one recovery cluster; not the 20 August USV. |
| Tourist-beach explosive detonation at Olimp | E052 | 26 August 2026 | One discovery/evacuation/disposal event; 27 August is a follow-up publication date. |
| Tuzla explosive-drone debris | E048 | 22 August 2026 | One discovery/disposal event; two blasts do not mean two drones. |
| Shepherd discovery / partial dismantling at Viișoara | E054 | 1 September 2026 | One civilian discovery followed by professional disposal; discovery date is not established crash date. |

## Reading and counting rules

Dates distinguish flight, crash, discovery, disposal and publication wherever the evidence allows. Local time is used when reported: EET/EEST for Romania, Bulgaria, Greece, Finland and the Baltic states; CET/CEST for Poland, Germany and Sweden. A clock time for a warning, report or scramble is not silently converted into an impact time. “Not reported” means missing information, **not zero or confirmed absence**. “No casualties reported” is limited to the cited account.

Aerial drones found floating at sea remain **aerial-drone wreckage**, not unmanned surface vessels. A controlled explosion is a disposal method, not by itself proof that the recovered object carried a live warhead. Model/manufacture, operator, intended target, route and cause of deviation are separate attributes. Ukrainian manufacture does not establish Ukrainian operational ownership, and Russian design does not by itself prove deliberate targeting of an EU state.

EEZs are identified separately from sovereign land, airspace and territorial seas. Unresolved maritime attacks and near-border alerts are retained as related records rather than omitted or counted as confirmed EU-territory drone strikes. A single cross-border track or recovery/disposal chain is not multiplied merely because several countries, agencies or articles reported it. Where public evidence cannot establish whether objects belong to the same airframe, the uncertainty is preserved rather than forcing a false merge or a false split.

**Stable IDs are not chronological row numbers.** Later-added records keep later IDs but appear at their chronological position. Source references such as [S51][S51] are portable Markdown links; source titles and audit notes appear at the end.

## Master data table

| Record ID | Date / period | Date basis / linked dates | EU state(s) | Location / jurisdiction | Record status | Event categories | Aircraft / vessel / quantity | Origin / operator / attribution | Route / entry mechanism | Discovery / circumstances | Explosive payload | Damage / casualties / disruption | Response / outcome | Reported investigation / uncertainty | Deduplication / links | Research provenance | Sources |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| E001 | 2026-01-28 | Incident 28 January; public report 2 February; CET | Poland | Przasnysz military base; EU land | Unresolved origin | Military-site overflight; crash; recovery | 1 small, toy-like UAV | Origin/operator unknown; foreign involvement not established | Route unknown | Security staff saw it over the base before it fell. | Not reported | No damage/casualties reported | Secured and handed to Military Police. | Unsophisticated device; no recording media identified; investigation reported. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S01][S01] |
| E002 | 2026-02-25 | 25 February; EET (UTC+2). Prior report gave about 20 minutes; retained only as unverified detail. | Romania | Sfântu Gheorghe–north of Sulina, Tulcea; airspace over territorial waters | Reported foreign | Airspace incursion; tracking; fighter scramble | 1 UAV; model unknown | Reported Russian; MApN connected incident to Russian strikes on Ukraine | Entered near Sfântu Gheorghe; left north of Sulina | Radar detection during attacks on Ukrainian Danube ports. | Not reported | No harm or debris reported | Two F-16s scrambled 17:50; RO-Alert 18:07; alert ended about 18:45. | Short incursion confirmed; exact duration not established in reopened statement. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S02][S02] |
| E003 | 2026-02-25/26 (date discrepancy) | Prior report: 26 February. Rechecked account citing Swedish military: 25 February. Do not resolve by inventing a second incident; CET. | Sweden | Öresund off Malmö, Sweden; Swedish airspace/maritime area near visiting French carrier | Reported foreign | Ship-launched reconnaissance; unauthorized flight; electronic interception | 1 UAV; model not conclusively identified | Swedish military attributed launch to Russian intelligence ship Zhigulevsk; Russia rejected allegation | Launched from ship transiting Öresund; flew near carrier-protection area | HMS Rapp detected drone during Charles de Gaulle visit. | Not reported | No casualties; carrier operations reportedly unaffected | Swedish vessel jammed/disrupted drone; final fate unknown. | Technical data reportedly linked launch to Russian ship; no confirmed kinetic shoot-down. | One encounter. Jamming, possible return to vessel and possible sea crash are not separate established events. Earlier approximate coordinate 55.6075 N, 12.8608 E was secondary/unverified. | Prior research plus export check; date discrepancy explicitly retained | [S03][S03]; [S04][S04]; [S64][S64] |
| E004 | 2026-03-12 | Discovery 12 March 2026; attribution update 13 March; CET. Probable flight: September 2025. | Poland | Lignite mine near Konin / Mniszków–Gałczyce, Greater Poland; EU land | Reported foreign recovery | Civilian discovery; old wreckage; military recovery | 1 military UAV; model unspecified | Probably Russian, linked by defence minister to September 2025 incursion | 2026 flight not established | Mine employee reportedly found drone that may have lain there for months. | Not reported | No harm reported | Police and Military Police investigated. | Minister described linkage to 2025 as probable, not proven. | One 2026 recovery; do not count as a new 2026 flight or as a second event on 13 March. | Prior research; relevant event source rechecked during export | [S05][S05]; [S06][S06] |
| E005 | 2026-03-23 | Crash 23 March; attribution 24 March; EET | Lithuania | Ice-covered Lake Lavysas, Varėna district; EU land/water | Reported foreign | Incursion; lake crash; reported explosion; recovery | 1 Ukrainian military UAV | Lithuanian government identified Ukrainian origin | Intended attack on Primorsk oil-export facilities; went astray | Wreckage on frozen lake, roughly 20 km from Belarus. | Military payload; exact charge unspecified | No casualties reported | Site secured; wreckage examined. | Government attribution announced next day; EW explanation remains an assessment. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S07][S07]; [S09][S09] |
| E006 | 2026-03-25 | Morning 25 March; EET | Estonia | Auvere power station, Ida-Viru County; EU land | Reported foreign | Incursion; infrastructure impact; recovery | 1 military UAV | Ukrainian according to Estonian authorities | Entered from Russia; intended Russian target, not Estonia | Drone hit chimney of power station. | Not reported | No injuries or interruption of plant operations reported | Authorities examined impact/wreckage. | Treated as war spillover; intentional attack on Estonia not established. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S08][S08]; [S09][S09]; [S10][S10] |
| E007 | 2026-03-25 | Morning 25 March; EET | Latvia | Krāslava region; Dobročina in additional OSW account; EU land | Reported foreign | Incursion; crash; recovery | 1 military UAV | Ukrainian according to Latvian president | Entered via Russian airspace during Ukrainian strikes on Russian targets | Drone crashed in rural area. | Not reported | No casualties reported | Latvian authorities recovered/investigated wreckage. | Ukrainian identification; precise malfunction/diversion mechanism not demonstrated. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S08][S08]; [S09][S09]; [S10][S10] |
| E008 | 2026-03-25 | 25 March; EET | Latvia | Transit corridor between Belarus and Russia; exact Latvian track unspecified | Foreign transit; operator unresolved | Brief incursion; transit; monitoring | 1 additional UAV; model unknown | Nationality/operator unspecified; foreign entry established in reporting | Belarus → Latvia → Russia | Latvian authorities reported an additional brief transit. | Not reported | No harm reported | Monitored; no engagement reported. | No wreckage or public operator identification in collected evidence. | Separate reported track from Krāslava crash (E007); not inferred solely from simultaneous reporting. | Prior research; relevant event source rechecked during export | [S08][S08] |
| E009 | 2026-03-29 to 2026-03-30 | 29–30 March reporting window; EEST | Finland | Southeast Finland, Kouvola area; EU land/airspace | Multi-drone cluster | Incursions; fighter identification; crashes; recovery | At least 2 UAVs; at least 1 identified as AN-196 | At least one Ukrainian; attribution of each object not equally established | Strayed during attacks on Russian targets; interference considered possible | Drones came down in southeast Finland, including north of Kouvola. | Not reported | No casualties reported | F/A-18s deployed; pilot reportedly withheld fire because of ground risk. | Territorial-violation investigation; EW explanation not forensic certainty. | One grouped record for multiple vehicles; precise vehicle-level dates/sites not resolved in earlier research. | Prior research; relevant event source rechecked during export | [S11][S11]; [S12][S12] |
| E010 | 2026-03-31 to 2026-04-01 | 31 March–1 April reporting window; EEST; not precise crash dates | Estonia; Finland | Tartu County, Estonia; separate Finnish border-area find; precise sites unresolved | Multi-country cluster | Detections; suspected incursions; debris discovery; recovery | Several reported objects/finds; count unresolved | Estonian assessment: Ukrainian drones intended for Russia; Finnish attribution not established for every find | Border activity associated in reporting with further strikes in Russia | Earlier report grouped Estonian activity/debris and a Finnish recovery. | Not reported | No casualties reported | Military/border searches and technical examination. | Granularity insufficient to match each track to each recovered object. | Preserved as one unresolved cluster, not a claim that all sightings were one drone or that each was a new vehicle. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S24][S24]; [S63][S63] |
| E011 | 2026-04-25 | Crash and disposal 25 April; EEST | Romania | Bariera Traian, Galați; EU land | Reported foreign | Incursion; urban crash; property damage; explosive disposal | 1 military UAV; model unspecified | Reported Russian in contemporaneous disposal coverage | Reported low approach over Lake Brateș; precise track not independently reconstructed | Drone damaged an electricity pole and a household/workshop structure. | Explosive material confirmed in disposal coverage | Property damage; no casualties reported | RAF Typhoons had scrambled for nearby threats; this drone was not shot down. Recovered explosive material detonated. | Earlier report understated explosive-disposal stage; restored from contemporaneous reporting. | Crash and later detonation are one record. Distinct from Galați apartment impact on 29 May (E028). | Prior research; relevant event source rechecked during export | [S13][S13]; [S14][S14] |
| E012 | 2026-04-25 | Discovery 25 April; EEST; crash date unknown | Romania | Farm area near Văcăreni, Tulcea County; EU land | Recovery; origin unresolved | Agricultural-site debris find; recovery | Drone fragments; number of parent airframes unknown | Foreign military association reported; exact operator unestablished | Original flight/crash date and route unknown | Fragments found near a farm. | Not reported | No casualties reported | Area investigated; fragments collected/reviewed by specialists. | Separate previous-day find is distinguished in 26 April reporting. | Separate discovery from E013. No proof that the two fragment finds represent two distinct airframes. | Prior research; relevant event source rechecked during export | [S15][S15] |
| E013 | 2026-04-26 | Discovery/disposal 26 April; EEST | Romania | Between Luncavița and Văcăreni, Tulcea County; EU land | Recovery; origin unresolved | Additional debris discovery; explosive confirmation; controlled detonation | Drone fragments; parent-airframe count unknown | Provenance under investigation | Original flight/crash date unknown | Additional fragments reported the day after the farm-area discovery. | Explosive charge confirmed | No casualties reported; RO-Alert safety warning | SRI pyrotechnicians and MApN assessed material; controlled on-site disposal under prosecutor authority. | Constanța Court of Appeal prosecutor investigation reported. | Do not call this a confirmed second complete drone. E012 and E013 are two recovery records with unresolved airframe linkage. | Prior research; relevant event source rechecked during export | [S15][S15] |
| E014 | 2026-05-03 | Discovery/report 3 May; EEST | Romania | Near Șerbăuți, Suceava County, around 20 km from Ukraine; EU land | Recovery; origin unresolved | Rural crash/discovery; recovery | 1 UAV; model unspecified | Nationality/operator not established in collected account | Route and actual crash time unknown | Drone found near northern border. | Reported absent in prior research; not reconfirmed in reopened article | No harm reported | Romanian authorities investigated. | Device identity/provenance unresolved in available record. | One incident record; no duplicate stages added. | Prior research; discovery source rechecked, payload assertion not independently reconfirmed | [S16][S16] |
| E015 | 2026-05-03 | 3 May; EEST | Finland | Virolahti, southeastern Finland; border airspace | Suspected foreign incursion | Detection; suspected territorial violation; exit | 1 suspected UAV | Origin/model unresolved | Reported exit toward Russia | Border-area drone track reported. | Not reported | No impact reported | Monitored/investigated. | Suspected territorial violation; attribution unresolved. | One incident record; no duplicate stages added. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S24][S24]; [S63][S63] |
| E016 | 2026-05-07 | 7 May; EEST | Latvia | Balvi, Ludza and Rēzekne region; EU land/airspace | Multi-drone cluster | Incursion; two crashes; infrastructure impact; fire; one transit; recovery | 3 UAVs reported | Initial technical origin unresolved; later reporting associated incidents with Ukrainian strike drones | Entered from Russian airspace; Latvian MoD discussed Russian EW as a possible cause | Two crashed; one left Latvia. One impact affected an oil-storage site. | Explosive effects reported; exact charges unknown | Four empty oil tanks damaged at Rēzekne; fire; no casualties reported | NATO aircraft deployed; mobile alerts; one crash site recovered while another was being sought. | Military and police investigation; criminal proceedings under Latvian Criminal Law Chapter 10. | One three-vehicle cluster, not three events plus a separate oil-depot strike. Transit not assumed to be a fourth vehicle. | Prior research; relevant event source rechecked during export | [S17][S17]; [S18][S18] |
| E017 | 2026-05-07 | Discovery 7 May; major reports 8 and 15 May; EEST | Greece | Coastal cave on Lefkada; Greek coast/waters | Military USV; disputed operator | Fisherman discovery; maritime recovery; seizure; explosive disposal | 1 military unmanned surface vessel | Greek officials: Ukrainian-built/type; Ukraine denied ownership | Launch point/route unknown; malfunction considered possible | Fisherman found vessel and reportedly moved/towed it before authorities secured it. | Explosives reported | No casualties reported | Coast Guard, police and Navy investigated; transferred to naval facility; explosives later destroyed. | Ownership disputed; later probe considered technical failure/off-course travel. | Discovery, transfer and disposal are linked stages, not separate drones. | Prior research; not independently rechecked in full for this export | [S19][S19]; [S20][S20]; [S21][S21] |
| E018 | 2026-05-15 | 15 May; EEST | Finland | Helsinki metropolitan area and airport; EU territory | Unresolved-origin alert | Suspected drone detection; shelter warning; airport disruption; scramble | Suspected UAV(s); count/type unresolved | Foreign origin not proven in collected account | Route unresolved | Suspected activity triggered broad protective measures. | Not reported | Residents warned to stay indoors; airport activity suspended; no physical harm reported | Fighters scrambled; Finnish authorities assessed threat. | No confirmed direct military threat in contemporaneous statement. | One alert/disruption record; not a confirmed attack or a separate event for each closure. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E019 | 2026-05-17 to 2026-05-18 | Discovery 17 May; follow-up 18 May; EEST | Lithuania | Samanė / Utena area; EU land | Suspected foreign recovery | Crash-site discovery; explosive recovery | 1 suspected military UAV | Suspected Ukrainian; not stated as final forensic identification | Flight path unknown | Wreckage found, followed by nearby explosive material. | Explosives found near wreckage | No injuries reported | Authorities cordoned site, recovered material and investigated. | Technical identification under investigation in reporting. | Explosive find linked to same wreckage, not automatically a second drone. | Prior research; relevant event source rechecked during export | [S22][S22] |
| E020 | 2026-05-17 | 17 May; EEST | Latvia | Near Russian border; precise location unresolved | Reported incursion; origin unresolved | Airspace entry; tracking; exit | 1 UAV reported | Operator/model unknown; Ukrainian association only a contextual suspicion | Entered and subsequently left Latvian airspace | Military reportedly tracked temporary incursion. | Not reported | No impact reported | Monitored; no shoot-down reported. | No final identity in prior record. | One incident record; no duplicate stages added. | Prior research; not independently rechecked in full for this export | [S24][S24] |
| E021 | 2026-05-19 | 19 May; EEST | Estonia | Kablaküla / Põltsamaa area; EU airspace | Reported foreign | Incursion; NATO interception; kinetic shoot-down; debris recovery | 1 UAV | Ukrainian according to Estonia; Kyiv apologized | Intended Russian target; Ukraine said Russian EW diverted it | NATO fighter tracked incoming drone. | Not reported | No civilian harm reported | Romanian F-16 under NATO command shot it down; debris investigated. | Nationality acknowledged; causal EW claim attributed to Ukraine. | One shoot-down record. Same-day Latvian alert E022 may be linked and is not an additional confirmed drone. | Prior research; relevant event source rechecked during export | [S23][S23] |
| E022 | 2026-05-19 | 19 May; EEST | Latvia | Eastern Latvia; exact locations unresolved | Possibly linked alert | Air warning; shelter measures; transport/school disruption | Distinct vehicle not established | Origin and relationship to Estonian track unresolved | Potentially same operational wave as E021 | Concurrent Latvian air alert was reported. | Not reported | Train services/exams disrupted; some shops reportedly closed | Civil warnings and NATO response. | Open reporting did not establish whether this was a separate object. | Retained for completeness but not additive to confirmed vehicle/incident totals without track reconciliation. | Prior research; not independently rechecked in full for this export | [S23][S23] |
| E023 | 2026-05-20 | 20 May; EEST | Lithuania | Vilnius and surrounding airspace; EU territory | Unresolved-origin alert | Drone detection; shelter warning; airport/rail/institution disruption | Suspected UAV; count/model unspecified | Nationality/operator unresolved | Route unresolved | Air-danger warning triggered protective closures. | Not reported | Airport, rail, parliament and schools reportedly disrupted | Warnings and temporary traffic restrictions. | No confirmed impact or final attribution in collected record. | One incident record; no duplicate stages added. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E024 | 2026-05-21 | 21 May; EEST | Latvia | Regions adjoining Belarus and Russia; EU airspace | Reported incursion; origin unresolved | Detection; incursion; shelter warning; fighter scramble | At least 1 UAV reported | Operator/model unknown | One account described entry from Belarus | Air threat reported in border municipalities. | Not reported | Residents instructed to shelter; no confirmed impact | NATO fighters launched. | Final identity and relationship to adjacent-country tracks unresolved. | Not automatically merged with Lithuanian two-object detection E025; no cross-border track match established. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E025 | 2026-05-21 | 21 May; EEST | Lithuania | Utena County; EU airspace | Suspected-object cluster | Detection; warning; interception response | 2 suspected aerial objects | UAV identity and foreign origin not definitively established | Route unspecified | Two objects prompted response. | Not reported | No physical harm reported | NATO aircraft and warnings reported. | Object-level findings not available in prior record. | One two-object detection record; not two confirmed foreign-drone incidents. | Prior research; not independently rechecked in full for this export | [S24][S24] |
| E026 | 2026-05-23 | 23 May; report around 08:00 EEST, not necessarily exact impact time | Latvia | Lake Drīdzis, Kombuļi parish, Krāslava municipality; EU inland water | Crash; origin unresolved | Civilian report; lake crash; explosion; underwater/debris search | 1 reported UAV | Nationality/operator unknown | Reported arrival direction near Belarus; attribution not established | Locals reported drone falling into lake around 08:00. | Explosion observed; charge/type unknown | No casualties reported | State Police, rescuers with boat and armed forces searched; possible debris located. | Sensors reportedly registered no prior breach; origin investigated. | One crash/explosion record; underwater search is a linked stage. | Prior research; relevant event source rechecked during export | [S65][S65] |
| E027 | 2026-05-23 | 23 May; EEST | Lithuania | Dumblė, Šalčininkai district, Belarus border; EU land | Cross-border smuggling | Cargo-drone interception; forced landing; seizure | 1 homemade cargo UAV | Reported arrival from Belarus; criminal operator unidentified | Belarus → Lithuania | Cargo-bearing drone reportedly forced down. | Smuggled cargo; explosive payload not reported | No casualties reported | Border-enforcement interception and seizure. | Individual cargo/technical details not available in prior research. | Included within aggregate A001 (18 cargo drones by this date); do not add the aggregate as 18 further events. | Prior research; not independently rechecked in full for this export | [S24][S24] |
| E028 | 2026-05-29 | Overnight 29 May; EEST; exact impact time not established here | Romania | Mazepa district, Galați; apartment-block roof; EU land | Reported foreign | Incursion; residential impact; explosion/fire; injuries; recovery | 1 Geran-2; associated with wider 43-drone attack wave | Romanian authorities identified Russian drone; Moscow disputed attribution without access | From attacks on Ukraine; brief Romanian flight before impact | Drone hit apartment block and ignited a fire. | Officials estimated at least 30 kg explosives | 2 minor injuries; residents evacuated; residential damage | Two Romanian F-16s and helicopter scrambled; no engagement over city. Site examined. | Official radar/debris assessment; Romania did not characterize it as an intentional attack directed at Romania. Russian consul expelled and consulate closed in response. | Distinct from 25 April Galați crash E011. Wider 43-drone wave is not 43 Romanian incursions. | Prior research; not independently rechecked in full for this export | [S25][S25]; [S26][S26] |
| E029 | 2026-06-03 | Overnight 3 June; EEST | Latvia; Estonia | Eastern border regions; precise tracks not published in collected account | Unresolved-origin alert cluster | Suspected UAV activity; civil warnings; fighter scramble | Number and identity unresolved | Foreign origin suspected, not established for each object | Routes unspecified | Border-region alerts in both countries. | Not reported | No confirmed impact or casualties in prior record | Warnings and NATO fighter response. | No wreckage or definitive attribution supplied in collected chronology. | One cross-country alert cluster; individual tracks cannot be counted reliably. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E030 | 2026-06-05 | Morning 5 June; EEST | Romania | Constanța port and nearby offshore waters; port is sovereign territory, offshore jurisdiction varies | Military-USV cluster | Maritime entry; recovery/security response; self-detonation | At least 1 USV inside port; additional offshore USVs reported, number unresolved in original register | Type used by Ukraine; Ukraine attributed drift to Russian jamming | Reported off-course movement into port; offshore routes unspecified | Sea drone found near oil-terminal/berth area; later self-detonated. Other nearby detonations reported. | Explosive/self-destruct charges reported | No casualties or major additional damage reported | Port and security authorities secured the area; military/coast-guard intervention. | Exact operators, number of separate offshore vehicles and mechanisms not fully established in the visible report. | Port arrival and later detonation are one vehicle’s stages. Retain offshore activity within cluster rather than fabricate separately dated incidents. | Prior research; not independently rechecked in full for this export | [S27][S27]; [S28][S28]; [S29][S29] |
| E031 | 2026-06-08 | 8 June; EEST | Latvia | Bērzgale area; EU airspace | Foreign-drone shoot-down; origin unresolved | Incursion; interception; NATO shoot-down; wreckage search | 1 UAV | Nationality/model not conclusively identified in contemporaneous account | Route unspecified | Drone intercepted in Latvian airspace. | Not reported | No casualties reported | French NATO fighter shot it down; debris investigation. | Origin and payload unresolved in collected account. | One incident record; no duplicate stages added. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E032 | 2026-06-30 | 30 June disposal date; original flight/discovery time not established | Romania | Near Rachelu, Tulcea County; EU land | Foreign-drone debris disposal | Wreckage recovery; controlled detonation | Drone fragments; unique airframe number unknown | Romanian MoD identified Russian drone fragments | Original flight date and route unspecified | Recovered material required explosive-ordnance disposal. | Explosive hazard reported; amount unspecified | No casualties reported | Romanian military controlled detonation. | Identification attributed to MoD in Reuters imagery/caption. | One recovery/disposal record, not a separately demonstrated new incursion. | Prior research; not independently rechecked in full for this export | [S30][S30] |
| E033 | 2026-07-21 | Night/morning 21 July; crew interviews published 21 July; EEST | Romania (adjacent maritime case) | Black Sea, approximately 26 km off Sfântu Gheorghe; reported outside territorial waters | Suspected maritime attack; drone cause unconfirmed | Reported strike; ship explosion/fire; crew rescue | LPG-carrying merchant vessel; crew described 3 attacking drones; drone type unresolved | Operator/nationality unidentified | Approach and launch point not established | Two crew members described a night-time drone attack. | Explosions reported; device type and charges unidentified | Vessel badly damaged; crew rescued; injuries reported, including burns | Romanian maritime rescue intervention; crew brought to safety. | Eyewitness drone account retained as an allegation, not a final weapon identification. | Distinct from 24 July bulk-carrier emergency E034 and August Progress IV E053. Not three separate incidents merely because crew reported three drones. | Prior research; relevant event source rechecked during export | [S57][S57] |
| E034 | 2026-07-24 | 24 July; EEST | Romania (adjacent maritime case) | Black Sea EEZ, approximately 22 miles off Sfântu Gheorghe; outside sovereign territorial waters | Unresolved mine-versus-drone impact | Merchant-vessel impact; distress call; damage assessment | Liberian-flagged bulk carrier CHRISTINA B; attacking device unidentified | Origin/operator unresolved; drone involvement not confirmed | Ship route reported USA → Ukraine; weapon route unknown | Coal carrier issued emergency call after possible mine or maritime-drone impact. | Possible explosive impact; mechanism unknown | Ship damage reported; no injuries reported | Romanian maritime authorities responded; vessel assessed for onward movement/repairs. | Mine and drone alternatives remained open. | Separate ship and event from E033. No mine incident is recategorized as a confirmed drone incident. | Prior research; relevant event source rechecked during export | [S58][S58] |
| E035 | 2026-07-24 | 24 July; EEST | Romania | Padina–Pogoanele area, Buzău County; EU airspace/land | Reported foreign | Long inland incursion; attempted interception; shoot-down | 1 Shahed-type UAV; exact designation not conclusively established here | Romanian authorities identified Russian drone | Black Sea/Danube approach, followed by inland flight | Aircraft responded before drone was destroyed over an uninhabited area. | Not reported | No casualties reported | Italian/NATO and Romanian aircraft responded; Romanian F-16 ultimately downed it. | Wreckage investigation; type and precise track details in prior secondary chronology. | First of three distinct daily Romanian shoot-downs, E035–E037; not the same-day ship event E034. | Prior research; not independently rechecked in full for this export | [S31][S31]; [S32][S32] |
| E036 | 2026-07-25 | 25 July; EEST | Romania | Sfântu Gheorghe/Tulcea coastal sector; EU airspace | Reported foreign | Brief incursion; fighter shoot-down | 1 UAV | Reported Russian; detailed model/payload under investigation | Short entry from Ukraine-war operational area | Second consecutive day of a Romanian kinetic interception. | Not reported | No casualties reported | Romanian fighter destroyed drone; fragments sought. | Technical identification under investigation in contemporary account. | Separate vehicle/day from E035 and E037. | Prior research; not independently rechecked in full for this export | [S31][S31]; [S32][S32] |
| E037 | 2026-07-26 | 26 July; EEST | Romania | 12 km northeast of Sulina; Romanian territorial waters | Reported foreign | Incursion; fighter shoot-down over sea | 1 UAV | Romania identified Russian drone; model unspecified | Black Sea approach | Third drone destroyed on three successive days. | Not reported | No casualties reported | Romanian F-16 shot it down over sea; ambassador summoned over repeated violations. | Model/payload investigation not completed in collected account. | Separate from E035–E036; the three-day total is not an additional incident. | Prior research; not independently rechecked in full for this export | [S31][S31] |
| E038 | 2026-07-27 | 27 July; EEST | Romania | Southeastern airspace; exact route unspecified | Reported foreign; limited detail | Brief incursion; exit without engagement | 1 UAV reported | Reported Russian | Brief entry, then exit into Ukraine | Drone departed before engagement. | Not reported | No impact reported | Air-defence monitoring/response. | No technical findings available in prior entry. | One incident record; no duplicate stages added. | Prior research; not independently rechecked in full for this export | [S32][S32] |
| E039 | 2026-08-02 | 2 August; detection 15:09, F-16 scramble 15:17, alert ended 16:05 EEST, as reported | Romania | Sulina branch / Periprava, Tulcea County; airspace and border field | Foreign-war spillover | Incursion; tracking; Ukrainian interception; debris fall in Romania | 1 UAV; fragments near Periprava | Associated with attacks on Ukraine; final model not established in rechecked account | Romania → Ukraine; reportedly destroyed by Ukrainian forces; debris fell back in Romania | Debris landed in a field near the border. | Not reported | No casualties or property damage reported | Romanian F-16s monitored; field searched and material investigated. | Flight and recovery reported by MApN via HotNews. | One linked flight/interception/debris chain. Earlier nearby detection without entry is not counted as a second Romanian incursion. | Prior research; relevant event source rechecked during export | [S33][S33] |
| E040 | 2026-08-04 to 2026-08-05; linked recovery 2026-08-14 | Main event overnight 4–5 August; linked find 14 August, reported 25 August; attribution 1 September; CEST | Germany | Leipzig/Halle Airport, Schkeuditz; nearby Kabelsketal; associated diversion to Hanover | Explosive-drone attack cluster; official state attribution | Attempted explosive attack; airport disruption; suspected aircraft collision; subsequent recovery | Main explosive drone; possible second collision object; further drone found 14 August | Germany attributed operation to persons acting for Russian state agencies on 1 September; Russia denied responsibility | Launch point and full device movements not established | Explosive drone reached airport but charge failed. Cargo aircraft separately reported object encounter and diverted. Additional suspected attack drone recovered near Kabelsketal. | Main drone carried professional explosives and detonator; later recovered object reportedly associated with about 50 g suspected RDX | No casualties; airport disruption; minor aircraft damage reported, but second object not conclusively a drone in initial account | Police, bomb-disposal robot/teams and federal prosecutors investigated; additional device seized; later diplomatic measures. | Official German attribution is recorded as an attribution, not public release of all underlying forensic/intelligence evidence. Russian denial retained. | The prior report’s separate 14 August Kabelsketal recovery is retained inside this linked cluster. Distinct physical objects are not erased, but follow-up publication/attribution is not another attack. | Prior research consolidated; September attribution and denial sources rechecked, not every underlying technical claim | [S34][S34]; [S35][S35]; [S36][S36]; [S37][S37]; [S66][S66]; [S67][S67] |
| E041 | 2026-08-07 to 2026-08-08 | Night of 7–8 August; CEST; report 8 August | Germany | Military installation in western Germany; precise site unspecified in prior register | Unresolved foreign involvement | Sensitive-site overflight; surveillance investigation | 2 drones sighted | Foreign/Russian linkage not established | Launch points unknown | Drones seen above military installation shortly after Leipzig event. | Not reported | No damage or casualties reported | Authorities investigated. | Not demonstrated to be part of the Leipzig operation. | Separate sighting cluster, not automatically merged into E040 or labeled Russian. | Prior research; not independently rechecked in full for this export | [S38][S38] |
| E042 | 2026-08-08 | 8 August; EEST; attribution-status follow-up 26 August | Bulgaria; Romania (reported transit) | Kardam, Bulgaria, near Romanian border and gas infrastructure; cross-border airspace | Crash with reported Ukrainian-type attribution | Cross-border transit; crash; explosion; infrastructure proximity | 1 reported Maya-type decoy UAV | Assessed as Ukrainian-type in prior reporting; final attribution not independently established here | Reported transit through Romania and Bulgaria before crash | Drone exploded in sunflower field. | Explosive effect observed; exact configuration not established | No casualties or significant infrastructure damage reported | Bulgarian investigation; additional counter-drone defensive measures reported. | By 26 August, Bulgarian minister said Ukraine had not provided requested information; Sliven military prosecutors responsible. | One cross-border vehicle/crash, not separate additive Romanian and Bulgarian incidents. | Prior research; not independently rechecked in full for this export | [S39][S39]; [S40][S40]; [S81][S81] |
| E043 | 2026-08-11 | 11 August; civilian report around 08:00 EEST | Romania (offshore EEZ) | Neptun Deep works area, approximately 90 nautical miles off Constanța; EEZ, not territorial sea | Military aerial-drone recovery cluster | Civilian-vessel discovery; floating aerial wreckage; controlled destruction; component recovery | 2 Gerbera aerial UAVs and 1 separate wing; wing not proven to be a third airframe | Gerbera/Russian-used type; Ukraine said objects were not Ukrainian; positive operator not conclusively established | Floating/drifting at sea; original flight routes unknown | Civilian vessel reported two drifting drones near offshore works. | Potential explosive hazard; exact payloads not established in collected account; wing reported non-hazardous | No casualties reported | Navy divers/EOD, supported by Coast Guard, destroyed two drones and recovered wing. | Aircraft type reported; individual origin/flight histories unresolved. | Distinct from 20 August maritime USV E047. These were aerial drones floating at sea, not USVs. Two destruction operations retained within one discovery cluster. | Added during export source checks; absent from the visible chronological report | [S60][S60] |
| E060 | 2026-08-13 | Night of 12–13 August; EEST | Romania | Chilia branch; exit around 13 km southwest of Chilia Veche; EU airspace | Reported cross-border incursion | Entry; tracking; exit; nearby explosions | 1 UAV | Nationality/operator not established in collected account | About 10 minutes along Chilia branch; departed toward Ukraine | Overnight drone track reported separately from Costinești coastal discovery. | Not reported | Explosions reported after departure; no Romanian impact established | Romanian military monitoring; F-16s also responded to a later nearby target. | Individual identity and relationship to later recoveries unresolved. | Not automatically linked to Costinești wreckage E061 or counted again for later near-border scramble. | Added during export source checks; absent from the visible chronological report | [S91][S91] |
| E061 | 2026-08-13 to 2026-08-14 | Discovery 13 August; follow-on find 14 August; EEST | Romania | Costinești, Tineretului beach/breakwaters; EU coast | Linked coastal discoveries; airframe identity unresolved | Civilian/lifeguard report; beach evacuation; floating aerial debris; follow-on fragment recovery | Aerial-drone material found 13 August; another nearby fragment found 14 August; number of unique drones unknown | Origin/operator unresolved | Washed/drifted ashore; no observed flight route | Initial report around 08:15 on 13 August near breakwaters; additional material next day. | No pyrotechnic risk reported for examined material | Tourist access restricted; no injuries reported | Military divers/EOD, Coast Guard and other emergency services; material recovered; Constanța appeals prosecutors notified. | Relationship between fragments and exact provenance under investigation. | Retain two discovery stages in one provisional location cluster, not two proven foreign airframes. Official aerial-fragment identification overrides misleading maritime-drone headline. | Added during export source checks; absent from the visible chronological report | [S88][S88]; [S89][S89]; [S92][S92] |
| E044 | 2026-08-14 | Early 14 August; attribution announced 20 August; EEST | Latvia | Near Rugāji, Balvi municipality, about 35 km from Russian border; EU airspace | Confirmed Ukrainian attribution in later report | Incursion; NATO fighter shoot-down; recovery | 1 UAV | Initially unidentified; Latvia confirmed Ukrainian origin on 20 August | Possible Belarus entry; Russian electronic interference considered, not independently proven here | Incoming drone engaged by NATO aircraft. | Not reported | No casualties reported | Italian Eurofighter shot it down; troops searched wreckage. | Later nationality identification retained instead of initial unknown-only label. | 20 August identity update is not a second incident. | Prior research; not independently rechecked in full for this export | [S41][S41]; [S42][S42] |
| E062 | 2026-08-14 | Afternoon 14 August; EEST | Romania | Saturn beach, Constanța County; EU coast | Aerial-drone fragment; origin unresolved | Tourist discovery; washed-ashore debris; access restriction; recovery | 1 fragment; airframe identity unknown | Origin/operator unresolved | Carried onto beach by waves | Tourists alerted authorities. | Specialists reported no pyrotechnic elements | Access restricted; no injuries reported | Object examined and recovered. | Any link to Costinești fragments not established. | Separate discovery location from E061; does not prove an additional distinct airframe. | Added during export source checks; absent from the visible chronological report | [S90][S90] |
| E063 | 2026-08-14 | 14 August; EEST; later follow-up refers to same-day Măcin disposal | Romania | Northern Tulcea: initial Luncavița/Cetățuia reports; later Greci/Măcin Mountains wreckage report; location reconciliation incomplete | Crash/recovery cluster; exact event boundaries unresolved | Low-altitude entry; crash; localized fire; warning; recovery; disposal | At least 1 crashed UAV; reports may describe linked or separate sites | Origin/model not established in collected contemporary reporting | Low-altitude flight reportedly escaped radar; route unresolved | Emergency call reported forest crash; later reports located wreckage in Măcin Mountains. | Controlled disposal subsequently reported; precise charge not established | Localized burning; no casualties or property damage reported | Military specialists, helicopter support, Border Police cordon and controlled disposal. | Initial Luncavița location and later Greci location require original-track/site reconciliation. | Locations retained within one unresolved cluster rather than inventing multiple unique drones. Separate Plauru object is E064. Headline “fourth drone” is not a reliable unique-airframe total. | Added during export source checks; absent from the visible chronological report | [S84][S84]; [S85][S85]; [S86][S86]; [S87][S87] |
| E064 | 2026-08-14 to 2026-08-15 | Discovery 14 August; disposal 15 August; EEST | Romania | Plauru, Tulcea County, near Ukrainian border; EU land | Drone discovery and controlled disposal | Wreckage discovery; cordon; EOD destruction | 1 reported drone/object | Nationality/model unresolved | Original flight date and route unknown | Military team identified a drone near Plauru. | Controlled detonation reported; exact payload unspecified | No casualties reported | Site secured 14 August; specialists destroyed object on 15 August. | Technical details not supplied in collected releases. | One discovery/disposal chain, not a second new incident on 15 August; distinct location from E063. | Added during export source checks; absent from the visible chronological report | [S84][S84]; [S87][S87] |
| E065 | 2026-08-14 | Discovery/response date unless described as report date; EEST | Bulgaria | Tyulenovo, Dobrich district; about 50 m offshore | Related unidentified object — NOT a confirmed drone | Coastal/sea discovery; identification; recovery or disposal | Starter motor; drone connection not established | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Navy examined drifting object. | Not specified | No casualties reported in cited account | Taken to naval base. | Identified as a starter motor only; foreign-drone status unproven. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S82][S82] |
| E066 | 2026-08-14 | Discovery/response date unless described as report date; EEST | Bulgaria | Primorsko beach, Burgas district | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Reconnaissance UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Washed ashore and examined. | Not specified for this object | No casualties reported in cited account | Navy transported it to base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S82][S82] |
| E067 | 2026-08-14 | Discovery/response date unless described as report date; EEST | Bulgaria | Lozenets beach, Burgas district | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Drone parts | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Beach discovery prompted naval response. | Not specified | No casualties reported in cited account | Parts recovered to base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S82][S82] |
| E045 | 2026-08-16 | 16 August; EEST | Romania | Between Băleni and Cudalbi, Galați County, about 24 km from Galați; EU airspace/land | Reported foreign | Incursion via Moldova; NATO shoot-down; debris recovery | 1 UAV; Geran-2 designation reported in prior chronology | Reported Russian; rechecked NATO account described apparent Russian origin | Reported entry through Moldovan airspace | Drone engaged above an uninhabited area. | Not reported | No casualties reported | Spanish F/A-18 assigned to NATO shot it down; wreckage investigated. | Shoot-down confirmed in rechecked reporting; exact type not independently forensically verified in this export. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S43][S43]; [S32][S32] |
| E046 | 2026-08-20 | 20 August: group detection 02:23, warning 03:20, entry 03:21, crash 03:24, warning ended 03:52 EEST | Romania | About 4 km northeast of Grindu, Tulcea County; EU land | Cross-border drone crash | Incursion; military tracking; crash; wreckage recovery | 1 UAV from group detected near Ukraine | Associated with attacks across Danube; final model/operator of this object not specified in initial official release | Entry about 13 km east of Galați; crash near Grindu | Tracked target crashed and briefly burned. | Prior report said recovered fragments posed no explosive hazard; not independently confirmed by initial release | No casualties or property damage reported; fire extinguished itself | Spanish F-18s and Romanian IAR-330 SOCAT helicopter responded; search/technical examination. | Official initial timeline available; subsequent complete forensic result not available here. | Distinct from same-day Neptun Deep maritime drone E047; different location, platform and circumstances. | Prior research; relevant event source rechecked during export | [S44][S44] |
| E047 | 2026-08-20 | 20 August; EEST; aircraft engagement and later naval disposal same event | Romania (offshore EEZ) | Few hundred metres from Neptun Deep works; roughly 80 nautical miles east of Constanța; Romanian EEZ | Explosive military-USV incident; origin unresolved | Offshore energy-infrastructure proximity; aircraft engagement; naval explosive disposal | 1 maritime unmanned surface vessel (USV), not 2 | Defence minister said Ukraine confirmed it was not Ukrainian; that does not positively establish another operator | Detected at sea near offshore works; launch point unknown | Explosive-laden sea drone approached/drifted near works; exact intent unresolved. | Explosive charge confirmed in official reporting; quantity unspecified | No casualties or infrastructure damage reported in collected account | Romanian F-16 cannon fire damaged but did not fully destroy drone; Navy EOD subsequently neutralized it. | MApN reconciled aircraft and vessel observations and corrected initial two-drone account to one. | MANDATORY RESTORED EVENT. One USV with two intervention stages. Not the 11 August aerial-drone cluster E043 or Grindu crash E046. | Restored from correction; relevant sources rechecked during export | [S51][S51]; [S70][S70] |
| E048 | 2026-08-22 | 22 August discovery/disposal; EEST | Romania | Tuzla beach area, Constanța County; EU coast | Explosive aerial-drone debris; preliminary foreign-manufacture assessment | Beach discovery; emergency call; cordon; controlled explosive disposal | Aerial-drone fragments; unique airframe count not established | MApN preliminary assessment: Ukrainian manufacture; operator/mission not confirmed | Original flight unknown; discovery near beach | Object reported through emergency services and examined by specialists. | Explosives confirmed | No casualties reported | Navy EOD conducted two detonations because first did not fully destroy charge; prosecutors notified. | Constanța Court of Appeal prosecution notified; provenance preliminary. | Two blasts are one disposal event, not two drones. Separate from Olimp E052 and nearby coastal finds. | Restored from correction; relevant sources rechecked during export | [S56][S56] |
| E068 | 2026-08-22 | Discovery/response date unless described as report date; EEST | Bulgaria | Coast between Albena resort and Kranevo | Unverified detailed lead; secondary reporting only | Coastal/sea discovery; identification; recovery or disposal | Reported aircraft/drone debris | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Secondary report describes a naval response. | Unknown | No casualties reported in cited account | Reported inspection/recovery. | Exact object, origin and original official release still require verification. | Separate recovery site; an additional unique airframe is not established. | Added during export; secondary lead retained, official source not independently retrieved | [S83][S83] |
| E069 | 2026-08-22 | Discovery/response date unless described as report date; EEST | Bulgaria | Rakitnika area near Varna | Unverified detailed lead; secondary reporting only | Coastal/sea discovery; identification; recovery or disposal | Reported aircraft/drone debris | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Secondary report identifies another response site. | Unknown | No casualties reported in cited account | Reported naval inspection/recovery. | Exact object, origin and original official release still require verification. | Separate recovery site; an additional unique airframe is not established. | Added during export; secondary lead retained, official source not independently retrieved | [S83][S83] |
| E049 | 2026-08-23 | 23 August; EEST | Romania | Off Gura Portiței, Tulcea County; coastal waters, exact offshore jurisdiction not specified | Explosive aerial-drone fragment recovery | Floating debris discovery; Coast Guard response; in-situ neutralization | Gerbera aerial-drone body/fragment | Gerbera/Russian-used type; prior report called it Russian; exact operator not established by type alone | Floating at sea; original flight route/date unknown | Suspect floating object examined by Navy EOD. | Explosive material present | No casualties reported | EOD team aboard Coast Guard vessel neutralized object in place. | Romanian MoD confirmed type and explosive hazard. | Aerial-drone wreckage at sea, not a naval USV and not another stage of Neptun Deep E047. | Prior research; relevant event source rechecked during export | [S45][S45] |
| E050 | 2026-08-24 | 24 August; EEST | Romania | Ciușlea, Vrancea County; tree about 5 m from a residence; EU land | Reported foreign | Incursion via Moldova; crash near home; protective measures; recovery | 1 UAV | Reported Russian; precise model not established here | Reported route through Moldova | Drone came down in tree close to dwelling. | MApN reported no explosive payload | No injuries reported; close proximity to residence | Fighter/helicopter response; area secured; recovery and investigation; protective evacuation reported in prior chronology. | Absence of explosives confirmed in rechecked MApN reporting. | One incident record; no duplicate stages added. | Prior research; relevant event source rechecked during export | [S46][S46] |
| E051 | 2026-08-25 | Evening 25 August; reported in 26 August coverage; EEST | Romania | Constanța Casino promenade / breakwaters; EU coast | Suspected drone fragment; origin unresolved | Civilian discovery; washed-ashore debris; recovery | Suspected drone component; full identity not established in collected report | Origin/operator unresolved | Reportedly washed ashore between breakwaters | Passers-by noticed object near casino. | No explosives identified in reported examination | No harm reported | Firefighters/specialists recovered and examined object. | Suspected drone identity should not be upgraded to final foreign attribution. | Separate from Olimp discovery next morning E052 and Tuzla E048; not another publication of those events. | Added during export source checks; absent from the visible chronological report | [S52][S52]; [S71][S71] |
| E070 | 2026-08-25 | Discovery/response date unless described as report date; EEST | Bulgaria | Sea between Tsarevo and Varvara | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Electric reconnaissance UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Object inspected at sea. | Reported non-dangerous | No casualties reported in cited account | Burgas Navy team transported it to base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S76][S76]; [S93][S93] |
| E071 | 2026-08-25 | Discovery/response date unless described as report date; EEST | Bulgaria | Kamchia resort coast | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Military-drone wing | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Wing washed ashore. | No ammunition | No casualties reported in cited account | Varna Navy team recovered it. | No final individual operator identification in collected release. | Evening 25 August wing find; separate reported response from 27 August UAV E079. Shared airframe not established. | Added during export source checks; absent from the visible chronological report | [S76][S76]; [S93][S93] |
| E052 | 2026-08-26 | Discovery and disposal 26 August; Rador follow-up published 27 August; EEST | Romania | Olimp tourist beach, Constanța County; EU coast | Confirmed explosive-drone fragment; origin unresolved | Beach discovery; evacuation; access restriction; RO-Alert; controlled detonation | Drone fragment with explosive material | Authorities had not announced provenance in 26–27 August reporting | Original flight date and route unknown; shoreline discovery | Explosive drone material found on tourist beach. | Explosive material confirmed | Beach evacuated; no casualties reported | SRI Antiterrorist Brigade specialists detonated material on the beach; warnings and cordon. | Origin and model unannounced in available contemporary reporting. | MANDATORY RESTORED EVENT. Discovery, evacuation and blast are one event. 27 August publication is not a second incident. | Restored from correction; relevant sources rechecked during export | [S52][S52]; [S53][S53] |
| E072 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | Kabakum / Cabacum beach near Varna | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV/fuselage remains; reports use both descriptions | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Alert received about 01:30; beach secured. | No explosives found | No casualties reported in cited account | Navy inspected and transported material to Varna. | No final individual operator identification in collected release. | Morning and afternoon reports overlap at same site; consolidated as one discovery cluster, not two proven drones. | Added during export source checks; absent from the visible chronological report | [S76][S76]; [S77][S77]; [S93][S93] |
| E073 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | Black Sea near Pomorie | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Floating object identified as drone. | Exact charge not stated | No casualties reported in cited account | Navy destroyed it at sea. | No final individual operator identification in collected release. | Disposal is part of discovery response. Controlled destruction alone does not prove a live warhead. | Added during export source checks; absent from the visible chronological report | [S76][S76]; [S93][S93] |
| E074 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | Pasha Dere, south of Varna; coastal water | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Object inspected in the sea. | Exact charge not stated | No casualties reported in cited account | Navy destroyed it at sea. | No final individual operator identification in collected release. | Separate place from Pomorie E073; controlled destruction does not itself establish explosive payload. | Added during export source checks; absent from the visible chronological report | [S76][S76]; [S93][S93] |
| E075 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | 2.6 nautical miles northeast of Cape Galata | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Part-submerged aerial UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Engine/nose underwater; tail visible. | No explosive material found | No casualties reported in cited account | Towed to Varna Naval Base and lifted from water. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S77][S77] |
| E076 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | Laguna campground, Golden Sands resort | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Drone wing | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Wing found near resort beach. | Not specified | No casualties reported in cited account | Varna Navy team transported it to base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S77][S77] |
| E077 | 2026-08-26 | Discovery/response date unless described as report date; EEST | Bulgaria | Northern beach of Burgas | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Drone wing | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Initial UAV report resolved as a wing. | Not specified | No casualties reported in cited account | Burgas Navy team recovered it. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S77][S77] |
| E053 | 2026-08-27 | 27 August: distress around 17:55, rescue by 20:47 EEST; prior register incorrectly used 28 August (publication date) | Romania (adjacent maritime case) | Black Sea, about 15–20 nautical miles off Sfântu Gheorghe; Romanian EEZ | Ship casualty; alleged drone strike unconfirmed | Reported impact; fire; sinking; maritime rescue | Merchant vessel Progress IV; suspected attacking device unidentified | Attacker/weapon unknown; flag reported Dominican Republic, while shipping-industry source cites Dominica | Ship route and alleged weapon approach not independently resolved | Vessel caught fire and sank; authorities said cause of alleged impact required investigation. | Weapon/explosive or incendiary mechanism unconfirmed | All 12 crew rescued; one injured, reportedly fractured arm; ship lost | MRCC coordinated commercial vessel, Border Police and rescue ships. | Drone attack remained a hypothesis. Earlier report’s “seriously injured” wording is not substantiated by rechecked accounts. | One ship casualty, not an additional incident on 28 or 29 August. Distinct from July tanker E033 and bulk carrier E034. | Prior research; relevant event source rechecked during export | [S59][S59]; [S74][S74]; [S75][S75] |
| E078 | 2026-08-27 | Discovery/response date unless described as report date; EEST | Bulgaria | Sea 8 nautical miles south of Kavarna | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Drone tail section | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Naval team identified floating fragment. | Not specified | No casualties reported in cited account | Transported to Varna Naval Base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S78][S78] |
| E079 | 2026-08-27 | Discovery/response date unless described as report date; EEST | Bulgaria | Kamchia, Black Sea waters | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Team inspected a reported object. | No explosives onboard | No casualties reported in cited account | Transported to Varna Naval Base. | No final individual operator identification in collected release. | Not automatically the same object as 25 August wing E071; relationship unresolved, no unique-airframe sum asserted. | Added during export source checks; absent from the visible chronological report | [S78][S78] |
| E080 | 2026-08-27 to 2026-08-28 | Discovery/response date unless described as report date; EEST | Bulgaria | Chernomorets, Sozopol municipality; offshore sighting and beach recovery | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | Suspected UAV offshore; later UAV debris on beach | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Object seen about 1–1.5 km offshore on 27 August; beach debris recovered in 28 August report. | Not specified | No casualties reported in cited account | Burgas Navy response and transport to base. | No final individual operator identification in collected release. | Sight-and-recovery reports grouped provisionally; same-object relationship not proven. Not counted as two unique drones. | Added during export source checks; absent from the visible chronological report | [S78][S78]; [S79][S79]; [S80][S80] |
| E081 | 2026-08-27 to 2026-08-28 | Discovery/response date unless described as report date; EEST | Bulgaria | Northern pier opposite Sveti Ivan island, Sozopol area | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Drone spotted 27 August. | Exact hazard unspecified | No casualties reported in cited account | Navy destroyed object in place; announced 28 August. | No final individual operator identification in collected release. | Discovery and disposal announcement one linked record; exact disposal time not specified. | Added during export source checks; absent from the visible chronological report | [S79][S79] |
| E084 | 2026-08-27 | 27 August; EEST; exact time not established here | Romania (adjacent aerial response) | Black Sea, reported target 33 km north of Snake Island; outside demonstrated Romanian airspace | Nearby air alert — NOT a confirmed EU incursion | Radar detection; NATO fighter scramble | Aerial target; full UAV identity not established in cited summary | Unknown | Near Ukrainian Black Sea sector; no Romanian entry established | Reported alongside Progress IV coverage, without a proven causal link. | Not reported | No Romanian impact established | Two Spanish F-18s scrambled. | Target identity and any link to maritime incident unresolved. | Related regional alert only; not another confirmed EU incursion and not proof of what struck Progress IV E053. | Added during export source checks; absent from the visible chronological report | [S74][S74] |
| E082 | 2026-08-28 | Discovery/response date unless described as report date; EEST | Bulgaria | About 1 km north of Shabla Lighthouse | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Found and identified by naval team. | Assessed safe | No casualties reported in cited account | Transported to Varna base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S79][S79]; [S80][S80] |
| E083 | 2026-08-28 | Discovery/response date unless described as report date; EEST | Bulgaria | Bungalata beach, Ahtopol | Coastal aerial-drone recovery; individual origin unresolved | Coastal/sea discovery; identification; recovery or disposal | UAV debris | Individual origin unresolved; cohort-level Russian/Ukrainian associations do not identify this object. | Found at sea/on shore; original flight route and crash date unknown | Beach material identified by Navy. | Not specified | No casualties reported in cited account | Burgas Navy team transported material to base. | No final individual operator identification in collected release. | Separate recovery site; an additional unique airframe is not established. | Added during export source checks; absent from the visible chronological report | [S80][S80] |
| E054 | 2026-09-01 | Verified discovery 1 September; not an established crash date; EEST | Romania | Field near Viișoara, Vaslui County; EU land | Explosive drone discovered by civilian; origin disputed | Shepherd discovery; civilian handling/partial dismantling; cordon; professional detonation | 1 damaged UAV; type unconfirmed | Official origin unresolved; local reports offered conflicting Russian/Ukrainian claims | Flight route/crash time unknown; finder did not witness it falling | Shepherd Marcel Bogos found drone while tending sheep and handled/disconnected parts before authorities arrived. | Explosive material confirmed by specialists | No casualties reported | SRI bomb specialists carried out controlled detonation; gendarmes secured site; Iași Court of Appeal prosecutors notified. | Device identity and provenance investigated; civilian handling is not described as successful bomb disposal. | MANDATORY RESTORED EVENT. Shepherd discovery, unsafe handling and specialist disposal are stages of one incident. | Restored from correction; relevant sources rechecked during export | [S54][S54]; [S55][S55]; [S72][S72]; [S73][S73] |
| E055 | 2026-09-02 | 2 September recovery date; EEST | Finland | Southern Finnish coast; precise location not supplied in prior report | Recovery; foreign status unresolved | Coastal recovery; possible territorial violation investigation | Survey/mapping UAV | Origin/operator unknown; not automatically foreign military | Flight route/date unknown | Non-dangerous mapping drone recovered. | No hazardous payload identified in account | No damage or casualties reported | Authorities recovered drone and investigated possible territorial violation. | Foreign provenance unresolved. | One recovery; no separate flight-incursion date established. | Prior research; not independently rechecked in full for this export | [S12][S12]; [S63][S63] |
| E056 | 2026-09-08 | 8 September; entry reported about 16:37 EEST; exact segment timing varies across accounts | Romania | Northeastern Romania, Neamț/Botoșani/Iași sector; Moldova entry/exit; EU airspace | Reported foreign | Jet-drone incursion; airport disruption; fighter scramble; exit | 1 reported jet-powered Geran-4 | Reported Russian; technical identification attributed to Romanian/Moldovan reporting | Moldova → Romania → Moldova, where drone reportedly crashed | Drone remained in Romanian airspace roughly 30 minutes before leaving. | Not reported | Iași Airport restrictions and civil alerts; no Romanian impact/casualties | Two Spanish F/A-18s scrambled; authorities monitored and warned residents. | Crash was outside EU, but Romanian airspace entry belongs in register. | One cross-border flight, not a separate Romanian crash or another event for airport closure. | Prior research; relevant event source rechecked during export | [S47][S47] |
| E057 | 2026-09-14 | 14 September discovery/recovery; CEST | Poland | Baltic Sea near Rusinowo beach, close to Jarosławiec; coastal recovery | Military-drone recovery; preliminary foreign attribution | Sea/beach-adjacent discovery; military recovery | 1 suspected military UAV | Defence minister: preliminary assessment Russian military drone | Flight date/route unknown; found at sea | Polish military located object just off beach. | Not reported | No casualties or damage reported | Military pulled drone from sea for examination. | Russian identification preliminary pending examination. | One recovery date, not evidence that the flight occurred that day. | Prior research; not independently rechecked in full for this export | [S48][S48] |
| E058 | 2026-09-15 | Overnight 14–15 September, recorded in prior report as 15 September; attribution update 16 September; EEST | Lithuania | Near Pratkūnai; EU airspace/land | Foreign-drone shoot-down; official Russian-type assessment | Incursion; NATO interception; shoot-down; electronics recovery | 1 Gerbera UAV | Russian-used type; president assessed likely intended Ukrainian target | Possible diversion by Ukrainian electronic warfare; causal account is an assessment | Italian NATO fighter engaged drone. | Not established for this airframe; Gerbera variants may be decoys or armed | No casualties reported | Italian NATO aircraft shot it down; Lithuanian authorities examined debris/electronics. | Russian-type identification and intended-target assessment distinguished from proof of deliberate attack on Lithuania. | Initial story dated 14 September and update 16 September concern same shoot-down. | Prior research; not independently rechecked in full for this export | [S49][S49]; [S50][S50] |
| E059 | 2026-09-24 | 24 September; helicopter launch 07:21 EEST; not asserted to be exact impact time | Romania | Near Solca, Suceava County; entry through northern Botoșani sector; EU land/airspace | Cross-border drone crash; operator unresolved | Radar detection; incursion; crash; security perimeter; helicopter response | 1 small UAV; model unresolved | Entered from Ukraine; operator/nationality not established by route alone | Ukraine → northern Romanian airspace; approximately 4 minutes before crash | Tracked drone crashed near Solca. | Not established in initial release | No fire, casualties or material damage reported in official update | Police secured area; IAR-330 SOCAT helicopter scrambled at 07:21; military verification. | Initial same-day official update; full technical findings not yet available in collected material. | One radar/entry/crash/response record. | Added during export source checks; absent from the visible chronological report | [S61][S61]; [S62][S62] |

## Aggregate and context records — do not add to the master-table totals

| Record ID | Date / period | Date basis / linked dates | EU state(s) | Location / jurisdiction | Record status | Event categories | Aircraft / vessel / quantity | Origin / operator / attribution | Route / entry mechanism | Discovery / circumstances | Explosive payload | Damage / casualties / disruption | Response / outcome | Reported investigation / uncertainty | Deduplication / links | Research provenance | Sources |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| A001 | 2026-01-01 to 2026-05-23 | Year-to-date total through 23 May | Lithuania | Belarus border; exact sites of all cases unavailable | Aggregate only — NOT additive | Cross-border smuggling; forced landings; seizure series | 18 cargo-bearing drones reportedly knocked out by 23 May | Reported arrival from Belarus; criminal operators not individually identified | Belarus → Lithuania | Prior research supplied series total, not 18 dated case files. | Smuggled cargo; explosive status not established for series | Not reported | Border-enforcement counter-drone operations. | Aggregate from secondary reporting; underlying individual incident log not available. | Includes E027; do not add 18 to the master-table count or invent 17 additional dated rows. | Prior research; not independently rechecked in full for this export | [S24][S24] |
| A002 | 2024-08 to 2026-02 | Study window spans 2024–2026; individual 2026 dates unavailable | Multiple European countries; EU-only breakdown unavailable | Reported 13-country European campaign; includes non-EU countries | Multi-year research context — NOT a 2026 EU incident total | Suspected reconnaissance/probing; military/critical-site sightings | 144 reported incidents across the study period; not 144 drones or 144 EU-2026 events | IISS campaign-level assessment of likely Russian involvement; not attribution of every sighting | Launch/recovery routes and vessels discussed at campaign level | Prior research cited IISS-linked announcement/summary without a complete 2026 incident appendix. | Not reported | Not reported | Various national investigations; event-level actions not enumerated. | Underlying dated 2026-only dataset not obtained; claim retained as research context, not verified event census. | May overlap listed events; no subtraction or addition possible without the underlying dataset. | Prior research; not independently rechecked in full for this export | [S68][S68]; [S69][S69] |
| A003 | 2026 year to date; dashboard checked 2026-09-24 | Dashboard snapshot updated 24 September 2026 | Romania | MApN official national dashboard; categories defined by the ministry | Official overlapping counters — NOT additive | Near-border attacks; scrambles; unauthorized access; shoot-downs; fragments; separate mine counter | 2026 dashboard: 77 near-border attacks; 60 scrambles; 28 unauthorized accesses; 4 shot-down drones; 42 drones/fragments identified; 2 naval mines | Different populations: nearby attacks, responses, airspace incidents and recoveries | Not an event-by-event route dataset | Official snapshot retained separately from the research chronology. | Not reported | Not reported | MApN operational/recovery categories. | Counters cannot be reconciled automatically with all-agency/news rows; individual category scope may differ. | All categories overlap. Mine counter is not a drone count. Do not total counters or use them to replace the incident register. | Official aggregate rechecked during export | [S62][S62] |
| A004 | Through 2026-08-26 | Ministerial statement 26 August | Bulgaria | Black Sea coastal recoveries; individual subset not enumerated in ministerial statement | Cohort assessment — NOT another incident count | Reconnaissance/decoy wreckage; sea-drift recoveries | Number unspecified in the minister’s statement | Defence minister: most recovered examples Russian-made, including Gerbera and Orlan; Ukrainian components and unidentified parts also found | Minister linked beach finds to sea currents after fighting near Odesa/Izmail, not evidence each crossed Bulgarian airspace | Minister summarized recent coastal discoveries. | Minister said recovered coastal drones to that date were unarmed | Not reported | Naval recovery teams; public warned not to approach objects. | Cannot assign Russian nationality, model or lack of explosives to a later or individually unidentified object solely from cohort statement. | Overlaps Bulgarian coastal rows; no additional incidents or airframes added. | Official statement reported by BTA; rechecked during export | [S81][S81] |

## Deduplication and correction audit

| Records | Treatment / correction |
| --- | --- |
| E047 | Neptun Deep 20 August: initial report of two drones corrected to **one**; fighter damage and naval disposal retained as stages. |
| E043 versus E047 | Neptun Deep 11 August aerial-drone recoveries are separate from the 20 August maritime USV. |
| E046 versus E047 | Grindu aerial crash and offshore Neptun Deep maritime incident on 20 August are different events. |
| E048 | Two Tuzla detonations are not two discoveries or two aircraft. |
| E051 versus E052 | Constanța casino debris on 25 August is not the Olimp explosive fragment found on 26 August. |
| E052 | Olimp event date is 26 August, not the 27 August date of a follow-up report. |
| E054 | Shepherd handling and specialists’ detonation belong to one Viișoara record; successful civilian disarming is not claimed. |
| E040 | Main Leipzig attack, possible aircraft encounter and 14 August Kabelsketal recovery are preserved within one linked operational cluster. The later recovery is explicitly retained, not dropped. |
| E021–E022 | Same-day Latvian alert might be linked to the drone downed in Estonia; it is not another confirmed vehicle. |
| E012–E013 | Separate Văcăreni discovery dates remain visible, but the evidence does not establish two complete, unrelated airframes. |
| E061–E062 | Costinești’s 13/14 August discoveries are linked provisionally; Saturn is a separate discovery site, with any shared-airframe relationship unresolved. |
| E063–E064 | Luncavița/Greci/Măcin reporting is preserved as an unresolved location/track cluster; the separately reported Plauru discovery and next-day disposal stay linked to each other. |
| E071 versus E079 | Kamchia’s 25 August wing and 27 August UAV recovery are different reported responses; not asserted to be different airframes without evidence. |
| E072 | Kabakum morning/afternoon reports are consolidated because the location and discovery details overlap. |
| E080 | Chernomorets offshore sighting and next-day beach recovery grouped provisionally; relationship unresolved. |
| E003 | Prior report used 26 February; military-attributed follow-up used 25 February. Date discrepancy retained within one Swedish incident. |
| E053 | Progress IV casualty date corrected from 28 August to **27 August** using contemporary reporting; severe-injury wording not carried forward as established fact. Weapon and attacker remain unknown. |
| E027 / A001 | Dumblė cargo-drone case is part of the reported 18-drone Lithuanian aggregate, not additional to it. |
| A002–A004 | Multi-year study, overlapping official counters and coastal cohort assessment are context, not newly enumerated incidents. |

## Country coverage in this export

Country counts below count **records mentioning a location in that country**, including unresolved and adjacent cases. A cross-country cluster appears under each country it touches, so these counts must not be summed to obtain a total. The nationality of an intercepting NATO aircraft does not create another incident in its home country.

| EU member state | Record mentions | Record IDs | Interpretation |
| --- | --- | --- | --- |
| Austria | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Belgium | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Bulgaria | 20 | E042, E065, E066, E067, E068, E069, E070, E071, E072, E073, E074, E075, E076, E077, E078, E079, E080, E081, E082, E083 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Croatia | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Cyprus | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Czechia | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Denmark | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Estonia | 4 | E006, E010, E021, E029 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Finland | 5 | E009, E010, E015, E018, E055 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| France | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Germany | 2 | E040, E041 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Greece | 1 | E017 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Hungary | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Ireland | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Italy | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Latvia | 10 | E007, E008, E016, E020, E022, E024, E026, E029, E031, E044 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Lithuania | 6 | E005, E019, E023, E025, E027, E058 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Luxembourg | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Malta | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Netherlands | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Poland | 3 | E001, E004, E057 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Portugal | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Romania | 35 | E002, E011, E012, E013, E014, E028, E030, E032, E033, E034, E035, E036, E037, E038, E039, E042, E043, E060, E061, E062, E063, E064, E045, E046, E047, E048, E049, E050, E051, E052, E053, E084, E054, E056, E059 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |
| Slovakia | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Slovenia | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Spain | 0 | None in the consolidated event-level material | Not evidence of absence; no claim that all national records were searched |
| Sweden | 1 | E003 | Includes any related/adjacent/unresolved records; not a confirmed-incident count |

## Source register

**61 of 93 referenced source pages were rechecked or retrieved during export preparation.** “Rechecked” means the relevant page/search text was consulted; it is not a statement that all details in every linked row were independently verified. Reuters syndications and repeated official statements are not independent sources. Some older original pages could not be reopened; their URLs and imported claims remain visibly attributed rather than being presented as freshly verified. Source labels below are descriptive, not verbatim article quotations.

| Source | Publisher / authority | Descriptive source label | Export check / caveat |
| --- | --- | --- | --- |
| [S01][S01] | Reuters | Small drone fell on Polish army base; incident 28 January, report 2 February 2026 | Relevant page/text rechecked during export |
| [S02][S02] | Newsweek România / MApN statement | Romanian airspace incursion, 25 February 2026 | Relevant page/text rechecked during export |
| [S03][S03] | Associated Press | Swedish military attribution of drone launch to Zhigulevsk | Reference retained from prior research; not fully rechecked during export. Carried from the research report; direct reopening failed during export. |
| [S04][S04] | Reuters | France comments on drone incident near aircraft carrier, 27 February 2026 | Reference retained from prior research; not fully rechecked during export |
| [S05][S05] | Reuters | Military drone found at mine in western Poland, 12 March 2026 | Reference retained from prior research; not fully rechecked during export |
| [S06][S06] | Reuters | Polish recovery probably linked to September 2025 incursion; 13 March 2026 | Relevant page/text rechecked during export |
| [S07][S07] | Reuters | Lithuanian government identifies Ukrainian drone; 24 March 2026 | Relevant page/text rechecked during export |
| [S08][S08] | Reuters | Stray Ukrainian drones in Estonia and Latvia, 25 March 2026 | Relevant page/text rechecked during export |
| [S09][S09] | OSW Centre for Eastern Studies | The Baltic states respond to incidents involving Ukrainian drones, 25 March 2026 | Relevant page/text rechecked during export |
| [S10][S10] | Estonian Ministry of Defence | Joint statement by Baltic defence ministers on drone incidents | Reference retained from prior research; not fully rechecked during export |
| [S11][S11] | Reuters | Finnish territorial violation; at least one Ukrainian drone, 29 March 2026 | Relevant page/text rechecked during export |
| [S12][S12] | Reuters | Baltic and Finnish drone chronology, updated 15 September 2026 | Reference retained from prior research; not fully rechecked during export. Original research citation. Direct reopening failed; a Reuters syndication was located (S63). |
| [S13][S13] | TVR / MApN | Why RAF Typhoons did not fire before Galați crash, 25 April 2026 | Relevant page/text rechecked during export |
| [S14][S14] | HotNews | Controlled destruction of explosive drone recovered at Galați, 25 April 2026 | Relevant page/text rechecked during export |
| [S15][S15] | HotNews / MApN | Luncavița–Văcăreni explosive fragments, 26 April 2026; also distinguishes previous-day find | Relevant page/text rechecked during export |
| [S16][S16] | Digi24 | Drone recovered in Suceava County, 3 May 2026 | Relevant page/text rechecked during export |
| [S17][S17] | Latvian Ministry of Defence | Three drones enter from Russia; two crash, 7 May 2026 | Relevant page/text rechecked during export |
| [S18][S18] | Reuters | Baltic nations seek more NATO defence after Latvian oil-tank impacts, 7 May 2026 | Reference retained from prior research; not fully rechecked during export |
| [S19][S19] | Reuters | Military sea drone found in a cave on Lefkada, 8 May 2026 | Reference retained from prior research; not fully rechecked during export |
| [S20][S20] | Reuters | Greek investigation considers malfunction, 15 May 2026 | Reference retained from prior research; not fully rechecked during export |
| [S21][S21] | Associated Press | Greek sea-drone investigation and Ukrainian ownership denial | Reference retained from prior research; not fully rechecked during export |
| [S22][S22] | Reuters | Explosives near suspected Ukrainian drone in Lithuania, 17–18 May 2026 | Relevant page/text rechecked during export |
| [S23][S23] | Reuters | Ukrainian drone downed over Estonia; Ukraine cites Russian interference, 19 May 2026 | Relevant page/text rechecked during export |
| [S24][S24] | Wikipedia (original report source) | 2026 drone incursions into Baltic states and Finland | Relevant page/text rechecked during export. Secondary compilation only. Several granular rows remain imported and require primary-source verification. |
| [S25][S25] | Associated Press | Galați apartment-block impact and official attribution, 29 May 2026 | Reference retained from prior research; not fully rechecked during export |
| [S26][S26] | Reuters | French response to Romanian drone incident, 29 May 2026 | Reference retained from prior research; not fully rechecked during export |
| [S27][S27] | Reuters video | Sea drone reaches Constanța port, 5 June 2026 | Reference retained from prior research; not fully rechecked during export |
| [S28][S28] | Reuters video | Sea-drone detonation at Constanța, 5 June 2026 | Reference retained from prior research; not fully rechecked during export |
| [S29][S29] | Associated Press | Constanța maritime-drone incident | Reference retained from prior research; not fully rechecked during export |
| [S30][S30] | Reuters Connect / Romanian MoD handout | Russian drone fragments destroyed near Rachelu, 30 June 2026 | Reference retained from prior research; not fully rechecked during export |
| [S31][S31] | Reuters | Third Russian drone downed by Romania in three days, 26 July 2026 | Reference retained from prior research; not fully rechecked during export |
| [S32][S32] | Wikipedia (original report source) | 2026 drone incidents in Romania | Relevant page/text rechecked during export. Used as a source index; individual news and official sources replace it where rechecked. Not a primary investigation. |
| [S33][S33] | HotNews / MApN | Periprava debris after interception in Ukraine, 2 August 2026 | Relevant page/text rechecked during export |
| [S34][S34] | Reuters | Explosive drone at Leipzig/Halle airport, 5 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S35][S35] | Reuters | Leipzig follow-up, 6 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S36][S36] | The Guardian | Additional explosive drone recovered near Leipzig; report 25 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S37][S37] | Reuters | Germany attributes Leipzig attempted attack to Russian agencies, 1 September 2026 | Reference retained from prior research; not fully rechecked during export |
| [S38][S38] | Reuters | Drones sighted over western German military base, 8 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S39][S39] | Reuters | Drone explosion in Bulgaria, 8 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S40][S40] | Associated Press | Bulgarian drone crash near gas infrastructure, 8 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S41][S41] | Reuters | Italian NATO fighter downs drone in Latvia, 14 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S42][S42] | Reuters | Latvia identifies the 14 August drone as Ukrainian, 20 August 2026 | Reference retained from prior research; not fully rechecked during export |
| [S43][S43] | Antena 3 CNN / MApN / NATO | Spanish F-18 downs drone near Galați, 16 August 2026 | Relevant page/text rechecked during export |
| [S44][S44] | Romanian Ministry of National Defence | Press information: Grindu crash, 20 August 2026 | Relevant page/text rechecked during export |
| [S45][S45] | Romanian Ministry of National Defence | Press information: Gura Portiței recovery, 23 August 2026 | Relevant page/text rechecked during export |
| [S46][S46] | Forbes România / MApN | Ciușlea drone had no explosives, 24 August 2026 | Relevant page/text rechecked during export |
| [S47][S47] | Euronews România | Chronology of 8 September drone transit and crash in Moldova | Relevant page/text rechecked during export |
| [S48][S48] | Reuters | Suspected Russian drone recovered off Polish beach, 14 September 2026 | Reference retained from prior research; not fully rechecked during export |
| [S49][S49] | Reuters | Italian NATO fighter downs drone over Lithuania, overnight 14–15 September 2026 | Reference retained from prior research; not fully rechecked during export |
| [S50][S50] | Reuters | Lithuanian president on Gerbera drone and likely intended target, 16 September 2026 | Reference retained from prior research; not fully rechecked during export |
| [S51][S51] | AGERPRES / MApN | Neptun Deep maritime drone: one object, aircraft engagement followed by EOD, 20 August 2026 | Relevant page/text rechecked during export |
| [S52][S52] | Radio România Constanța | Olimp beach explosive-drone disposal, 26 August 2026 | Relevant page/text rechecked during export |
| [S53][S53] | Radio România / Rador | Olimp follow-up, 27 August 2026; incident was 26 August | Relevant page/text rechecked during export |
| [S54][S54] | HotNews | Shepherd discovers drone at Viișoara; 1 September 2026 | Relevant page/text rechecked during export |
| [S55][S55] | TVR | Viișoara explosive drone and disposal, 1 September 2026 | Relevant page/text rechecked during export |
| [S56][S56] | Digi24 / MApN | Tuzla explosive-drone debris: two detonations, 22 August 2026 | Relevant page/text rechecked during export |
| [S57][S57] | Digi24 | LPG ship crew describes attack by three drones, 21 July 2026 | Relevant page/text rechecked during export |
| [S58][S58] | Digi24 / Romanian maritime authorities | Bulk-carrier emergency: possible drone or mine, 24 July 2026 | Relevant page/text rechecked during export |
| [S59][S59] | Radio România Cluj / Romanian Naval Authority | Progress IV fire and rescue: event 27 August, report 28 August 2026 | Relevant page/text rechecked during export. Corrects the prior report’s 28 August event date to 27 August. Drone causation is not established by this report. |
| [S60][S60] | AGERPRES / Romanian Navy | Two Gerbera aerial drones found drifting near Neptun Deep, 11 August 2026 | Relevant page/text rechecked during export |
| [S61][S61] | Romanian Ministry of National Defence | Solca crash update, 24 September 2026 | Relevant page/text rechecked during export |
| [S62][S62] | Romanian Ministry of National Defence | Drone and sea-mine incident dashboard, updated 24 September 2026 | Relevant page/text rechecked during export. Official categories overlap and must not be summed. |
| [S63][S63] | Reuters via AOL | Baltic and Finnish drone chronology, 15 September 2026 | Relevant page/text rechecked during export. Syndication of S12; not independent corroboration. |
| [S64][S64] | Defence Industry Europe / Swedish Armed Forces | Swedish military statement; dates the encounter to 25 February 2026 | Relevant page/text rechecked during export. Date differs from the prior report, which used 26 February. One incident, not two. |
| [S65][S65] | RBC-Ukraine / Latvian State Police | Lake Drīdzis crash and explosion, 23 May 2026 | Relevant page/text rechecked during export |
| [S66][S66] | Reuters Connect | German government press conference on Leipzig attribution, 1 September 2026 | Relevant page/text rechecked during export |
| [S67][S67] | Reuters via AOL | Russian denial of German Leipzig attribution, 1 September 2026 | Relevant page/text rechecked during export |
| [S68][S68] | LinkedIn / author announcement | IISS European UAV-campaign research announcement | Reference retained from prior research; not fully rechecked during export. Prior-report context, not an event-level source or independently audited dataset. |
| [S69][S69] | Resilience Imperative | Summary of IISS UAV-campaign study, August 2024–February 2026 | Reference retained from prior research; not fully rechecked during export. Prior-report context; claimed 144-event total is multi-year, not a 2026 EU total. |
| [S70][S70] | Romanian Ministry of National Defence | Neptun Deep correction, 20 August 2026 | Relevant page/text rechecked during export |
| [S71][S71] | European Pravda / News.ro | Olimp discovery and separate Constanța casino debris find, 26 August 2026 | Relevant page/text rechecked during export |
| [S72][S72] | Digi24 | Shepherd account and professional disposal at Viișoara | Reference retained from prior research; not fully rechecked during export |
| [S73][S73] | Vaslui TV | Viișoara discovery; local provenance claim | Reference retained from prior research; not fully rechecked during export. Local attribution claim is not treated as an official identification. |
| [S74][S74] | European Pravda / News.ro / Romanian Naval Authority | Progress IV incident: impact mechanism unknown, 28 August 2026 | Relevant page/text rechecked during export |
| [S75][S75] | PortNews / Romanian Coast Guard | Progress IV sinking: event date, rescue and conflicting flag descriptions | Relevant page/text rechecked during export. Shipping-industry source distinguishes initial Dominican Republic reporting from a fleet listing indicating Dominica; flag is not independently resolved here. |
| [S76][S76] | Bulgarian News Agency (BTA) / Defence Ministry | Coastal UAV recovery and destruction missions, 26 August 2026, morning release | Relevant page/text rechecked during export |
| [S77][S77] | Bulgarian News Agency (BTA) / Defence Ministry | Four coastal recovery missions, 26 August 2026, afternoon release | Relevant page/text rechecked during export |
| [S78][S78] | The Sofia Globe / Bulgarian Defence Ministry | Kavarna, Kamchia and Chernomorets recovery reports, 27 August 2026 | Relevant page/text rechecked during export |
| [S79][S79] | The Sofia Globe / Bulgarian Defence Ministry | Sveti Ivan disposal and other coastal recoveries, 28 August 2026 | Relevant page/text rechecked during export |
| [S80][S80] | Bulgarian News Agency (BTA) / Defence Ministry | Shabla, Chernomorets and Ahtopol recoveries, 28 August 2026 | Relevant page/text rechecked during export |
| [S81][S81] | Bulgarian News Agency (BTA) | Defence minister on coastal drones: unarmed; most Russian-made, some Ukrainian/unidentified, 26 August 2026 | Relevant page/text rechecked during export. Campaign/cohort-level provenance assessment, not positive attribution of every individual object. |
| [S82][S82] | The Sofia Globe / Bulgarian Navy | Tyulenovo, Primorsko and Lozenets recoveries, 14 August 2026 | Relevant page/text rechecked during export |
| [S83][S83] | SofiaBeacon (secondary lead) | Kabakum report recalling two 22 August coastal debris recoveries | Relevant page/text rechecked during export. Lower-confidence source; used only to preserve the Albena/Kranevo and Rakitnika leads. Original official releases were not independently retrieved. |
| [S84][S84] | Radio România Actualități / MApN | Plauru discovery and Măcin Mountains wreckage, 14 August 2026 | Relevant page/text rechecked during export |
| [S85][S85] | RBC-Ukraine / MApN | Several Romanian discoveries on 14 August 2026 | Relevant page/text rechecked during export. Headline count is not converted into additional unidentified airframes. |
| [S86][S86] | The Romania Journal / MApN | Luncavița-area crash, 14 August 2026 | Relevant page/text rechecked during export |
| [S87][S87] | Informat.ro / MApN account | Plauru controlled disposal on 15 August, following 14 August discovery | Relevant page/text rechecked during export. Secondary follow-up; original disposal release not separately retrieved. |
| [S88][S88] | Romania Insider / MApN reporting | Costinești aerial-drone fragments recovered, 13 August 2026 | Relevant page/text rechecked during export |
| [S89][S89] | Informat.ro / contemporary Romanian reporting | Further Costinești fragment found, 14 August 2026 | Relevant page/text rechecked during export. Possible relationship to previous day’s object not established. |
| [S90][S90] | Informat.ro / contemporary Romanian reporting | Saturn beach fragment and related Costinești reporting, 14 August 2026 | Relevant page/text rechecked during export |
| [S91][S91] | Radio România Timișoara / MApN | Costinești report also describes overnight Chilia incursion, 13 August 2026 | Relevant page/text rechecked during export |
| [S92][S92] | CT100 / MApN | Aerial-drone fragment at Costinești: no pyrotechnic risk; prosecutor referral, 13 August 2026 | Relevant page/text rechecked during export. Headline says maritime drone, but the quoted MoD text explicitly identifies an aerial-drone fragment; classification follows the MoD text. |
| [S93][S93] | The Sofia Globe / Bulgarian Defence Ministry | Tsarevo–Varvara, Kamchia, Kabakum, Pomorie and Pasha Dere cases, 25–26 August 2026 | Relevant page/text rechecked during export |

## Link definitions

[S01]: https://www.reuters.com/world/drone-fell-onto-polish-military-base-january-28-radio-zet-reports-2026-02-02/
[S02]: https://newsweek.ro/actualitate/o-drona-ruseasca-intrat-spatiul-aerian-romaniei-doua-avioane-f-16-fost-ridicate-baza-fetesti
[S03]: https://apnews.com/article/c8905513cb9ade27176a88ef642411b7
[S04]: https://www.reuters.com/business/aerospace-defense/france-says-drone-incident-near-aircraft-carrier-would-be-provocation-if-russian-2026-02-27/
[S05]: https://www.reuters.com/world/europe/polish-police-say-drone-found-mine-western-poland-2026-03-12/
[S06]: https://www.reuters.com/world/drone-found-poland-likely-september-airspace-incursion-minister-says-2026-03-13/
[S07]: https://www.reuters.com/world/drone-that-crashed-lithuania-came-ukraine-lithuanian-pm-says-2026-03-24/
[S08]: https://www.reuters.com/world/europe/estonia-says-drone-enters-russia-hits-power-station-err-reports-2026-03-25/
[S09]: https://www.osw.waw.pl/en/publikacje/analyses/2026-03-25/baltic-states-respond-to-incidents-involving-ukrainian-drones
[S10]: https://kaitseministeerium.ee/en/news/joint-statement-ministers-defence-baltic-countries-drone-incidents
[S11]: https://www.reuters.com/world/finland-reports-suspected-territorial-violation-by-drones-2026-03-29/
[S12]: https://www.reuters.com/business/aerospace-defense/drone-incursions-sow-fear-chaos-along-natos-baltic-finnish-borders-2026-09-15/
[S13]: https://tvrinfo.ro/mapn-explica-de-ce-cele-doua-avioane-eurofighter-typhoon-ridicate-de-la-sol-n-au-putut-trage-in-drona-cazuta-in-galati/
[S14]: https://hotnews.ro/video-momentul-cand-drona-ruseasca-cu-explozibil-cazuta-la-galati-este-detonata-2229056
[S15]: https://hotnews.ro/drona-cazuta-in-judetul-tulcea-are-incarcatura-exploziva-va-fi-detonata-controlat-2229666
[S16]: https://www.digi24.ro/stiri/actualitate/o-drona-a-cazut-in-judetul-suceava-aproape-de-granita-cu-ucraina-autoritatile-fac-verificari-3754125
[S17]: https://www.mod.gov.lv/en/news/unmanned-aerial-vehicles-russia-enter-latvian-airspace-two-crash-within-national-territory
[S18]: https://www.reuters.com/world/two-drones-russia-crash-latvia-army-says-2026-05-07/
[S19]: https://www.reuters.com/world/greece-investigating-ukrainian-made-naval-drone-found-cave-island-2026-05-08/
[S20]: https://www.reuters.com/world/greek-probe-finds-suspected-ukrainian-sea-drone-lost-course-after-malfunction-2026-05-15/
[S21]: https://apnews.com/article/greece-ukraine-russia-sea-drone-c51b74a4472ab60411b330515eadf5e8
[S22]: https://www.reuters.com/world/suspected-ukrainian-military-drone-was-found-crashed-lithuania-2026-05-17/
[S23]: https://www.reuters.com/business/aerospace-defense/nato-jet-shoots-down-drone-estonia-news-website-delfi-reports-2026-05-19/
[S24]: https://en.wikipedia.org/wiki/2026_drone_incursions_into_the_Baltic_states_and_Finland
[S25]: https://apnews.com/article/aa90986c237b8fa1d9116685c8c32f95
[S26]: https://www.reuters.com/business/aerospace-defense/france-demand-explanation-russian-envoy-over-romania-drone-incident-2026-05-29/
[S27]: https://www.reuters.com/video/watch/idRW635705062026RP1/
[S28]: https://www.reuters.com/video/watch/idRW639705062026RP1/
[S29]: https://apnews.com/article/defc53b2383a67475230c8349a47d7c6
[S30]: https://www.reutersconnect.com/item/romania-detonates-russian-drone-fragments-found-near-border-with-ukraine/dGFnOnJldXRlcnMuY29tLDIwMjY6bmV3c21sX1JDMkI0TUFPQVZETQ
[S31]: https://www.reuters.com/business/aerospace-defense/romania-shoots-down-third-russian-drone-president-calls-breaches-intolerable-2026-07-26/
[S32]: https://en.wikipedia.org/wiki/2026_drone_incidents_in_Romania
[S33]: https://hotnews.ro/o-noua-alerta-de-drone-in-judetul-tulcea-doua-aeronave-f-16-au-fost-trimise-in-misiune-2315367
[S34]: https://www.reuters.com/world/german-police-examine-suspicious-object-leipzig-airport-2026-08-05/
[S35]: https://www.reuters.com/world/europe/plane-near-drone-found-german-airport-was-carrying-ammunition-media-reports-say-2026-08-06/
[S36]: https://www.theguardian.com/world/2026/aug/25/germany-drone-suspected-military-explosives-found-near-leipzig-airport
[S37]: https://www.reuters.com/world/europe/germany-says-russia-responsible-drone-attack-leipzig-airport-2026-09-01/
[S38]: https://www.reuters.com/world/drones-spotted-above-german-military-base-two-days-after-suspected-drone-attack-2026-08-08/
[S39]: https://www.reuters.com/world/bulgarias-radev-says-drone-exploded-bulgarias-airspace-2026-08-08/
[S40]: https://apnews.com/article/427dcc0875f5e416dadfee0c022f1cb4
[S41]: https://www.reuters.com/business/aerospace-defense/latvia-shoots-down-drone-its-airspace-finland-restricts-parts-baltic-sea-2026-08-14/
[S42]: https://www.reuters.com/business/aerospace-defense/latvia-says-drone-its-airspace-august-14-was-ukrainian-2026-08-20/
[S43]: https://www.antena3.ro/actualitate/o-drona-care-a-intrat-in-spatiul-aerian-al-romaniei-a-fost-doborata-de-un-avion-nato-in-apropiere-de-galati-799614.html
[S44]: https://www.mapn.ro/cpresa/19358_informa%C8%9Bie-de-presa
[S45]: https://www.mapn.ro/cpresa/19369_informa%C8%9Bie-de-presa
[S46]: https://www.forbes.ro/drona-ruseasca-prabusita-in-vrancea-la-doar-cinci-metri-de-o-locuinta-mapn-nu-avea-explozibil-517872
[S47]: https://www.euronews.ro/articole/cronologie-drona-care-a-survolat-romania-30-de-minute-si-a-cazut-in-republica-mol
[S48]: https://www.reuters.com/world/poland-finds-suspected-russian-drone-close-baltic-sea-beach-2026-09-14/
[S49]: https://www.reuters.com/business/aerospace-defense/nato-fighter-shoots-down-drone-lithuania-2026-09-14/
[S50]: https://www.reuters.com/business/aerospace-defense/drone-shot-down-lithuania-was-likely-aimed-ukraine-lithuanian-president-says-2026-09-16/
[S51]: https://agerpres.ro/social/2026/08/20/mapn-echipa-eod-a-fortelor-navale-a-neutralizat-o-drona-marina-din-zona-platformei-neptun-deep--1586518
[S52]: https://www.radioconstanta.ro/2026/08/26/update-drona-gasita-la-olimp-avea-incarcatura-exploziva-si-a-fost-detonata-controlat/
[S53]: https://www.rador.ro/2026/08/27/o-plaja-din-olimp-a-fost-evacuata-de-urgenta-dupa-ce-genistii-au-detonat-o-drona-cu-incarcatura-explozibila/
[S54]: https://hotnews.ro/un-cioban-a-gasit-drona-prabusita-in-vaslui-si-i-a-scos-firele-inainte-sa-vina-politia-tiuia-se-aprindeau-becuri-2338694
[S55]: https://tvrinfo.ro/vaslui-drona-cu-incarcatura-exploziva-cazuta-pe-un-teren-la-viisoara-cel-care-a-gasit-o-a-riscat-enorm/
[S56]: https://www.digi24.ro/stiri/actualitate/momentul-in-care-drona-gasita-la-tuzla-este-detonata-mapn-a-confirmat-ca-avea-incarcatura-exploziva-3917085
[S57]: https://www.digi24.ro/stiri/actualitate/primele-marturii-ale-echipajului-navei-lovite-pe-marea-neagra-trei-drone-ne-au-atacat-in-timpul-noptii-totul-era-distrus-3872177
[S58]: https://www.digi24.ro/stiri/actualitate/inca-o-nava-aflata-in-zona-economica-exclusiva-a-romaniei-a-transmis-un-apel-de-urgenta-dsu-posibil-impact-cu-o-drona-sau-mina-marina-3876501
[S59]: https://www.radiocluj.ro/2026/08/28/nava-comerciala-in-flacari-in-marea-neagra/
[S60]: https://agerpres.ro/english/2026/08/11/romanian-naval-forces-divers-destroy-two-drones-found-drifting-in-the-black-sea--1584137
[S61]: https://english.mapn.ro/cpresa/6871_update-%E2%80%93-press-release
[S62]: https://english.mapn.ro/
[S63]: https://www.aol.com/articles/drone-incursions-sow-fear-chaos-060621000.html
[S64]: https://defence-industry.eu/sweden-confirms-russian-drone-launched-near-french-carrier-charles-de-gaulle-was-detected-and-neutralised-in-malmo/
[S65]: https://newsukraine.rbc.ua/news/drone-explodes-after-crashing-into-lake-in-1779544681.html
[S66]: https://www.reutersconnect.com/item/germany-says-russia-responsible-for-drone-attack-at-leipzig-airport/dGFnOnJldXRlcnMuY29tLDIwMjY6bmV3c21sX1ZBOTQzNDAxMDkyMDI2UlAx
[S67]: https://www.aol.com/articles/russia-calls-germanys-leipzig-drone-190315000.html
[S68]: https://www.linkedin.com/posts/rexfoxoloughlin_im-very-excited-to-announce-the-publication-activity-7478400095181508608-KJWv
[S69]: https://www.resilienceimperative.com/items/iiss-report%3A-russia%27s-uav-campaign-over-europe-exposes-nato-air-defence-gaps
[S70]: https://www.mapn.ro/cpresa/19361_informa%C8%9Bie-de-presa---update
[S71]: https://www.eurointegration.com.ua/eng/news/2026/08/26/7244209/
[S72]: https://www.digi24.ro/stiri/actualitate/un-localnic-povesteste-cum-s-a-apucat-sa-demonteze-drona-cu-explozibil-gasita-in-vaslui-tiuia-se-aprindeau-becurile-am-scos-firele-3931021
[S73]: https://www.vasluitv.ro/video-drona-gasita-pe-un-camp-in-comuna-viisoara-zona-a-fost-izolata-iar-specialistii-sri-intervin-la-fata-locului/
[S74]: https://www.eurointegration.com.ua/eng/news/2026/08/28/7244354/index.amp
[S75]: https://en.portnews.ru/news/print/396155/
[S76]: https://www.bta.bg/en/news/bulgaria/1192191-bulgarian-navy-destroys-unmanned-aerial-vehicles-in-the-black-sea-region
[S77]: https://www.bta.bg/en/news/1192677-bulgarian-navy-retrieves-debris-of-unmanned-aerial-vehicles-from-black-sea-beac
[S78]: https://sofiaglobe.com/2026/08/27/more-drone-incidents-along-bulgarias-black-sea-coast/
[S79]: https://sofiaglobe.com/2026/08/28/bulgarian-navy-destroys-drone-found-near-sveti-ivan-island/
[S80]: https://www.bta.bg/en/news/1194192-bulgarian-navy-carries-out-reconnaissance-transport-of-objects-found-at-sea
[S81]: https://www.bta.bg/en/news/bulgaria/1192407-all-drones-along-black-sea-coast-were-unarmed-defence-minister-says
[S82]: https://sofiaglobe.com/2026/08/14/bulgarian-navy-responds-to-three-reports-of-drone-and-drone-parts-spotted-along-the-coast/
[S83]: https://bulgarianewsdaily.com/debris-found-near-kabakum-beach-in-varna/
[S84]: https://www.romania-actualitati.ro/news-in-english/ministry-of-national-defense-new-drone-discovered-in-tulcea-county-near-plauru-id232930.html
[S85]: https://newsukraine.rbc.ua/news/romania-finds-debris-from-fourth-drone-in-1786737796.html
[S86]: https://www.romaniajournal.ro/society-people/social/drone-crashes-in-northern-tulcea-near-ukrainian-border/
[S87]: https://informat.ro/en/current-affairs/drone-destroyed-by-controlled-detonation-in-tulcea-134950
[S88]: https://www.romania-insider.com/drone-fragments-costinesti-beach-aug-2026
[S89]: https://informat.ro/en/current-affairs/drone-fragment-discovered-at-costinesti-restricted-access-in-the-area-134794
[S90]: https://informat.ro/en/current-affairs/drone-fragments-found-on-the-beaches-of-saturn-and-costinesti-134880
[S91]: https://www.radiotimisoara.ro/administratie-politica/administratie-public/drona-descoperita-pe-plaja-din-costinesti-387032.html
[S92]: https://www.ct100.ro/ce-spune-armata-despre-drona-marina-gasita-in-costinesti/
[S93]: https://sofiaglobe.com/2026/08/26/drone-washes-up-on-cabacum-beach-near-bulgarias-varna/

---
End of consolidated register. No aggregate, follow-up article, disposal stage, or unresolved alert should be converted into an additional confirmed foreign-drone count without the reconciliation described above.