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.

RU16 Oct 2026·Armed conflictNew

Armed conflict

Drone wave reported in Russia

Russia, Russia16 Oct 2026 · event date · covers a wave of incidentscountry reference point on the map; exact location not yet known

In short

What happened: armed conflict at Russia on 16 October 2026.

Effect: not established. That does not mean nothing happened.

Was it a drone? Reported, not confirmed. Who was behind it: not established.

Single-source report: one source reports this, and no second independent source has corroborated it yet. It is shown so that early and local reports are visible. Treat it as unverified.

Story timeline

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

Revision 2 · Current dossier · 16 Oct 2026
Drone presence: Reported · Impact: Not established · Attribution: Not established
Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Current dossier

Country reference only
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.

<iframe src="https://droneincidents.com/embed/dossier/auto-ru-2026-10-16-884365e151/en/" title="Embed this dossier" width="100%" height="320" loading="lazy" referrerpolicy="no-referrer"></iframe>

According to qq.com, drones were reported in Russia on 16 October 2026.

Drone presenceReported[1]

ImpactNot established

AttributionNot established

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.

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
- qq.com (2026-10-16) [1]

Show source graph

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

Drones involved

The cited sources do not name the type of drone.

What we know

No eligible attributed impact claim is included; this does not mean no impact occurred.

Single-source report, automatically published: one source reports drone presence at this place and date. It has not been corroborated by a second independent source and may be incomplete or wrong. It is shown so that early and local reports are visible; treat it as unverified. 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. DroneLedger has not independently verified the claims and an editor has not yet reviewed this dossier.

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

16 Oct 2026
qq.com published a report on this incident. [1]

Original sources (1)

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

1qq.com (2026-10-16)16 Oct 2026 · source family: qq

First observed: 2026-10-16 16:22:01 UTC
Recorded fetches only; no exact edit time or interpretation. Unavailable does not mean removed.

Editorial changes

Revision 2 · 16 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 wave reported in Russia.” Dossier auto-ru-2026-10-16-884365e151, revision 2, updated 16 Oct 2026. https://droneincidents.com/incident/auto-ru-2026-10-16-884365e151/v2/

APA

DroneLedger. (16 Oct 2026). Drone wave reported in Russia (Dossier auto-ru-2026-10-16-884365e151, revision 2). https://droneincidents.com/incident/auto-ru-2026-10-16-884365e151/v2/

Dataset DOI: 10.5281/zenodo.23345422

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

Press graphics

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

Download dossier JSON

Automatically compiled · sources retrieved on 16 Oct 2026
Dossier updated 16 Oct 2026

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

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.

150dossiers

34countries

15with drone presence confirmed

Curated dossiers and automatic reports · no live detectionLatest source check 16 Oct 2026

Editorial country/category selection; not a live or legal safety boundary.

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 per day (last 14 days) 03 Oct 2026 – 16 Oct 2026

Showing: the whole map period

Click a day to show only that day on the map, or press play. Days are UTC calendar days. Some dossiers are dated by the report (statement date) because the source gives no event day, so these are dossier dates, not event times or incident totals.

Latest editor-reviewed dossiers

Full archive ↓

Newer automatic reports (unverified) are in the strip above and in the archive.

RO15 Oct 2026Wine Trader hit off Romania; president says drones struck the ship UA14 Oct 2026Regional authorities report three dead and six injured after drone attack in Kropyvnytskyi RO14 Oct 2026Yara J hit off Romania; president says drones struck the ship OM14 Oct 2026GFS Giselle damaged in attack; drone involvement unclear

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.

Was there a drone?

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

ConfirmedReportedInconclusiveDebunked

What was the impact?

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

ConfirmedReportedNot established

Who is responsible?

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

Not establishedClaimedChargedConvicted

Incident archive

No matching dossiers