Part 141 · Programs & scheduling
TCO hierarchy
Your Training Course Outline lives as a program → course → lesson hierarchy with per-trainee enrollment dashboards, so the approved catalog and the actual records are the same structure. Lessons mark whether they need a simulator or a classroom and how long they run. It replaces the binder that never quite matches the records.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
The chief instructor who wants the FAA-approved catalog and the actual records to be the same structure, so a student's place in the TCO is the record itself.
What it replaces
The Training Course Outline binder that never quite matches the records.
What tco hierarchy gives you
- Program → course → lesson hierarchy mirroring your TCO
- Per-trainee enrollment dashboards
- Lessons mark simulator / classroom and duration
The TCO is the record structure
A school's Training Course Outline lives as a program → course → lesson hierarchy, so the FAA-approved catalog and the actual records are the same structure rather than a binder reconciled against a spreadsheet. Per-trainee enrollment dashboards hang off that same hierarchy, so a student's place in the TCO is the record itself.
- Program → course → lesson hierarchy mirroring your TCO
- Per-trainee enrollment dashboards
Lessons carry resource and duration
Each lesson marks whether it needs a simulator or a classroom and how long it runs, which is what lets the calendar and the funnel reason about it. Mark a lesson's resource and duration once, and progress reads against the approved catalog rather than a separate binder.
- Lessons mark simulator / classroom and duration
- Progress reads against the approved catalog
How an operator uses this
A school's Training Course Outline lives as a program → course → lesson hierarchy, so the FAA-approved catalog and the actual records are the same structure rather than a binder reconciled against a spreadsheet. Each lesson marks whether it needs a simulator or a classroom and how long it runs, which is what lets the calendar and the funnel reason about it. Per-trainee enrollment dashboards hang off that same hierarchy, so a student's place in the TCO is the record itself.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
TCO hierarchy, step by step
Build your TCO as a program → course → lesson hierarchy.
Mark each lesson's resource — simulator or classroom — and its duration.
Enroll students; each gets an enrollment dashboard against the same hierarchy.
Read progress against the approved catalog, not a separate binder.
Questions
TCO hierarchy — frequently asked
Does the catalog match my FAA-approved TCO?
Yes. Your Training Course Outline lives as a program → course → lesson hierarchy, so the approved catalog and the actual records are the same structure instead of a binder that never quite matches.
Can lessons specify what resource they need?
Yes. Each lesson marks whether it needs a simulator or a classroom and how long it runs, which is what lets the calendar catch a simulator or instructor conflict — including the chief instructor's own time and approved time off — before the booking posts.
Keep exploring
Other features in Part 141
Stage-check workflow (in development)
Planned Scheduled → Pass / Fail → Re-check → Waive state machine — the data model and API exist, but no in-app screen calls it yet.
Deep diveEndorsement library
Per-trainee endorsement history with expiry, issuing CFI, and stored signed document.
Deep diveFunnel & progress tracking
Enrolled → started → stage 1/2/3 → completed conversion across the program.
Deep diveIACRA 8710-1 pre-fill
Builds from completed training records; CSV export ready for IACRA.
Deep diveSimulator + classroom calendar
Conflict detection on simulators and the instructor's own time.
Deep diveTrainee portals
Students see the same progress and endorsements you do.
Deep diveDPE network
Designated Pilot Examiner roster — designation #, ratings, type ratings, fee (add-on module).
Deep diveEvery Part 141 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee tco hierarchy on your operation.
It's part of the Part 141 workspace. Request a demo or join the waitlist.