DroneLedger

Armed conflict · Single source · unverified

Airport disruption after drone alert in Schkeuditz

Schkeuditz · 08 Nov 2026 · event date · city reference point on the map; exact location not yet known

According to a cited source, drones were reported in Schkeuditz, Germany on 8 November 2026. [1]

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

Drone presenceReported[1]
ImpactReported[1]
AttributionNot 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 11 Nov 2026 · Dossier updated 11 Nov 2026

What do we know now?

What happened

MDR, citing an official source of an involved party, reported airport disruption in Schkeuditz on 8 November 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 MDR, citing an official source of an involved party, the report published on 11 November 2026, 07:00 UTC describes airport disruption
Who reported what
  • MDR: 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.

Three clocks, one reading line
TrackRecorded date / time
1 · Event
  • · Calendar day; time unknown
2 · Source publication
3 · Dossier revisions

Citable archive context

50 km / 90 days
Point-distance context is not established: this dossier has no usable own coordinates. Display reference points are not substituted.

Region / category / 30 days
Other Armed conflict single-event dossiers in Europe during 09 Oct 2026–07 Nov 2026: 205; currently labelled drone-confirmed: 0.

Counted dossiers (current revisions)

Archive snapshot 11 Nov 2026, 14:47 UTC; release 20261111T144704216449-305e30. Current evidence labels, not what was known on the event date. Earlier calendar days only; waves, reporting windows and statement dates are excluded. Coverage is selective; these are not world totals, risk estimates or evidence of a common cause.

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

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.

For conflict incidents only the city or region is shown, never a precise location, and no operational details. This is not a warning service: for incoming threats, follow official alerts.

How to read this dossier

