DroneLedger

Armed conflict

Fire reported after drone attack in Kyiv

Kyiv (Київ) · 09 Nov 2026 · event date · city reference point on the map; exact location not yet known

According to TSN and Glavcom, drones were reported in Kyiv, Ukraine on 09 Nov 2026. [1][2]

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

Drone presenceReported[1][2]
ImpactReported[1][2]
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

2 source families · a count of sources is not a verification score

Automatically compiled · sources retrieved on 09 Nov 2026 · Dossier updated 09 Nov 2026

Latest material change

Updated automatically after the new revision passed the automatic checks. (Source revision 3.)

Revision 4

What do we know now?

What happened

TSN, citing The Kyiv City Military Administration, reported fire in Kyiv on 9 November 2026. Glavcom, citing Київська міська військова адміністрація (КМВА), reported a hit or damage to schools and a hit or damage to government buildings.

Facts at a glance
Drone type
  • No named drone type is recorded in this dossier.
Hit / damaged
  • According to Glavcom, citing Київська міська військова адміністрація (КМВА), a hit or damage was reported to an object in the category “schools” (source wording: школи)
  • According to Glavcom, citing Київська міська військова адміністрація (КМВА), a hit or damage was reported to an object in the category “government buildings” (source wording: адміністрацію)
  • According to Glavcom, citing a non-involved official body, the report published on 9 November 2026, 12:23 UTC+02:00 describes civilian infrastructure damage
  • According to Glavcom, citing an official source of an involved party, the report published on 9 November 2026, 12:23 UTC+02:00 describes civilian infrastructure damage
  • According to TSN, citing The Kyiv City Military Administration, the report describes damage; fire
Human consequences
  • Casualty details are not established in this dossier.
Who reported what
  • TSN: Assessment of drone involvement; hit / damaged
  • Glavcom: Assessment of drone involvement; hit / damaged
Source families
  • 2 source families are recorded; republication is not independent confirmation. Their independence has not yet been established by an editor

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 10 Oct 2026–08 Nov 2026: 209; currently labelled drone-confirmed: 0.

Counted dossiers (current revisions)

Archive snapshot 09 Nov 2026, 12:50 UTC; release 20261109T125014254230-32f8de. 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

Automatically published from the cited sources; their independence and this dossier have not yet been reviewed by an editor.

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

