Drone pilot logbook: tracking hours and currency across a roster

The drone pilot logbook inherited its shape from manned aviation, where logged hours gate certificates and ratings. Part 107 broke that link: the FAA sets no flight-hour minimums for remote pilots and no requirement to log time at all. The hours still matter, just to different audiences. Insurers price on them, clients screen on them, waiver applications lean on operational history, and programs assign work based on them.

Meanwhile, the clock the regulation does run, certificate currency, is the one personal logbooks track worst. A program managing one pilot can hold all of this in one head. A program managing a roster cannot, and the gap between individual logbooks and a program-level record is where lapses hide.

What Part 107 requires of pilot records, and what it does not

Part 107 asks remote pilots to hold a current certificate and to keep their aeronautical knowledge recent, and very little else on the records front. The recency rule, 14 CFR 107.65, requires completing the applicable training or testing within the previous 24 calendar months. The certificate itself does not expire; the privilege of exercising it depends on that recency window staying satisfied, which makes the training date the single most consequential field in any pilot record. A lapse is recoverable but not gracefully: a pilot whose window closes may not exercise the certificate's privileges until the training is completed, which means the discovery is best made by the roster, months out, rather than by the client, on site.

Everything beyond that is the program's own construction: hour totals, type breakdowns, qualifications, and internal sign-offs exist because operations, insurance, and contracts need them, and the program gets to design them well or badly.

The hours worth tracking and who asks for them

Total flight time is the number everyone quotes and the least useful one on its own. The breakdowns are where the questions land. Hours per aircraft type tell an insurer whether the pilot assigned to the heavy-lift airframe has meaningful time on it. Hours per mission profile, mapping, vertical inspection, night operations, public-safety support, tell a client whether the crew has done this specific kind of work before. Recent hours, over the last quarter or year, tell the program whether a pilot is flying enough to stay sharp or coasting on a total built years ago.

Waiver applications draw on the same well: an operational history that demonstrates depth in the relevant conditions supports the safety case in ways a raw total cannot. The requests arrive on their own schedule. Insurance renewals land annually and want the year's hours by aircraft type, client prequalification packets appear with bid deadlines attached, and a waiver application can surface any quarter the program decides to expand. A roster that maintains the breakdowns continuously treats each request as an export; one that does not treats each request as a project. The rule of thumb for what to track is borrowed from the flight log itself: record the breakdowns someone will eventually ask for, because reconstructing them later from raw entries is possible and miserable.

Currency and qualifications beyond the certificate

The recurrent training date is the anchor, and it deserves a horizon, since a date discovered the week it lapses helps nobody. Around it sits a second layer the regulation never mentions: internal aircraft checkouts before a pilot flies a new platform, mission qualifications for work like night operations or operations near energized equipment, client- and site-required training such as safety inductions for utility or rail environments, and any medical or background requirements company policy or contracts impose.

Each item carries the same three fields: what it is, when it was satisfied, and when it expires or needs renewal. The list grows with the program's verticals. A utility client adds an arc-flash awareness requirement, a rail client adds track safety training, a municipal contract adds a background check. Each addition is easy to satisfy once and easy to lose track of afterward, which is the argument for holding them all in one structure with one expiration horizon. Programs that track the first two fields and skip the third have built a museum of qualifications rather than a roster they can staff from.

From personal logbooks to a program roster

The individual drone pilot logbook answers questions about one pilot. The program needs the roster view: who is current, who is qualified for the mission type, whose certification lapses inside the next sixty days, and who has the type hours the client contract specifies. That view has to exist independently of anyone's personal records, because personal logs follow personal formats, live on personal devices, and leave with the pilot.

The roster earns its keep at assignment time. Work should route only to pilots whose currency and qualifications clear it, and assignment and visibility travel together: the same structure behind why pilots should only see their assigned jobs lets a program put the right people on the work and keep everyone else's view scoped to their own. When a pilot departs, they take a personal copy of their history; the program record, the one that supports insurance renewals, client audits, and waiver applications, stays. On the horizon itself, a rolling window of roughly sixty days works for many programs: long enough to schedule recurrent training around committed work, short enough that the list stays actionable, reviewed as a standing item in the operations cadence rather than an annual archaeology project.

Common mistakes in pilot logbook and roster management

Relying on each pilot's personal logbook. Personal logs leave with the pilot, follow personal formats, and answer to nobody. The program record supports insurance, contracts, and audits, and it has to exist independently.

Tracking hours and ignoring the currency clock. Hours have no regulatory deadline; recurrent training does. A roster with rich hour totals and no expiration horizon still produces a lapsed pilot on a job site.

Finding lapses at assignment time. Currency discovered the morning of a mobilization becomes a scramble or a violation. Expirations should surface on a horizon long enough to schedule training around the work.

Logging total time without type or mission breakdowns. Four hundred hours answers almost nothing an insurer or client asks. Hours per aircraft type and mission profile are where the real questions land.

Running the roster in a spreadsheet with no owner. Shared sheets drift: stale dates, overwritten cells, no history of who changed what. A roster is a living record that needs an owner, a review cadence, and a trail behind changes.

FAQ

Do Part 107 pilots have to log flight hours?

No. Part 107 sets no hour minimums and no logging requirement for remote pilots. Hours get tracked because insurers, clients, and waiver applications ask for them, and because programs use them to qualify pilots for mission types.

How does a remote pilot stay current?

By completing the required recurrent training within the preceding 24 calendar months under 107.65. The certificate itself does not expire; the privilege to exercise it depends on that recency window staying satisfied.

What should a program track for each pilot?

Certificate number and status, recurrent training dates, total and per-type hours, mission qualifications, client or site-specific training, and internal sign-offs, with every expiration visible far enough ahead to act on.

Who owns the pilot logbook, the pilot or the program?

Both keep records with different jobs. The pilot's personal log supports a career. The program's roster record supports operations, insurance, and audits, and it stays behind when the pilot moves on.

What happens if a pilot's recurrent training lapses?

The certificate is not revoked, but the pilot may not exercise its privileges until the required training is completed. For a program, that pilot comes off assignable status the day the window closes, which is why expirations belong on a forward-looking horizon.

Closing thought

A drone pilot logbook does its real work at the roster level, where hours, currency, and qualifications stop being personal history and become the basis for who flies what tomorrow. The programs that get this right track the breakdowns their audiences ask for, watch the one clock the regulation runs, and keep the record in program hands with expirations visible before they bite.

If you are tracking hours and currency across a pilot roster, FlybyOps was built for the operational record problem at the center of regulated drone work. A pilot registry with certification and currency tracking, role-based access control, a job hierarchy that ties assignments to the people cleared for them, and an append-only audit log are all part of how the platform supports a roster the program can staff from with confidence.