DroneLedger

Armed conflict · Single source · unverified

Drone report in Odesa, Ukraine

Odesa (Одеса) · 12 Nov 2026 · event date · city reference point on the map; exact location not yet known

According to Dumskaya, drones were reported in Odesa, Ukraine on 12 November 2026. [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 12 Nov 2026 · Dossier updated 13 Nov 2026

What do we know now?

What happened

Dumskaya, citing полиции, reported a hit or damage to apartment buildings in Odesa on 12 November 2026. Dumskaya reported a hit or damage to cars.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Hit / damaged
  • According to Dumskaya, citing полиции, a hit or damage was reported to an object in the category “apartment buildings” (source wording: многоэтажке)
  • According to Dumskaya, a hit or damage was reported to an object in the category “cars” (source wording: автомобиль)
Human consequences
  • Casualty details are not established in this dossier.
Who reported what
  • Dumskaya: Assessment of drone involvement; hit / damaged
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 13 Oct 2026–11 Nov 2026: 232; currently labelled drone-confirmed: 0.

Counted dossiers (current revisions)

Archive snapshot 13 Nov 2026, 04:47 UTC; release 20261113T044703715291-bed505. 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
  • полиции · “многоэтажке” Dumskaya
  • media · “автомобиль” Dumskaya
Live warnings in Ukraine: use the official alerts
Air Alert app (Povitriana tryvoha), official, developed with the Ministry of Digital Transformation · Official air alert map

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
    • Dumskaya (12 November 2026) [1]
    • Град [2]
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.

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

Original sources (2)

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

1Dumskaya ()12 Nov 2026 · source family: Dumskaya

First observed:

2Град12 Nov 2026 · source family: Odesa police · additional reporting

First observed:

Search native-language coverage

External Google News search using the recorded place and dossier date. Results may concern other events; they have not been reviewed by DroneLedger.

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

Editorial changes

  1. Revision 3 · 13 Nov 2026Sources checked with AI; existing assessments retained. Added: Град.
  2. Revision 2 · 12 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 3 · Current dossier ·

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

  2. 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: 134
Same category: 316

Cite this dossier

Permanent page · Revision 3

Chicago

DroneLedger editorial team. “Drone report in Odesa, Ukraine.” Dossier auto-ua-2026-11-12-8eecf0e83e, revision 3, updated 13 Nov 2026. https://droneincidents.com/incident/auto-ua-2026-11-12-8eecf0e83e/v3/

APA

DroneLedger editorial team. (13 Nov 2026). Drone report in Odesa, Ukraine (Dossier auto-ua-2026-11-12-8eecf0e83e, revision 3). https://droneincidents.com/incident/auto-ua-2026-11-12-8eecf0e83e/v3/

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

Cite this version

Maker
DroneLedger editorial team
ID
auto-ua-2026-11-12-8eecf0e83e
Revision or edition
3
Release
20261113T044703715291-bed505
Publication date
13 Nov 2026
Accessed
13 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-ua-2026-11-12-8eecf0e83e/v3/
Hashed file
JSON · SHA-256 f7d57be204fd62e9dc144330932dbe18468a942ac1ed21abe13fea96f47eedf9

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 Odesa, Ukraine. ID auto-ua-2026-11-12-8eecf0e83e; revision or edition 3; release 20261113T044703715291-bed505; published 13 Nov 2026. https://droneincidents.com/incident/auto-ua-2026-11-12-8eecf0e83e/v3/ Accessed 13 Nov 2026. SHA-256 f7d57be204fd62e9dc144330932dbe18468a942ac1ed21abe13fea96f47eedf9 (https://droneincidents.com/data/citations/incident/auto-ua-2026-11-12-8eecf0e83e/r3/f7d57be204fd62e9dc144330932dbe18468a942ac1ed21abe13fea96f47eedf9/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.

OdesaKhersonTulcea
Approximate: city 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.

UA12 Nov 2026·Armed conflictNew

Drone report in Odesa, Ukraine

OdesaSingle source · unverifiedUA12 Nov 2026·Armed conflictNew

Drone report in Bila Tserkva, Ukraine

Bila TserkvaSingle source · unverifiedUA12 Nov 2026·Armed conflictNew

Drone report in Zaporizhzhia region, Ukraine

Zaporizhzhia regionSingle source · unverifiedUA12 Nov 2026·Armed conflictNew

Fire reported after drone attack in Kovel

KovelOne-way attack drone · Family-level link · model not establishedAuto-compiledUA12 Nov 2026·Armed conflictNew

1 person killed in reported drone attack in Kyiv

KyivAuto-compiledUA12 Nov 2026·Armed conflictNew

Drone report in Kherson region, Ukraine

Kherson regionSingle source · unverifiedUA12 Nov 2026·Armed conflictNew

Drone report in Rivne, Ukraine

RivneSingle source · unverifiedUA11 Nov 2026·Armed conflictNew

Drone report in Kyiv, Ukraine

KyivSingle source · unverifiedUA11 Nov 2026·Armed conflictNew

Fire reported after drone attack in Kharkiv region

Kharkiv regionFPV quadcopter · Source reports typeSingle source · unverifiedUA11 Nov 2026·Armed conflictNew

Drone report in Zaporizhzhia region, Ukraine

Zaporizhzhia regionFPV quadcopter · Source reports typeSingle source · unverifiedUA11 Nov 2026·Armed conflictNew

Industrial damage reported after drone attack in Chernivtsi

ChernivtsiSingle source · unverifiedUA11 Nov 2026·Armed conflictNew

Fire reported after drone attack in Yahotyn

YahotynAuto-compiledUA10 Nov 2026·Armed conflictNew

Fire reported after drone attack in Zhytomyr Oblast

Zhytomyr OblastSingle source · unverifiedUA10 Nov 2026·Armed conflictNew

Drone report in Kramatorsk, Ukraine

KramatorskFPV quadcopter · Source reports typeSingle source · unverifiedUA10 Nov 2026·Armed conflictNew

Fire reported after drone attack in Shostka

ShostkaSingle source · unverifiedUA10 Nov 2026·Armed conflict

Energy infrastructure damage reported after drone attack in Ladyzhyn

LadyzhynSingle source · unverifiedUA10 Nov 2026·Armed conflict

Drones shot down over Sevastopol, reports say

SevastopolSingle source · unverifiedUA10 Nov 2026·Armed conflict

Power outage reported after drone attack in Luhansk

LuhanskSingle source · unverifiedUA10 Nov 2026·Armed conflict

Power outage reported after drone attack in Donetsk

DonetskSingle source · unverifiedUA10 Nov 2026·Armed conflict

Explosions reported during drone attack on Berdyansk

BerdyanskSingle source · unverifiedUA10 Nov 2026·Armed conflict

Drone report in Sumy, Ukraine

SumyAuto-compiledUA10 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Kryvyy Rih

Kryvyy RihSingle source · unverifiedUA09 Nov 2026·Armed conflictNew

Drone report in Kramatorsk, Ukraine

KramatorskFPV quadcopter · Source reports typeSingle source · unverifiedUA09 Nov 2026·Armed conflict

Drone report in Kherson, Ukraine

KhersonSingle source · unverifiedUA09 Nov 2026·Armed conflictNew

Drone report in Ukraine

UkraineSingle source · unverifiedUA09 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Kharkiv region

Kharkiv regionSingle source · unverifiedUA09 Nov 2026·Armed conflict

Drone debris falls in Kyiv, reports say

KyivAuto-compiledUA09 Nov 2026·Armed conflict

3 people injured in reported drone attack in Sumy

SumyFPV quadcopter · Source reports typeSingle source · unverifiedUA09 Nov 2026·Armed conflict

Fire reported after drone attack in Khmelnytskyi

KhmelnytskyiAuto-compiledUA08 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Khmelnytskyi region

Khmelnytskyi regionOne-way attack drone · Family-level link · model not establishedSingle source · unverified

Showing the newest 30 of 503 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.

503dossiers
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 report in Ukraine≈ UkraineDrone report in Zaporizhzhia region, Ukraine≈ Zaporizhzhia regionDrone report in Kherson region, Ukraine≈ Kherson regionFire reported after drone attack in Kharkiv region≈ Kharkiv regionDrone report in Zaporizhzhia region, Ukraine≈ Zaporizhzhia regionFire reported after drone attack in Zhytomyr Oblast≈ Zhytomyr OblastResidential building damaged in reported drone attack in Kharkiv region≈ Kharkiv regionResidential building damaged in reported drone attack in Khmelnytskyi region≈ Khmelnytskyi regionDrone report in Bila Tserkva, Ukraine≈ Bila TserkvaFire reported after drone attack in Kovel≈ Kovel1 person killed in reported drone attack in Kyiv≈ KyivDrone report in Rivne, Ukraine≈ RivneDrone report in Kyiv, Ukraine≈ KyivIndustrial damage reported after drone attack in Chernivtsi≈ ChernivtsiFire reported after drone attack in Yahotyn≈ YahotynDrone report in Kramatorsk, Ukraine≈ KramatorskFire reported after drone attack in Shostka≈ ShostkaEnergy infrastructure damage reported after drone attack in Ladyzhyn≈ LadyzhynDrones shot down over Sevastopol, reports say≈ SevastopolPower outage reported after drone attack in Luhansk≈ LuhanskPower outage reported after drone attack in Donetsk≈ DonetskExplosions reported during drone attack on Berdyansk≈ BerdyanskDrone report in Sumy, Ukraine≈ SumyResidential building damaged in reported drone attack in Kryvyy Rih≈ Kryvyy RihDrone report in Kramatorsk, Ukraine≈ KramatorskDrone report in Kherson, Ukraine≈ KhersonDrone debris falls in Kyiv, reports say≈ Kyiv3 people injured in reported drone attack in Sumy≈ SumyFire reported after drone attack in Khmelnytskyi≈ KhmelnytskyiDrone report in Odesa, Ukraine≈ Odesa
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