# EU foreign-drone events, 2026 — final deduplicated database update

**Coverage cutoff:** 24 September 2026. **Prepared:** 24 September 2026. **Format:** UTF-8 Markdown.  
**Baseline:** `eu_foreign_drone_events_2026_consolidated.md`, records E001–E084.  
**Purpose:** a final **supplement/update**, not a replacement full-year master register. The original files are unchanged.

## 1. Import this version

**Add the 27 rows in Section 2 to the event table.** They are distinct reported occurrences under the agreed **event/discovery date + normalized location** rule, after linking explicit follow-up stages. **All 15 discovery/recovery rows are accepted as events now**; an unknown original flight or unknown airframe history is not an import blocker.

This file supersedes the earlier supplement's merge instructions and the restrictive “root-incident” treatment in `eu_foreign_drone_events_2026_import_decisions.md`. It preserves every N001–N061 source record and adds N062–N063 for two separately reported beach finds uncovered while resolving N038.

If only E001–E084 are in your database, insert the applicable N-series rows. If any N-series rows are already imported, **update/upsert the same IDs instead of appending another copy**. Where your database uses its own IDs, match the occurrence date(s), country and normalized locality first. N038 is narrowed; N023 and N055 are moved to the event table, not copied into it while leaving duplicate daily rows behind.

| Section | Record class | Rows | Action |
| --- | --- | --- | --- |
| 2 | Event additions: 9 cross-border seizures, 15 discoveries/recoveries, 1 suspected-espionage episode, 2 specified military-UAV encounters | 27 | ADD_EVENT |
| 3 | Precautionary alerts / national response sequences | 3 | ADD_ALERT; keep out of confirmed-incursion counts |
| 4 | Daily activity summaries: 25 Greek-claimed airspace-violation dates and 7 FIR-only dates | 32 | ADD_DAILY_REPORT; not individual-event rows |
| 5 | Unidentified object not established to be a drone | 1 | KEEP_CANDIDATE |
| 6 | Aggregate / recurring-pattern records | 4 | KEEP_CONTEXT; never add aggregate totals to event rows |
| Total | 63 dated records plus 4 context records | 67 | One canonical detailed record per ID in Sections 2–6 |

**Event count is not airframe count or attribution confidence.** These 27 event additions include reported/provisional cases and unresolved-origin discoveries. One offshore recovery remains explicitly outside territorial waters. Filtering for confirmed foreign operators or sovereign-territory incursions is a separate database view; do not remove an otherwise distinct discovery merely because its attribution is unknown.

### Applied matching rules

Match the actual occurrence/discovery day, not the publication date. Normalize spellings and nearby administrative labels, but do not collapse clearly separate beach sites or police notifications. A same-day/same-place match is a candidate for merging, not an unconditional SQL uniqueness constraint: separate times or clearly separate episodes can distinguish events. Date ranges below either preserve an uncertain overnight boundary or link an explicitly documented discovery/interception with later recovery/disposal. The first date is the sorting anchor, not invented timestamp precision.

Multiple articles, multiple fragments, multiple detonations, and a later investigation correction about the same find remain one event. Separately reported locations/days stay separate unless the evidence explicitly links their stages. Source totals and daily bulletins remain separate from individual events.

**Comparison result:** none of the retained N-series occurrences was identified as a duplicate of an E-series occurrence in the supplied baseline. Most duplicate reporting/stages were already bundled in the supplement. The main corrections here are removing the airframe-based import hold, splitting the over-grouped coastal record, and extracting two specified encounters from the daily-report bucket—not manufacturing a smaller count by discarding distinct finds.

## 2. Event additions — import all 27 rows

`ADD_EVENT` means a distinct reported occurrence relative to the supplied E-series baseline under the rule above. The status and attribution columns retain allegations and uncertainty. Discovery/recovery events do **not** require a known parent flight or proof of a newly encountered airframe.

