Drone training records: what to keep for every pilot

Drone training records are the documents that prove each pilot was qualified for the work they were given, and the striking thing about them is how few the FAA demands and how many everyone else expects. Part 107 requires a certificate and current aeronautical knowledge, full stop. Clients, insurers, waiver conditions, and courtrooms require considerably more: evidence of aircraft checkouts, mission specific preparation, and the recurrent completions behind the word current. The gap between the legal minimum and the practical expectation is exactly where training records live.

This article sorts the paperwork into three piles: what the rules require, the one certificate the FAA will ask to see, and the training the FAA never sees but a program still has to be able to prove. It closes with retention, because a training file's value is realized years after the training, usually on short notice, usually by someone checking dates.

What the rules require and what they assume

The regulatory floor is short. A remote pilot in command holds the certificate and has satisfied the recency requirement within the previous 24 calendar months; everyone else on the crew operates under that pilot's supervision. No rule obliges a standard Part 107 operation to run a training program, keep a syllabus, or document a single practice flight. Waivers and specific authorizations change that picture, since their conditions frequently require training on the waived provisions, and an operation flying under one has agreed to whatever documentation those conditions imply.

The assumption buried under the floor is the interesting part. The rules assume the remote pilot in command is competent on the actual aircraft, in the actual operation, and that assumption becomes the operator's problem the moment anything goes wrong. An insurer, a plaintiff's attorney, or the FAA itself will ask how the company knew this pilot could fly this aircraft on this mission, and the certificate answers none of that. Training records are how an operation converts we assumed into we verified, dated and signed.

The recurrent certificate the FAA asks about

One training document has a regulator attached. Currency under Part 107 is maintained by completing recurrent training every 24 calendar months, and for most working pilots that means the FAA's free online course, ALC-677 on the FAA Safety Team site, which finishes with a completion certificate. That certificate is the proof of currency a pilot presents when the FAA asks, which makes it the rare training record with a specific, external audience. It also carries the date the next 24 calendar month window runs from, to the end of that month.

Handled well, the certificate is a two minute filing event: pilot completes the course, downloads the certificate, and a copy lands in the program's records with the completion date and the computed deadline. Handled badly, it lives in a personal downloads folder until a ramp check or a client audit asks for it, and the program discovers it has been scheduling a pilot whose currency it cannot demonstrate. Currency lapses do not cancel the certificate, but they suspend the privileges, which for a commercial operation is the same thing on the day it matters.

Records for the training the FAA never sees

Everything else a good program teaches is invisible to the regulator and vital to everyone else. Aircraft type checkouts, that a pilot has demonstrated the specific airframe, its failure modes, and its quirks before flying it on paid work. Mission qualifications, night operations, over people categories, complex sites, mapped to the jobs that need them. Crew roles, visual observer briefings, emergency procedures rehearsed rather than merely read. Each of these deserves the same minimal record: what was trained, who trained it, who demonstrated it, and the date, signed by someone accountable.

Those records earn their keep at assignment time, because qualification and access are two views of the same decision. A scheduler should see which pilots are checked out on the aircraft a job requires, and a pilot's day should contain the work they are cleared for, which is the argument FlybyOps makes for aligning each pilot's access with their assigned jobs. When the training file and the assignment system agree, an unqualified pairing becomes hard to create by accident. When they live apart, the gap is discovered by the incident report.

Training that is not written down did not happen

That sentence is unfair to the trainer and exactly how every outside reviewer will treat the question. An insurer pricing a policy, a client's vendor audit, an attorney after a mishap, and an FAA inspector examining a waiver operation all reduce training to the same test: show me. A program that ran excellent checkouts and kept nothing fails that test identically to a program that ran none, and it fails while telling the truth, which is the most expensive way to fail.

The record that passes is unglamorous. A per pilot file holding the certificate and its dates, each recurrent completion, each checkout and qualification with signatures, and any waiver specific training the operation's authorizations require. A retention habit that keeps files for former pilots, because questions about a flight outlive the employment of the person who flew it. And a rhythm, quarterly is plenty, of reconciling the files against the roster and the schedule. An afternoon a quarter buys the ability to answer show me in five minutes for years.

Common mistakes in keeping drone training records

Equating the certificate with training. The Part 107 certificate proves a knowledge test, nothing about the aircraft or mission in front of the pilot. Programs that stop documenting at the certificate have records for the one thing nobody disputes.

Letting completion certificates live in personal inboxes. The recurrent certificate is the proof of currency the FAA can request. If the program cannot produce it without the pilot's help, the program cannot really demonstrate its own roster is legal.

Training without signatures and dates. An undated checkout is a rumor. Every training event needs what was covered, who conducted it, who demonstrated it, and when, signed, or it will not survive the first skeptical reader.

Ignoring waiver training conditions. Waivers and authorizations often carry explicit training requirements, and flying under one adopts them. The waiver file and the training file must point at each other, or the operation is out of compliance while feeling diligent.

Purging files when pilots leave. Questions about a flight arrive years later and attach to the flight, not the employment. Former pilots' training records belong in retention, closed and dated, for as long as the operation's exposure runs.

FAQ

What training records does the FAA require for Part 107?

For standard operations, none beyond holding the certificate and maintaining recency through recurrent training every 24 calendar months. Waivers and specific authorizations add their own training conditions, which the operation must document as agreed.

What proves a pilot's currency to the FAA?

The completion certificate from the recurrent training course, dated within the previous 24 calendar months. Pilots present it on request, so both the pilot and the program should hold copies with the deadline computed and tracked.

What should an aircraft checkout record include?

The airframe or type covered, the skills and failure procedures demonstrated, who conducted and who completed the checkout, and the date, with signatures. That single page is what later connects a pilot to the aircraft they were assigned.

How long should drone training records be kept?

Keep them at least as long as questions about the flights can arrive, which means across insurance cycles, contract audit windows, and any litigation horizon. Records for departed pilots stay in retention rather than leaving with them.

Closing thought

Training is the part of a drone program that most resembles culture: everyone insists theirs is strong, and only the documentation says whether that is a fact or a feeling. The records are small, a certificate here, a signed checkout there, and their sum is the program's answer to the only question outsiders ever really ask, which is how it knew its people were ready.

If you are putting structure behind a drone team's training records, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry that tracks certification and currency, a document vault with expiration tracking, role-based access control, and an append-only audit log are all part of how the platform keeps every completion certificate and sign-off dated, attributed, and ready to produce.