DroneLedger

Armed conflict · Single source · unverified

Drone hit on port reported in Leningrad Oblast

Leningrad Oblast · 11 Nov 2026 · event date · region reference point on the map; exact location not yet known

According to REN TV, citing Alexander Drozdenko: a reported hit affected a port. According to Interfax, citing Alexander Drozdenko: a drone was reportedly shot down. [1]

Drone presence is reported. Damage reported; not independently verified. 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

What do we know now?

Added after an AI-assisted check of the cited source; quote verified, not reviewed by an editor.

What happened

According to Interfax, citing Alexander Drozdenko: a drone was reportedly shot down. According to TASS, citing Alexander Drozdenko: a fire was reported. According to REN TV, citing Alexander Drozdenko: a reported hit affected a port. According to 24 Kanal, citing Russian media via local social media reports: a fire was reported. According to RBC-Ukraine: a fire was reported.

Facts at a glance

Added after an AI-assisted check of the cited source; quote verified, not reviewed by an editor.

What the source reports
  • a drone was reportedly shot down (Interfax, citing Alexander Drozdenko)
  • a fire was reported (TASS, citing Alexander Drozdenko)
  • a reported hit affected a port (REN TV, citing Alexander Drozdenko)
  • a fire was reported (24 Kanal, citing Russian media via local social media reports)
  • a fire was reported (RBC-Ukraine)
Drone type
  • No named drone type is recorded in this dossier.
Human consequences
  • Casualty details are not established in this dossier.
Who reported what
  • Ukrainska Pravda: Assessment of drone involvement
  • Interfax · additional reporting: What the source reports
  • TASS · additional reporting: What the source reports
  • REN TV · additional reporting: What the source reports
  • 24 Kanal · additional reporting: What the source reports
  • RBC-Ukraine · additional reporting: What the source reports
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 12 Oct 2026–10 Nov 2026: 226; 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 passage
  • “"Над территорией Ленинградской области (...) сбито 42 БПЛА"” Interfax
  • “a drone attack resulted in a strike within the Ust-Luga port zone, sparking a fire.” TASS
  • “Предварительно в результате атаки БПЛА есть попадание в портовой зоне Усть-Луга, произошло возгорание” REN TV
  • “Уночі 11 листопада Ленінградську область атакували безпілотники, спричинивши масштабну пожежу у порту Усть-Луга.” 24 Kanal
  • “У ніч на 11 листопада українські безпілотники здійснили атаку порт Усть-Луга в Ленінградській області Росії. Внаслідок ударів на території об'єкта виникла пожежа.” RBC-Ukraine
Live warnings in Russia: use the official alerts
EMERCOM of Russia (MChS): official civil-defence warnings

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.

How to read this table

Reading aid only. Switch off a source or its recorded family to inspect the remaining visible support for exact claim texts. Evidence status is not recalculated. Shared wording or a shared family does not prove independence. Only recorded links labelled “supports” count here; context and contradiction links are not support. The dossier itself is unchanged.

Claim → supporting sources · recorded links
ClaimSupporting sourcesVisible support
a drone was reportedly shot down (source published on 11 Nov 2026, 02:02 UTC+03:00)[2]Support remains visible
a fire was reported (source published on 11 Nov 2026, 03:47 UTC)[5]Support remains visible
a reported hit affected a port (source published on 11 Nov 2026, 06:23 UTC+03:00)[6]Support remains visible
a fire was reported (source published on 11 Nov 2026, 04:24 UTC+02:00)[8]Support remains visible
a fire was reported (source published on 11 Nov 2026, 10:02 UTC+02:00)[13]Support remains visible

Drones involved

The cited sources do not name the type of drone.

What we know

A hit or damage is reported above as a claim of the cited source. No attributed impact claim has passed the impact check for this dossier, so the impact status reads “not established”: that status is a separate evidence assessment, not a statement that nothing happened.

Data
No structured detail recorded
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 (14)

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

1Ukrainska Pravda ()11 Nov 2026 · source family: Pravda

First observed:

2Interfax11 Nov 2026 · source family: Interfax · additional reporting

First observed:

3Interfax11 Nov 2026 · source family: Interfax · additional reporting

First observed:

4Interfax11 Nov 2026 · source family: Interfax · additional reporting

First observed:

5TASS11 Nov 2026 · source family: TASS · additional reporting

First observed:

6РЕН ТВ11 Nov 2026 · source family: Ren tv · additional reporting

First observed:

7Еспресо11 Nov 2026 · source family: Espreso · additional reporting

First observed:

824 Канал11 Nov 2026 · source family: 24tv · additional reporting

First observed:

9ERR11 Nov 2026 · source family: ERR · additional reporting