Automatically compiled and published from 2 cited articles that each report drone presence at this place and date. An automatic check found them to describe the same incident and found claims that appear to come from at least two different sources; that independence has not been established by an editor. 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
  • Київська міська військова адміністрація (КМВА) · “школи” Glavcom
  • Київська міська військова адміністрація (КМВА) · “адміністрацію” Glavcom
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
    • TSN (9 November 2026) [1]
    • Glavcom (9 November 2026) [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

According to a non-involved official body, via Glavcom, as of 09 Nov 2026 12:23 UTC+02:00: civilian infrastructure damage. According to an official source of an involved party, via Glavcom, as of 09 Nov 2026 12:23 UTC+02:00: civilian infrastructure damage. According to The Kyiv City Military Administration, via TSN, as of 09 Nov 2026 11:09 UTC+02:00: damage. According to an official source of an involved party, via TSN, as of 09 Nov 2026 11:09 UTC+02:00: fire.

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

  2. Glavcom published a report on this incident. [2]

Original sources (2)

2 source families · a count of sources is not a verification score

1TSN ()09 Nov 2026 · source family: Tsn

First observed:

2Glavcom ()09 Nov 2026 · source family: Glavcom

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 4 · 09 Nov 2026Updated automatically after the new revision passed the automatic checks. (Source revision 3.)
  2. Revision 2 · 09 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 4 · Current dossier ·

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

  2. Revision 2 ·

    Drone presence: Reported · Impact: Reported · 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: 13
Same country: 112
Same category: 278

Cite this dossier

Permanent page · Revision 4

Chicago

DroneLedger editorial team. “Drone report in Kyiv, Ukraine.” Dossier auto-ua-2026-11-09-02917a8067, revision 4, updated 09 Nov 2026. https://droneincidents.com/incident/auto-ua-2026-11-09-02917a8067/v4/

APA

DroneLedger editorial team. (09 Nov 2026). Drone report in Kyiv, Ukraine (Dossier auto-ua-2026-11-09-02917a8067, revision 4). https://droneincidents.com/incident/auto-ua-2026-11-09-02917a8067/v4/

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

Cite this version

Maker
DroneLedger editorial team
ID
auto-ua-2026-11-09-02917a8067
Revision or edition
4
Release
20261109T125014254230-32f8de
Publication date
09 Nov 2026
Accessed
09 Nov 2026
Permanent URL
https://droneincidents.com/incident/auto-ua-2026-11-09-02917a8067/v4/
Hashed file
JSON · SHA-256 4960ea5c979aa7c8e6ad8daf856337212ff3c3b1275aa148982b3f7cf63da6e5

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 Kyiv, Ukraine. ID auto-ua-2026-11-09-02917a8067; revision or edition 4; release 20261109T125014254230-32f8de; published 09 Nov 2026. https://droneincidents.com/incident/auto-ua-2026-11-09-02917a8067/v4/ Accessed 09 Nov 2026. SHA-256 4960ea5c979aa7c8e6ad8daf856337212ff3c3b1275aa148982b3f7cf63da6e5 (https://droneincidents.com/data/citations/incident/auto-ua-2026-11-09-02917a8067/r4/4960ea5c979aa7c8e6ad8daf856337212ff3c3b1275aa148982b3f7cf63da6e5/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.

Kyiv
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.
  • 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.

UA09 Nov 2026·Armed conflictNew

Fire reported after drone attack in Kyiv

KyivAuto-compiledUA09 Nov 2026·Armed conflictNew

Vehicle damage reported after drone attack in Sumy

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

Residential damage reported after drone attack in Khmelnytskyi

KhmelnytskyiAuto-compiledUA08 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Khmelnytskyi region

Khmelnytskyi regionOne-way attack drone · Family-level link · model not establishedSingle source · unverifiedUA08 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Sarny

SarnyOne-way attack drone · Family-level link · model not establishedSingle source · unverifiedUA08 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Kharkiv

KharkivSingle source · unverifiedUA08 Nov 2026·Armed conflictNew

Damage reported after drone attack in Zaporizhzhia region

Zaporizhzhia regionSingle source · unverifiedUA07 Nov 2026·Armed conflictNew

Drone report in Derhachi, Ukraine

DerhachiFPV quadcopter · Source reports typeSingle source · unverifiedUA07 Nov 2026·Armed conflictNew

Residential damage reported after drone attack in Khmelnytskyi

KhmelnytskyiAuto-compiledUA07 Nov 2026·Armed conflictNew

Vehicle damaged in reported drone attack in Kharkiv

KharkivFPV quadcopter · Source reports typeSingle source · unverifiedUA07 Nov 2026·Armed conflictNew

Drone report in Kremenchuk, Ukraine

KremenchukSingle source · unverifiedUA07 Nov 2026·Armed conflictNew

Drone report in Pavlohrad, Ukraine

PavlohradSingle source · unverifiedUA07 Nov 2026·Armed conflictNew

Drone hit on residential building reported in Kyiv Oblast

Kyiv OblastSingle source · unverifiedUA05 Nov 2026·Armed conflict

Drone report in Sumy region, Ukraine

Sumy regionSingle source · unverifiedUA05 Nov 2026·Armed conflict

Drone report in Derhachi, Ukraine

DerhachiOne-way attack drone · Family-level link · model not establishedSingle source · unverifiedUA05 Nov 2026·Armed conflict

Drones shot down over Vinnytsia region, reports say

Vinnytsia regionSingle source · unverifiedUA05 Nov 2026·Armed conflict

Drone debris falls in Kyiv, reports say

KyivOne-way attack drone · Family-level link · model not establishedSingle source · unverifiedUA05 Nov 2026·Armed conflict

Drone report in Dnipropetrovsk region, Ukraine

Dnipropetrovsk regionSingle source · unverifiedUA04 Nov 2026·Armed conflict

Energy facility damaged in reported drone attack in Kovel District

Kovel DistrictSingle source · unverifiedUA04 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Kirovohrad region

Kirovohrad regionSingle source · unverifiedUA04 Nov 2026·Armed conflict

Drone debris falls in Kyiv, reports say

KyivSingle source · unverifiedUA04 Nov 2026·Armed conflict

Drone report in Dnipropetrovsk region, Ukraine

Dnipropetrovsk regionSingle source · unverifiedUA03 Nov 2026·Armed conflict

Fire reported after drone attack in Rivne Oblast

Rivne OblastSingle source · unverifiedUA03 Nov 2026·Armed conflict

Drone report in Khmelnytskyi region, Ukraine

Khmelnytskyi regionSingle source · unverifiedUA03 Nov 2026·Armed conflict

Drone report in Cherkasy region, Ukraine

Cherkasy regionSingle source · unverifiedUA02 Nov 2026·Armed conflict

Drone report in Kyiv, Ukraine

KyivSingle source · unverifiedUA02 Nov 2026·Armed conflict

Drone report in Kherson region, Ukraine

Kherson regionSingle source · unverifiedUA02 Nov 2026·Armed conflict

Drone hit on vehicle reported in Kharkiv region

Kharkiv regionSingle source · unverifiedUA02 Nov 2026·Armed conflict

Residential building damaged in reported drone attack in Vinnytsia region

Vinnytsia regionSingle source · unverifiedUA02 Nov 2026·Armed conflict

Explosions reported during drone attack on Luhansk

LuhanskSingle source · unverified

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

456dossiers
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.
Energy facility damaged in reported drone attack in Kovel District≈ Kovel DistrictResidential damage reported after drone attack in Khmelnytskyi region≈ Khmelnytskyi regionDamage reported after drone attack in Zaporizhzhia region≈ Zaporizhzhia regionDrone hit on residential building reported in Kyiv Oblast≈ Kyiv OblastDrone report in Sumy region, Ukraine≈ Sumy regionDrones shot down over Vinnytsia region, reports say≈ Vinnytsia regionDrone report in Dnipropetrovsk region, Ukraine≈ Dnipropetrovsk regionResidential building damaged in reported drone attack in Kirovohrad region≈ Kirovohrad regionDrone report in Dnipropetrovsk region, Ukraine≈ Dnipropetrovsk regionFire reported after drone attack in Rivne Oblast≈ Rivne OblastDrone report in Khmelnytskyi region, Ukraine≈ Khmelnytskyi regionDrone report in Cherkasy region, Ukraine≈ Cherkasy regionDrone report in Kherson region, Ukraine≈ Kherson regionDrone hit on vehicle reported in Kharkiv region≈ Kharkiv regionResidential building damaged in reported drone attack in Vinnytsia region≈ Vinnytsia regionVehicle damage reported after drone attack in Sumy≈ SumyResidential damage reported after drone attack in Khmelnytskyi≈ KhmelnytskyiResidential damage reported after drone attack in Sarny≈ SarnyResidential damage reported after drone attack in Kharkiv≈ KharkivDrone report in Derhachi, Ukraine≈ DerhachiResidential damage reported after drone attack in Khmelnytskyi≈ KhmelnytskyiVehicle damaged in reported drone attack in Kharkiv≈ KharkivDrone report in Kremenchuk, Ukraine≈ KremenchukDrone report in Pavlohrad, Ukraine≈ PavlohradDrone report in Derhachi, Ukraine≈ DerhachiDrone debris falls in Kyiv, reports say≈ KyivDrone debris falls in Kyiv, reports say≈ KyivDrone report in Kyiv, Ukraine≈ KyivExplosions reported during drone attack on Luhansk≈ LuhanskFire reported after drone attack in Kyiv≈ Kyiv
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