Airport disruption
Frankfurt operations suspended twice after reported drones on 2 March 2020
Frankfurt am Main · 02 Mar 2020 · event date · approximate location
Reported drone sightings caused two interruptions to take-off and landing clearances at Frankfurt Airport on 2 March 2020. The reported morning and afternoon interruptions are kept together as one same-day dossier. [1][2]
Drone presence is reported. The consequences are established. The operator is not established.
DroneLedger editorial team, publisher and editor responsible for this project.
AI-assisted editorial source review. This label records the editorial workflow, not a personal check of every source or sentence. Method and corrections
2 source families · a count of sources is not a verification score
AI-assisted editorial source review · 16 Oct 2026 · Dossier updated 16 Oct 2026
What do we know now?
Reported drone sightings caused two interruptions to take-off and landing clearances at Frankfurt Airport on 2 March 2020. The reported morning and afternoon interruptions are kept together as one same-day dossier.
The recorded closure lasted 97 minutes. The recorded closure lasted 54 minutes.
Facts at a glance
- Drone type
- No named drone type is recorded in this dossier.
- Effects
- According to xinhuanet.com, citing Federal police / DFS via Xinhua, the report describes a suspension of operations, from 2 March 2020, 10:23 UTC to 2 March 2020, 12:00 UTC
- According to xinhuanet.com, citing Federal police / DFS via Xinhua, the report describes a suspension of operations, from 2 March 2020, 14:10 UTC to 2 March 2020, 15:04 UTC
- According to fr.de, citing Frankfurter Rundschau / airport operations, The local report describes a halt to take-off and landing clearances
- According to xinhuanet.com, citing Federal police via Fraport, Xinhua relays the later operator-derived cancelled and diverted totals
- Who reported what
- fr.de: Assessment of drone involvement; reported outcome
- xinhuanet.com: Assessment of drone involvement; effects; reported outcome
- Source families
- 2 source families are recorded; republication is not 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.
Check the evidence
Source passage
- Frankfurter Rundschau / airport operations · “Die Deutsche Flugsicherung erteilte keine Genehmigungen für Starts und Landungen.” fr.de
- Federal police citing Fraport · “57 flights were diverted and 72 flights canceled” xinhuanet.com
- German federal police · “the cause of the incident has not yet been identified” xinhuanet.com
- Federal police / DFS via Xinhua · “Between 11:23 a.m. and 1:00 p.m.,” xinhuanet.com
- Federal police / DFS via Xinhua · “between 3:10 p.m. and 4:04 p.m. local time” xinhuanet.com
Operational effects
The cited source reports an airport disruption window.
Disruption window · Start: · Restrictions lifted: · Elapsed time between cited endpoints: ≈97 min Source [2]
Between 11:23 a.m. and 1:00 p.m.,
Federal police / DFS via Xinhua · Source [2]
As of: Time not established
Europe/Berlin CET+01. First distinct clearance-suspension interval; not the first drone-sighting time.
The cited source reports an airport disruption window.
Disruption window · Start: · Restrictions lifted: · Elapsed time between cited endpoints: ≈54 min Source [2]
between 3:10 p.m. and 4:04 p.m. local time
Federal police / DFS via Xinhua · Source [2]
As of: Time not established
Second distinct clearance-suspension interval. Do not display a continuous closure across the gap.
Claims and evidence
2 sources · 2 original statements
Sources that repeat the same original statement count once: a number of articles is not a number of independent confirmations.
| Claim | Original source | Assessment |
|---|---|---|
| Impact The local report describes a halt to take-off and landing clearances. [1]Source passage“Die Deutsche Flugsicherung erteilte keine Genehmigungen für Starts und Landungen.” Original term: Passage checked word for word against the source on 16 Oct 2026. | Frankfurter Rundschau / airport operations via Frankfurter Rundschau | Supports the report Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Impact Xinhua relays the later operator-derived cancelled and diverted totals. [2]Source passage“57 flights were diverted and 72 flights canceled” Passage checked word for word against the source on 16 Oct 2026. | Federal police citing Fraport via Xinhua | Supports the report Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Drone Police said the cause had not been identified after the search. [2]Source passage“the cause of the incident has not yet been identified” Passage checked word for word against the source on 16 Oct 2026. | German federal police via Xinhua | Context only Short literal passage read on the public source page; reported drone presence is not technical identification. |
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.
- Federal police citing Fraport / Frankfurter Rundschau / airport operations
- German federal police
- Xinhua: federal police statement and operator totals [2] · Relayed statement
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.
How to read this table
Reading aid only. Switch off a source or its recorded family to inspect the remaining visible support for exact claim texts. Evidence status is not recalculated. Shared wording or a shared family does not prove independence. Only recorded links labelled “supports” count here; context and contradiction links are not support. The dossier itself is unchanged.
| Claim | Supporting sources | Visible support |
|---|---|---|
| The local report describes a halt to take-off and landing clearances. | [1] | Support remains visible |
| Xinhua relays the later operator-derived cancelled and diverted totals. | [2] | Support remains visible |
| Police said the cause had not been identified after the search. | No supporting link recorded | No supporting link recorded |
What we know
Xinhua gives local suspension windows of 11:23–13:00 and 15:10–16:04, citing federal police. A later same-day account gives 57 diverted and 72 cancelled flights. Earlier figures in the local report differ; they are not added to the later totals.
Frankfurter Rundschau records a direct airport-operator response and successive police updates. Xinhua separately reports the police statement, including operator-derived totals. Police and Fraport are distinct operational origins, with shared underlying official information rather than independent technical drone identification.
Data
- No structured detail recorded
- Hit / damaged · Fell near · Intercepted (claimed) · Human consequences
What remains unknown
The local page currently displays a July 2020 publication/version timestamp, while its body explicitly dates the event updates 2 March; the event date comes from those updates and the Xinhua dateline. The local report’s earlier description of an approximately hour-long interruption differs from the later explicit windows. Do not turn this into one continuous all-day closure or combine rolling counts. No recovered device, model, operator, collision or physical damage established.
No operator or responsible organisation established by the reviewed sources.
How the story changed
Reported drone sightings caused two interruptions to take-off and landing clearances at Frankfurt Airport on 2 March 2020. The reported morning and afternoon interruptions are kept together as one same-day dossier. [1]
Original sources (2)
2 source families · a count of sources is not a verification score
1Frankfurter Rundschau: Fraport response and dated police updates30 Jul 2020 · source family: Ippen fr2Xinhua: federal police statement and operator totals03 Mar 2020 · source family: XinhuaEditorial changes
- Revision 2 · 16 Oct 2026Added source-stated disruption windows (UTC) and the original key term used by the source.
- Revision 1 · 16 Oct 2026Curated dossier created after checking the cited sources line by line.
Cite this dossier
Chicago
DroneLedger editorial team. “Frankfurt operations suspended twice after reported drones on 2 March 2020.” Dossier frankfurt-airport-drone-disruption-2020-03-02, revision 2, updated 16 Oct 2026. https://droneincidents.com/incident/frankfurt-airport-drone-disruption-2020-03-02/v2/
APA
DroneLedger editorial team. (16 Oct 2026). Frankfurt operations suspended twice after reported drones on 2 March 2020 (Dossier frankfurt-airport-drone-disruption-2020-03-02, revision 2). https://droneincidents.com/incident/frankfurt-airport-drone-disruption-2020-03-02/v2/
Cite the revision you used: later revisions may change evidence states.
Cite this version
- Maker
- DroneLedger editorial team
- ID
- frankfurt-airport-drone-disruption-2020-03-02
- Revision or edition
- 2
- Release
- 20261102T055221362217-c8d330
- Publication date
- 16 Oct 2026
- Accessed
- 09 Nov 2026
- Permanent URL
- https://droneincidents.com/incident/frankfurt-airport-drone-disruption-2020-03-02/v2/
- Hashed file
- JSON · SHA-256
2c9035de6b04df9f2ab640b47e963050c51cdd6bc92debda6beae8c2446f76c8
Dataset DOI for this exact version: 10.5281/zenodo.23877662 · DOI binding manifest
Dataset DOI (series, not this revision): 10.5281/zenodo.23345422
DroneLedger editorial team. Frankfurt operations suspended twice after reported drones on 2 March 2020. ID frankfurt-airport-drone-disruption-2020-03-02; revision or edition 2; release 20261102T055221362217-c8d330; published 16 Oct 2026. https://droneincidents.com/incident/frankfurt-airport-drone-disruption-2020-03-02/v2/ Accessed 09 Nov 2026. SHA-256 2c9035de6b04df9f2ab640b47e963050c51cdd6bc92debda6beae8c2446f76c8 (https://droneincidents.com/data/citations/incident/frankfurt-airport-drone-disruption-2020-03-02/r2/2c9035de6b04df9f2ab640b47e963050c51cdd6bc92debda6beae8c2446f76c8/data.json). Exact archived dataset version: https://doi.org/10.5281/zenodo.23877662.
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