Skip to content
Tobren Operations Docs

Part 107 currency

Tobren Operations tracks crew currency on two separate clocks and labels them apart, because only one of them is an FAA requirement. Currency shows on the Crew roster, on each crew member’s detail page, and in a crew-scope compliance report.

The two clocks

1. Aeronautical knowledge recency — the regulation

14 CFR §107.65 is the only recency requirement in Part 107: within the previous 24 calendar months, a remote pilot must have completed one of three things. You record which one, because it’s what an auditor asks for:

  • Initial knowledge test (§107.73)
  • Recurrent training (§107.73)
  • Part 61 flight review + §107.74 training

You enter the completion date — a fact the pilot holds a certificate for — and Tobren Operations derives the boundary from it. You never have to work out the expiry date yourself, and a report prints the date the product computed rather than one somebody typed in.

The remote pilot certificate itself does not expire, and letting recency lapse does not revoke it: it means the holder may not exercise its privileges until they’re current again. The product’s wording follows that distinction.

The 24-month boundary is the FAA’s and is not configurable. The 30-day warning window before it is ours.

2. Flight recency — your operating policy

“No qualifying flight in the last N days,” counted from filed flight logs. A crew member is current inside 60 days and lapsed past 90.

Part 107 has no flight-recency requirement — no 90-day takeoffs and landings, no minimum hours. (§61.57 is Part 61, manned aircraft.) These thresholds are Tobren Operations’ defaults, and the product says so wherever it shows them. Don’t present flight recency to an auditor as a Part 107 obligation.

Only filed, non-superseded flight logs count. Drafts and superseded amendments never do.

What each status means

StatusMeaning
CurrentInside the boundary on that clock.
Expiring SoonInside the warning window — 30 days out on knowledge recency.
LapsedPast the boundary.
Not VerifiedNothing on file to judge against.

“Not Verified” is a real state, not a blank. A crew member with no completion date recorded is never shown as current — the badge is neutral and named, so nobody reads a missing record as a clean one. Entering the paperwork is what clears it.

Overall status names its cause

A crew member’s headline currency status is the worse of the two clocks — but it also tells you which clock produced it, because “lapsed” on its own sends an operator to panic about the wrong thing. A lapsed knowledge recency and a stale flight-recency count need entirely different fixes.

Recording currency

Currency comes from each crew member’s record under Crew: their Part 107 certificate number, the knowledge-recency completion date, and how that recency was established. Leave the date blank and the member reads Not Verified — never “Current.”

Lapsing and expiring-soon currency also raise alerts, so it surfaces without anyone re-reading the roster.

Self-service, with evidence

Certification is read-only to the crew member themselves — they can’t just type in a new cert number and have it stick. From Settings → Your profile, they can propose an updated certificate number and/or knowledge-recency date, attaching an evidence document — the proposal is refused without one.

An admin or the billing manager reviews the queue at Settings → Credential review, where the evidence must actually be opened before a decision. Approve writes the proposed value and records that this organization verified it; Reject requires a reason and leaves the existing record untouched. Verification is per-organization: a crew member shared with another operator may already be verified there, and this queue never reads or writes that org’s attestation.

What’s next