| Record ID | Import action | Record type | Date / period | Date start | Date end / linked stage | EU state(s) | Normalized locality | Date basis / linked dates | 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 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| N004 | ADD_EVENT | cross_border_seizure | 2026-01-27 (night; midnight boundary unspecified) | 2026-01-27 | 2026-01-28 | Lithuania | Purvėnai | Official release 28 January refers to Tuesday night; exact date on either side of midnight not supplied. | Purvėnai, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Border surveillance detected a quadcopter entering; drone and nearby cargo recovered after counter-drone intervention. Cargo: 1,000 Belarus-stamped packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | UAV forced down and cargo seized. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Not E027 (23 May, Dumblė). A001/NA001 are overlapping cumulative statistics, not duplicate event rows. | New finding; primary VSAT statement. | [L01][L01] |
| N005 | ADD_EVENT | cross_border_seizure | 2026-02-23–24 | 2026-02-23 | 2026-02-24 | Lithuania | Milvydai | Night interception followed by 24 February recovery; published 25 February. | Milvydai, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Belarus-border cargo interception; individual full flight track not publicly supplied. | Intercepted UAV lodged in a pine crown about 0.5 km from the border. Cargo: 500 packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Forestry personnel helped guards retrieve it on 24 February; seizure and administrative proceedings. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Tree interception and 24 February retrieval stay together. Not E027; A001/NA001 statistics are not additive. | New finding; primary VSAT statement. | [L02][L02] |
| N010 | ADD_EVENT | cross_border_seizure | 2026-04-05 (night; possible spill into 6 April) | 2026-04-05 | 2026-04-06 | Lithuania | Dubas | Sunday-night wording in release dated 7 April; later page update is not a second event. | Dubas, Varėna district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Thermal surveillance detected an inbound UAV; counter-drone action brought it down in nearby woodland. Cargo: 1,000 NZ Gold packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Drone and cargo seized; administrative proceedings. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. One overnight interception/recovery; page update is not another event. Not E027; A001/NA001 are statistics. | New finding; primary VSAT statement. | [L03][L03] |
| N011 | ADD_EVENT | cross_border_seizure | 2026-05-07 (predawn) | 2026-05-07 | 2026-05-07 | Lithuania | Krupaviesai | Thursday-morning operation, published 8 May. | Krupaviesai, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Counter-drone intervention brought the loaded UAV down into a field. Cargo: 850 Minsk Capital QS packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Broken UAV and cargo seized; described as the year’s 17th such interception. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Same date as E016/E017 but different countries/sites and circumstances. Not E027; included in A001/NA001 series. | New finding; primary VSAT statement. | [L04][L04] |
| N012 | ADD_EVENT | cross_border_seizure | 2026-06-14 | 2026-06-14 | 2026-06-14 | Lithuania | Daugidonys–Dimitrai | Sunday event reported Monday, 15 June. | Detection near Daugidonys; recovery in Dimitrai fields, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Guards detected an approaching cargo drone and used counter-drone equipment. Cargo: 200 NZ Gold packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Forced down, recovered and seized; administrative proceedings. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Detection near Daugidonys and recovery at Dimitrai are one linked episode. Separate from September N036. | New finding; LRT/ELTA reporting of VSAT account. | [L05][L05] |
| N015 | ADD_EVENT | suspected_espionage | 2026-07-15 (evening) | 2026-07-15 | 2026-07-15 | Germany | Munich — defence-manufacturer site | Flight and arrest on Wednesday, 15 July; Friday, 17 July is announcement/report date. | Munich defence-manufacturer site; KNDS named by Reuters security source | Arrest and espionage allegation; foreign sponsor unspecified | Suspected surveillance/espionage; defence-site drone flight; operator arrest | One reported drone; model not specified | 37-year-old Moldovan suspect; investigators alleged intelligence gathering for a foreign entity/prohibited organisation. No named sponsoring state established. | Local launch alleged; cross-border flight not alleged. Foreign link is the suspected espionage purpose, not manufacture. | Residents alerted police to a drone filming a weapons-manufacturer’s premises. | Not reported; no inference from disposal method. | Not reported in cited account. | Suspect arrested near site; warrant/remand announced 17 July. | Allegation, not conviction. Citizenship alone does not prove foreign-state direction; KNDS identification has a separate source attribution. | No matching baseline event. July Munich surveillance/arrest is distinct from August Leipzig E040 and western-Germany sightings E041. Foreign-intelligence purpose remains alleged. | New finding; ZDF plus Reuters-syndicated reports of police/prosecutor statements. | [D01][D01]; [D02][D02]; [D03][D03] |
| N023 | ADD_EVENT | reported_military_encounter | 2026-08-28 (morning) | 2026-08-28 | 2026-08-28 | Greece | Northern Aegean — Samothrace–Lemnos / Alexandroupoli-linked encounter | Encounter and reporting on 28 August; exact time not established here. | Northern Aegean, between Samothrace and Lemnos; related precaution near Alexandroupoli airport | Reported Turkish military UAV encounter; airspace violation attributed to the Greek account | Reported incursion; fighter identification/interception; civil-flight precaution | One reported UAV; model and exact crossing count unspecified | Turkish military UAV according to Greek reporting; legal characterization remains attributed, not independently adjudicated. | Reported flight between Samothrace and Lemnos and near the Alexandroupoli terminal area; exact track unpublished. | Greek account links the UAV encounter to a precaution during an Aegean passenger departure. | Not reported. | Passenger flight reportedly followed an alternative path/low-altitude precaution, then continued to Athens; no collision or casualty reported. | Two Greek F-16s reportedly identified/intercepted the UAV. No firing or shoot-down reported. | One linked encounter, not a separate incident for the airport precaution. No independent forensic attribution claimed. | No matching baseline event; E017 is the unrelated May Lefkada USV. One reported interception, including its Alexandroupoli civil-flight precaution. Reclassified from daily report, not duplicated there. | N023 reclassified from daily_report to encounter; original Euronews URL failed to reopen, but dated eKathimerini and AOL/Euronews reporting corroborate the event. | [G0828K][G0828K]; [G0828A][G0828A] |
| N028 | ADD_EVENT | discovery_recovery | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Burgas bridge / Pomorie Reef — offshore reported site | Operation 2 September; announced 3 September, later reprinted. | About 9 nautical miles opposite Burgas bridge / Pomorie Reef; reported Bulgarian coastal/territorial waters | Officially reported UAV recovery/disposal; operator unknown | Floating aerial-drone discovery; naval identification; in-situ destruction | UAV/object at one response site; model unspecified | No operator or national origin announced for this object. | Not established in cited account. | One of three Burgas-base offshore response sites in the Ministry’s six-task announcement. | Not reported; no inference from disposal method. | Not reported in cited account. | Navy identified the UAV and destroyed it at sea. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. A separately reported 2 September offshore response, not the 26 August Pomorie find E073. One site, not another row for the six-task headline. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B02][B02] |
| N029 | ADD_EVENT | discovery_recovery | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Cape Kaliakra — shore | Operation 2 September; announcement 3 September. | Cape Kaliakra seashore; Bulgarian coast | Reconnaissance UAV officially identified; origin unresolved | Shore discovery; reconnaissance-drone recovery | One reconnaissance UAV; model unspecified | Operator/manufacturer not announced. | Not established in cited account. | Naval personnel identified a shore find as a reconnaissance drone. | Not reported; no inference from disposal method. | Not reported in cited account. | Transported to Varna Naval Base. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. The 2 September Kaliakra shoreline recovery is distinct from the 6 September offshore operation N035. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B02][B02] |
| N030 | ADD_EVENT | discovery_recovery | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Cape Kolokita — waters | Operation 2 September; announced 3 September, later reprinted. | Cape Kolokita waters; reported Bulgarian coastal/territorial waters | Officially reported UAV recovery/disposal; operator unknown | Floating aerial-drone discovery; naval identification; in-situ destruction | UAV/object at one response site; model unspecified | No operator or national origin announced for this object. | Not established in cited account. | One of three Burgas-base offshore response sites in the Ministry’s six-task announcement. | Not reported; no inference from disposal method. | Not reported in cited account. | Navy identified the UAV and destroyed it at sea. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. Cape Kolokita response is a separately identified 2 September location in the same multi-task release. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B02][B02] |
| N031 | ADD_EVENT | discovery_recovery | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Maslen Nos — waters | Operation 2 September; announced 3 September, later reprinted. | Maslen Nos waters; reported Bulgarian coastal/territorial waters | Officially reported UAV recovery/disposal; operator unknown | Floating aerial-drone discovery; naval identification; in-situ destruction | UAV/object at one response site; model unspecified | No operator or national origin announced for this object. | Not established in cited account. | One of three Burgas-base offshore response sites in the Ministry’s six-task announcement. | Not reported; no inference from disposal method. | Not reported in cited account. | Navy identified UAV material and destroyed it at sea. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. Maslen Nos response is a separately identified 2 September location in the same multi-task release. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B02][B02] |
| N032 | ADD_EVENT | discovery_recovery | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Pomorie — town beach | Operation 2 September; Ministry announcement 3 September. | Pomorie town beach; Bulgarian territory | Military-drone fragments officially reported; operator unknown | Beach discovery; military-drone debris; naval response | Fragments; airframe count unknown | Unidentified military drone; operator unknown. | Not established in cited account. | Burgas naval personnel responded to fragments on the beach. | Not reported; no inference from disposal method. | Not reported in cited account. | Naval examination/response reported; final method not specified. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. 2 September Pomorie beach find is a different reported day/site from offshore E073 on 26 August and from N028. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B02][B02] |
| N035 | ADD_EVENT | discovery_recovery | 2026-09-06 (late afternoon) | 2026-09-06 | 2026-09-06 | Bulgaria | Cape Kaliakra — northeast coastal waters | Previous-afternoon operation in 7 September reports. | About 3.5 cables / 650 m northeast of Cape Kaliakra; coastal waters | Official retrieval reported; operator unresolved | Floating UAV discovery; naval recovery | One UAV; type unspecified | Origin/operator not announced. | Not established in cited account. | Varna naval team activated following an Interior Ministry request. | Reported safe for retrieval; detailed payload not published. | Not reported in cited account. | Assessed as safe and removed to the naval base. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. 6 September offshore retrieval is distinct from N029 on 2 September; 7 September articles are follow-ups, not new operations. | New finding; local reporting of official response; attribution limited to cited account. | [B04][B04]; [B05][B05] |
| N036 | ADD_EVENT | cross_border_seizure | 2026-09-06 (just after midnight) | 2026-09-06 | 2026-09-06 | Lithuania | Daugidonys | Night of 5–6 September; operation dated 6 September, report 7 September. | Daugidonys, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Guards intercepted a homemade loaded UAV during the Saturday–Sunday night. Cargo: 1,000 packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Drone and cargo seized; VSAT identified this as the year’s 55th. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Same locality as N012 but a separate September operation, not its June follow-up. Link to NA001 as a component, not an additional national total. | New finding; primary VSAT statement. | [L06][L06] |
| N038 | ADD_EVENT | discovery_recovery | 2026-09-09–10 | 2026-09-09 | 2026-09-10 | Romania | Capu Midia — beach | Discovery reported 9 September about 20:00; overnight cordon; Navy EOD response 10 September about 09:30. Dates describe stages, not two events. | Capu Midia beach, Constanța County; Romanian coast | Officially reported non-explosive aerial-drone-fragment discovery and disposal; origin unresolved | Beach discovery; overnight isolation; Navy EOD response | Aerial-drone fragments; number of parent aircraft unspecified | No confirmed operator or national provenance. | Not established in cited account. | Fragments reported around 20:00 on 9 September; area isolated overnight. | MApN reported no explosive charge. | Not reported in cited account. | Navy EOD responded around 09:30 on 10 September and neutralized the material. | Operator and original flight unknown. The separate 10 September police notifications at Mamaia Nord and Corbu are now N062 and N063, not aliases of this record. | No matching baseline event. Merge the 9 September Capu Midia discovery and 10 September disposal. Narrow old N038 to this chain; separate police-notified finds are N062/N063. | Carried from N038; Ministry chronology rechecked through Radio România. Conflicting place labels reconciled against separately timed police reports. | [R01][R01]; [R02][R02]; [R03][R03]; [R04][R04] |
| N063 | ADD_EVENT | discovery_recovery | 2026-09-10 | 2026-09-10 | 2026-09-10 | Romania | Corbu — beach | Police notification about 09:40 local time on 10 September; not a verified crash time. | Corbu beach, Constanța County; Romanian coast | Reported aerial-drone-fragment discovery; foreign origin unresolved | Beach discovery; police response; explosive-risk check; recovery | Drone fragments; aircraft count unspecified | Not established in the cited accounts. | Unknown; recovery is not proof of a same-day incursion. | Police received a separate beach-fragment notification at 09:40. | No explosive material reported after examination. | Not reported in the cited accounts. | Fragments examined and transferred to the Coast Guard / competent authorities. | Distinct reported find accepted by date/site; no claim of a unique airframe or identified operator. | No matching baseline event. Separate Corbu notification at 09:40 on 10 September; not the previous-evening Capu Midia discovery or the 08:30 Mamaia Nord report. | Separated during final reconciliation using the expanded R03 report and local reports R10/R11. | [R03][R03]; [R10][R10]; [R11][R11] |
| N062 | ADD_EVENT | discovery_recovery | 2026-09-10 | 2026-09-10 | 2026-09-10 | Romania | Mamaia Nord — beach | Police notification about 08:30 local time on 10 September; not a verified crash time. | Mamaia Nord beach, Constanța County; Romanian coast | Reported aerial-drone-fragment discovery; foreign origin unresolved | Beach discovery; police response; explosive-risk check; recovery | Drone fragments; aircraft count unspecified | Not established in the cited accounts. | Unknown; recovery is not proof of a same-day incursion. | Police received a separate beach-fragment notification at 08:30. | No explosive material reported after examination. | Not reported in the cited accounts. | Fragments examined and transferred to the Coast Guard / competent authorities. | Distinct reported find accepted by date/site; no claim of a unique airframe or identified operator. | No matching baseline event. Separate Mamaia Nord notification at 08:30 on 10 September; not the previous-evening Capu Midia discovery or the 09:40 Corbu report. | Separated during final reconciliation using the expanded R03 report and local reports R10/R11. | [R03][R03]; [R10][R10]; [R11][R11] |
| N040 | ADD_EVENT | discovery_recovery | 2026-09-11 (about 05:00 discovery) | 2026-09-11 | 2026-09-11 | Bulgaria | Kavatsi — beach | Event/discovery date; exact clock time not reported. | Kavatsi tourist beach, near Sozopol; Bulgarian territory | Military-type drone find reported; attribution and final assessment unresolved | Tourist/civilian discovery; beach recovery; security cordon | Drone body with damage; model unspecified | Reported military-type appearance, not a confirmed national/operator attribution. | Not established in cited account. | Tourists found the drone on the beach; specialists were summoned. | Not reported; no inference from disposal method. | Not reported in cited account. | Area secured; final disposal outcome not established in retrieved report. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. Kavatsi, 11 September, is not E081 (late-August Sveti Ivan/Sozopol pier); nearby municipal labels do not make those the same find. | New finding; local reporting of official response; attribution limited to cited account. | [B06][B06] |
| N043 | ADD_EVENT | discovery_recovery | 2026-09-11 | 2026-09-11 | 2026-09-11 | Romania | Câșla Vădanei — beach | 13:30 is response/assessment time, not a known crash time. | Câșla Vădanei, between Sulina and Sfântu Gheorghe, Tulcea; beach | Official aerial-drone fragment assessment; origin unknown | Beach discovery; washed-ashore fragments; EOD assessment | Two aerial-drone fragments; aircraft count unknown | No operator/national attribution in Ministry account. | Not established in cited account. | Two beached fragments assessed at 13:30. | No explosive charge found. | Not reported in cited account. | MApN EOD assessment found no explosive charge. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. One find/assessment at Câșla Vădanei on 11 September; two fragments do not create two rows. | New finding; local reporting of official response; attribution limited to cited account. | [R05][R05]; [R06][R06] |
| N044 | ADD_EVENT | recovery_cluster | 2026-09-11 | 2026-09-11 | 2026-09-11 | Romania | Edighiol–Periboina — coastal sector | 17:55 intervention entry; no established flight/crash dates. | Edighiol–Periboina, Constanța County; coastal sector | Official multi-aircraft recovery cluster; national origins unresolved | Helicopter-assisted search; multi-drone remains; interceptor-drone discovery; explosive disposal | Remains of FOUR aerial drones, including one interceptor drone | No operator/national attribution in cited MApN chronology. | Not established in cited account. | While checking a Coast Guard report, a helicopter-borne EOD team observed multiple wrecks; response listed at 17:55. | Explosives specifically reported aboard the interceptor drone. | Not reported in cited account. | All elements secured and neutralized. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. One dated Edighiol–Periboina recovery cluster; reported remains of four aircraft stay in quantity, not four invented event rows. | New finding; local reporting of official response; attribution limited to cited account. | [R05][R05]; [R07][R07] |
| N042 | ADD_EVENT | discovery_recovery | 2026-09-11 | 2026-09-11 | 2026-09-11 | Romania | Midia — 46 nautical miles east, offshore | 16:00 is the Ministry’s response chronology time. | Black Sea, about 46 nautical miles east of Midia; offshore/EEZ-related, outside territorial sea | Official offshore aerial-debris recovery; not sovereign-territory incursion | Commercial-vessel report; floating aerial-drone debris; Coast Guard recovery | Two aerial-drone fragments; not a maritime drone/USV | No operator/national attribution announced. | Not established in cited account. | Merchant ship reported fragments in the water; response listed at 16:00. | No pyrotechnic hazard identified. | Not reported in cited account. | Coast Guard patrol vessel recovered both. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. One 11 September offshore recovery; not August Neptun Deep E043/E047 and not the same-day beach sites N043–N045. Retain offshore scope tag. | New finding; local reporting of official response; attribution limited to cited account. | [R05][R05]; [R07][R07] |
| N045 | ADD_EVENT | discovery_recovery | 2026-09-11 | 2026-09-11 | 2026-09-11 | Romania | Periteașca — beach | 09:30 discovery; 15:18 intervention; flight date unknown. | Periteașca beach, Tulcea; Romanian territory | Official explosive debris recovery/disposal; origin unknown | Border-Police discovery; beach fragments; explosive neutralization | Two fragments; number of parent airframes unknown | No operator/national attribution announced. | Not established in cited account. | Border Police found two fragments around 09:30; intervention listed at 15:18. | Explosives confirmed in one fragment. | Not reported in cited account. | SRI bomb specialists neutralized the explosive item; Coast Guard took the other. | Flight/crash date, operator and link to other recovered airframes unresolved. | No matching baseline event. One Periteașca discovery/disposal chain; two fragments and two agencies are not two events. Not E049 at Gura Portiței on 23 August. | New finding; local reporting of official response; attribution limited to cited account. | [R05][R05]; [R06][R06] |
| N049 | ADD_EVENT | cross_border_seizure | 2026-09-13 (late evening) | 2026-09-13 | 2026-09-13 | Lithuania | Ūta–Versekėlė | Sunday operation; report 14 September. | Detection near Ūta; recovery at Versekėlė, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Counter-drone action disrupted the inbound UAV; it turned toward the border and crashed in a meadow roughly 500 m inside. Cargo: 200 Minsk Superslims packs and a GPS device. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Guards recovered the broken drone within about an hour and opened administrative proceedings. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Ūta detection and Versekėlė recovery are explicitly one interception episode. Not a separate event for each village. | New finding; primary VSAT statement. | [L07][L07] |
| N052 | ADD_EVENT | discovery_recovery | 2026-09-16 (13:06 report) | 2026-09-16 | 2026-09-16 | Lithuania | Keneliai — Pasvalys district forest | Discovery/report 16 September, police follow-up 17 September; not evidence of a flight that day. | Keneliai village forest, Pasvalys district; Lithuanian territory | Drone recovery; foreign origin unproven; later smuggling-investigation link | Civilian/forest discovery; old wreckage; bomb-squad check; police correction | One old/overgrown drone; not identified as a Russian or Ukrainian strike UAV | Police later associated it with a smuggling investigation; foreign origin not publicly established. | Not established in cited account. | A drone apparently lying in vegetation for months was reported to police. | No explosives found, according to follow-up. | Not reported in cited account. | ARAS/military explosive-risk response; police said no explosives and updated the investigation on 17 September. | Initial speculation about a foreign military drone was not confirmed by the later police account. | No matching baseline event. 16 September Keneliai/Pasvalys find is not May Utena E019 or September Pratkūnai E058. Merge the 17 September police correction into this recovery. | New finding; local reporting of official response; attribution limited to cited account. | [L10][L10]; [L11][L11] |
| N053 | ADD_EVENT | cross_border_seizure | 2026-09-16 (shortly after midnight) | 2026-09-16 | 2026-09-16 | Lithuania | Norviliškės | Tuesday–Wednesday night; dated 16 September. | Norviliškės, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Thermal imaging detected a UAV with rectangular cargo entering from Belarus. Cargo: 1,000 NZ Gold packs. | Cigarette cargo; explosive payload not reported. | No casualty or third-party damage reported; UAV seized/damaged as described. | Counter-drone action forced it down; drone/cargo seized, administrative proceedings; year’s 57th. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Norviliškės is a separately dated 16 September seizure; not the 13 September N049 or 21–22 September N059. | New finding; primary VSAT statement. | [L08][L08] |
| N055 | ADD_EVENT | reported_military_encounter | 2026-09-18 | 2026-09-18 | 2026-09-18 | Greece | Zourafa — islet overflight | Reported overflight on 18 September, described in same-day Greek daily reporting; exact time unspecified. | Zourafa islet, northeastern Aegean; UAV overflight location reported by Greece | Greek-reported Turkish UAV overflight of a named islet | Reported military UAV overflight; claimed airspace violation | One reported UAV overflight; model unspecified. Five UAVs appeared in wider daily activity, not five overflights at this site. | Turkish UAV according to the Greek military account relayed by Politica; no independent track verification here. | Reported overflight of Zourafa; complete route unspecified. | The Greek account distinguishes a UAV over Zourafa from a manned F-16 formation over Ro. Only the UAV overflight is the event here. | Not reported. | No UAV impact or casualty reported in the cited account. | Specific operational response to this overflight not detailed in the reopened source. | Wider daily totals: five UAVs among ten aircraft, 13 FIR infringements and seven airspace violations across mixed aircraft. Drone-only infringement totals are unspecified; the earlier nine/five subdivision is not carried forward. | No matching baseline event. Retain one specific Zourafa UAV overflight; the Ro F-16 overflight is manned and excluded. Mixed daily statistics remain context inside this row, not additional events. | N055 narrowed to its dated, named-location UAV overflight. G0918 reopened; unsupported drone-only daily subdivisions removed. | [G0918][G0918] |
| N059 | ADD_EVENT | cross_border_seizure | 2026-09-21–22 | 2026-09-21 | 2026-09-22 | Lithuania | Liškūniškės–Antaniškės | 21–22 September night; discovery 22 September; report 23 September. | Detection at Liškūniškės; recovery near Antaniškės, Šalčininkai district; Lithuanian border area | Officially reported cross-border smuggling-drone incident | Cross-border entry; electronic interception; forced descent/crash; cargo seizure | One homemade/cargo UAV; model unspecified | Smugglers operating from/across the Belarus border according to VSAT; operator nationality and state sponsorship not established. | Reported approach from Belarus; criminal cargo operation, not a military strike. | Inbound UAV descended after counter-drone action; guards found the damaged, scorched craft about 800 m from the border the next morning. Cargo: 1,000 Minsk Superslims packs. | Cigarette cargo; explosive payload not reported. | Drone impact and fire damage reported; no reported third-party casualties. | Cargo survived; UAV and cigarettes seized, administrative proceedings; year’s 58th. | Official criminal/border-enforcement account; not evidence of a foreign-state attack. | No matching baseline event. Liškūniškės detection and Antaniškės next-morning recovery form one episode. NA001 counts the same seizure within 58; do not add 58 again. | New finding; primary VSAT statement. | [L09][L09] |

