Getting started
About twenty minutes from a new account to a compliance verdict on a real mission.
1. Create your organisation — and pick the jurisdiction carefully
An organisation is bound to one civil-aviation jurisdiction, chosen when you create it, and it inherits that regulator’s rulebook. Everything downstream — which limits apply, which documents are required, what counts as a night flight — follows from that choice.
Operating in more than one country means more than one organisation under the same account. That is deliberate: a single blurred ruleset would be wrong everywhere.
2. Add your fleet
Aircraft, batteries, controllers and equipment each have a profile (the shared specification) and instances (the physical items, with serial numbers). Add the profile once, then add each airframe against it.
Every instance gets a system number and a QR code you can print and scan.
3. Add your people and their certificates
Pilots, their licences and their recency. Upload the documents and set expiry dates — the daily scan warns you before anything lapses, which is the difference between finding out now and finding out during an audit.
4. Plan a mission
Draw the operating area, set the window and assign the kit and crew. DronOps evaluates the plan against the regulator bound to that organisation and tells you where you stand before you fly.
Times are entered in the site’s local time, not your browser’s. A mission planned in Dubai from London still means Dubai evening.
5. Get the approval, then record it
Regulator approval happens outside DronOps. Record the authority, the reference and upload the approval document — a mission cannot reach approved without them, because an approval with no evidence is not an approval.
6. Import the flight log
After flying, import the aircraft’s log. DronOps matches it to the approved mission and records the actuals. There is no way to type in a flight that never happened — which is precisely what makes the record worth showing a regulator.
Two things worth knowing early
Nothing is really deleted. Archiving hides a record; it stays retrievable. If you genuinely need erasure there is a deliberate path for it, with a 30-day window in which you can change your mind.
Warnings do not block you. DronOps flags problems and records that you proceeded anyway. The regulator’s approval is the real gate — our job is to make sure nothing is a surprise.