Claims are shown as made by the named source; claims by a party to a conflict remain claims. For conflict incidents only the city or region named in the reports is shown, never a precise location, and no operational details; the cited articles may contain more precise details than this dossier. This is not a warning service: for incoming threats, follow official alerts.

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
    • MDR (11 November 2026) [1]
    • TAG24 [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.

Drones involved

The cited sources do not name the type of drone.

What we know

According to an official source of an involved party, via MDR, as of 11 Nov 2026 07:00 UTC+00:00: airport 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

  1. MDR published a report on this incident. [1]

Original sources (2)

1 source family · a count of sources is not a verification score

1MDR ()11 Nov 2026 · source family: Mdr

First observed:

2TAG2409 Nov 2026 · source family: TAG24 · additional reporting

First observed:

Recorded fetches only; no exact edit time or interpretation. Unavailable does not mean removed.

Editorial changes

  1. Revision 7 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: TAG24.
  2. Revision 6 · 11 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Story timeline

Published revisions; dates are revision dates, not event dates.

  1. Revision 7 · Current dossier ·

    Drone presence: Reported · Impact: Reported · Attribution: Not established

  2. Revision 6 ·

    Drone presence: Reported · Impact: Reported · Attribution: Not established

Current dossier

Earlier in this archive

Published single-event dossiers with an earlier established event date only. Counts describe this archive, not frequency, risk or a common cause.

Same country: 9
Same category: 270

Cite this dossier

Permanent page · Revision 7

Chicago

DroneLedger editorial team. “Drone report in Schkeuditz, Germany.” Dossier auto-de-2026-11-08-3bdf245832, revision 7, updated 11 Nov 2026. https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v7/

APA

DroneLedger editorial team. (11 Nov 2026). Drone report in Schkeuditz, Germany (Dossier auto-de-2026-11-08-3bdf245832, revision 7). https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v7/

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

Cite this version

Maker
DroneLedger editorial team
ID
auto-de-2026-11-08-3bdf245832
Revision or edition
7
Release
20261111T144704216449-305e30
Publication date
11 Nov 2026
Accessed
11 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v7/
Hashed file
JSON · SHA-256 521ac00b9f8ad89587f87cc646ae7464eabf9c40296b0c5b674ffd79ec297f2e

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. Drone report in Schkeuditz, Germany. ID auto-de-2026-11-08-3bdf245832; revision or edition 7; release 20261111T144704216449-305e30; published 11 Nov 2026. https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v7/ Accessed 11 Nov 2026. SHA-256 521ac00b9f8ad89587f87cc646ae7464eabf9c40296b0c5b674ffd79ec297f2e (https://droneincidents.com/data/citations/incident/auto-de-2026-11-08-3bdf245832/r7/521ac00b9f8ad89587f87cc646ae7464eabf9c40296b0c5b674ffd79ec297f2e/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.

SchkeuditzBerlin
Approximate: city level
Reference marker and schematic precision area; not an incident position or measured error radius. Natural Earth boundaries; reference cities: GeoNames, CC BY 4.0.
Embed this dossier

No cookies, tracking or scripts. Reader browsers request this card from DroneLedger; standard server logs may record requests. This card updates with the next site release; reload to see changes.

Press graphics

SVG 16:9 SVG 1:1 SVG 9:16

What would help verify this dossier

  • A primary source or verifiable evidence that clarifies whether the reported object was a drone. Evidence for another explanation is welcome too.
  • An additional account with an independently checked origin. Reprints or several reports quoting the same statement do not add independent confirmation.
  • A source identifying the event area at city or region level. A destination or reference point does not establish where an event occurred.

These are research questions based on the public dossier, not a checklist that guarantees confirmation. Editors review new sources and record any change as a new revision.

Suggest a public source

Share links to published material. Do not send private names, exact coordinates, live positions or flight paths.

Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions

Incident archive

Newest first. Select an incident to open its dossier.

D = was there a drone? · I = impact (closure, damage, injuries) · A = attribution (who was behind it). Solid = confirmed · striped = reported · grey = not established · struck through = debunked.

DE08 Nov 2026·Armed conflictNew

Airport disruption after drone alert in Schkeuditz

SchkeuditzSingle source · unverified
DE13 Oct 2026·Airport disruption

Possible drone reports disrupt flights in Nuremberg

Nuremberg
DE23 Sep 2026·Airport disruption

Reported drone sighting briefly interrupts Berlin Brandenburg flights

Schönefeld, Brandenburg
DEduring the reporting window 04 Aug 2026–05 Aug 2026·Airport disruption

Authorities report an explosive device attached to a drone in Leipzig/Halle

Leipzig/Halle
DE30 May 2026·Airport disruption

Munich Airport closes runways for an hour after pilots report a possible drone

Munich Airport
DE26 Dec 2025·Airport disruption

Reported drones prompt Christmas-period Hannover Airport closure

Langenhagen, Lower Saxony
DE05 Nov 2025·Airport disruption

Drone report briefly halts flights at Hannover Airport

Langenhagen, Lower Saxony
DE02 Nov 2025·Airport disruption

Drone report briefly halts flights at Bremen Airport

Bremen
DE31 Oct 2025·Airport disruption

Drone report interrupts flights at Berlin Brandenburg Airport

Schönefeld, Brandenburg
DE02 Oct 2025·Airport disruption

Drone reports interrupt Munich flight operations

Munich Airport
DE16 Dec 2024·Military site

US Air Force and German police acknowledge Ramstein drone reports

Ramstein-Miesenbach, Rhineland-Palatinate
DE04 Sep 2024·Critical infrastructure

Brunsbüttel drone investigation reports mixed explanations

Brunsbüttel, Schleswig-Holstein
DE02 Mar 2020·Airport disruption

Frankfurt operations suspended twice after reported drones on 2 March 2020

Frankfurt am Main
UA11 Nov 2026·Armed conflictNew

Industrial damage reported after drone attack in Chernivtsi

ChernivtsiSingle source · unverified
RU11 Nov 2026·Armed conflictNew

Drone report in Omsk, Russia

OmskAuto-compiled
UA11 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Yahotyn

YahotynSingle source · unverified
RU11 Nov 2026·Armed conflictNew

Drone report in St.-Petersburg region, Russia

St.-Petersburg regionAuto-compiled
RU11 Nov 2026·Armed conflictNew

Drone report in Tver, Russia

TverSingle source · unverified
RU11 Nov 2026·Armed conflictNew

Flight disruption after drone alert in Rostov region

Rostov regionSingle source · unverified
RU11 Nov 2026·Armed conflictNew

Drone hit on port reported in Leningrad Oblast

Leningrad OblastSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Zhytomyr Oblast

Zhytomyr OblastSingle source · unverified
RU10 Nov 2026·Armed conflictNew

Drone report in Yartsevo, Russia

YartsevoSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Drone report in Kramatorsk, Ukraine

KramatorskFPV quadcopter · Source reports typeSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Fire reported after drone attack in Shostka

ShostkaSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Energy infrastructure damage reported after drone attack in Ladyzhyn

LadyzhynSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Drones shot down over Sevastopol, reports say

SevastopolSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Power outage reported after drone attack in Luhansk

LuhanskSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Power outage reported after drone attack in Donetsk

DonetskSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Explosions reported during drone attack on Berdyansk

BerdyanskSingle source · unverified
UA10 Nov 2026·Armed conflictNew

Drone report in Sumy, Ukraine

SumyAuto-compiled

Showing the newest 30 of 486 dossiers. Open the full archive

Global drone incident observatory

What happened.What we actually know.

Drone incidents worldwide, each traced to its original sources. We keep what was reported apart from what is confirmed, and show how the story changed.

486dossiers
47countries
19with drone presence confirmed
Curated dossiers and automatic reports · no live detection
Curated dossiers updated
Automatic reports updated
Dossier update dates, not incident dates. Automatic reports are not editorial approval.

Recorded two-source editorial review:

No recent two-source editorial review is recorded on this page. Automatic reports may still update.

Editorial country/category selection; not a live or legal safety boundary.
Authorities report an explosive device attached to a drone in Leipzig/Halle≈ Leipzig/HalleDrone report in St.-Petersburg region, Russia≈ St.-Petersburg regionFlight disruption after drone alert in Rostov region≈ Rostov regionDrone hit on port reported in Leningrad Oblast≈ Leningrad OblastResidential damage reported after drone attack in Zhytomyr Oblast≈ Zhytomyr OblastPossible drone reports disrupt flights in Nuremberg≈ NurembergIndustrial damage reported after drone attack in Chernivtsi≈ ChernivtsiDrone report in Omsk, Russia≈ OmskResidential damage reported after drone attack in Yahotyn≈ YahotynDrone report in Tver, Russia≈ TverDrone report in Yartsevo, Russia≈ YartsevoDrone report in Kramatorsk, Ukraine≈ KramatorskFire reported after drone attack in Shostka≈ ShostkaEnergy infrastructure damage reported after drone attack in Ladyzhyn≈ LadyzhynDrones shot down over Sevastopol, reports say≈ SevastopolPower outage reported after drone attack in Luhansk≈ LuhanskPower outage reported after drone attack in Donetsk≈ DonetskExplosions reported during drone attack on Berdyansk≈ BerdyanskDrone report in Sumy, Ukraine≈ SumyReported drone sighting briefly interrupts Berlin Brandenburg flightsSchönefeld, BrandenburgMunich Airport closes runways for an hour after pilots report a possible droneMunich AirportReported drones prompt Christmas-period Hannover Airport closureLangenhagen, Lower SaxonyDrone report briefly halts flights at Hannover AirportLangenhagen, Lower SaxonyDrone report briefly halts flights at Bremen AirportBremenDrone report interrupts flights at Berlin Brandenburg AirportSchönefeld, BrandenburgDrone reports interrupt Munich flight operationsMunich AirportUS Air Force and German police acknowledge Ramstein drone reportsRamstein-Miesenbach, Rhineland-PalatinateBrunsbüttel drone investigation reports mixed explanationsBrunsbüttel, Schleswig-HolsteinFrankfurt operations suspended twice after reported drones on 2 March 2020Frankfurt am MainAirport disruption after drone alert in Schkeuditz≈ Schkeuditz
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.ConfirmedReportedInconclusiveDebunkedDashed: location not yet known (city, region, sea or country)Natural Earth · approximate locations
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.
Shape: dossier category. Colour and fill: drone evidence. White outer ring: confirmed impact; this does not confirm a drone or an operator.
  • Airport disruption
  • Maritime attack
  • Critical infrastructure
  • Military site
  • Armed conflict
  • Public safety
  • Reported sightings

Event age: <48 h / 48 h–14 days / >14 days. Date-only reports near a boundary and statement dates stay unshaded. Colours still show evidence status.

Dossiers on the map: 0

The dossiers in the part of the map you are looking at, for the chosen region and period. Zoom or drag the map and this list follows. A dot marks the city, region or sea named in the sources, not the exact spot.

    How to read a dossier

    Every incident is judged on three separate questions. An airport can be confirmed closed while it is still unclear whether a drone was involved at all.

    1

    Was there a drone?

    Drone presence: reported by a source, confirmed by explicit evidence, inconclusive after investigation, or debunked.

    ConfirmedReportedInconclusiveDebunked
    2

    What was the impact?

    Closures, diversions, damage or injuries, with their own evidence state. “Not established” means no source reports an impact.

    ConfirmedReportedNot established
    3

    Who is responsible?

    Attribution is never inferred. A party’s claim, a charge and a court finding are shown as different things.

    Not establishedClaimedChargedConvicted