## 3. Related alerts — three separate response records

These are distinct response occurrences, not established incursions into the responding country. Store as alerts, or in the same physical table with `Record type = precautionary_alert`; do not present them as confirmed intruding drones. Repeated warnings within one response sequence are already merged.

| Record ID | Import action | Record type | Date / period | Date start | Date end / linked stage | EU state(s) | Normalized locality | Date basis / linked dates | 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 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| N046 | ADD_ALERT | precautionary_alert | 2026-09-11 (04:15–06:30) | 2026-09-11 | 2026-09-11 | Romania | Northern Tulcea — Vylkove-adjacent alert | Response on 11 September, approximately 04:15–06:30 local time; warning about 04:36. Not a drone crash/discovery time. | Targets near Vylkove, Ukraine; warnings for northern Tulcea, Romania | ADJACENT ALERT: MApN said no national-airspace penetration | Near-border aerial detection; RO-Alert; fighter scramble | Aerial targets/drone-related threat; quantity not established | Associated with attacks near Ukraine border; individual UAV identity not established. | No confirmed entry into Romania. | Targets detected roughly 16 km north of Vylkove; warning issued around 04:36. | Not established. | Not reported in cited account. | Two F-16s scrambled from Borcea; alert ended about 06:30. | No evidential link supplied between this alert and coastal wreckage recovered later the same day. | No matching baseline response. Northern Tulcea alert on 11 September is not E084 on 27 August. No evidence links it to later same-day beach recoveries. | New finding; local reporting of official response; attribution limited to cited account. | [R08][R08] |
| N050 | ADD_ALERT | precautionary_alert | 2026-09-15 | 2026-09-15 | 2026-09-15 | Poland | Poland — national precautionary activation | Precautionary Polish activation reported on 15 September; precise patrol location and time not supplied. | Polish national air-defence response to strikes in Ukraine; exact patrol areas unpublished | PRECAUTIONARY ACTIVATION: no Polish airspace violation reported | Fighter activation; adjacent-war protective response | No confirmed intruding drone | Preventive response to Russian strikes on Ukraine; no individual Polish intruder established. | No confirmed entry into Poland. | Polish military announced a brief precautionary aviation operation. | Not applicable to a proven Polish intruder. | Not reported in cited account. | Air-defence aviation activated; no violation reported. | Not a drone incursion, crash or shoot-down in Poland. | No matching baseline response. National Polish activation on 15 September is not E057 sea recovery on 14 September and not Lithuanian E058. | New finding; local reporting of official response; attribution limited to cited account. | [R09][R09] |
| N051 | ADD_ALERT | precautionary_alert | 2026-09-15 (03:10–05:18) | 2026-09-15 | 2026-09-15 | Romania | Northern Tulcea — Chilia/Periprava-adjacent alert | One response sequence on 15 September, approximately 03:10–05:18 local time; warnings at 03:18 and 04:51. | Ukraine-side targets north of Chilia/Periprava; northern Tulcea warnings | ADJACENT ALERT: no Romanian airspace violation reported | Near-border detection; two warning stages; fighter scramble | Several aerial targets; not an established number of intruding UAVs | Threat associated with Russian strikes in Ukraine; individual identity unspecified. | Targets remained outside national airspace in official account. | Target around 03:10, further targets around 04:20; warnings at 03:18 and 04:51. | Not established. | Not reported in cited account. | Two F-16s activated; alert ended 05:18. | Response record only; no Romanian incursion reported. | No matching baseline response. One Romanian alert sequence with two warnings on 15 September, not two incursions or Lithuanian E058. | New finding; local reporting of official response; attribution limited to cited account. | [R09][R09] |

## 4. Daily activity reports — 32 reporting dates, not individual events

These rows retain the remaining 25 Greek-claimed national-airspace-violation dates and seven FIR-only reporting dates. They are distinct dated **reports**, not a synthetic event for every aircraft appearance or crossing. N023 (28 August) and N055 (18 September) are **not repeated here**: their specified encounters are in Section 2. Wider 18 September mixed-aircraft statistics are retained as context in N055.

Greek-reported violations are attributed claims. The Greek and Turkish foreign ministries set out differing positions on Aegean national-airspace limits in [G00][G00] and [T00][T00]. An Athens FIR traffic-rule infringement is not by itself proof of a sovereign-airspace incursion. Manned-aircraft figures are not treated as UAV counts, and identification/interception does not imply firing or a shoot-down. Original daily subdivisions are retained unless a targeted recheck identified a correction; this pass did not independently re-audit every daily bulletin.

