DroneLedger

Airport disruption

Possible drone reports disrupt flights in Nuremberg

Nuremberg · 13 Oct 2026 · event date · exact location not established

Police reported possible drone sightings early on 13 October 2026. The airport operator reported precautionary disruption of flights. [1][2]

Drone presence is reported. Consequences are reported. The operator is not established.

Drone presenceReported[1][2]
ImpactReported[1]
AttributionNot 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 · 15 Oct 2026 · Dossier updated 15 Oct 2026

You are viewing revision 2 as published on 15 Oct 2026. The dossier text, evidence states, claims and sources of this revision are fixed; catalogue context such as cost estimates is not shown here. View the current version

What do we know now?

Police reported possible drone sightings early on 13 October 2026. The airport operator reported precautionary disruption of flights. The reported object was not verified.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Who reported what
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.

Three clocks, one reading line
TrackRecorded date / time
1 · Event
  • · Calendar day; time unknown
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 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.

  1. Unknown dependency
    • Airport operator: possible drone sightings [1]
    • Anadolu: suspected sightings and police response [2]
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

As described in the airport operator’s report read on 13 October: six flights were delayed, comprising two arrivals and four departures; two arrivals diverted and subsequently continued to Nuremberg. Anadolu quotes police as saying reports occurred approximately 02:00–04:00 local time (CEST, UTC+02:00). These are sighting-report times, not a demonstrated two-hour closure interval.

The airport operator supplies its own account of operational disruption. Anadolu separately quotes police about reports from three pilots and the unsuccessful verification. These are separate reporting organisations and distinct operational observations, but the drone assertion shares the pilots’ reports; there are not two independent physical confirmations of a drone.

Data
No structured detail recorded
Hit / damaged · Fell near · Intercepted (claimed) · Human consequences · Effects

What remains unknown

Whether the object was a drone, who operated it and the precise start and end of the precautionary flight suspension remain unresolved. The operator page displays 12 October while its body expressly identifies Tuesday 13 October; use the explicit event date, preserve the publication discrepancy. A later aircraft emergency is a separate reported event; no causal connection is established here.

Not established.

How the story changed

  1. Police received possible-drone reports approximately 02:00–04:00 local time. The reported object could not be verified. [2]

  2. The operator reported six delayed flights and two temporary diversions; it did not provide a complete closure interval. [1]

Original sources (2)

2 source families · a count of sources is not a verification score

1Airport operator: possible drone sightings12 Oct 2026 · source family: Nuremberg airport2Anadolu: suspected sightings and police response13 Oct 2026 · source family: Anadolu

Editorial changes

  1. Revision 2 · 15 Oct 2026Linked the dossier to its facility page (location named in the cited source).
  2. Revision 1 · 14 Oct 2026Curated dossier created after checking the cited sources line by line.

Cite this dossier

Permanent page · Revision 2

Chicago

DroneLedger editorial team. “Possible drone reports disrupt flights in Nuremberg.” Dossier nuremberg-suspected-drone-reports-2026-10-13, revision 2, updated 15 Oct 2026. https://droneincidents.com/incident/nuremberg-suspected-drone-reports-2026-10-13/v2/

APA

DroneLedger editorial team. (15 Oct 2026). Possible drone reports disrupt flights in Nuremberg (Dossier nuremberg-suspected-drone-reports-2026-10-13, revision 2). https://droneincidents.com/incident/nuremberg-suspected-drone-reports-2026-10-13/v2/

Cite the revision you used: later revisions may change evidence states.

Cite this version

Maker
DroneLedger editorial team
ID
nuremberg-suspected-drone-reports-2026-10-13
Revision or edition
2
Release
20261102T055221362217-c8d330
Publication date
15 Oct 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/nuremberg-suspected-drone-reports-2026-10-13/v2/
Hashed file
JSON · SHA-256 c92e54540043f541d2788ae492610c88209aeafcb9c081a230020b1e99351a68

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. Possible drone reports disrupt flights in Nuremberg. ID nuremberg-suspected-drone-reports-2026-10-13; revision or edition 2; release 20261102T055221362217-c8d330; published 15 Oct 2026. https://droneincidents.com/incident/nuremberg-suspected-drone-reports-2026-10-13/v2/ Accessed 09 Nov 2026. SHA-256 c92e54540043f541d2788ae492610c88209aeafcb9c081a230020b1e99351a68 (https://droneincidents.com/data/citations/incident/nuremberg-suspected-drone-reports-2026-10-13/r2/c92e54540043f541d2788ae492610c88209aeafcb9c081a230020b1e99351a68/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