About

About DroneLedger.

DroneLedger is an independent archive of drone incidents worldwide. Each dossier separates what was reported from what is confirmed, and links to the original sources.

How this site is made

DroneLedger is an independent project. Its editorial work is done with AI tools, and we say so openly. There are two kinds of dossiers:

Curated dossiers are researched and checked line by line against their cited sources: every sentence, date, number and evidence state must be traceable to an original source, preferably an official or first-hand one. The page shows the date of that check.

Automatically compiled dossiers are clearly labelled “not yet curated”. In them, every claim must be supported by a passage in the cited source, claims by parties to a conflict are never shown as confirmed, and operator attribution is never inferred.

If you find an error in either kind, please tell us: corrections are part of the record.

Corrections

Found an error, a better source, or a dossier that should be updated? Email info@droneincidents.com with the dossier link and the source. Corrections are recorded as a new revision with a public change note in the dossier.

Contact

General questions and press: info@droneincidents.com.

Privacy

This site sets no cookies, uses no analytics or advertising trackers, and loads no third-party resources: fonts and map data are served from our own server. Like any web server, ours keeps short technical access logs (including IP addresses) for security and troubleshooting; they are rotated automatically and not used for profiling. If you email us, we use your message only to respond and to process your correction.

Independence

DroneLedger is not affiliated with any government, military, airport, drone manufacturer or counter-drone company, and does not accept payment for coverage.