| Record ID | Import action | Record type | Date / period | Date start | Date end / linked stage | EU state(s) | Normalized locality | Date basis / linked dates | 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 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| N001 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-01-13 | 2026-01-13 | 2026-01-13 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 1 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 1. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. The five reported national-airspace violations were by F-16s, not the UAV. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0113][G0113] |
| N002 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-01-15 | 2026-01-15 | 2026-01-15 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 1 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 3; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. CN-235 FIR infringements excluded. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0115][G0115] |
| N003 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-01-17 | 2026-01-17 | 2026-01-17 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean; precise tracks not supplied; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 5; drone-only FIR infringements: 4. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0117][G0117] |
| N006 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-03-02 | 2026-03-02 | 2026-03-02 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 4; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0302][G0302] |
| N007 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-03-05 | 2026-03-05 | 2026-03-05 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 1 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 1. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Reported national-airspace violations were assigned to F-16/ATR aircraft; this is the UAV FIR component only. Secondary-source-only entry. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0305][G0305] |
| N008 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-03-10 | 2026-03-10 | 2026-03-10 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 1 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: Not separately quantified; FIR flight without filed plan reported. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Reported on 11 March about 10 March; six national violations were assigned to a CN-235, not the UAV. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0310][G0310] |
| N009 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-03-26 | 2026-03-26 | 2026-03-26 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Southeastern Aegean / Athens FIR; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Nine national violations were attributed to F-16/CN-235 aircraft. UAVs account for three FIR infringements, not those nine crossings. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0326][G0326] |
| N013 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-06-17 | 2026-06-17 | 2026-06-17 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: 4. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Five further national violations were assigned to an ATR-72, not included here. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0617][G0617] |
| N014 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-06-23 | 2026-06-23 | 2026-06-23 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean / Athens FIR; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 5. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Six national violations and fighter engagements were assigned to manned aircraft, not UAVs. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0623][G0623] |
| N016 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-10 | 2026-08-10 | 2026-08-10 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 12; drone-only FIR infringements: Not separated: four combined with an ATR-72. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Four is the mixed-aircraft FIR total; it is not assigned wholesale to the two UAVs. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0810][G0810] |
| N017 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-17 | 2026-08-17 | 2026-08-17 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 3 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 6; drone-only FIR infringements: 5. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. The CN-235 accounts for the other six national violations and one FIR infringement in the mixed totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0817][G0817] |
| N018 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-08-22 | 2026-08-22 | 2026-08-22 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 2. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. FIR infringements only; do not relabel as national-airspace incursions. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | UAVs identified; no kinetic engagement or shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0822][G0822] |
| N019 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-23 | 2026-08-23 | 2026-08-23 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: 2. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0823][G0823] |
| N020 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-24 | 2026-08-24 | 2026-08-24 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 6 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 8; drone-only FIR infringements: 9. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0824][G0824] |
| N021 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-25 | 2026-08-25 | 2026-08-25 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 3; drone-only FIR infringements: 8. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Contemporaneous breakdown is three national and eight UAV FIR infringements; some next-day retrospectives incorrectly conflate these counts. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0825][G0825] |
| N022 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-26 | 2026-08-26 | 2026-08-26 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 5 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 6; drone-only FIR infringements: 7. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. The mixed total of 13 national violations also includes seven by a CN-235. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0826][G0826] |
| N024 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-29 | 2026-08-29 | 2026-08-29 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: 2. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0829][G0829] |
| N025 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-30 | 2026-08-30 | 2026-08-30 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Central Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 3 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 1; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0830][G0830] |
| N026 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-08-31 | 2026-08-31 | 2026-08-31 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 3 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Within NA004 January–August coverage; do not add that aggregate. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0831][G0831] |
| N027 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-01 | 2026-09-01 | 2026-09-01 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 5; drone-only FIR infringements: 6. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0901][G0901] |
| N034 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-02 | 2026-09-02 | 2026-09-02 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 5; drone-only FIR infringements: 5. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. CN-235 contributes six further national violations and one FIR infringement, excluded from UAV figures. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0902][G0902] |
| N037 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-07 | 2026-09-07 | 2026-09-07 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 4; drone-only FIR infringements: Not separated in retrieved account; five mixed-aircraft total. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Reported fighter engagement is not evidence that either UAV was fired upon. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0907][G0907] |
| N039 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-10 | 2026-09-10 | 2026-09-10 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: Not separated in retrieved account; eight mixed-aircraft total. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Other seven national violations were assigned to an ATR, not the four UAVs. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0910][G0910] |
| N041 | ADD_DAILY_REPORT | fir_only_daily_report | 2026-09-11 | 2026-09-11 | 2026-09-11 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean / Athens FIR; Athens FIR / Greek-claimed national airspace as specified | FIR-ONLY RELATED ACTIVITY: no UAV sovereign-airspace violation established | Military UAV flight; FIR traffic-rule infringement | 3 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 0; drone-only FIR infringements: 7. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Reported 12 September about 11 September. Ten national violations and two fighter engagements concerned F-16s, not the UAVs. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0911][G0911] |
| N047 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-12 | 2026-09-12 | 2026-09-12 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 5; drone-only FIR infringements: 8. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0912][G0912] |
| N048 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-13 | 2026-09-13 | 2026-09-13 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 3 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 4; drone-only FIR infringements: 5. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0913][G0913] |
| N054 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-17 | 2026-09-17 | 2026-09-17 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 1 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 1; drone-only FIR infringements: 3. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0917][G0917] |
| N056 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-19 | 2026-09-19 | 2026-09-19 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 4 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 4; drone-only FIR infringements: 5. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0919][G0919] |
| N057 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-20 | 2026-09-20 | 2026-09-20 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/central/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 6 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 6; drone-only FIR infringements: 7. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0920][G0920] |
| N058 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-21 | 2026-09-21 | 2026-09-21 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Northeastern/southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 2 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 1; drone-only FIR infringements: 2. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. One of the two UAVs was assigned the national-airspace violation; ATR FIR statistics excluded. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0921][G0921] |
| N060 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-22 | 2026-09-22 | 2026-09-22 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Aegean; detailed tracks unpublished; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 5 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 3; drone-only FIR infringements: 9. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. National violations assigned to two of five UAVs; two ATR aircraft excluded from drone totals. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0922][G0922] |
| N061 | ADD_DAILY_REPORT | claimed_airspace_daily_report | 2026-09-23 | 2026-09-23 | 2026-09-23 | Greece | Aegean / Athens FIR — daily reporting area | Operational date in report/bulletin; publication may be the following day where source says so. | Southeastern Aegean; Athens FIR / Greek-claimed national airspace as specified | Greek-reported Turkish military UAV airspace violation(s) | Reported incursion; military UAV overflight; identification/interception | 7 UAV(s) reported; model unspecified. Drone-only national-airspace violations: 2; drone-only FIR infringements: 7. | Turkish military UAVs according to Greek reporting. The legal airspace characterization is attributed to Greece. | Not reconstructed; an Athens FIR infringement alone does not prove entry into sovereign airspace. | One dated operational bulletin/encounter; manned-aircraft statistics excluded from drone totals. Original bulletin says 23 September. Some syndications erroneously retain a 22 September header; they are not another record. | Model-specific armament/explosive payload not established; no inference from archive photographs. | No UAV strike, shoot-down or casualty reported in cited bulletin. | Greek account reports identification/interception under standing procedures; no shoot-down reported. | Figures are official Greek allegations reported in the source. See Greek/Turkish legal-position notes; no public track-by-track adjudication here. | No matching baseline report; E017 is the unrelated Lefkada USV. One daily reporting date; retain aircraft/crossing figures as reported, not one event per crossing. Outside the January–August period of NA004; no aggregate-membership claim is made. | New finding; drone-only figures separated from manned aircraft in cited Greek reporting. | [G0923][G0923] |

## 5. Unidentified-object candidate — not a drone-event addition

This record is not a duplicate. It stays outside the drone-event table because drone identity was not established in the collected evidence.

| Record ID | Import action | Record type | Date / period | Date start | Date end / linked stage | EU state(s) | Normalized locality | Date basis / linked dates | 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 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| N033 | KEEP_CANDIDATE | unidentified_object | 2026-09-02 | 2026-09-02 | 2026-09-02 | Bulgaria | Topola — beach | 2 September task, announced 3 September. | Topola beach, Dobrich; Bulgarian territory | RELATED OBJECT: identity not established | Suspicious shore object; naval recovery | One cone-shaped object; not confirmed UAV | Unknown; foreign origin unproven. | Not established in cited account. | Object included in the Navy’s six-task response announcement. | Not reported; no inference from disposal method. | Not reported in cited account. | Taken to Varna Naval Base. | Shape alone does not establish drone identity. | No matching baseline candidate. Topola, 2 September, differs from Tyulenovo E065 on 14 August. Identity, not duplication, keeps it outside drone-event totals. | New finding; local reporting of official response; attribution limited to cited account. | [B01][B01]; [B03][B03] |

## 6. Aggregate and pattern context — four non-additive records

Keep statistics as dated snapshots or pattern reports. Do not turn an aggregate into individual events, add already itemized episodes on top of the cumulative total, or use a publication day as the date of every underlying flight. NA001 is a later snapshot of the series represented by baseline A001, not a replacement that erases the earlier snapshot.

| Aggregate ID | Import action | EU state | Period / reporting date | What the source reports | Counting and evidentiary limitation | Sources |
| --- | --- | --- | --- | --- | --- | --- |
| NA001 | UPDATE_AGGREGATE_SERIES | Lithuania | 2026-01-01 through official release 2026-09-23 | 58 smuggling drones intercepted by VSAT in 2026; previous year 59. | Retain as the 23 September snapshot of the same VSAT series as baseline A001. The nine dated seizures and baseline E027 are component detail, not additions on top of 58. Unknown missing individual events are not synthesized. | [L09][L09] |
| NA002 | KEEP_CONTEXT | Cyprus | 2026-01-01–2026-02-28; submission reported 2026-03-30 | Cyprus reported 305 mixed airspace/FIR violations, including 81 involving Turkish military UAVs. | Cypriot allegation circulated to the UN, not a UN verification. Drone-specific dates/tracks in annex S/2026/240 were not individually extracted here. Do not count 305 as drones or 81 as 81 independently verified sovereign-airspace entries. | [C01][C01]; [C02][C02] |
| NA003 | KEEP_CONTEXT | Cyprus | Recurring activity described 2026-09-01; individual flight dates not supplied | Air-traffic-controller representative alleged near-daily Turkish UAV activity affecting Larnaca/Paphos flight paths, sometimes up to five UAVs simultaneously. | Attributed recurring-pattern report, not a single dated September 1 near-collision. May overlap NA002 or other unitemized activity; exact tracks and Turkish response not supplied in source. | [C03][C03] |
| NA004 | KEEP_CONTEXT | Greece | 2026-01-01–2026-08-31 | To Vima reported 276 UAV appearances/activity entries, including 102 in August and 30 in July. | Reported January–August aggregate, not unique aircraft or incursions. Overlaps applicable January–August daily rows and N023; September records, including N055, are outside this period. Do not sum this figure with its component records. | [G99][G99] |

