Get started

Writing about Dronetrake · Articles

Before take-off

After a drone incident, the decisive question is often not what happened, but what the pilot knew and had done before the flight. Three news stories from August 2026, and what it takes to prove it.

Checked on 6 October 2026 — re-checked on 6 October 2026

Languages: Italiano · English · Français · Deutsch · Ελληνικά · Español · Nederlands · Polski · Português · Română

After a drone incident, the decisive question is rarely about the incident itself. It is about what happened before: what the pilot knew, what they had checked, which risks they had assessed and what measures they had taken. And at that point, it is not enough to have done things properly. You have to be able to prove it.

Three news stories from August 2026 show this from three different angles.

Kent: preparation under scrutiny

In August 2025, on the Isle of Sheppey, a Kent Police drone struck an overhead cable seconds after take-off and fell on a child, who had two surgeries on their hand and has since recovered. A year later, the Independent Office for Police Conduct (IOPC), which oversees the police complaints system in England and Wales, concluded that the officer who was flying the drone, a special inspector, should attend a misconduct meeting. The reason is an alleged breach of the police standards of professional behaviour “relating to their preparation and risk assessment prior to launching the drone”.

At issue is not the flight. It is the minutes before.

Brussels: poor planning becomes a reportable occurrence

Commission Implementing Regulation (EU) 2026/1821, in force since 17 August 2026, updates the list of occurrences that must be reported to the authorities. For the first time, it includes an annex dedicated to drones. The annex covers UAS for which a certificate or declaration for design is required and, among the reportable occurrences, it lists at point 1.1(2) “inappropriate planning of the UAS operation and the related mitigation measures, which have or could have endangered any aircraft or any other person”.

In other words, for some operators, planning well is no longer just good practice: inappropriate planning is an occurrence that can end up in an official report. And to prove that yours was not, you have to be able to show it exactly as it was before the flight.

Zwolle: the notice was there, but that has to be proved

On 28 August 2026, in Zwolle in the Netherlands, an operator was carrying out photogrammetric surveys of the facades of two residential complexes. One drone was damaged, probably by a shot from an air rifle. According to the operator, a second drone was shot at with what sounded like an airsoft pistol; a few seconds later another man came out onto the balcony and threw a potted plant at it, bringing it down. The operator says they notified the tenants in advance, by email and with notices in the entrance halls, and has reported the incident to the Human Environment and Transport Inspectorate (ILT) and the Dutch Safety Board (OVV).

If a case like this ever reaches a judge or an insurer, that email and a photo of the notice in the entrance hall will count only if it can be proved that they existed before the flight, and that they were not prepared afterwards.

What turns a record into evidence

A PDF flight plan, a paper checklist, a folder of photos: these are useful documents, but after an incident they all have the same flaw. Anyone can argue that they were written, corrected or completed after the fact.

For a record to hold up before third parties, three things are needed:

  1. It must be created as things happen, not reconstructed afterwards.
  2. Any change must be visible. A correction must become a new entry, not an overwrite.
  3. The date must be certified by someone else. In Europe, there is a specific instrument for this: the qualified electronic time stamp. Under the eIDAS Regulation, it enjoys the presumption of the accuracy of the date and time it indicates, and of the integrity of the data to which it is bound (Article 41(2)). Anyone who challenges it has to prove otherwise.

How Dronetrake does it

Dronetrake, the European platform for people who work with drones, is built on these three requirements.

Created on the spot. A checklist is frozen when it is signed, with the signer's name and the time. Every file attached to a mission, whether a NOTAM, a permit or the photo of the notice to residents, is recorded on upload with a digital fingerprint (SHA-256), its size, its type and the time.

Nothing is changed in secret. A logged flight cannot be edited: a correction becomes a new entry, and no flight can be deleted before three years have passed. Flights, checklists, files and video recordings each have their own chain: every entry carries the fingerprint of the one before, and altering one breaks the chain from that point on.

Someone else certifies the date. If the operator switches time stamps on, the chains are sealed every night with a time stamp from an external service. On the plans that include it, missions with the “Must hold up before third parties” option instead receive a qualified eIDAS time stamp, issued by FNMT-RCM, the Spanish Royal Mint.

And verification is open to everyone. The mission report carries a QR code that anyone can scan, without an account, to check the flights and the files delivered. The operator can also download the full dossier, with instructions for verifying it even without Dronetrake.

None of this prevents incidents or replaces the pilot's judgement. It does just one thing: when someone asks “What did you know before you took off?”, the answer already exists, with its date, and no one has been able to change it.

Sources

Do you fly for work? This survey came out of a question we ask every day: «may I fly here?». If you ask it too, tell us how you work — three questions, and we tell you what you'd need.

Tell us your scenario

← Back to the press room