Part 142 · Training Specifications & records
TS document control
Training Specifications live as controlled sections (A001 / A002 / B055 …) that move DRAFT → PROPOSED → APPROVED with the POI's sign-off name and date captured on the approving revision. Every save creates a new revision tied to the editor and timestamp, so the history is append-only and the current text is never in doubt. It replaces the TS document in a shared drive with no revision history.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
The director of training who owns the center's Training Specifications and needs the current approved text — and the record of who changed what — never in doubt.
What it replaces
The TS document sitting in a shared drive with no revision history and no record of who changed what.
What ts document control gives you
- Controlled sections (A001 / A002 / B055 …)
- DRAFT → PROPOSED → APPROVED with POI sign-off name and date
- Append-only revision log tied to editor and timestamp
Controlled sections with a real workflow
Training Specifications live as controlled sections — A001, A002, B055, and so on — that move through DRAFT → PROPOSED → APPROVED, with the POI's sign-off name and date captured on the approving revision. A section moves to PROPOSED when it's ready for the POI, and approval captures who signed off and when.
- Controlled sections (A001 / A002 / B055 …)
- DRAFT → PROPOSED → APPROVED with POI sign-off name and date
An append-only revision log
Every save creates a new revision tied to the editor and the timestamp, so the history is append-only and the current text is never in doubt. It replaces the TS document sitting in a shared drive with no revision history — the current approved text and how it got there are both on the record.
- Append-only revision log tied to editor and timestamp
- Current approved text never in doubt
How an operator uses this
Training Specifications live as controlled sections — A001, A002, B055, and so on — that move through DRAFT → PROPOSED → APPROVED, with the POI's sign-off name and date captured on the approving revision. Every save creates a new revision tied to the editor and the timestamp, so the history is append-only and the current text is never in doubt. It replaces the TS document sitting in a shared drive with no revision history and no record of who changed what.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
TS document control, step by step
Each TS section (A001 / A002 / B055 …) is a controlled document with its own state.
Draft and edit a section; every save creates a new revision tied to the editor and timestamp.
Move the section DRAFT → PROPOSED when it's ready for the POI.
On approval, the POI's sign-off name and date are captured on the approving revision — the history stays append-only.
Questions
TS document control — frequently asked
Does it track Training Specifications revisions with POI sign-off?
Yes. Each TS section moves DRAFT → PROPOSED → APPROVED with the POI sign-off name and date captured on the approving revision. The history is append-only — every save creates a new revision tied to the editor and timestamp.
Can I tell what the current approved text is?
Yes. Because every save creates a new revision and approvals capture the POI sign-off, the current text and how it got there are never in doubt.
Keep exploring
Other features in Part 142
Device inventory
FFS Level A–D and FTD with Part 60 qualification levels; AATD and BATD tracked by their LOA instead.
Deep diveConflict-free calendar
Briefing + debrief blocks built into the sim schedule; conflicts caught before they post.
Deep diveUtilization reporting
Per-sim hours, sessions, and by-type breakdown — no month-end rebuild.
Deep diveNSP evaluation cycles
Each device's recurring Part 60 eval auto-rolls its next-due date with 30/60-day reminders.
Deep diveInstructor currency
Per-instructor CFI / CFII / ATP currency on the Due-Soon → Overdue pipeline.
Deep diveFAA inspection mode
Read-only navigation for a POI/PMI visit, scoped to the records they need.
Deep diveInstructor authorization matrix
Who's authorized on which course on which device — every sign-off an audited event.
Deep diveFAA Form 8710 / IACRA prep
Pre-fills from completed training records; CSV export ready for IACRA upload.
Deep diveAQP (14 CFR 121 App. Y)
Per-fleet proficiency objectives and CQ-cycle tracking (add-on module).
Deep diveEvery Part 142 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee ts document control on your operation.
It's part of the Part 142 workspace. Request a demo or join the waitlist.