## 7. Changes and deduplication audit

### Changes to previously imported N-series rows

| Record(s) | Final action | Reason | Evidence / comparison |
| --- | --- | --- | --- |
| N028–N032, N035, N038, N040, N042–N045, N052 | UPDATE TYPE → ADD_EVENT | All 13 previously held recovery records are accepted as dated occurrences. No proof of unique airframes is required. N038 is also narrowed as explained below. | Same dated source rows; compared against E001–E084. |
| N038 | UPDATE EXISTING ROW | Retain only the Capu Midia 9 September discovery and 10 September disposal. Do not merge it with the independently timed 10 September Mamaia Nord/Corbu notifications. | [R01][R01]; [R03][R03]; [R04][R04] |
| N062; N063 | ADD_EVENT — TWO NEW IDS | Add Mamaia Nord (10 September, notification 08:30) and Corbu (10 September, notification 09:40) as separate reported finds. Same coast is not same locality. Airframe relationship remains irrelevant to occurrence-level inclusion. | [R03][R03]; [R10][R10]; [R11][R11] |
| N023 | MOVE daily_report → event; KEEP SAME ID | The Samothrace–Lemnos interception is a specific encounter. Its Alexandroupoli departure precaution is a linked effect, not another event. Original URL failed to reopen; dated alternative reporting supports it. | [G0828K][G0828K]; [G0828A][G0828A] |
| N055 | MOVE daily_report → event; NARROW TO ZOURAFA | Keep one reported Zourafa UAV overflight. The separate Ro overflight involved manned F-16s. The reopened source supplies only mixed-aircraft violation totals; remove the unsupported drone-only nine-FIR/five-airspace subdivision. | [G0918][G0918] |
| N046; N051 | UPDATE DATE-BASIS TEXT | Remove the contradictory template assertion that no clock times were reported. Keep the response time windows already present, as response times rather than crash times. | [R08][R08]; [R09][R09] |
| Other N-series rows | KEEP ID; APPLY ACTION IN THIS FILE | Retain the evidence, but replace older root-incident/airframe counting restrictions with the occurrence-level actions above. No N001–N061 ID is silently omitted. | Source references in each canonical row. |

### Merged stages, same-source repeats and tempting false matches

| Records / reports | Final treatment | Evidence |
| --- | --- | --- |
| N005 | Interception and next-day retrieval from the pine tree are one episode. | [L02][L02] |
| N012; N036 | Keep June and September Daugidonys operations separate; merge the June detection/recovery locations within N012. | [L05][L05]; [L06][L06] |
| N049; N059 | Each detection-village / recovery-village pair is one tracked episode. Do not insert each village as another incident. | [L07][L07]; [L09][L09] |
| N028–N033 | The six-task Bulgarian release reports separate 2 September sites; its 3/4/6 September publications are not more operations. Five drone-related rows and one unidentified-object candidate are preserved. | [B01][B01]; [B02][B02]; [B03][B03] |
| N029; N035 | Keep 2 September Kaliakra shore find and 6 September offshore retrieval as separate responses. The 7 September article is not a third operation. | [B01][B01]; [B04][B04]; [B05][B05] |
| N032 versus E073 | Different dates and beach/offshore settings; no source establishes one response. Keep separate. | [B01][B01]; baseline E073 |
| N038 / N062 / N063 | Capu Midia: discovery then disposal merged. Mamaia Nord and Corbu: separate 10 September police notifications retained. Broad Corbu wording in R04 does not override distinct dated evidence. | [R01][R01]; [R03][R03]; [R04][R04]; [R10][R10] |
| N042–N045 | Four separately named 11 September response areas remain four events. The four-aircraft Edighiol–Periboina quantity stays in N044, and Periteașca discovery/disposal remains N045. | [R05][R05]; [R06][R06]; [R07][R07] |
| N052 | 16 September forest discovery and 17 September police correction are one record. It is not May Utena E019 or September Pratkūnai E058. | [L10][L10]; [L11][L11] |
| N050; N051 | Polish and Romanian precautionary responses on the same day are distinct national response records; neither is another Lithuanian shoot-down E058. | [R09][R09]; baseline E058 |
| N021; N061 | Retain the supplement’s 25 August category correction and 23 September operational date rather than misleading retrospective subdivisions/publication headers. | [G0825][G0825]; [G0923][G0923] |
| B07 versus E081 | The supplement already identified this 1 September kayaker article as retrospective coverage of the late-August Sozopol find. No new N-series event is created from that article. | [B07][B07]; baseline E081 |
| A001 / NA001 / detailed seizures | Component records and a national aggregate are not competing duplicate incidents. Store both at their respective levels; do not add their numbers together. | [L09][L09]; baseline A001/E027 |

### Already in the baseline — not re-added by this update

The specifically requested cases remain in the original register: Neptun Deep aerial recoveries on 11 August (E043), Neptun Deep maritime-drone intervention on 20 August (E047), Tuzla on 22 August (E048), Olimp on 26 August (E052), and the Viișoara shepherd discovery on 1 September (E054). They are baseline records, not missing additions in this delta. Their full evidence and linked stages remain in the original file. This update neither deletes them nor inserts a second copy.

## 8. Compact import manifest and matching keys

The manifest below is an index to Sections 2–5, **not another set of rows to import**. A key is `country::occurrence-date-or-range::normalized-locality`. It helps matching; the stable N-series ID is the repeat-import key. Do not treat a date-only key as proof that two demonstrably distinct episodes are the same. No two canonical N-series rows below share a full key.

| Record ID | Import action | Record type | Match key | Canonical data section |
| --- | --- | --- | --- | --- |
| N001 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-01-13::aegean-athens-fir-daily-reporting-area | 4 |
| N002 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-01-15::aegean-athens-fir-daily-reporting-area | 4 |
| N003 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-01-17::aegean-athens-fir-daily-reporting-area | 4 |
| N004 | ADD_EVENT | cross_border_seizure | LT::2026-01-27..2026-01-28::purvenai | 2 |
| N005 | ADD_EVENT | cross_border_seizure | LT::2026-02-23..2026-02-24::milvydai | 2 |
| N006 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-03-02::aegean-athens-fir-daily-reporting-area | 4 |
| N007 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-03-05::aegean-athens-fir-daily-reporting-area | 4 |
| N008 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-03-10::aegean-athens-fir-daily-reporting-area | 4 |
| N009 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-03-26::aegean-athens-fir-daily-reporting-area | 4 |
| N010 | ADD_EVENT | cross_border_seizure | LT::2026-04-05..2026-04-06::dubas | 2 |
| N011 | ADD_EVENT | cross_border_seizure | LT::2026-05-07::krupaviesai | 2 |
| N012 | ADD_EVENT | cross_border_seizure | LT::2026-06-14::daugidonys-dimitrai | 2 |
| N013 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-06-17::aegean-athens-fir-daily-reporting-area | 4 |
| N014 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-06-23::aegean-athens-fir-daily-reporting-area | 4 |
| N015 | ADD_EVENT | suspected_espionage | DE::2026-07-15::munich-defence-manufacturer-site | 2 |
| N016 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-10::aegean-athens-fir-daily-reporting-area | 4 |
| N017 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-17::aegean-athens-fir-daily-reporting-area | 4 |
| N018 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-08-22::aegean-athens-fir-daily-reporting-area | 4 |
| N019 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-23::aegean-athens-fir-daily-reporting-area | 4 |
| N020 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-24::aegean-athens-fir-daily-reporting-area | 4 |
| N021 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-25::aegean-athens-fir-daily-reporting-area | 4 |
| N022 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-26::aegean-athens-fir-daily-reporting-area | 4 |
| N023 | ADD_EVENT | reported_military_encounter | GR::2026-08-28::northern-aegean-samothrace-lemnos-alexandroupoli-linked-encounter | 2 |
| N024 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-29::aegean-athens-fir-daily-reporting-area | 4 |
| N025 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-30::aegean-athens-fir-daily-reporting-area | 4 |
| N026 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-08-31::aegean-athens-fir-daily-reporting-area | 4 |
| N027 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-01::aegean-athens-fir-daily-reporting-area | 4 |
| N028 | ADD_EVENT | discovery_recovery | BG::2026-09-02::burgas-bridge-pomorie-reef-offshore-reported-site | 2 |
| N029 | ADD_EVENT | discovery_recovery | BG::2026-09-02::cape-kaliakra-shore | 2 |
| N030 | ADD_EVENT | discovery_recovery | BG::2026-09-02::cape-kolokita-waters | 2 |
| N031 | ADD_EVENT | discovery_recovery | BG::2026-09-02::maslen-nos-waters | 2 |
| N032 | ADD_EVENT | discovery_recovery | BG::2026-09-02::pomorie-town-beach | 2 |
| N033 | KEEP_CANDIDATE | unidentified_object | BG::2026-09-02::topola-beach | 5 |
| N034 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-02::aegean-athens-fir-daily-reporting-area | 4 |
| N035 | ADD_EVENT | discovery_recovery | BG::2026-09-06::cape-kaliakra-northeast-coastal-waters | 2 |
| N036 | ADD_EVENT | cross_border_seizure | LT::2026-09-06::daugidonys | 2 |
| N037 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-07::aegean-athens-fir-daily-reporting-area | 4 |
| N038 | ADD_EVENT | discovery_recovery | RO::2026-09-09..2026-09-10::capu-midia-beach | 2 |
| N039 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-10::aegean-athens-fir-daily-reporting-area | 4 |
| N063 | ADD_EVENT | discovery_recovery | RO::2026-09-10::corbu-beach | 2 |
| N062 | ADD_EVENT | discovery_recovery | RO::2026-09-10::mamaia-nord-beach | 2 |
| N040 | ADD_EVENT | discovery_recovery | BG::2026-09-11::kavatsi-beach | 2 |
| N041 | ADD_DAILY_REPORT | fir_only_daily_report | GR::2026-09-11::aegean-athens-fir-daily-reporting-area | 4 |
| N043 | ADD_EVENT | discovery_recovery | RO::2026-09-11::casla-vadanei-beach | 2 |
| N044 | ADD_EVENT | recovery_cluster | RO::2026-09-11::edighiol-periboina-coastal-sector | 2 |
| N042 | ADD_EVENT | discovery_recovery | RO::2026-09-11::midia-46-nautical-miles-east-offshore | 2 |
| N046 | ADD_ALERT | precautionary_alert | RO::2026-09-11::northern-tulcea-vylkove-adjacent-alert | 3 |
| N045 | ADD_EVENT | discovery_recovery | RO::2026-09-11::periteasca-beach | 2 |
| N047 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-12::aegean-athens-fir-daily-reporting-area | 4 |
| N048 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-13::aegean-athens-fir-daily-reporting-area | 4 |
| N049 | ADD_EVENT | cross_border_seizure | LT::2026-09-13::uta-versekele | 2 |
| N050 | ADD_ALERT | precautionary_alert | PL::2026-09-15::poland-national-precautionary-activation | 3 |
| N051 | ADD_ALERT | precautionary_alert | RO::2026-09-15::northern-tulcea-chilia-periprava-adjacent-alert | 3 |
| N052 | ADD_EVENT | discovery_recovery | LT::2026-09-16::keneliai-pasvalys-district-forest | 2 |
| N053 | ADD_EVENT | cross_border_seizure | LT::2026-09-16::norviliskes | 2 |
| N054 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-17::aegean-athens-fir-daily-reporting-area | 4 |
| N055 | ADD_EVENT | reported_military_encounter | GR::2026-09-18::zourafa-islet-overflight | 2 |
| N056 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-19::aegean-athens-fir-daily-reporting-area | 4 |
| N057 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-20::aegean-athens-fir-daily-reporting-area | 4 |
| N058 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-21::aegean-athens-fir-daily-reporting-area | 4 |
| N059 | ADD_EVENT | cross_border_seizure | LT::2026-09-21..2026-09-22::liskuniskes-antaniskes | 2 |
| N060 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-22::aegean-athens-fir-daily-reporting-area | 4 |
| N061 | ADD_DAILY_REPORT | claimed_airspace_daily_report | GR::2026-09-23::aegean-athens-fir-daily-reporting-area | 4 |

