Editorial pack · DroneLedger
Frankfurt operations suspended twice after reported drones on 2 March 2020
Current state
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.
Evidence states
| Drone presence | reported · sources [1], [2] |
|---|---|
| Impact | confirmed · sources [1], [2] |
| Attribution | none · sources none |
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.
Claims
2 sources · 2 original statements. Sources that repeat the same statement count once.
| Claim and source passage | Original source | Assessment |
|---|---|---|
| The local report describes a halt to take-off and landing clearances. “Die Deutsche Flugsicherung erteilte keine Genehmigungen für Starts und Landungen.” [1] | Frankfurter Rundschau / airport operations (relayed) | supports: Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Xinhua relays the later operator-derived cancelled and diverted totals. “57 flights were diverted and 72 flights canceled” [2] | Federal police citing Fraport (relayed) | supports: Short literal passage read on the public source page; reported drone presence is not technical identification. |
| Police said the cause had not been identified after the search. “the cause of the incident has not yet been identified” [2] | German federal police (relayed) | context: Short literal passage read on the public source page; reported drone presence is not technical identification. |
Earlier matching archive records
Published archive records only, not all real-world incidents or a common cause.
30 days: 0
90 days: 0
As of: 2026-10-16T02:26:41+00:00
Not established
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.
Chronology
- 02 Mar 2020: 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]
Sources
- Frankfurter Rundschau: Fraport response and dated police updates (2020-07-30, source family: ippen-fr)
https://www.fr.de/frankfurt/flughafen-frankfurt-wegen-drohne-ohne-flugbetrieb-zr-13568620.html - Xinhua: federal police statement and operator totals (2020-03-03, source family: xinhua)
https://www.xinhuanet.com/english/2020-03/03/c_138836918.htm
How to cite
DroneLedger. “Frankfurt operations suspended twice after reported drones on 2 March 2020.” Dossier frankfurt-airport-drone-disruption-2020-03-02, revision 1, updated 16 Oct 2026. https://droneincidents.com/incident/frankfurt-airport-drone-disruption-2020-03-02/v1/
Editorial changes
- Revision 1 (2026-10-16): Curated dossier created after checking the cited sources line by line.
Evidence states: confirmed = established by the cited evidence; reported = stated by a source, not independently established; inconclusive; debunked; unknown. A claim by a party to a conflict remains a claim. Methodology: https://droneincidents.com/methodology/