Armed conflict
Drone report in Moscow region, Russia
Moscow region, Russia28 Oct 2026 · event dateexact location not established What happened
TSN, citing an official source of an involved party, reported flight disruption in Moscow region on 28 October 2026.
Drone presenceReported[1] AttributionNot established
1 source family · a count of sources is not a verification score
Automatically compiled · sources retrieved on 29 Oct 2026 · Dossier updated 29 Oct 2026
You are viewing revision 2 as published on 29 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
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.
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 TSN, citing an official source of an involved party, the report describes flight disruption, in a report published on 29 October 2026, 07:30 UTC+02:00
- Who reported what
- TSN: Assessment of drone involvement; Effects
- Source families
- One source family is recorded; there is no second independent confirmation
- No structured detail recorded
- Hit / damaged · Fell near · Intercepted (claimed)
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.
- Unknown dependency
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 TSN, as of 29 October 2026, 07:30 UTC+02:00: flight disruption.
What remains unknown
Not yet assessed by an editor: impact, exact location, operator and intent.
Operator attribution: Not established. Not assessed in this automatic report; see the cited sources for any claims of responsibility.
How the story changed
TSN published a report on this incident. [1]
Editorial changes
- Revision 2 · 29 Oct 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.
Cite this dossier
Permanent page · Revision 2
Chicago
DroneLedger. “Drone report in Moscow region, Russia.” Dossier auto-ru-2026-10-28-5545d8f209, revision 2, updated 29 Oct 2026. https://droneincidents.com/incident/auto-ru-2026-10-28-5545d8f209/v2/
APA
DroneLedger. (29 Oct 2026). Drone report in Moscow region, Russia (Dossier auto-ru-2026-10-28-5545d8f209, revision 2). https://droneincidents.com/incident/auto-ru-2026-10-28-5545d8f209/v2/
Dataset DOI: 10.5281/zenodo.23345422
Cite the revision you used: later revisions may change evidence states.
Automatically compiled · sources retrieved on 29 Oct 2026
Dossier updated 29 Oct 2026 Editorial pack (print / PDF)Follow this dossier (feed)Earlier versions