## 9. Evidence boundary and source register

This is a deduplication and import reconciliation of the supplied files, with targeted external checks of ambiguous entries. **It is not a new exhaustive EU-wide search, a forensic identification of every drone, or a full factual re-audit of the original 84-row register.** It also does not certify an unseen external database: the comparison baseline is the supplied E001–E084 file. Investigation status means the status in the collected account, not a guarantee that no later development exists.

For this final pass, the Capu Midia/Corbu/Mamaia Nord material was reopened and expanded (R01/R03/R04, plus R10/R11), the Bulgarian six-task account was reopened (B01), the 28 August Greek encounter was corroborated through alternative reporting (G0828K/G0828A), and the Zourafa account was reopened (G0918). Other factual details and source links were carried from the supplied supplement and prior reconciliation. Newly checking multiple outlets that repeat an official statement does not amount to independent physical corroboration.

Source IDs are preserved for traceability. The 70 existing source-register entries remain, including duplicate-check/context references; four additional references support this reconciliation. The original Euronews link is retained as provenance but is not the sole support for N023. Descriptive English labels below do not adopt publishers’ editorial characterizations.

| Source ID | Publisher / authority | Publication or scope date | Source and audit note |
| --- | --- | --- | --- |
| L01 | Lithuanian State Border Guard Service (VSAT) | 2026-01-28 | [Cargo drone intercepted near Purvėnai][L01]. Primary official account; weekday wording retained rather than inventing an exact clock time. |
| L02 | VSAT | 2026-02-25 | [Forestry staff help retrieve a cigarette-carrying drone from a pine tree][L02]. Primary official account; interception and next-day tree recovery are one record. |
| L03 | VSAT | 2026-04-07; later updated 2026-05-04 | [Drone carrying cigarettes from Belarus intercepted near Dubas][L03]. Primary official account. Page update is not a second event. |
| L04 | VSAT | 2026-05-08 | [Cargo drone crashes after counter-drone intervention near Krupaviesai][L04]. Primary official account. |
| L05 | LRT / ELTA | 2026-06-15 | [Sunday border-guard interception of a cigarette-carrying drone][L05]. Public broadcaster carrying an official border-service account. |
| L06 | VSAT | 2026-09-07 | [Cargo drone intercepted near Daugidonys][L06]. Primary official account. |
| L07 | VSAT | 2026-09-14 | [Smuggling drone crashes near the Belarus border][L07]. Primary official account; detection at Ūta and recovery at Versekėlė are one track. |
| L08 | VSAT | 2026-09-16 | [Drone and 1,000 packs of cigarettes seized near Norviliškės][L08]. Primary official account. |
| L09 | VSAT | 2026-09-23 | [Intercepted drone burns, cigarette cargo survives][L09]. Primary official account; discovery on 22 September. Also supplies the non-additive annual total of 58. |
| L10 | Lrytas | 2026-09-17 | [Police update on the drone found in a Pasvalys district forest][L10]. Follow-up correction links the object to a smuggling investigation, not an established foreign military incursion. |
| L11 | Lrytas | 2026-09-16 | [Fallen drone discovered in Pasvalys district][L11]. Initial discovery account; read with next-day correction L10. |
| R01 | Radio România | 2026-09-10 | [MApN: Drone fragments neutralized at Capu Midia beach][R01]. Public broadcaster reporting Romanian Defence Ministry statement. |
| R02 | Radio Oltenia | 2026-09-10 | [Drone remains neutralized at Capu Midia][R02]. Specifies 9 September discovery and 10 September response. |
| R03 | Focus Press | 2026-09-10 | [Three coastal discovery reports: Capu Midia, Mamaia Nord and Corbu][R03]. Reopened for this reconciliation: the earlier URL redirects here. The article reports distinct police notifications at Mamaia Nord (10 September, 08:30) and Corbu (09:40), in addition to the 9 September Capu Midia find and next-day disposal. |
| R04 | Financial Intelligence | 2026-09-10 | [Corbu-labelled coverage repeating the Capu Midia Ministry chronology][R04]. Reopened for this reconciliation. Its 9 September 20:00 / 10 September 09:30 chronology supports N038; its broad Corbu label is not by itself evidence of a separate event. The independent Corbu police notification is N063, supported by R03/R10/R11. |
| R05 | Radio România Internațional | 2026-09-11 | [Drone fragments found in Constanța and Tulcea counties][R05]. Reproduces the MApN four-location intervention chronology, with times. |
| R06 | Observator News | 2026-09-11 | [Drone fragments, some explosive, found on the coast; MApN account][R06]. Additional reporting of the same Ministry chronology, not independent physical verification. |
| R07 | Adevărul | 2026-09-11 | [Defence Ministry report on coastal drone discoveries][R07]. Additional coverage of the 11 September recovery operations. |
| R08 | Digi24 | 2026-09-11 | [Targets near Vylkove prompt F-16 monitoring and Romanian border alert][R08]. MApN said no Romanian airspace penetration; related response, not an incursion. |
| R09 | The Sofia Globe | 2026-09-15 | [Romania and Poland scramble fighter jets over drone incidents][R09]. Both national accounts explicitly say no national airspace violation; two national response records, not two proven drone tracks. |
| B01 | The Sofia Globe | 2026-09-03 | [Bulgarian Navy responds to several more drone incidents][B01]. Defence Ministry announcement covers SIX tasks performed on 2 September: five drone-related locations and one unidentified cone-shaped object. |
| B02 | Petel | 2026-09-04 | [Bulgarian Navy six-task coastal and maritime response account][B02]. Local-language coverage of the same Ministry announcement; publication date is not a new incident date. |
| B03 | Direktno | 2026-09-06 | [Six naval tasks on the Black Sea: established facts and open questions][B03]. Retrospective corroboration of locations and uncertainty; not six additional September 6 events. |
| B04 | Darik News | 2026-09-07 | [Navy retrieves a drone from the Black Sea near Kaliakra][B04]. Reports response on the previous afternoon, 6 September. |
| B05 | OFFNews | 2026-09-07 | [Drone found afloat near Cape Kaliakra][B05]. Additional reporting of the same retrieval, not another event. |
| B06 | Eurocom / Bulgaria ON AIR reporting | 2026-09-11 | [Military-type drone washes up on Kavatsi beach][B06]. Discovery and security response; operator, payload and final disposal not established in the retrieved account. |
| B07 | Flagman | 2026-09-01 | [Kayaker account of a drone found near Sozopol][B07]. Duplicate-check source only: retrospective late-August discovery associated with baseline E081, not a newly counted 1 September event. |
| D01 | ZDFheute | 2026-07-17 | [Moldovan man arrested in Munich on suspicion of espionage][D01]. Police/prosecutor account; allegations are not a conviction. |
| D02 | Reuters via Onvista | 2026-07-17 | [Warrant against Moldovan suspect over alleged espionage at KNDS][D02]. KNDS identification attributed to Reuters security source, not an unqualified named-site police finding. |
| D03 | Reuters via MarketScreener | 2026-07-17 | [Germany arrests Moldovan over suspected drone espionage at KNDS][D03]. Specifies Wednesday evening, 15 July, rather than treating Friday publication as flight date. |
| C01 | Cyprus Mail | 2026-03-30 | [Cyprus reports Turkish airspace, FIR and territorial-water violations][C01]. Cypriot submission concerning January–February. Aggregate only; not independently verified by the UN. |
| C02 | SigmaLive | 2026-03-30 | [Cyprus reports Turkish violations to UN Security Council][C02]. Additional reporting of the same submission, S/2026/240. The annex was not extracted into individual records here. |
| C03 | Knews / Kathimerini Cyprus | 2026-09-01 | [Turkish drones disrupting flight paths near Larnaca and Paphos][C03]. Attributed statements by air-traffic-controller representative; undated recurring pattern, not a new individually timed September 1 encounter. |
| G00 | Greek Ministry of Foreign Affairs | Current official position accessed 2026-09-24 | [National airspace: Greek position][G00]. Primary statement of Greece’s 10-nautical-mile Aegean airspace claim. |
| T00 | Turkish Ministry of Foreign Affairs | Current official position accessed 2026-09-24 | [Background note on the Aegean dispute][T00]. Primary Turkish objection to Greece’s 10-mile airspace claim beyond a 6-mile territorial sea and to FIR-based sovereignty arguments. |
| G99 | To Vima | 2026; covers January–August | [The drone activity tally discussed in To Vima][G99]. 276 reported UAV appearances/activity entries, including 102 in August and 30 in July; do not reinterpret as 276 unique aircraft or individual sovereign-airspace incursions. |
| G0113 | Dimokratiki / Greek military figures | 2026-01-13 | [Turkish UAV activity reported for 2026-01-13][G0113]. Greek military figures as reported; not an independent adjudication of disputed airspace. The five reported national-airspace violations were by F-16s, not the UAV. |
| G0115 | OnAlert / GEETHA bulletin | 2026-01-15 | [Turkish UAV activity reported for 2026-01-15][G0115]. Greek military figures as reported; not an independent adjudication of disputed airspace. CN-235 FIR infringements excluded. |
| G0117 | CretaOne / Greek military figures | 2026-01-17 | [Turkish UAV activity reported for 2026-01-17][G0117]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0302 | OnAlert / GEETHA bulletin | 2026-03-02 | [Turkish UAV activity reported for 2026-03-02][G0302]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0305 | Athens Times / reported Greek breakdown | 2026-03-05 | [Turkish UAV activity reported for 2026-03-05][G0305]. Greek military figures as reported; not an independent adjudication of disputed airspace. Reported national-airspace violations were assigned to F-16/ATR aircraft; this is the UAV FIR component only. Secondary-source-only entry. |
| G0310 | Greek City Times / Greek military account | 2026-03-10 | [Turkish UAV activity reported for 2026-03-10][G0310]. Greek military figures as reported; not an independent adjudication of disputed airspace. Reported on 11 March about 10 March; six national violations were assigned to a CN-235, not the UAV. |
| G0326 | Athens Times / reported Greek breakdown | 2026-03-26 | [Turkish UAV activity reported for 2026-03-26][G0326]. Greek military figures as reported; not an independent adjudication of disputed airspace. Nine national violations were attributed to F-16/CN-235 aircraft. UAVs account for three FIR infringements, not those nine crossings. |
| G0617 | OnAlert / GEETHA bulletin | 2026-06-17 | [Turkish UAV activity reported for 2026-06-17][G0617]. Greek military figures as reported; not an independent adjudication of disputed airspace. Five further national violations were assigned to an ATR-72, not included here. |
| G0623 | Athens Times / reported Greek breakdown | 2026-06-23 | [Turkish UAV activity reported for 2026-06-23][G0623]. Greek military figures as reported; not an independent adjudication of disputed airspace. Six national violations and fighter engagements were assigned to manned aircraft, not UAVs. |
| G0810 | Newsit / GEETHA | 2026-08-10 | [Turkish UAV activity reported for 2026-08-10][G0810]. Greek military figures as reported; not an independent adjudication of disputed airspace. Four is the mixed-aircraft FIR total; it is not assigned wholesale to the two UAVs. |
| G0817 | Newsbomb / GEETHA | 2026-08-17 | [Turkish UAV activity reported for 2026-08-17][G0817]. Greek military figures as reported; not an independent adjudication of disputed airspace. The CN-235 accounts for the other six national violations and one FIR infringement in the mixed totals. |
| G0822 | OnAlert / GEETHA bulletin | 2026-08-22 | [Turkish UAV activity reported for 2026-08-22][G0822]. Greek military figures as reported; not an independent adjudication of disputed airspace. FIR infringements only; do not relabel as national-airspace incursions. |
| G0823 | OnAlert / GEETHA bulletin | 2026-08-23 | [Turkish UAV activity reported for 2026-08-23][G0823]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0824 | OnAlert / GEETHA bulletin | 2026-08-24 | [Turkish UAV activity reported for 2026-08-24][G0824]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0825 | SDNA / Newsit / reproduced GEETHA bulletin | 2026-08-25 | [Turkish UAV activity reported for 2026-08-25][G0825]. Greek military figures as reported; not an independent adjudication of disputed airspace. Contemporaneous breakdown is three national and eight UAV FIR infringements; some next-day retrospectives incorrectly conflate these counts. |
| G0826 | OnAlert / GEETHA bulletin | 2026-08-26 | [Turkish UAV activity reported for 2026-08-26][G0826]. Greek military figures as reported; not an independent adjudication of disputed airspace. The mixed total of 13 national violations also includes seven by a CN-235. |
| G0828 | Euronews / Greek military account | 2026-08-28 | [Greek F-16s intercept Turkish drone over northern Aegean][G0828]. Original supplement link; reopening returned a cache miss in this pass. N023 was instead corroborated with eKathimerini and a dated AOL syndication of the Euronews report (G0828K/G0828A). |
| G0829 | OnAlert / GEETHA bulletin | 2026-08-29 | [Turkish UAV activity reported for 2026-08-29][G0829]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0830 | OnAlert / GEETHA bulletin | 2026-08-30 | [Turkish UAV activity reported for 2026-08-30][G0830]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0831 | OnAlert / GEETHA bulletin | 2026-08-31 | [Turkish UAV activity reported for 2026-08-31][G0831]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0901 | OnAlert / GEETHA bulletin | 2026-09-01 | [Turkish UAV activity reported for 2026-09-01][G0901]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0902 | CNN Greece / GEETHA | 2026-09-02 | [Turkish UAV activity reported for 2026-09-02][G0902]. Greek military figures as reported; not an independent adjudication of disputed airspace. CN-235 contributes six further national violations and one FIR infringement, excluded from UAV figures. |
| G0907 | Proto Thema / Greek military figures | 2026-09-07 | [Turkish UAV activity reported for 2026-09-07][G0907]. Greek military figures as reported; not an independent adjudication of disputed airspace. Reported fighter engagement is not evidence that either UAV was fired upon. |
| G0910 | Ekriti / Greek military figures | 2026-09-10 | [Turkish UAV activity reported for 2026-09-10][G0910]. Greek military figures as reported; not an independent adjudication of disputed airspace. Other seven national violations were assigned to an ATR, not the four UAVs. |
| G0911 | Military Press / reported Greek breakdown | 2026-09-11 | [Turkish UAV activity reported for 2026-09-11][G0911]. Greek military figures as reported; not an independent adjudication of disputed airspace. Reported 12 September about 11 September. Ten national violations and two fighter engagements concerned F-16s, not the UAVs. |
| G0912 | OnAlert / GEETHA bulletin | 2026-09-12 | [Turkish UAV activity reported for 2026-09-12][G0912]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0913 | OnAlert / GEETHA bulletin | 2026-09-13 | [Turkish UAV activity reported for 2026-09-13][G0913]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0917 | OnAlert / GEETHA bulletin | 2026-09-17 | [Turkish UAV activity reported for 2026-09-17][G0917]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0918 | Politica / Greek military breakdown | 2026-09-18 | [Greek account of UAV overflight at Zourafa and mixed daily aircraft activity][G0918]. Reopened. Identifies a UAV over Zourafa and five UAVs in the wider daily activity; 13 FIR infringements and seven national-airspace violations are mixed-aircraft totals. Does not provide the earlier supplement’s claimed drone-only nine/five subdivision. |
| G0919 | Capital.gr / Greek military figures | 2026-09-19 | [Turkish UAV activity reported for 2026-09-19][G0919]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0920 | CNN Greece / GEETHA | 2026-09-20 | [Turkish UAV activity reported for 2026-09-20][G0920]. Greek military figures as reported; not an independent adjudication of disputed airspace. |
| G0921 | OnAlert / GEETHA bulletin | 2026-09-21 | [Turkish UAV activity reported for 2026-09-21][G0921]. Greek military figures as reported; not an independent adjudication of disputed airspace. One of the two UAVs was assigned the national-airspace violation; ATR FIR statistics excluded. |
| G0922 | Newsit / GEETHA | 2026-09-22 | [Turkish UAV activity reported for 2026-09-22][G0922]. Greek military figures as reported; not an independent adjudication of disputed airspace. National violations assigned to two of five UAVs; two ATR aircraft excluded from drone totals. |
| G0923 | OnAlert / GEETHA bulletin | 2026-09-23 | [Turkish UAV activity reported for 2026-09-23][G0923]. Greek military figures as reported; not an independent adjudication of disputed airspace. Original bulletin says 23 September. Some syndications erroneously retain a 22 September header; they are not another record. |
| R10 | Cuget Liber | 2026-09-10 | [Two separately timed beach-fragment notifications at Mamaia Nord and Corbu][R10]. Newly checked for reconciliation; local reporting, explicitly referring to unofficial sources. Neither reported find contained explosives. |
| R11 | Replica Online | 2026-09-10 | [Mamaia Nord beach recovery and separate Corbu police notification][R11]. Newly checked. The lead loosely says about 09:00; the quoted notification chronology gives 08:30 for Mamaia Nord and 09:40 for Corbu. Its Alezzi micro-location is outlet-specific, not used as the canonical matching site. |
| G0828K | eKathimerini | 2026-08-28 | [Greek account of Turkish UAV interception between Samothrace and Lemnos][G0828K]. Newly checked; links the encounter with the Alexandroupoli departure precaution, rather than describing another incident. |
| G0828A | AOL / Euronews syndication | 2026-08-28 | [Dated syndication of Greek F-16 interception report][G0828A]. Newly checked alternative to the original Euronews link; same encounter, not independent proof of another drone. |

