A day on site is one event.
Not twelve flight logs.
Reserve the airframes, flag the spares, lay the field out the way it’s staged, and start the whole thing with one press — every log stamped with the real time and tied to the day it came from. Twenty-two airframes, or one.
Built by a Part 107 operator. Commercial launch is on the way.
A twenty-two airframe show is a tested scenario, not a promise.
Twenty aircraft flying, two held as spares, four crew, three sorties — with airframes swapped between sorties and a spare substituted into a slot mid-show. That whole run is exercised end to end every time the product is tested, because a show is where operations software either holds together or quietly stops being used.
Operations has no production customers yet, so there are no testimonials on this page and no logos at the bottom of it. What we can show you is what the product is held to.
Audit-ready in one click — for the people who actually audit you.
Your insurer, at renewal and after a claim — the questionnaire asks what you fly, who flew it, and how it has been maintained. Your client’s safety or procurement team, before you are cleared onto the site at all. The prime contractor whose prequalification portal wants documents by Friday. One click, not a weekend of spreadsheets — and the request usually arrives while you are somewhere else.
Not the FAA. Part 107 does not require you to keep a flight log, there is no routine records audit of a small operator to be ready for, and we are not going to pretend otherwise — you would know. A product that sells you fear of an audit that does not happen is a product built by someone who has not done the job.
The whole operation, in one place
Crews, airframes, checklists and the flight record — so the day is planned, run and written down in the same place, instead of across six spreadsheets and a group chat.
Flight logging
Aircraft-first entries with crew manifest and client tagging, plus CSV bulk import from Aloft, AirData, DJI, or a spreadsheet — with per-row validation. Connect an AirData account and it syncs rather than waiting for a file.
Maintenance tracking
Manufacturer-spec service thresholds and airframe history in one place, with a template library across common commercial models and automatic threshold resets on service.
Currency — two clocks, not one
The FAA’s clock is aeronautical knowledge recency: recurrent training every 24 calendar months under §107.65, tracked per pilot with the next due date carried for you. The other clock is flight recency — not a Part 107 requirement, but the one insurers and enterprise clients ask about. Set your own threshold and see who is current, who is close, and who has lapsed.
Compliance reports
One-click PDF, a shareable no-login link, or direct email — scoped to fleet, aircraft, crew, or client. The records you need, when you’re asked for them.
Alerts before they bite
Alerts for maintenance coming due, certificates and insurance about to expire, and crew currency running out — while there is still time to do something about it rather than after a job has been lost.
Checklists that come due again
Run a checklist against an airframe, check every item, sign it off. Interim checks come back round for the next sortie rather than being ticked once in the morning and forgotten by the third launch.
Turn off what you don’t run
Three parts of the product are switches, set at onboarding or in Settings. Switching one off hides it — nav, entry points, the lot. Nothing is deleted and nothing is blocked, so switching it back on brings every screen back with its data intact.
Scheduling
Plan the flight, assign the aircraft and the crew, start it with one press. Off, and the product is a logbook and a maintenance record — which is all a single-aircraft operator wants it to be.
Events
A day on site as one thing rather than twelve unrelated flights: crew roles, reserved airframes, a layout grid and a live board. On when you run shows, off when you don’t.
Builds on SchedulingBusiness
Clients, jobs, quotes, invoices and revenue analytics. If you already have a bookkeeper you like, leave this one off and run the compliance side on its own.
Quote to paid, with the day in the middle.
Most fleet software starts at the logbook and stops there. This is one thread from the client record to the payment against the invoice — and the quote, the event, the signed checklists and the flights are links in it rather than five systems you reconcile by hand.
Client
A real record, not a name on an invoice: contacts, site and access notes, billing details, and the history of everything you have flown for them.
Job
The piece of work for that client. Location, contact, crew — and everything downstream inherits it instead of being retyped.
Quote
Branded PDF against that job, emailed, with sent-and-viewed tracking and a link the client can accept or decline without creating an account.
Event
The day itself, scheduled against the job: airframes reserved, spares flagged, the field laid out as it is staged. Checklists signed per airframe, and one press opens a log for every airframe flying.
Invoice
Generated from the accepted quote, with the lines filled from the flights that actually happened — so what you bill is what you flew, not what you meant to fly.
Payment, recorded
Money arrives however it arrives today — Operations is not in the middle of it. You record what came in, part payments included, and the invoice works out its own status from that ledger rather than waiting for someone to flip a flag.
One schedule
Schedule the flight, assign the aircraft and the crew, and start it with one click — the recorded start is stamped at the moment you press it, not typed in from memory afterwards. Schedule an aircraft group and it becomes one piece of work rather than six separate entries to keep in step.
It notices who is flying what
Put the same pilot on two aircraft in the air at once and it says so. It warns rather than blocks, and there is a setting for operators who hold a waiver — your call, on the record, not a wall in the middle of a job.
Imports amend, they don’t duplicate
An AirData or CSV import lands against the schedule you already made, matched on aircraft and time, instead of creating a second copy of the same flight. The provenance of every log is recorded, so you can see what came from a file and what came from the flightline.
Still optional, if you want it
The whole Business section is a switch. Turn it off and the quote-to-paid thread above simply is not there, and what is left runs the flying. It is deliberately not accounting either — no ledger, no reconciliation, no payroll, and the money arrives however it arrives today. If you have a bookkeeper you like, keep them.
Want in when Operations launches?
The compliance core and the business layer above are built and in test ahead of commercial launch. Leave your email and we’ll tell you the moment it’s ready.