Definition
The category looks like calendaring and is not. A calendar answers one question — is this slot free — while the real question a booking must answer is whether this pilot may take this aircraft for this purpose at this time. That involves several checks a calendar has no concept of.
**Is the aircraft airworthy and available?** Inspections and life limits fall due against hours and dates that keep moving, and open defects may ground it. A booking made against an aircraft that will be out of service when the slot arrives is not a booking, it is a future cancellation.
**Is the pilot eligible?** Checkout on type, currency, medical validity, licence and rating privileges, and for a student the syllabus prerequisites and any authorisation the exercise needs.
**Is the instructor or other resource available and qualified?** A dual booking needs both, and the constraints on the two do not coincide.
**Is the commercial position acceptable?** Whether an account is in arrears, a package exhausted or a contract allocation consumed is, for many schools, a precondition for dispatch rather than an afterthought.
Around those checks sit the policy decisions that determine whether the system is fair. **Booking windows** — how far ahead a member may reserve — decide whether the organised few take the good weather. **Minimum and maximum durations** stop an aircraft being held all day for a circuit detail. **Fair-share rules** limit how much of the scarce capacity one member can hold. **Cancellation lead times and no-show policy** decide whether a released slot can be re-used. Each is an allocation policy, and in a club they are political as much as operational.
The measure that matters is **whether a booking becomes a flight**. A system that accepts every request and produces cancellations is worse than one that declines some requests up front, because the second kind of refusal happens while the student can still rebook. Bookings that fail at the aircraft — the aircraft unserviceable, the currency lapsed, the account blocked — cost a slot that a different student could have used.
This is why the booking system is usually the first module a school outgrows a spreadsheet on, and why it is rarely useful in isolation: nearly every check it needs to make lives in maintenance, training or billing.
Why It Matters for Flight Schools
For a school or club, the booking rules encode who gets to fly, and that is worth deciding deliberately rather than inheriting from a tool's defaults. An unconstrained booking window plus no cancellation cost reliably produces the same outcome: a few members holding the best slots and releasing them late.
The diagnostic worth running is the ratio of bookings to completed flights, split by reason. A school cancelling a meaningful share at the aircraft has a validation problem rather than a demand problem, and the fix is upstream of the schedule.
The integration question decides the rest. A booking system that cannot see maintenance status will dispatch against a grounded aircraft; one that cannot see account status will fly students who cannot pay. Both failures show up as a schedule that looks full and an operation that does not run.
How Aviatize Handles This
Aviatize treats the booking as the point where the school's rules are enforced rather than recorded. The validation engine checks documents required by role, booking type, aircraft and syllabus; endorsements and recency; maintenance status; contract and balance conditions; and instructor and aircraft availability — with the school choosing per check whether a failure warns or blocks outright.
Because maintenance status limits an aircraft's availability directly, a tail under a hold is not offered to the schedule in the first place. Students book through a native iOS and Android app, repeat and duplicate bookings are supported, and the same record carries through to the invoice, so a completed booking bills from the recorded time rather than being re-entered. Pricing is per aircraft rather than per user, so opening booking access to the whole membership does not increase what the school pays.
Frequently Asked Questions
- How is an aircraft booking system different from a shared calendar?
- A calendar answers whether a slot is free. A booking system answers whether this pilot may take this aircraft for this purpose — checking airworthiness and open defects, checkout and currency, medical validity, syllabus prerequisites, instructor qualification and account status — and declines the booking when a check fails.
- What booking rules should a flying club set?
- The booking window, minimum and maximum durations, any fair-share limit on how much capacity one member may hold, and the cancellation lead time and no-show policy. These are allocation decisions rather than settings: an unlimited window with no cancellation cost reliably concentrates the best weather among the most organised few.
- What should a flight school measure about its bookings?
- The proportion that become completed flights, split by why the rest did not. Cancellations at the aircraft — unserviceable, lapsed currency, blocked account — mean the checks are happening too late. A refusal at booking time is far cheaper, because the student can still rebook.
- Does an aircraft booking system need to connect to maintenance and billing?
- In practice yes, because almost every check it must make lives elsewhere. Without maintenance status it will book a grounded aircraft; without account status it will dispatch a student who cannot pay. Both produce a schedule that looks full and an operation that does not run.