Most commercial UAS operators know when their Part 107 certificate expires. Fewer track pilot medical currency, insurance expiration, individual aircraft maintenance intervals, and battery health in a single system — and most don’t find out that’s a problem until an audit, an incident, or a client’s compliance questionnaire forces the issue.
These are the records that prove your operation was conducted safely and legally. They don’t need to be elaborate — but they need to exist, and they need to be current.
What Compliance Actually Requires You to Track
For a commercial UAS operation, the baseline compliance record set includes Part 107 certificate numbers and expiration dates for every pilot, medical certificate class and currency where applicable, insurance policy expiration, FAA registration numbers for every aircraft, and aircraft-specific maintenance records.
COA applications require you to list your RPIC roster with certificate numbers. Insurance certificates come up in client onboarding. Maintenance records matter if an incident occurs and the question becomes whether the aircraft was airworthy. These aren’t theoretical requirements — they’re documents that get requested, and “I didn’t keep that” is not an acceptable answer in any of those situations.
FlightDeck’s Compliance Manager
The Compliance Manager in FlightDeck tracks all of this in a structured database, organized into tabs that mirror how the information is actually used.
The RPIC Roster tab records each pilot’s full name, contact information, Part 107 certificate number and expiration, medical certificate class and expiration, and insurance expiration. Every expiration date gets a status indicator — green for current, yellow for approaching, red for expired or critically close. If any single expiration is red, the overall pilot status shows red. The status rolls up so you can see at a glance whether every pilot on your roster is current.
The Aircraft Fleet tab records make, model, FAA registration number, airframe serial number, flight controller serial number, and Remote ID module — the fields that go into COA applications and appear on incident reports.
The Maintenance Log
The Maintenance Log tab is the flight-by-flight inspection record. Each entry records the date, the RPIC, the aircraft by FAA registration and model, flight hours, whether props were inspected, battery condition, whether any cracks or structural issues were found, screw tightness, firmware versions for both aircraft and remote, software version, and GPS/RTK status. There’s also a notes field for anything that doesn’t fit a checkbox.
These entries are written from the Drone Maintenance app and read by the Compliance Manager, which means the record is populated as part of normal pre- and post-flight operations rather than as a separate administrative task.
The entire maintenance history is filterable by RPIC, by aircraft, and by date range. When you need to pull records for a specific aircraft over a specific period — for an audit, an insurance claim, or a client requirement — the filter takes seconds.
Battery Pool
The Battery Pool tab tracks each battery in your fleet: serial number, model, type, assigned RPIC, current custody, status, cycle count, health percentage, and date last seen. Battery health degrades over cycles, and tracking this per-unit lets you catch batteries that are approaching end-of-service before they become a problem in the field.
The Record That Wasn’t There
Compliance records have a way of mattering at exactly the worst time — when something goes wrong, when a client’s procurement team runs a vendor audit, when a government contract requires documentation. The operators who fare best in those situations are the ones who’ve been keeping records all along, not the ones who have to reconstruct history from memory.
The Compliance Manager in FlightDeck doesn’t turn record-keeping into a project. It makes it part of the normal workflow so that when the records are needed, they’re already there.