## 10. File provenance and reconciliation checks

| Check | Result |
| --- | --- |
| Baseline examined | 84 distinct E-series IDs, E001–E084 |
| Original supplemental dated IDs accounted for | All 61, N001–N061 |
| Newly allocated IDs | N062 Mamaia Nord; N063 Corbu |
| Canonical event additions | 27 |
| Canonical related alerts | 3 |
| Canonical daily reports | 32 |
| Canonical unidentified-object candidates | 1 |
| Canonical aggregate/pattern records | 4 |
| Total canonical detailed records in Sections 2–6 | 67 = 63 dated + 4 context |
| Duplicate full N-series matching keys | 0 |
| Confirmed N-to-E occurrence duplicates found | 0 in this supplied-file comparison |
| Original input files | Unchanged |

Input SHA-256 digests identify the exact comparison versions:

| Input file | SHA-256 |
| --- | --- |
| eu_foreign_drone_events_2026_consolidated.md | 4ca03b0096d3150eaa9293a1ca1dbb2175392a7fd5adb52d59ca69210c10c892 |
| eu_foreign_drone_events_2026_new_findings.md | f430bb0799908720e6b64c32a5ded0a366787bde4c2340dee44d2034d6b60011 |
| eu_foreign_drone_events_2026_import_decisions.md | d712caa3d9183cfc88ce60add03d7f8d0433b760f8a0d4aff6f0acaf06343340 |

## Link definitions

