DroneLedger

Armed conflict · Single source · unverified

Drone report in Leningradskaya Oblast', Russia

Leningradskaya Oblast' · 11 Nov 2026 · event date · exact location not established

According to a cited source (reported by Ukrainska Pravda), drones were reported in Leningradskaya Oblast', Russia on 11 November 2026. [1]

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

Drone presenceReported[1]
ImpactNot established
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 12 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

Ukrainska Pravda reported a drone incident in Leningrad Oblast on 11 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.
Who reported what
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.
  • What were the consequences? Source-bound impact reporting is missing.
  • 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
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

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

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

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. Ukrainska Pravda published a report on this incident. [1]

Original sources (11)

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

1Ukrainska Pravda ()11 Nov 2026 · source family: Pravda2Interfax11 Nov 2026 · source family: Interfax · additional reporting3Interfax11 Nov 2026 · source family: Interfax · additional reporting4Interfax11 Nov 2026 · source family: Interfax · additional reporting5TASS11 Nov 2026 · source family: TASS · additional reporting6РЕН ТВ11 Nov 2026 · source family: Ren tv · additional reporting7Еспресо11 Nov 2026 · source family: Espreso · additional reporting824 Канал11 Nov 2026 · source family: 24tv · additional reporting9ERR11 Nov 2026 · source family: ERR · additional reporting10Yle11 Nov 2026 · source family: Yle · additional reporting11Interfax11 Nov 2026 · source family: Interfax · additional reporting

Editorial changes

  1. Revision 12 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Interfax.
  2. Revision 11 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Yle.
  3. Revision 10 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: 24 Канал, ERR.
  4. Revision 9 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Еспресо, РЕН ТВ.
  5. Revision 8 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: TASS.
  6. Revision 7 · 11 Nov 2026Same note as Revision 12
  7. Revision 6 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 5.)
  8. Revision 4 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 3.)
  9. Revision 2 · 10 Nov 2026Published automatically after passing the automatic checks (pilot); not yet reviewed by an editor.

Cite this dossier

Permanent page · Revision 12

Chicago

DroneLedger editorial team. “Drone report in Leningradskaya Oblast', Russia.” Dossier auto-ru-2026-11-11-ac1994c10c, revision 12, updated 11 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v12/

APA

DroneLedger editorial team. (11 Nov 2026). Drone report in Leningradskaya Oblast', Russia (Dossier auto-ru-2026-11-11-ac1994c10c, revision 12). https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v12/

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

Cite this version

Maker
DroneLedger editorial team
ID
auto-ru-2026-11-11-ac1994c10c
Revision or edition
12
Release
20261111T152411484016-d53a24
Publication date
11 Nov 2026
Accessed
11 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v12/
Hashed file
JSON · SHA-256 6b139f44fd347a8a3ce7b451b482e39f1fb10b4e0b662cd889a521b7f38176d3

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 Leningradskaya Oblast', Russia. ID auto-ru-2026-11-11-ac1994c10c; revision or edition 12; release 20261111T152411484016-d53a24; published 11 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v12/ Accessed 11 Nov 2026. SHA-256 6b139f44fd347a8a3ce7b451b482e39f1fb10b4e0b662cd889a521b7f38176d3 (https://droneincidents.com/data/citations/incident/auto-ru-2026-11-11-ac1994c10c/r12/6b139f44fd347a8a3ce7b451b482e39f1fb10b4e0b662cd889a521b7f38176d3/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