Pilot certification tracking: keeping a roster current

Pilot certification tracking is the unglamorous discipline of knowing, at any moment and for every pilot, what credentials they hold and when the clock behind each one runs out. A drone program's roster is a set of expiration dates wearing name tags: certificates that never expire attached to currency that always does, waiver training tied to specific authorizations, checkouts tied to specific aircraft. One person can juggle their own dates. A program juggling ten pilots is doing calendar math for a living whether it admits it or not, and the math fails silently.

This article covers what a genuinely current roster knows about each pilot, the 24 calendar month clock that governs everyone on it, and the difference between a roster and a list, which turns out to be visibility. It closes with the maintenance rhythm, because a roster is a living record that decays the moment nobody owns it.

What a current roster knows about each pilot

The minimum viable entry per pilot: certificate number and issue date, verified against the FAA rather than transcribed from an interview; the date of the most recent currency event and the deadline it produces; any waiver or authorization specific training the operation's approvals require, with completion dates; aircraft checkouts by type; and the practical details audits always want, legal name as certificated and contact information. Each item exists somewhere already. Tracking means they exist together, attached to the pilot, dated, and maintained by someone whose job it is.

The distinction worth engineering into the roster is between the credential and the clock. A remote pilot certificate, once issued, does not expire; the privileges it grants are usable only when the recency requirement is satisfied. A roster that records certificate: yes and stops has captured the fact that never changes and missed the one that always does. The useful roster leads with the deadlines, sorted soonest first, because the deadlines are where a program quietly becomes illegal one pilot at a time.

The 24 calendar month clock behind every name

The governing rule is 14 CFR 107.65: a person may not exercise remote pilot in command privileges unless, within the previous 24 calendar months, they passed the initial knowledge test or completed recurrent training, with a parallel path for current Part 61 pilots. Calendar months means the window runs to the end of the 24th month, so a pilot current as of a March 10 completion remains current through March 31 two years later. Free online recurrent training resets the clock, which removes cost as an excuse and leaves scheduling as the only failure mode.

Scheduling is exactly what fails. The FAA sends no reminders, the certificate in the wallet looks identical current or lapsed, and a lapsed pilot loses nothing visible, only the legal ability to fly commercially, which reappears the moment the training is completed. That combination, silent lapse, easy cure, is what makes tracking a program responsibility rather than a personal one. The program is the party exposed when a lapsed pilot flies a client job, and the program is the party that can see all the deadlines at once.

Visibility is the difference between a roster and a list

A list is a spreadsheet somebody updates. A roster is the same data made visible at the moments decisions get made: when a scheduler assigns a pilot to next week's job, when a bid promises certificated crews, when a client audit asks who flew their site in April. The failure pattern is never that the data was unknowable; it is that the deadline lived in a file the scheduler was not looking at while making the assignment the deadline should have blocked.

The fix is to put currency where assignment happens, which is part of a broader access design argument. FlybyOps makes the case for pinning each pilot's view to the jobs they are assigned, and the roster is the management side mirror of that idea: the person handing out work sees, in the act of assigning, who is current, checked out on the required aircraft, and trained for the applicable waiver. When qualification data and assignment live in the same view, an unqualified assignment requires a deliberate override instead of a routine oversight. That single design choice retires most of the ways rosters fail.

A roster is a living record, not a snapshot

Rosters decay at the speed of the operation. A pilot completes recurrent training and tells nobody. A new hire is flying before their file exists. Someone leaves, and their row lingers, current looking, for a year. None of these are dramatic failures; all of them mean the roster and reality drift apart until an audit, an incident, or an embarrassed phone call reconciles them. The countermeasure is ownership plus rhythm: one named owner, a standing monthly pass over upcoming deadlines, and a standing rule that certain events, hire, departure, completion, incident, trigger a roster update the same week.

The payoff compounds quietly. Renewal training gets scheduled in slow weeks instead of discovered in busy ones. Bids cite verifiable facts. Insurance renewals and client questionnaires become export tasks. And when something goes wrong, the first question every reviewer asks, was the pilot qualified and current, has an answer with a date on it, produced in minutes. Programs rarely notice the roster working. They only ever notice it missing, and by then the notice is public.

Common mistakes in tracking pilot certifications

Recording the certificate and ignoring the clock. The certificate never expires; the privileges lapse every 24 calendar months without a currency event. A roster of certificate numbers with no deadlines is a list of facts that cannot go wrong and misses the one that can.

Trusting pilots to self report. The FAA sends no reminders and a lapse is invisible in the wallet. Programs that wait for pilots to mention renewals inherit every lapse as a surprise, usually mid schedule.

Keeping the roster away from scheduling. Deadlines stored where assignments are not made will be missed at assignment time. Currency and checkouts belong in the same view as the job board, blocking rather than merely documenting.

Doing the calendar math casually. Calendar months run to month end, and hand computed deadlines drift. Compute the window once, correctly, per pilot, and let the system carry it rather than re-deriving it under deadline.

Letting departures linger. A departed pilot's current looking row is a liability twice over, in audits and in the temptation to use it. Close rows on departure and move the file to retention the same week.

FAQ

What should a pilot certification tracker record?

Per pilot: verified certificate number and issue date, latest currency event and its deadline, waiver specific training, aircraft checkouts, and certificated legal name. Together, dated, owned by someone accountable, and visible where assignments are made.

How is the 24 month currency deadline calculated?

From the currency event to the end of the 24th calendar month after it. A recurrent completion dated March 10 keeps the pilot current through March 31 two years later, and the next completion resets the clock.

Does a Part 107 certificate ever expire?

No. The certificate itself is permanent, but its privileges are exercisable only with currency inside the previous 24 calendar months. A lapsed pilot regains privileges immediately upon completing the free recurrent training.

Who should own the roster in a drone program?

One named person, with a monthly review of upcoming deadlines and event triggered updates for hires, departures, completions, and incidents. Shared ownership is the polite name for the arrangement where nobody notices the lapse.

Closing thought

Certification tracking is a program's pulse check on its own legality, taken continuously and cheaply, or not at all. The data is small, the math is fixed by regulation, and the entire discipline reduces to ownership and visibility: someone maintains the dates, and the dates appear wherever work gets handed out. Programs that build that loop stop having currency emergencies. The rest schedule them, unknowingly, months in advance.

If you are responsible for knowing every pilot's certificate status at a glance, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry that tracks certification and currency, a project and job hierarchy that puts qualifications beside assignments, a document vault with expiration tracking, and an append-only audit log are all part of how the platform keeps every certificate date and recurrent deadline visible across the roster before anything lapses.