For journalists
Drone reports, traced to their evidence.
DroneLedger helps newsrooms check a drone report quickly, cite it responsibly and see later what changed. Every dossier separates whether a drone was involved, what the impact was and who was responsible, and shows which source says what.
What you can check in a dossier
Each curated dossier answers five questions: what happened operationally, whether drones were actually established, who said so first and which outlets only repeated it, what remains unknown, and what changed since. The claims table shows each key claim with its source passage, the original source and our assessment; passages are checked word for word against the source. The line “N sources · M original statements” shows how many independent statements sit behind the coverage.
What the data does and does not measure
DroneLedger is a curated archive plus clearly labelled automatically compiled reports. It is not a complete or live record of all drone incidents, and counts and trends describe this archive, not the world. Automatically compiled dossiers say so at the top; they publish only that drones were reported, attributed to the named source. Conflict incidents appear at least 24 hours after the first report and never include map coordinates or details about units or positions.
How to cite
Cite the dossier and its revision. Every published revision has a fixed page that never changes, for example /incident/<id>/v3/, so readers can see exactly what you saw. The “Cite this dossier” box and the editorial pack give a ready citation.
Data and tools
Download the archive as CSV or use the JSON API (OpenAPI). Follow everything, a country, a type of incident or a single dossier with feeds. Each dossier has a printable editorial pack (claims, limits, chronology, sources and citation). AI assistants can use our read-only MCP server at /mcp; see llms.txt.
Corrections and contact
The DroneLedger editorial desk reads every message at info@droneincidents.com: errors, missing primary sources, later investigation results or requests for clarification. Corrections are published as a new revision with a public change note; earlier revisions stay viewable unless they must be withdrawn, in which case we say so. We do not publish the names of individual editors, because the site reports on attacks by parties to armed conflicts.
How AI is used
Dossiers are compiled with AI assistance. Curated dossiers are checked against their sources line by line; automatically compiled ones are marked as such and checked afterwards. AI is never the source of a fact: every claim points to a passage in a cited source.
Reuse and licence
Our own dossier text, structured data, drawings and videos are published under CC BY 4.0: you may reuse them, also commercially, if you credit “DroneLedger (droneincidents.com)” and link to the dossier. Quoted source passages and the linked articles remain the copyright of their publishers; we include them as short quotations so you can verify our claims.
Not covered by our licence: the fonts (SIL Open Font License) and the map data (Natural Earth, public domain) keep their own terms, and quoted source passages belong to their publishers. The drone drawings and animations are schematic illustrations of a type, not evidence about any incident.
Coverage
| Published dossiers | 19 |
|---|---|
| Countries with dossiers | 10 |
| News languages monitored | 11 (ar, de, en, es, fa, fr, he, hi, ja, ru, uk) |
| Publishers we can read automatically | 111 |
| Dossiers with a claims table | 19 |
| Automatically compiled dossiers | 0 |
Dossiers per country
- Saudi Arabia · 5
- Russia · 3
- Germany · 2
- Denmark · 2
- United States · 2
- United Kingdom · 1
- Ireland · 1
- Oman · 1
- Sudan · 1
- Ukraine · 1