Watch every student progress, stage by stage.
Training records are only useful if the structure is real. Not a folder per student and a shared spreadsheet, but syllabi with versions, lessons with prerequisites, stage checks with outcomes, and endorsements that know which regulation they came from.
The syllabus is data, not a PDF.
Syllabi, versioned
Each syllabus belongs to your organisation and carries a category and a version. Revise the Private course without rewriting history for the students already halfway through the old one.
Lessons with objectives
A lesson is not just a calendar row. It carries defined objectives and prerequisite lessons, tracking individual student progress accurately.
Prerequisites as a graph
What a student can fly next is derived automatically from prerequisites met, next in sequence, instructor suggestions, or lessons needing review.
Stage checks on the syllabus
Stage checks are defined on the syllabus in order, then instantiated per student with a requester, an outcome, and notes. The definition and the event are different records, because they are different things.
Signed by someone, on a date, under a rule.
Templates carry the reference
An endorsement template holds its title, text, and regulatory reference. A pre-solo endorsement is recorded directly against the relevant regulation.
Records carry the signature trail
Each issued endorsement records the instructor who issued it and when. Add one and it posts into that student's instructor thread automatically.
Solo time is its own column
Solo, PIC, dual received and dual given are separate totals, and they export separately. Solo cross-country readiness is a question the data can answer.
Every column a checkride asks for.
Entries are approved by the instructor and roll up into totals per student. The same columns export to CSV, so a student leaving with their hours doesn't leave with a screenshot.
- Solo
- PIC
- Dual received
- Dual given
- Cross-country
- Night
- Instrument actual
- Instrument simulated
- Ground training
- Day landings
- Night landings
- Full-stop landings
- Approaches
- Holds
Certificated programmes get the extra machinery they need.
FAA course templates
Standard course templates carry minimum ground hours, minimum flight hours, and the stage-check codes a course requires. Applying one to a syllabus creates its lessons and stage checks in a single transaction.
Part 141 course categories
Your own course categories, each with a code, minimum ground and flight hours, and the list of stage-check codes it requires.
Compliance records
Per student: ground hours completed, flight hours completed, stage checks completed against stage checks required, whether the record is compliant, and what the outstanding issues are.
An audit log that exists
Part 141 compliance changes are logged against the compliance record, so the answer to “when did this change and why” isn't a memory test.
A lesson touches three other systems.
The lesson is a booking. Scheduling a stage check opens its own coordination thread with the student and the examiner.
BillingDual, solo, and ground time are logged once. The same hours are what instruction is billed against.
ChatSubmit a logbook entry after a dual flight and the debrief prompt lands in the instructor's thread with that student.
Does WingWrangler handle both Part 61 and Part 141?
Yes. Syllabi, lessons, stage checks, and endorsements work the same either way. Part 141 adds course categories with minimum hours and required stage-check codes, per-student compliance records, and an audit log against those records.
How is a student's next lesson decided?
From the syllabus prerequisite graph. Each recommendation is labelled with its exact reason: prerequisites met, next in sequence, instructor suggested, or previously attempted and needing review.
Who can create and change a syllabus?
Syllabus and assignment management is restricted to admins and chief instructors. A line instructor teaches the course; they don't quietly redefine it.