Part 107 renewal: how it works and how programs track currency

Part 107 renewal is one of the most misunderstood ideas in commercial drone work, because the certificate it seems to describe never expires. The remote pilot certificate the FAA issues does not lapse, get revoked by the calendar, or need to be reissued every few years. What does lapse is currency: a remote pilot must have completed an initial or recurrent knowledge requirement within the previous 24 calendar months to keep exercising the certificate's privileges. For a single pilot that distinction is a technicality. For a program running several pilots, it is the difference between a job that flies and a pilot who is quietly grounded.

This article covers what renewal really means under Part 107, how the 24-month currency clock is counted, and how a program keeps currency straight across a whole roster so that the pilot assigned to a job is a pilot legally cleared to fly it. The vocabulary matters here, because treating currency as an expiration date invites exactly the wrong reaction when the clock runs out.

What "renewal" really means under Part 107

Under 14 CFR 107.65, a person may not operate a small unmanned aircraft system unless they have, within the previous 24 calendar months, passed an initial aeronautical knowledge test, completed recurrent training, or met the equivalent training path available to certain Part 61 pilots. The certificate itself carries no expiration date. Search the FAA airman registry for a remote pilot and you will find a date of issue, not a date the certificate stops working. What the regulation governs is recency of aeronautical knowledge, which is a rolling status, not a document with a shelf life.

The reason this framing is worth getting right is that it changes the fix. When people think of a certificate expiring, they imagine having to start over. Under the current rule, a pilot who has lapsed does not retake the initial test to get back; they complete the recurrent training and their currency is restored. The certificate was valid the whole time. Only the authority to exercise it was paused. A program that understands currency as a status to maintain, rather than a card to renew, plans around it far more sensibly.

How the 24-month currency clock works

Currency is measured in calendar months, which is more forgiving than a to-the-day deadline and easy to misread. A pilot who completed recurrent training on the fifteenth of a month has until the last day of that month, 24 months later, to complete it again. The clock does not care about the exact day of the original completion; it runs to the end of the month. Completing training resets the window from the new completion date, and there is no penalty for doing it early, so many pilots complete a few weeks ahead to avoid any risk of a gap.

The consequence of letting the window close is specific. Once more than 24 calendar months have passed, the pilot is no longer current and may not fly under Part 107 until they complete the recurrent training. Nothing about the certificate changes, but the pilot cannot serve as remote pilot in command for a commercial operation in the meantime. For a solo operator that is an inconvenience. For a program that has scheduled that pilot on a job next week, it is a scheduling failure that surfaces at the worst possible time unless someone was tracking the date.

Tracking currency across a roster

Once a program has more than a couple of pilots, currency stops being a personal reminder and becomes a management problem. Each pilot carries an independent 24-month clock tied to their own last completion, and those dates do not line up. A ten-pilot roster has ten separate deadlines scattered across the calendar, and a single lapsed pilot can stall a project, disrupt a client deliverable, or force a last-minute reassignment. Keeping a central record of each pilot's certificate and current recency date turns ten deadlines a manager has to remember into a list the system watches.

Access is part of keeping that record trustworthy. When a program's platform is set up to show each pilot only the jobs they are assigned, and currency is tracked against each pilot in the same place, the assignment step and the currency check stop being separate tasks. A pilot whose recency has lapsed is visible as such before anyone schedules them, rather than after the flight when a client or an insurer asks who was current. The point is not more paperwork; it is that the roster carries its own status instead of living in a manager's memory.

Building currency into how jobs get assigned

The payoff of tracking currency is that it can gate assignment rather than merely inform it. If the record shows which pilots are current, then assigning a job becomes a matter of choosing from the pilots who can legally fly it, and the ones approaching a lapse are flagged early enough to complete their training first. A program that works this way rarely has a currency surprise, because the deadlines are surfaced weeks out and handled in the ordinary course of scheduling.

There is a defensibility angle too. Recency is one of the things an FAA inspector, an insurer, or a client's compliance team can ask about after the fact, and the useful answer is a record showing the pilot was current on the day of the flight. Reconstructing that from certificates and completion emails after a question is asked is slow and error-prone. A running record that ties each flight to a pilot whose currency was confirmed at the time is far easier to stand behind, and it is built as flights happen rather than assembled under pressure.

Common mistakes in Part 107 renewal

Believing the remote pilot certificate expires. The certificate does not lapse; only recency of knowledge does. Treating it as an expiring document leads pilots to think they must start over, when completing recurrent training restores currency and the certificate was valid all along.

Counting the 24 months to the exact day. Currency runs in calendar months to the end of the month, not to the anniversary date. Pilots who count to the day either cut it too close or misjudge when they lapse.

Waiting until the deadline to complete training. There is no penalty for completing recurrent training early, and early completion simply resets the clock from the new date. Leaving it to the final days risks a lapse from a busy week or a forgotten reminder.

Tracking currency only for the whole team, not each pilot. Every pilot has an independent clock tied to their own last completion. A single team-wide reminder misses the reality that ten pilots have ten different deadlines, and one lapse can ground a scheduled job.

Assuming a lapsed pilot can still fly if the certificate looks valid. A valid-looking certificate says nothing about recency. A pilot past 24 calendar months without current training may not act as remote pilot in command, regardless of what the certificate shows.

FAQ

Does a Part 107 remote pilot certificate expire?

No. The certificate itself does not expire. What must stay current is recency of aeronautical knowledge, which requires completing an initial or recurrent knowledge requirement within the previous 24 calendar months. A lapsed pilot regains currency by completing recurrent training, not by starting over.

How is the 24-month currency window counted?

It is counted in calendar months to the end of the month. If you completed training in March, you have until the last day of March two years later. Completing training early resets the window from the new completion date with no penalty.

What happens if my currency lapses?

You may not fly under Part 107 as remote pilot in command until you complete the recurrent training. The certificate remains valid, but its privileges are paused until your recency is restored. Completing the training returns you to current status.

How should a program track currency across many pilots?

Keep a central record of each pilot's certificate and current recency date, since every pilot has an independent clock. Tracking those dates against each pilot lets a program flag approaching lapses early and assign only pilots who are current on the day of the flight.

Closing thought

Part 107 renewal is really currency management wearing a misleading name. The certificate stands; recency is what has to be kept alive, on a rolling 24-calendar-month clock that runs separately for every pilot. A solo operator can track that with a calendar reminder. A program cannot, because the deadlines multiply and a single lapse can ground a scheduled job. The programs that never get caught are the ones that keep each pilot's recency in a record the system watches, so the pilot assigned to a job is always one who can legally fly it.

If you are keeping a roster of remote pilots current, 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 document vault that flags expirations, and an append-only audit log are all part of how the platform surfaces each pilot's currency before the assignment rather than after the flight.