For flight schools

Flight school software for a school that flies every day.

Dispatch, training records, maintenance, and billing on one set of data — so a squawk at 10am changes the 2pm schedule without anyone retyping it.

Start Dispatch Book Demo
  • Part 61 & 141
  • Endorsements & stage checks
  • Squawks that ground the schedule
  • Hobbs & tach billing
The school day

Six things that go wrong between the first brief and the last close-out.

Morning

Fill the line without a whiteboard.

One board shows who's flying, in which tail, with which instructor. Front desk dispatches; a grounded airplane can't be assigned, because the maintenance hold sits on the same schedule.

Midday

Know where every student stands.

Lessons, stages, and hours track against the syllabus — Part 61 or Part 141. Solo endorsements and stage checks are records, not sticky notes on the dispatch desk.

Squawk

A called squawk grounds the tail.

The mechanic logs it once. AOG items pull the airplane off the schedule immediately, so the 4pm dual doesn't walk out to an airplane that's down.

Close-out

The flight bills itself.

Hobbs and tach close the flight; rental, fuel, and instructor time post to the student's account. Overdue balances surface before they age into a collections problem.

Front of house

Discovery flights that book themselves.

Publish discovery-flight products with real bookable slots and take payment up front. Enquiries land as leads in the same system that will schedule them.

Audit

Part 141 records that survive an inspection.

Enrollments create compliance records against the course, and the course's cohort. When the FSDO asks, the paperwork is a query rather than an archaeology project.

Who sees what

A school isn't one kind of user.

Six staff and student roles, each with its own permission set. The off-site bookkeeper never sees a training record; the mechanic never sees a balance. Wingman AI is bound by the same rules as the person asking.

How access is isolated
  • Chief instructor
    Curriculum, student progression, and the authority to override a maintenance block.
  • Line instructor
    Their own students — grading, logbook signing, endorsements. Not other instructors' students.
  • Front desk / dispatcher
    Scheduling, the member directory, aircraft status. No financials.
  • Mechanic (A&P)
    Squawks, aircraft status, maintenance logs. Nothing else.
  • Billing admin
    Invoices, payments, and reporting — with no access to training records.
  • Student
    Own records and own bookings. Student bookings require approval; that gate is on the role itself.
Go deeper

The capabilities behind the school.

Scheduling & dispatch
The line, the holds, the conflicts.
Training records
Syllabus, stages, endorsements, stage checks.
Maintenance
Squawks, inspections, grounded tails.
Billing
Per-flight charges and student balances.
Wingman AI
Ask the operation a question, get an answer.
Chat
Dispatch and the flight line, same thread.

Certificated already? The Part 141 syllabus guide covers TCO structure, stage checks, and audit reports. Outside the FAA, see regulator coverage.

Questions schools ask
Does WingWrangler handle both Part 61 and Part 141?
Yes. Students track against a syllabus either way; Part 141 courses additionally create compliance records against the approved course, which is what an inspection asks for.
Which plan does a flight school need?
Academy. Syllabi, student progress, stage checks, endorsements, and compliance reports are Academy features — Club covers the fleet and the money but not the training records.
Can the front desk schedule without seeing the books?
Yes. Dispatcher is a distinct role: scheduling, directory, and aircraft status, with no financial access. Billing admin is the mirror image — money, no training records.
Do students book their own flights?
They can request them. Bookings made by a student require approval before they hold the airplane; club members, by contrast, book directly.
Ready to Dispatch?

Run the school from one board.

Start Dispatch See Pricing