DroneLedger

Armed conflict · Single source · unverified

Drone report in Schkeuditz, Germany

Schkeuditz · 08 Nov 2026 · event date · exact location not established

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

You are viewing revision 6 as published on 11 Nov 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?

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

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]
Show source graph

Left: publishers; right: recorded original statement. Converging lines show shared origin, not publication order. Dashed nodes have unknown dependency.

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 (1)

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

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

Editorial changes

  1. Revision 6 · 11 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Cite this dossier

Permanent page · Revision 6

Chicago

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

APA

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

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
6
Release
20261111T152411484016-d53a24
Publication date
11 Nov 2026
Accessed
11 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v6/
Hashed file
JSON · SHA-256 04d24e4456d83b3000569e8cb279a5184b5ca6e6866a22efee4bea391c7a4b7a

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 6; release 20261111T152411484016-d53a24; published 11 Nov 2026. https://droneincidents.com/incident/auto-de-2026-11-08-3bdf245832/v6/ Accessed 11 Nov 2026. SHA-256 04d24e4456d83b3000569e8cb279a5184b5ca6e6866a22efee4bea391c7a4b7a (https://droneincidents.com/data/citations/incident/auto-de-2026-11-08-3bdf245832/r6/04d24e4456d83b3000569e8cb279a5184b5ca6e6866a22efee4bea391c7a4b7a/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