For insurers
An operator working on Dronetrake keeps a register that cannot be rewritten afterwards, dated by a third party and verifiable by anyone, without an account. This page says what is in it, what it proves, what it does not prove and how you receive it. The premium is yours to decide: there is no talk of discounts here.
Drone, pilot, take-off and landing to the second, places and coordinates, batteries fitted, VLOS or BVLOS, anomalies, mission and operation order. Duration is computed, drone and pilot hours grow from it. The forecast for the flight hours, read before take-off, is sealed with the entry.
UAS geographical zones on the map, hourly weather forecast with wind, gusts and rain, fetched before the flight with the time of the fetch; signed checklists; crew with certificates in force.
Serial number, class, flight hours from the register, batteries with cycles, maintenance and schedules, insurance expiry. A past date is red, thirty days before it is amber.
Certificates with type, number, country, expiry and document. A pilot with an expired certificate cannot be assigned to a mission.
One file in one package: the register entry with its chain, the aircraft, the pilot's qualifications at the time, signed checklists, weather, telemetry and evidence with SHA-256 fingerprints. As PDF and as ZIP.
Live-stream recordings, with the file fingerprint and the start time. A recording marked as evidence cannot be deleted and gets a copy off the server.
Each entry carries a SHA-256 fingerprint computed on its content plus the fingerprint of the previous entry. Changing or removing an entry breaks the chain visibly. Deleting leaves a tombstone.
Every night the head of each chain receives an RFC 3161 timestamp from an independent authority. It is free and applies to every plan: it shows that at that hour the chain was exactly that.
On the flights, recordings and files the operator marks as evidence, or on a whole mission that "must hold up before third parties", the date is set by an eIDAS qualified provider, FNMT-RCM, on the plans that include it. It is the date that can be relied upon against third parties.
The data belongs to the operator, and the operator hands it over. No Dronetrake account is needed and there is no insurer login.
A public link for a mission, a drone or a certificate: it opens without an account and shows the chain and the seals.
The logbook export per aircraft, with the head fingerprint of the chain printed on the document.
PDF and ZIP with telemetry and evidence, ready for a claim file.
A sharing link to a mission's files, with their fingerprints.
With the operator's consent, read access to their data through the documented public API.
A ZIP produced by the same exporters an operator uses, on the data of a demo European organisation: the flight register as PDF, an incident file, a flight as it leaves the API, the public verification link and a README saying what it proves and what it does not.
MGAs, carriers and association programmes that want to read their policyholders' register will find a model already written elsewhere: the software provider as a verified technology partner, data shared on the policyholder's consent, policy terms decided by the insurer. We are ready to do it that way.
The operator decides what to share and with whom. Without their yes, nothing leaves.
JSON from the API, PDF and ZIP from the files, with fingerprints to check that nothing has changed.
The chain can be recomputed and the timestamp checked with the provider, without trusting us.
We say what the register proves. What it is worth for the policy is your decision.
It is the simplest way to let your insurer read how you document your flights. The text is ready: add whatever you like.
We never promise premium discounts. We say what the register proves; the rest is the insurer's decision.