Training & Currency answers the question a chief or an auditor asks first: who on this program is legal to fly right now. It pulls each pilot's Part 107 certificate, flight recency, night recency, and whatever recurrent training your department mandates onto one board.
This article covers logging training records, setting the windows that define currency, reading the board, and turning on the automatic reminder emails. You need at least Supervisor to open the board or add records, and Global Admin to change department policy.
Before you start. Training & Currency is a paid capability. If it is missing from the Organization group in your sidebar, your account's plan does not include it. Currency is calculated from flight data, so pilots need flights logged before the board says anything useful.
The four kinds of training record
Every training entry lives on a pilot and carries a type. Open Pilots, select a pilot, then the Training & Certifications tab, and click Add Record. The Type dropdown offers four options, and the type determines how the record is read:
- Training Course — any course you want on file. It appears in the pilot's training history and on the training report, but drives no badge.
- Certification (initial) — the pilot's one-time department certification. Saving one stamps the pilot's certification date, which the board's Certification column reads.
- Mandated training (recurrent) — a completion of the recurring training your department requires. Only this type satisfies the recurrent requirement.
- Part 107 (issue/renewal) — an FAA certificate issue or recurrent-training completion. The most recent one drives the Part 107 badge everywhere in the product.
Each record takes a Completed date, an optional Expires date, and notes. Remove one with the trash icon on its row.
Certification and mandated training are two different things. Initial certification says the pilot completed your department's onboarding course once. Mandated recurrent training is the repeating obligation, and only records saved as Mandated training (recurrent) count toward it. Once mandated tracking is switched on, a pilot who is certified but has never had a mandated record logged shows No record and counts as out of compliance.
Entering the Part 107 certificate and renewals
When you pick Part 107 (issue/renewal) as the type, the name field changes to FAA Certificate Number. It is prefilled from the pilot's record, and if you type a different number there, the pilot's record is updated to match when you save — the number lives on the pilot, the renewal dates live in the training records. The record names itself Part 107 — #<number>.
Leave Expires blank and the system dates the certificate 24 months from the completion date, matching the recurrent-training cycle described in the Part 107 guide. An explicit date, when you have one, wins.
Log each recurrent completion as a new Part 107 record rather than editing the old one — the latest record by completion date is the one evaluated, and the history stays intact for audits.
Setting the proficiency and night currency windows
Currency windows are department policy, and they live in one place: Admin, in the Training & Currency card. It opens as a read-only summary of the three settings; click Edit settings to change them, then Save training settings.
- Track flight proficiency — the switch, plus Flights required and Within (days). The built-in default is 3 flights in 90 days.
- Track night currency — Night flights required and Within (days), defaulting to 3 night flights in 90 days.
- Track department-mandated recurrent training — Required every (months), accepted between 1 and 120.
Turning a switch off is a real off, not a display preference: the column disappears from the currency board, the badge disappears from the pilot page, and nobody is ever counted out of compliance for that metric. Turn it back on and every pilot is re-evaluated immediately, since currency is computed from flight data on each page load rather than stored.
These values are the department-wide default, and every unit inherits them. A unit only diverges where a unit-level override was explicitly saved for it, in which case its saved numbers replace the department values for its pilots. Pilots not assigned to a unit always use the department default.
Reading the currency board
Open Training & Currency from the sidebar. The scope selector at the top right defaults to Department-wide (all units); pick a single unit to narrow it. Four stat cards sit above the board — Pilots, Fully Current, Part 107 Expiring, and Out of Currency — and the board has these columns:
- Pilot, linking to the pilot's detail page, and Unit when you are in department-wide scope.
- Part 107 — a status badge plus the expiration date.
- Night Ops and Proficiency — a status badge plus a count of qualifying flights against the requirement, like
2/3. - Certification — Certified with the date, or Not certified.
- Mandated Training — Current with the next due date, Overdue with the date it was due, or No record. The column is hidden entirely when mandated tracking is off.
- Total Hrs, Night Hrs, and Recent Flights — the last being flights inside the proficiency window.
Badges read Current, Expiring, Out, or No record; Part 107 turns Expiring inside 60 days of its expiration date. The Out of compliance only switch above the table filters to just the pilots who need attention, and the count beside it matches the Out of Currency stat card. The table's search box matches on pilot name and unit.
What puts a pilot out of compliance
| Currency type | Counted from | Out of compliance when | Affects the count |
|---|---|---|---|
| Part 107 certificate | Latest part107 record's expiration, or 24 months from completion | The expiration date has passed | Yes |
| Flight proficiency | All flights plus manual entries in the window | Fewer flights than required inside the window | Yes |
| Night currency | Night flights plus manual entries marked night | Fewer night flights than required inside the window | Yes |
| Mandated recurrent training | Latest mandated record | The interval has elapsed, or no record exists | Yes |
| Initial certification | The pilot's certification date | Never — the column shows Not certified | No |
A pilot with no Part 107 record at all shows No record rather than Out and is not counted against the out-of-compliance total; only a lapsed certificate is. Fully Current is stricter than the inverse of out-of-compliance: it counts pilots whose Part 107, night, and proficiency are all Current, so a certificate inside its 60-day expiring window keeps a pilot out of that tile.
Night is decided per flight from the takeoff coordinates and time — a flight counts as night when it happened after civil dusk or before civil dawn at that location. Manual flight entries carry their own Night checkbox and count toward hours, proficiency, and night currency exactly like logged flights.
Turning on automatic reminder emails
Reminders live in Admin, under Notifications & Reminders, and every rule is off until you enable it. Six rules are available; four of them are training-related:
- Flight proficiency and Night currency — the pilot is currently out, using the windows from the Training & Currency card.
- Mandated recurrent training — the pilot is overdue, using the interval from that same card.
- Part 107 expiration — a warning before the certificate lapses.
The other two, Aircraft registration expiration and COA / COWA expiration, cover the fleet and your airspace authorizations, which is why the same screen also holds a COA/COWA list.
Each enabled rule gets its own recipients. Currency and training rules can go to Pilot and Unit admin; registration and authorization rules go to Unit admin and Global admin. The number field means different things by rule type: for the currency rules it is Remind at most every N days while out, and for the expiration rules it is Remind N days before. Click Save reminders when you are done.
Sending is a sweep that runs at most every 20 hours, triggered by ordinary use of the app rather than at a fixed clock time. Each out-of-compliance pilot gets one consolidated email listing every enabled requirement they fail, throttled by the shortest cadence among the rules that flagged them, sent to the address on their pilot record. Inactive pilots are skipped.
Admins get a digest instead of per-pilot mail. Unit admins see the pilots in their own unit plus aircraft registrations for it; global and system admins see everything. Digests are throttled by the shortest interval among your enabled rules, never wait longer than seven days, and are not sent at all when there is nothing to report.
Reminders need working email. The sweep does nothing at all if email delivery is not configured for your instance. Pilots also need an email address on their pilot record, and admin digests go to the email on the user account, not the pilot record. See agency setup for the email configuration.
Exporting currency and training records
Two PDF reports on the Reports page, under Additional Reports, cover this area. Pilot Currency is a per-pilot compliance snapshot with the active proficiency windows printed in the header. Pilot Training Records is the per-pilot training history — courses, certification, and Part 107. Both respect the unit filter on the Reports page and are recorded in the audit trail when exported. For how these fit your broader recordkeeping obligations, see the UAS recordkeeping and audit guide.
Frequently asked questions
Why is a pilot showing out of proficiency when they have been flying?
Flights count toward a pilot's currency when they are the remote pilot in command or are listed on the flight in a flying role, and the match is by name. Flights logged under a different spelling of the name, or left attributed to an import catch-all pilot, will not count. Compare the pilot's Flights tab against the flights-in-window figure in the Proficiency column.
Does changing the proficiency window change anyone's history?
No. Currency is calculated fresh from flight data every time a page loads, so raising or lowering a requirement changes who is compliant immediately, in both directions, without editing any record. The same is true of the on/off switches: turning a metric back on re-evaluates every pilot against the flights already logged.
Can different units have different currency requirements?
Every unit inherits the department-wide numbers set on the Admin Training & Currency card. A unit shows its own values only where a unit-level override was previously saved for it, and unassigned pilots always fall back to the department default. The board's scope selector changes which pilots you are looking at, not which policy applies to them.
What happens if I delete a Part 107 record by mistake?
The badge falls back to the next most recent Part 107 record for that pilot, or shows No record if none remains. Re-adding the record with the same completion and expiration dates restores the badge. The certificate number itself lives on the pilot record and is not affected by deleting a training record.
Why do a pilot's total hours look too low?
A single flight longer than 24 hours contributes zero hours to every total. Controllers with bad clocks have produced logs spanning years, and one of them would otherwise poison every hours figure on the page. The flight still counts as a flight for proficiency, and it stays visible in the flight list so you can correct or delete it.
Where to go next
Set the department policy first in the Training & Currency card, then enable only the reminder rules you want people to receive — both are covered in agency and admin setup. Once the board reads the way you expect, reports and exports covers getting currency and training snapshots out as PDFs for a records request or program review.