[L01]: https://vsat.lrv.lt/lt/naujienos/baltarusijos-pasienyje-vsat-pareigunai-nutupde-cigaretes-skraidinusi-kontrabandininku-drona-foto-video-Bs2/
[L02]: https://vsat.lrv.lt/lt/naujienos/uredui-padedant-pasienieciai-is-pusies-virsunes-iskele-nutupdyta-drona-su-baltarusiskomis-cigaretemis-foto-cgH/
[L03]: https://vsat.lrv.lt/lt/naujienos/pasienieciai-pereme-dar-viena-is-baltarusijos-rukalus-skraidinusi-drona-video-foto-wTh/
[L04]: https://vsat.lrv.lt/lt/naujienos/pasienieciams-panaudojus-antidrona-kontrabandininku-skraidykle-su-kroviniu-teskesi-i-zeme-foto-uPP/
[L05]: https://www.lrt.lt/naujienos/lietuvoje/2/2961328/sekmadieni-vsat-pareigunai-nutupde-kontrabandines-cigaretes-skraidinusi-drona
[L06]: https://vsat.lrv.lt/lt/naujienos/baltarusijos-pasienyje-vsat-pareigunai-pereme-kontrabandininku-drona-su-kroviniu-foto-P2j/
[L07]: https://vsat.lrv.lt/lt/naujienos/pasienyje-su-baltarusija-avarija-patyre-kontrabandininku-dronas-gabenes-cigaretes-foto-J9M/
[L08]: https://vsat.lrv.lt/lt/naujienos/juodoji-rinka-prarado-1-000-pakeliu-cigareciu-ir-juos-gabenusi-kontrabandininku-drona-foto-bSR/
[L09]: https://vsat.lrv.lt/lt/naujienos/pasienieciu-nutupdytas-dronas-uzsidege-bet-baltarusiskos-cigaretes-isliko-foto-QXq/
[L10]: https://www.lrytas.lt/lietuvosdiena/aktualijos/2026/09/17/news/pasvalio-r-miske-radus-drona-naujausia-policijos-zinai-del-tyrimo-44044686
[L11]: https://www.lrytas.lt/lietuvosdiena/aktualijos/2026/09/16/news/pasvalio-raj-rastas-nukrites-dronas-44018042
[R01]: https://www.radioromania.ro/Actualitate/mapn-fragmente-de-drona-neutralizate-in-zona-plajei-de-la-capu-midia-id216948.html
[R02]: https://www.radiooltenia.ro/resturi-de-drona-neutralizate-la-capu-midia/
[R03]: https://focuspress.ro/alerta-la-constanta-resturi-de-drona-gasite-in-mai-multe-zone-inclusiv-la-corbu-si-mamaia-nord-49ab7a5ed/
[R04]: https://financialintelligence.ro/fragment-de-drona-gasit-pe-plaja-de-la-corbu-nu-avea-incarcatura-exploziva-fiind-neutralizat-la-fata-locului/
[R05]: https://www.rri.ro/actualitate/stiri/fragmente-de-drone-gasite-in-judetele-constanta-si-tulcea-id1058610.html
[R06]: https://observatornews.ro/eveniment/fragmente-de-drone-unele-cu-incarcatura-exploziva-gasite-pe-litoral-reactia-mapn-665968.html
[R07]: https://adevarul.ro/stiri-interne/evenimente/ministerul-apararii-nationale-in-stare-de-alerta-2557004.html
[R08]: https://www.digi24.ro/amphtml/stiri/actualitate/alerta-la-granita-romaniei-tinte-aeriene-detectate-langa-valcove-f-16-ridicate-pentru-monitorizare-3943395
[R09]: https://sofiaglobe.com/2026/09/15/romania-poland-scramble-fighter-jets-over-drone-incidents/
[B01]: https://sofiaglobe.com/2026/09/03/bulgarian-navy-responds-to-several-more-drone-incidents/
[B02]: https://petel.bg/m/667593
[B03]: https://direktno.bg/article/shest-zadachi-na-vms-po-chernomorieto-kakvo-e-potvyrdeno-i-kakvo-ostava-neyasno
[B04]: https://dariknews.bg/novini/bylgariia/otkriha-dron-v-cherno-more-vms-go-iztegliha-2465810
[B05]: https://offnews.bg/112/dron-izpluva-kraj-nos-kaliakra-874215.html
[B06]: https://eurocom.bg/2026/09/11/voenen-dron-izpluva-na-plazh-kavatsi-spetsializirani-sili-ohranyavat-rayona/
[B07]: https://www.flagman.bg/article/389012
[D01]: https://www.zdfheute.de/politik/deutschland/muenchen-spionage-mann-moldau-100.html
[D02]: https://www.onvista.de/news/2026/07-17-spionageverdacht-bei-panzerbauer-knds-haftbefehl-gegen-moldauer-0-20-26533395
[D03]: https://de.marketscreener.com/boerse-nachrichten/deutschland-nimmt-moldauer-wegen-mutmasslichem-spionage-drohnenflug-ueber-ruestungshersteller-knds-fest-ce7f51dad88ef221
[C01]: https://cyprus-mail.com/2026/03/30/cyprus-reports-new-turkish-violations-of-airspace-fir-territorial-waters
[C02]: https://en.sigmalive.com/cyprus-reports-turkish-violations-to-un-security-council/
[C03]: https://knews.kathimerini.com.cy/en/news/turkish-drones-disrupting-flight-paths-near-larnaca-and-paphos
[G00]: https://www.mfa.gr/en/foreign-policy/foreign-policy-issues/issues-of-greek-turkish-relations/national-airspace/
[T00]: https://www.mfa.gov.tr/background-note-on-aegean-dispute.en.mfa
[G99]: https://www.tovima.gr/print/politics/i-damokleios-spathi-ton-drones
[G0113]: https://www.dimokratiki.gr/13-01-2026/nees-tourkikes-proklisis-sto-egeo-pente-paraviasis-ke-dyo-paravasis-apo-f-16-ke-uav/
[G0115]: https://www.onalert.gr/ellinotourkika/enochlise-i-afixi-toy-kimona-toyrkika-cn-235-kai-uav-ekanan-3-paraviaseis-sto-aigaio/656144/
[G0117]: https://cretaone.gr/nees-toyrkikes-paraviaseis-sto-aigaio-me-drones-ayti-ti-fora/
[G0302]: https://www.onalert.gr/ellinotourkika/dyo-toyrkika-drones-ekanan-4-paraviaseis-kai-3-paravaseis-sto-aigaio/662737/
[G0305]: https://athens-times.com/turkish-air-violations-over-the-aegean-amid-regional-tensions/
[G0310]: https://greekcitytimes.com/2026/03/11/turkish-airspace-violations-aegean-march-2026/
[G0326]: https://athens-times.com/turkey-provokes-in-the-aegean-f-16s-fly-unannounced-exercise-cn-235-and-uavs-violate-greek-airspace/
[G0617]: https://www.onalert.gr/ellinotourkika/tourkiko-atr-72-kai-dyo-uav-ekanan-paraviaseis-kai-paravaseis-se-olo-to-aigaio/678664/
[G0623]: https://athens-times.com/new-turkish-air-violations-in-the-aegean-armed-f-16s-intrude-clashes-with-greek-fighters/
[G0810]: https://www.newsit.gr/ellada/neo-resital-proklitikotitas-apo-tin-tourkia-me-12-paraviaseis-sto-aigaio/4748229/
[G0817]: https://www.newsbomb.gr/ellada/ethnika/story/1757082/baraz-tourkikon-paraviaseon-sto-aigaio-me-uav-kai-aeroskafos
[G0822]: https://www.onalert.gr/ellinotourkika/aigaio-paravaseis-sto-fir-athinon-apo-dyo-tourkika-uav/815066/
[G0823]: https://www.onalert.gr/ellinotourkika/tourkika-uav-paraviasan-gia-akomi-mia-mera-ton-ethniko-enaerio-xoro-sto-aigaio/815175/
[G0824]: https://www.onalert.gr/ellinotourkika/paraviaseis-kai-paravaseis-apo-eksi-tourkika-drones-sto-aigaio/815317/
[G0825]: https://www.sdna.gr/politiko-deltio/ellada/1460934_nea-toyrkiki-proklisi-sto-aigaio-me-tessera-uav-deka-parabaseis-sto
[G0826]: https://www.onalert.gr/ellinotourkika/aigaio-synexizontai-oi-paraviaseis-kai-oi-paravaseis-apo-tourkika-drones-kai-cn-235/815675/
[G0828]: https://www.euronews.com/2026/08/28/greek-f-16s-intercept-turkish-drone-over-northern-aegean
[G0829]: https://www.onalert.gr/ellinotourkika/nees-paravaseis-kai-paraviaseis-apo-tourkika-uav/816143/
[G0830]: https://www.onalert.gr/ellinotourkika/nees-paravaseis-tourkikon-uav-sto-kentriko-aigaio/816240/
[G0831]: https://www.onalert.gr/ellinotourkika/synexizoun-tis-paraviaseis-sto-aigaio-ta-tourkika-drones-mia-paravasi-apo-cn-235/816429/
[G0901]: https://www.onalert.gr/ellinotourkika/paraviaseis-kai-paravaseis-apo-4-tourkika-drones-sto-aigaio/816630/
[G0902]: https://www.cnn.gr/ellada/story/550515/mparaz-paraviaseon-apo-tourkika-aeroskafi-kai-drone-sto-aigaio
[G0907]: https://www.protothema.gr/greece/article/1875290/tesseris-paraviaseis-apo-tourkika-uav-kai-mia-ebloki-me-elliniko-aeroskafos-epifulakis/AMP/
[G0910]: https://www.ekriti.gr/ellada/nees-prokliseis-apo-tin-toyrkia-sto-aigaio-stin-premiera-tis-askisis-medusa-stin-kriti
[G0911]: https://militarypress.gr/en/2026/09/12/armed-turkish-f16s-aegean-second-incident-five-days/
[G0912]: https://www.onalert.gr/ellinotourkika/aigaio-nees-paravaseis-kai-paraviaseis-tourkikon-uav/819055/
[G0913]: https://www.onalert.gr/ellinotourkika/paravaseis-kai-paraviaseis-apo-tourkika-uav-sto-aigaio/819183/
[G0917]: https://www.onalert.gr/ellinotourkika/aigaio-paravaseis-sto-fir-athinon-apo-tourkika-f-16-kai-uav/820146/
[G0918]: https://www.politica.gr/kriti/aigaio-tourkika-f-16-kai-uav-pano-apo-ro-kai-zourafa-se-exelixi-i-medusa-15-stin-kriti
[G0919]: https://www.capital.gr/epikairotita/4018039/nees-tourkikes-parabaseis-sto-aigaio-apo-drones/
[G0920]: https://www.cnn.gr/ellada/story/553191/123
[G0921]: https://www.onalert.gr/ellinotourkika/paravaseis-kai-paraviasi-sto-aigaio-apo-dyo-tourkika-drones-kai-ena-atr-72/821033/
[G0922]: https://www.newsit.gr/ellada/tourkika-drones-paraviasan-ton-ethniko-enaerio-xoro-sto-aigaio-paravaseis-kai-apo-dyo-atr-72/4780725/amp/
[G0923]: https://www.onalert.gr/ellinotourkika/tourkika-drones-ekanan-paraviaseis-kai-paravaseis-sto-notioanatoliko-aigaio/821605/
[R10]: https://cugetliber.ro/mobile/stiri-eveniment-fragmente-de-drona-pe-plaja-din-mamaia-nord-politistii-au-fost-alertati-dimineata-563717
[R11]: https://www.replicaonline.ro/inca-o-drona-a-fost-gasita-pe-plaja-alezzi-din-mamaia-nu-avea-explozibil-668064/
[G0828K]: https://www.ekathimerini.com/politics/foreign-policy/1313618/turkish-drone-violates-greek-airspace-over-northeastern-aegean/
[G0828A]: https://www.aol.com/articles/greek-f-16s-intercept-turkish-133414000.html