Skip to content
Tobren Operations Docs

Part 107 currency

Tobren Operations tracks crew currency as their §107.65 knowledge recency, and shows flight recency beside it as a separate, non-regulatory fact. Currency shows on the Crew roster, on each crew member’s detail page, and in a crew-scope compliance report.

Knowledge recency is the status

Section titled “Knowledge recency is the status”

Aeronautical knowledge recency — the regulation

Section titled “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 (the last day of the 24th calendar month). 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.

A crew member’s currency status is their §107.65 knowledge-recency status.

Flight recency — a fact and an optional house policy, not a status

Section titled “Flight recency — a fact and an optional house policy, not a status”

Part 107 has no flight-recency requirement — no 90-day takeoffs and landings, no minimum hours. (§61.57 is Part 61, manned aircraft.) So Tobren Operations does not give flight recency a status. It shows two separate things:

  • Last flight with your organization — the date of the crew member’s most recent filed, non-superseded flight log with your organization. Drafts and superseded amendments never count, and flights logged with other organizations are not visible to yours.
  • An optional note from your organization’s policy. An Admin can set two informational marks under Settings → Flight recency. The defaults are 60 and 90 days; whole days only, and a blank box or 0 turns a mark off. When a pilot’s time since their last flight with you reaches a mark, the roster, the crew page and the crew pickers show a note such as “No flight with Acme in 64 days (org policy: 60)”.

That note is never a verdict, never an FAA requirement, and never changes a report’s status. Don’t present it to an auditor as a Part 107 obligation. When a mark is reached, an informational flight recency alert is raised too, unless the marks are off.

What each status means

Section titled “What each status means”
Status Meaning
Current Inside the boundary on that clock.
Expiring soon Inside the warning window — 30 days out.
Lapsed Past the boundary.
Not verified Nothing 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.

Recording currency

Section titled “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 knowledge recency also raise alerts, so it surfaces without anyone re-reading the roster.

Self-service, with evidence

Section titled “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 Account owner 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

Section titled “What’s next”