You dispatched the flight.
Did anyone check it was legal to?
Run the flight line safely and bill it without building invoices. Scheduling, dispatch, the flight release, maintenance, and billing on the same foundation the training record lives on.
Schedule it. Gaps surface first.
Build the event with the instructor, student, aircraft, and event type. As you do, the system checks each against the record, so compliance, qualifications, maintenance, and open squawks all surface right in the form, before you save.
An obvious go/no-go. Every time.
The dispatcher checks the aircraft out, then reviews meter readings, plus fuel and notes. One flight release verdict clears it (or not). It weighs pilot currency, airworthiness, squawks, and METAR data, frozen as a snapshot at dispatch.
Maintenance that talks to dispatch.
Every aircraft carries its inspections, airworthiness directives, and meter logs. The 100-hour counts down against live meter readings, and each inspection calculates its own expiration. Squawks carry a severity and can be filed right from the flight line.
Left main tire treads are looking pretty worn down.
Fly, then submit the return.
When the flight is done, a check-in is submitted with Hobbs and Tach in, instruction time, fuel, notes, and any squawks. It lands in the dispatcher's queue as Pending Review. Nothing is finalized in the field, the office does that on the web.
Review invoices. Don't build them.
The dispatcher reviews the return, deltas, flight and ground time, fuel, and squawks, then finalizes it into a read-only Flight Record. That data drafts an invoice, itemized and taxed your way, landing in the billing inbox from Needs Review to Paid.
Explore the rest of the platform.
See the whole flight in one place.
Tell us about your school and we'll walk you through it, on your syllabus, your way.