Civilian Airports / Training

Part 139 Training Records

Personnel training records and currency, aligned to the requirements outlined in FAA regulations.

app.glidepathops.com
The compliance matrix: every member against every §139.303 topic, with current, expiring, and expired cells colored so a gap reads at a glance.

Training currency is a fact about a person and a date, not a checkbox

§139.303(e) lists specific topics personnel have to be trained on, each running on its own recurrence, so "trained" is never one yes-or-no for the whole roster. It's a separate fact for every person on every topic, current on some, lapsed on others, and the mix keeps shifting every time one comes due again.

Reconstructed from memory or a shared spreadsheet, that fact is only as reliable as whoever last touched it. And the version an inspector wants (a clean roll-up of who's covered on what, as of today) is the hardest one to produce by hand on short notice.

Every person, every topic, current or not

  1. The required topics ship pre-loaded

    Every §139.303(e) topic arrives seeded with its own recurrence, editable in place, and the airport can add its own custom topics alongside them. Nothing starts from a blank list.

  2. The roster sorts itself by who needs attention

    A per-person rollup tallies current, expiring, expired, and not-started counts and ranks the worst-off first, so the people who need training aren't buried under everyone who's already covered.

  3. One grid is the whole audit picture

    Every person crossed with every topic in a single grid, each cell colored by its latest status. Click a cell for that person's history on that topic, with no separate report to assemble first.

  4. Logging a completion updates everything at once

    Attach the evidence or certificate straight to the person's record, and the roster and the grid both recompute immediately. Currency is never a separate step from the record that proves it.

What it automates

The topic list is never blank

Every §139.303(e) topic is seeded in with a working recurrence from day one, and adding a base-specific topic alongside them takes one form, not a rebuild.

A gap shows up as a colored cell, not a surprise

The compliance grid reflects every person against every topic continuously, so a lapse is visible the moment it happens instead of the week before a visit.

The transcript is a download, not a reconstruction

A PDF transcript per person and a CSV of the full grid both pull from the same live record, so nothing gets rebuilt by hand to answer a request for it.

Straight answers

What topics does §139.303(e) actually require?

The 13 system topics ship pre-loaded with editable recurrence, and the topics catalog is where the airport adds any airport-specific topic beyond them.

How do I see who's behind, without checking each person one by one?

The roster ranks every person by current, expiring, expired, and not-started counts, worst-off first, so nobody who needs attention is buried in the full list.

What's the difference between the roster and the compliance matrix?

The roster is a per-person summary; the compliance matrix is the full person-by-topic grid behind it, with every cell clickable for that person's history on that specific topic.

Can I get a record out for an FAA inspector?

Yes: a PDF transcript per person, or a CSV of the whole compliance matrix, both pulled from the live record instead of assembled by hand.