Flight training scheduling on one board

Flight training scheduling means matching three scarce things into one slot: a student who needs hours, an instructor who is available and current, and an aircraft that is free to fly. Saiga Aviation builds tomorrow's flying on one board from those three records, flies each sortie against its booking, and logs the hours on all three at once.

This guide describes how the board works and what has to exist before it can. It does not quote any regulator's scheduling or rest requirements; those are not on this site and are not claimed here.

Most flying schools start on a whiteboard, and the whiteboard is not the problem until the day it is. Three things go wrong, and each has a cost that lands on the day rather than in a report.

1. 1.Scheduling lives on a whiteboard or a spreadsheet. The cost is double-booked aircraft and instructors, and sorties lost on the day.
2. 2.Flight hours are logged on paper and totted up later. The cost is that nobody can say what a student actually has until someone counts it by hand.
3. 3.Aircraft utilisation is a feeling, not a figure. The cost is your most expensive assets sitting idle, or getting committed twice over.

A booking on the board is not a note; it is a slot that holds a student, an instructor and an aircraft together. That only works because each of the three is a record of its own: one record per student from enrolment onward, holding the hours they need to reach and the hours they have flown; fleet records with availability, so a booked aircraft is genuinely free; and instructor availability held alongside the fleet rather than in a separate diary.

Tomorrow's flying is built by matching those three into one slot, on one board. A student who exists only on an enrolment form cannot be scheduled with any confidence; a student on the record can, because the person building the programme has the hours they need in front of them.

The board earns its keep after the sortie, not before it. The booking is the entry the flight flies against, so what was planned and what actually flew are the same entry. When the sortie is logged, the hours are recorded against the student, the aircraft and the instructor at once, instead of in three books that have to agree later. From there a student's progress toward their required hours is read off the record, so nobody counts a logbook by hand to answer it, and fleet and instructor utilisation come from the same bookings, so an idle aircraft shows up as a figure rather than a feeling.

In the order the day runs:

1. 1.Enrol. A student goes onto the record when they join, with the hours they need to reach in front of everyone who schedules them.
2. 2.Schedule. Tomorrow's flying is built by matching a student, an available instructor and a free aircraft into one slot, on one board.
3. 3.Fly. The sortie goes ahead against that booking, so what was planned and what actually flew are the same entry.
4. 4.Log. Hours are recorded against the student, the aircraft and the instructor at once, instead of three books that have to agree later.
5. 5.Track. A student's progress toward their required hours is read off the record, so nobody counts a logbook by hand to answer it.
6. 6.Review. Fleet and instructor utilisation come from the same bookings, so an idle aircraft shows up as a figure rather than a feeling.

Scheduling is in the base tier. The tiers above it add the people and the checks that sit around a booking.

1. 1.Saiga Aviation ATLAS, the base tier: flight scheduling and logging, student records and syllabus progression, aircraft records and fee tracking. The board, and the student and fleet records it draws on.
2. 2.Saiga Aviation SABLE, for operating FTOs: instructor rostering and HRMS, so the instructor side of a booking comes from a roster rather than a diary; briefing and flight authorisation held on the record; fuel and resource logistics; and a management dashboard with utilisation, money and compliance in one view.
3. 3.Saiga Aviation VULCAN, the flagship: utilisation analytics, licence and hour tracking, compliance automation and audit packs, automated workflows including inventory and asset management, and multi-base operation.

The live sample on the Saiga Aviation page, Book, fly, log, is the board with sample data: two aircraft across a morning of hourly slots, three students with the hours they have and the hours they need, and two instructors. Tap an empty slot to book a sortie, then fly it, and watch the hours land on the student, the airframe and the instructor at once.

Two things the sample shows on purpose. Book the same instructor at the same time on both aircraft and the slot turns red until you swap the instructor, so a clash cannot hide on the board. And an aircraft that is due its check cannot be booked until maintenance releases it on the Fleet tab, so the board stops a sortie before it becomes a problem rather than after.

The board only works if the three records exist first. What to have in place before the first booking.

1. 1.Every student on the record, with the hours they need to reach and the hours already flown.
2. 2.Every aircraft on the fleet record, with its availability, so a booking can only take an aircraft that is free.
3. 3.Every instructor's availability held alongside the fleet, not in a diary of their own.
4. 4.A rule the whole school keeps: a sortie is logged against its booking, never into a separate book to be reconciled later.
5. 5.The question you want answered at the end of the week, usually which aircraft sat idle and which student is behind, so the figures come out of the bookings rather than from a count.