First observed:

10Yle11 Nov 2026 · source family: Yle · additional reporting

First observed:

11Interfax11 Nov 2026 · source family: Interfax · additional reporting

First observed:

12TV811 Nov 2026 · source family: Meduza · additional reporting

First observed:

13РБК-Україна11 Nov 2026 · source family: Rbc ukraine · additional reporting

First observed:

14WEB.DE News11 Nov 2026 · source family: Afp · additional reporting

First observed:

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

Editorial changes

  1. Revision 19 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 18.)
  2. Revision 17 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 16.)
  3. Revision 15 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: WEB.DE News.
  4. Revision 14 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: РБК-Україна.
  5. Revision 13 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: TV8.
  6. Revision 12 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Interfax.
  7. Revision 11 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Yle.
  8. Revision 10 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: 24 Канал, ERR.
  9. Revision 9 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: Еспресо, РЕН ТВ.
  10. Revision 8 · 11 Nov 2026Sources checked with AI; existing assessments retained. Added: TASS.
  11. Revision 7 · 11 Nov 2026Same note as Revision 12
  12. Revision 6 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 5.)
  13. Revision 4 · 11 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 3.)
  14. Revision 2 · 10 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 19 · Current dossier ·

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

  2. Revision 17 ·

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

  3. Revision 15 ·

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

  4. Revision 14 ·

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

  5. Revision 13 ·

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

  6. Revision 12 ·

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

  7. Revision 11 ·

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

  8. Revision 10 ·

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

  9. Revision 9 ·

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

  10. Revision 8 ·

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

  11. Revision 7 ·

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

  12. Revision 6 ·

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

  13. Revision 4 ·

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

  14. Revision 2 ·

    Drone presence: Reported · Impact: Not established · 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 place and country: 1
Same country: 105
Same category: 304

Cite this dossier

Permanent page · Revision 19

Chicago

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

APA

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

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
19
Release
20261111T144704216449-305e30
Publication date
11 Nov 2026
Accessed
11 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v19/
Hashed file
JSON · SHA-256 3712d885e325f68e42e94a985ec2358a12d5b1dcd7e36ed4085f03a75f65dc5b

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 19; release 20261111T144704216449-305e30; published 11 Nov 2026. https://droneincidents.com/incident/auto-ru-2026-11-11-ac1994c10c/v19/ Accessed 11 Nov 2026. SHA-256 3712d885e325f68e42e94a985ec2358a12d5b1dcd7e36ed4085f03a75f65dc5b (https://droneincidents.com/data/citations/incident/auto-ru-2026-11-11-ac1994c10c/r19/3712d885e325f68e42e94a985ec2358a12d5b1dcd7e36ed4085f03a75f65dc5b/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.

Leningrad OblastSaint PetersburgHelsinki
Approximate: region 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.

RU11 Nov 2026·Armed conflictNew

Drone hit on port reported in Leningrad Oblast

Leningrad OblastSingle source · unverifiedRU11 Nov 2026·Armed conflictNew

Drone report in Omsk, Russia

OmskAuto-compiledRU11 Nov 2026·Armed conflictNew

Drone report in St.-Petersburg region, Russia

St.-Petersburg regionAuto-compiledRU11 Nov 2026·Armed conflictNew

Drone report in Tver, Russia

TverSingle source · unverifiedRU11 Nov 2026·Armed conflictNew

Flight disruption after drone alert in Rostov region

Rostov regionSingle source · unverifiedRU10 Nov 2026·Armed conflictNew

Drone report in Yartsevo, Russia

YartsevoSingle source · unverifiedRU10 Nov 2026·Armed conflictNew

Explosions reported during drone attack on Staraya Russa

Staraya RussaSingle source · unverifiedRU09 Nov 2026·Armed conflictNew

Drone report in Shebekino, Russia

ShebekinoFPV quadcopter · Source reports typeSingle source · unverifiedRU09 Nov 2026·Armed conflictNew

Power outage reported after drone attack in Vsevolozhsk

VsevolozhskSingle source · unverifiedRU09 Nov 2026·Armed conflictNew

Drone report in Vsevolozhsk, Russia

VsevolozhskSingle source · unverifiedRU09 Nov 2026·Armed conflictNew

Fire reported after drone attack in Kirishi

KirishiAuto-compiledRU09 Nov 2026·Armed conflictNew

Drone report in St.-Petersburg region, Russia

St.-Petersburg regionSingle source · unverifiedRU08 Nov 2026·Armed conflict

Drone wave reported in Russia

RussiaAuto-compiledRU08 Nov 2026·Armed conflict

Energy infrastructure damage reported after drone attack in Rostov region

