Airport disruption · Single source · unverified
Airport disruption after drone alert in Romania
Romania · 31 Oct 2026 · event date · country-level location
According to an official source of an involved party (reported by click.ro), drones were reported in Romania on 31 Oct 2026. According to the operator of the affected site, via click.ro, as of 31 Oct 2026 17:10 UTC+00:00: airport disruption and flight disruption. [1]
Drone presence is reported. Consequences are reported. The operator is not established.
DroneLedger editorial team, publisher and editor responsible for this project.
Automatically compiled from cited sources; no individual human review is recorded. Method and corrections
1 source family · a count of sources is not a verification score
Automatically compiled · sources retrieved on 03 Nov 2026 · Dossier updated 06 Nov 2026
What do we know now?
What happened
click.ro, citing the operator of the affected site, reported airport disruption and flight disruption in Romania on 31 October 2026.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Human consequences
- Casualty details are not established in this dossier.
- Effects
- According to click.ro, citing the operator of the affected site, the report published on 31 October 2026, 17:10 UTC describes airport disruption; flight disruption
- Who reported what
- click.ro: Assessment of drone involvement; effects
- Source families
- One source family is recorded; there is no second independent confirmation
Further details are not known from the cited sources.
Timeline
Three clocks, one reading line
Shared calendar-day axis, from left to right. Bars mark days or reporting windows, not durations. Publication and revision clocks are not event clocks. Missing clocks remain unknown; the table gives all available precision and source links. The plot follows recorded calendar dates; time zones may differ. It establishes neither within-day order nor causality.
| Track | Recorded date / time |
|---|---|
| 1 · Event |
|
| 2 · Source publication | |
| 3 · Dossier revisions |
What remains uncertain?
- Was a drone established? A published investigation or identification could resolve this.
- Who operated it, and why? An attributed investigation finding is missing.
- Where did it happen? The record has no location more precise than a country or region.
Check the evidence
One source, not yet confirmed by a second independent source; automatically published, not yet reviewed by an editor. The report may be incomplete or wrong.
How to read this dossier
Claims are shown as made by the named source; claims by a party to a conflict remain claims.
Source genealogy
Grouped by recorded original statement, not by publisher. Unmapped sources have unknown dependency; linked statements may also share an earlier origin. This is not an independence score.
Show source graph
Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.
Read with a source omitted
Reading aid: switch off a source or family to inspect the remaining visible support below. Evidence status is not recalculated.
No source-indexed claims recorded. No support can be inferred from the number of sources.
What we know
According to the operator of the affected site, via click.ro, as of 31 Oct 2026 17:10 UTC+00:00: airport disruption and flight disruption.
Data
- No structured detail recorded
- Hit / damaged · Fell near · Intercepted (claimed)
What remains unknown
Not yet assessed by an editor: impact, exact location, operator and intent.
Not assessed in this automatic report; see the cited sources for any claims of responsibility.
How the story changed
click.ro published a report on this incident. [1]
Original sources (2)
1 source family · a count of sources is not a verification score
1click.ro (31 October 2026)31 Oct 2026 · source family: Click2Defence2401 Nov 2026 · source family: Romania defence ministry · additional reportingEditorial changes
- Revision 4 · 06 Nov 2026Additional reporting links reviewed; evidence assessments unchanged. Added: Defence24.
- Revision 3 · 05 Nov 2026Correction (): The source reports drone incursions into Romanian airspace and resulting airport restrictions. It does not locate a drone at Iași airport, so the incident location is broadened to Romania.
- Revision 2 · 03 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.
Cite this dossier
Chicago
DroneLedger editorial team. “Airport disruption after drone alert in Romania.” Dossier auto-ro-2026-10-31-be62870cb1, revision 4, updated 06 Nov 2026. https://droneincidents.com/incident/auto-ro-2026-10-31-be62870cb1/v4/
APA
DroneLedger editorial team. (06 Nov 2026). Airport disruption after drone alert in Romania (Dossier auto-ro-2026-10-31-be62870cb1, revision 4). https://droneincidents.com/incident/auto-ro-2026-10-31-be62870cb1/v4/
Cite the revision you used: later revisions may change evidence states.
Cite this version
- Maker
- DroneLedger editorial team
- ID
- auto-ro-2026-10-31-be62870cb1
- Revision or edition
- 4
- Release
- 20261109T002636372024-fb099f
- Publication date
- 06 Nov 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/auto-ro-2026-10-31-be62870cb1/v4/
- Hashed file
- JSON · SHA-256
e6a9ad096fa323d29321ad386c26cca6bbae77158980e94456e3c51d888745f4
Dataset DOI for this exact version: Not yet in a DOI snapshot · DOI binding manifest
Dataset DOI (series, not this revision): 10.5281/zenodo.23345422
DroneLedger editorial team. Airport disruption after drone alert in Romania. ID auto-ro-2026-10-31-be62870cb1; revision or edition 4; release 20261109T002636372024-fb099f; published 06 Nov 2026. https://droneincidents.com/incident/auto-ro-2026-10-31-be62870cb1/v4/ Accessed 09 Nov 2026. SHA-256 e6a9ad096fa323d29321ad386c26cca6bbae77158980e94456e3c51d888745f4 (https://droneincidents.com/data/citations/incident/auto-ro-2026-10-31-be62870cb1/r4/e6a9ad096fa323d29321ad386c26cca6bbae77158980e94456e3c51d888745f4/data.json). Not yet in a DOI snapshot.
Citation uses the English reference edition. Access date is the UTC date when this page was built; change it to your consultation date when reusing the citation.
Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions