FlightQ plans the day, re-books what gets cancelled, writes the logbook from every sign-off and prices every hour flown. Cadets, instructors, dispatchers and schedulers all work from the same record, each seeing their own part of it. You stay pilot in command: nothing goes live until you publish it.
Monday
A dozen+ flying schools across six countries shaped what FlightQ does.
FlightQ didn't start with software engineers. It started with the owners and chief flight instructors of these schools, and the gaps they live with because today's tools weren't built for how a flying school runs now. Every part of FlightQ answers one of those gaps.
A tail goes tech and three sorties need a new aircraft. An instructor calls in sick and a checkride slips a week. A front rolls in and the afternoon is gone. Every change ripples into the rest of the day, the cadet's progress and the month's billing, and most of it lands on one desk before 7 a.m.
Illustration · one morning at a flying school
One tech aircraft, and the next six sorties are wrong. Everyone finds out at a different time.
See it in the control centreA cancelled sortie frees an aircraft, an instructor and a slot. Usually nobody refills it.
See where the hours goRepeated exercises and missed sorties sit in different records, so the slip shows up at the check.
See cadet progressHobbs on a scrap of paper, hours in a sheet, the charge worked out later from memory.
See how the hour is provedFlightQ builds the day from each cadet's next mission, the aircraft it needs and the instructors who are free. Pick the mode, and it plans around it.
Where each cadet stands in the syllabus before today today
Every aircraft flown to its daily target. The leaders pull further ahead.
Illustration · the same day, planned three ways
Every aircraft flown to its daily target.
The batch moves together. Nobody gets ahead until the others catch up.
Aircraft kept busy, with a limit on how far any cadet can lead.
Cadets see their next sortie, their progress and their logbook. Instructors see their day and the sign-offs waiting on them. Dispatch runs the control centre. Leadership sees utilisation and the numbers behind it. One record underneath, with a role-based login for each, on phone or desktop.




Real FlightQ screens · sample school data
FlightQ accounts for all twenty-four hours of every aircraft day — flown, outside your operating window, grounded for maintenance, out on lease — and sets what you rostered against what was actually performed, sortie by sortie.
Most schools quote a number nobody can trace. FlightQ builds it from signed-off sorties, so every hour in the figure has a flight behind it.
A cancelled sortie is a typed, audited record, not a rubbed-out line on a whiteboard.
Hours flown is not progress. FlightQ tracks every cadet against the syllabus they are actually on — mission by mission, graded, with the exercises they had to repeat.
Checkout, check-in and sign-off happen in order, enforced on the server. The meter reading that closes a flight is the one that writes the logbook, and the one the invoice is built from — so the three can never drift apart.
Aircraft and simulators measured against the same benchmark, so you can see which tail is earning its keep and which is sitting idle, and take that into your next lease, purchase or disposal decision.
Nothing on a FlightQ screen is typed in. Every figure is built from signed-off sorties, so you can open it and get the flights behind it — the tail, the crew, the times, and why it was flagged.
A cadet checking tomorrow's sortie on a phone, an instructor signing off beside the aircraft, a dispatcher releasing the day — all writing to one record. Nobody has to ask anyone for the latest sheet, because there is only one.
Rules are enforced on the server, not in the browser. Publishing a day takes a snapshot of it, so months later you can still show exactly what the flight line was told to fly.
We bring in the fleet, people and syllabus you already have on paper, then set up your rooms, duties, rate cards and roles with you.
Your fleet list, your people and the syllabus you already fly.
Operating window, duty limits, cancellation reasons and what each one charges.
Rosterers, dispatchers, instructors and cadets, each with the right access.
Sample quoteThe whiteboard used to decide our day. Now the day is decided before anyone gets in, and the invoice at the end of the month agrees with the logbook.Chief Flying Instructor · Partner flight school
In a short briefing we map your fleet, your courses and your contracts to FlightQ, and show you the control centre, the utilization and the billing with a school set up like yours.