Rostov regionSingle source · unverifiedRU07 Nov 2026·Armed conflict

Drones shot down over Rostov region, reports say

Rostov regionAuto-compiledRU07 Nov 2026·Armed conflict

Drone report: Oryol Oblast, Russia

Oryol OblastSingle source · unverifiedRU07 Nov 2026·Armed conflict

Civilian infrastructure damaged in reported drone attack in Saratov Oblast

Saratov OblastSingle source · unverifiedRU07 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Belgorod

BelgorodSingle source · unverifiedRU06 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Shebekino

ShebekinoSingle source · unverifiedRU06 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Belgorod Oblast

Belgorod OblastFPV quadcopter · Source reports typeSingle source · unverifiedRU06 Nov 2026·Armed conflict

Drone report in Astrakhan Oblast, Russia

Astrakhan OblastSingle source · unverifiedRUduring the reporting window 05 Nov 2026–06 Nov 2026·Armed conflict

Residential damage reported after drone attack in Kursk Oblast

Kursk OblastSingle source · unverifiedRU06 Nov 2026·Armed conflict

Fire reported after drone attack in Krasnodar Krai

Krasnodar KraiSingle source · unverifiedRU05 Nov 2026·Armed conflict

Drone report in Shebekino, Russia

ShebekinoSingle source · unverifiedRU05 Nov 2026·Armed conflict

Fire reported after drone attack in Ryazan Oblast

Ryazan OblastAuto-compiledRUbetween the evening of 04 Nov 2026 and the morning of 05 Nov 2026·Armed conflict

Residential damage reported after drone attack in Voronezh Oblast

Voronezh OblastSingle source · unverifiedRU05 Nov 2026·Armed conflict

Drone report in Rostov region, Russia

Rostov regionSingle source · unverifiedRU04 Nov 2026·Armed conflict

Drone report in Tatarstan Republic, Russia

Tatarstan RepublicSingle source · unverifiedRU04 Nov 2026·Armed conflict

Drone report in Rostov region, Russia

Rostov regionSingle source · unverifiedRU04 Nov 2026·Armed conflict

Drone report in Kaluga Oblast, Russia

Kaluga OblastSingle source · unverified

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.
Drone wave reported in Russia≈ RussiaDrone report: Oryol Oblast, Russia≈ Oryol OblastDrone report in St.-Petersburg region, Russia≈ St.-Petersburg regionFlight disruption after drone alert in Rostov region≈ Rostov regionDrone report in St.-Petersburg region, Russia≈ St.-Petersburg regionEnergy infrastructure damage reported after drone attack in Rostov region≈ Rostov regionDrones shot down over Rostov region, reports say≈ Rostov regionCivilian infrastructure damaged in reported drone attack in Saratov Oblast≈ Saratov OblastResidential building damaged in reported drone attack in Belgorod Oblast≈ Belgorod OblastDrone report in Astrakhan Oblast, Russia≈ Astrakhan OblastResidential damage reported after drone attack in Kursk Oblast≈ Kursk OblastFire reported after drone attack in Krasnodar Krai≈ Krasnodar KraiFire reported after drone attack in Ryazan Oblast≈ Ryazan OblastResidential damage reported after drone attack in Voronezh Oblast≈ Voronezh OblastDrone report in Rostov region, Russia≈ Rostov regionDrone report in Tatarstan Republic, Russia≈ Tatarstan RepublicDrone report in Rostov region, Russia≈ Rostov regionDrone report in Kaluga Oblast, Russia≈ Kaluga OblastDrone report in Omsk, Russia≈ OmskDrone report in Tver, Russia≈ TverDrone report in Yartsevo, Russia≈ YartsevoExplosions reported during drone attack on Staraya Russa≈ Staraya RussaDrone report in Shebekino, Russia≈ ShebekinoPower outage reported after drone attack in Vsevolozhsk≈ VsevolozhskDrone report in Vsevolozhsk, Russia≈ VsevolozhskFire reported after drone attack in Kirishi≈ KirishiResidential damage reported after drone attack in Belgorod≈ BelgorodResidential building damaged in reported drone attack in Shebekino≈ ShebekinoDrone report in Shebekino, Russia≈ ShebekinoDrone hit on port reported in Leningrad Oblast≈ Leningrad Oblast
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.

    Latest editor-reviewed dossiers

    Full archive ↓

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

    SD30 Oct 2026Drone attack and blackout reported in ShendiSD26 Oct 2026Drone attacks reported in Gedaref State, Sudan; electricity supply disruptedRU26 Oct 2026Drone attack on Voronezh, Russia: governor reports more than 70 drones downed over the cityRU22 Oct 2026Drones downed over Kaluga Oblast, Russia, governor says

    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