No flight without sign-off
A flight approval is filed, reviewed with comments, revised if needed, and approved by someone other than its author — a clear record of who signed off, and when, before anyone flies.
UAS Flight Ops
Flight Approvals, flight campaigns, and the checklists behind them — one workspace for a UAS flight campaign operation to run its sign-off workflow, log every flight, and keep records ready for an EASA Light UAS Operator Certificate.
A flight approval is filed, reviewed with comments, revised if needed, and approved by someone other than its author — a clear record of who signed off, and when, before anyone flies.
Flight Campaigns capture crew, UAVs, and checklists, with takeoff, landing, and flight time rolled up automatically — nothing about a flight campaign day is left to a paper log.
A calendar and project rollups turn logged flights into an operational overview, not just an archive — organization-wide, and per pilot.
Run it on our servers, or on your own company's — either way, your organization gets its own branded, private space, kept completely separate from anyone else's.
Why this, not a paper log
Most flight-ops tools stop at "digital checklist." Here's what else is different.
Comments land on the exact field, line, or list item they're about — a specific risk item, a specific crew row — not just a single approve/reject button. Revise and resubmit until an Accountable Manager other than the flight approval's own owner signs off.
Preparation, equipment, preflight, and follow-up checklists are scoped to each crew member's actual role and marked off live as the team works through them on test day — not reconstructed from memory once the flight's over.
Every organization gets its own subdomain, branding, and reference data — kept completely separate from everyone else's — with usage-based billing built in, not bolted on later.
What's included
From filing a flight approval to closing out the flight campaign it authorized.
File, review, and approve flight authorizations with inline comments and a full audit trail, before a single crew member is cleared to fly.
Record every flight campaign's crew, UAVs, and flights flown, with takeoff and landing times and total flight time rolled up automatically.
Preparation, equipment, preflight, and follow-up checklists, scoped by crew role and tracked live through test day — not left to memory.
Flag what went wrong or what to watch, rated from critical to trivial, and keep it in front of whoever it concerns until they acknowledge it.
A month-by-month calendar of every flight campaign, project-by-project rollups, and flight logs that export straight to XLSX — organization-wide, and per pilot.
Accountable managers review and approve, Pilots in Command file and revise, crew acknowledge before flying — access follows who's actually accountable.
Shared reference data for aircraft and flight areas, complete with mapped geofences and a one-click PX4 mission-file export, kept current by the team that flies them.
Every flight approval's status change, decision, and crew acknowledgement is timestamped and attributed — a permanent record of who signed off, and when.
About
A closer look at the flight approval process and the people behind it.
A flight approval authorizes a specific crew to fly a specific set of tests, and nothing else. Every step below is timestamped, so there's always a record of who approved what, and when.
A Pilot in Command drafts the flight approval: crew, UAVs, flight areas, the steps to perform, and a risk analysis with mitigations.
An Accountable Manager reads it and can comment on any specific step or risk item, requesting changes.
Once satisfied, an Accountable Manager other than the flight approval's own owner approves it — never self-approval.
Every assigned crew member reads the approved flight approval and acknowledges it — only then are they cleared to fly what's written in it.
Once approved, each flight campaign records its own crew, UAVs, and ground equipment, a flight-by-flight log, and a debriefing note for anything worth flagging — with pre- and post-flight checklists built right in.
Checked article-by-article against Part C of the EU's Light UAS Operator Certificate regulation (UAS.LUC.010–090). Not a compliance certification by itself — an LUC is granted to an organization, not a piece of software — but built around the same obligations:
Contact
Tell us how your flight campaign program runs today — we'll get back to you by email.