Definition
The booking window is defined by two independent limits that operators frequently conflate but should configure separately. The booking lead time is the minimum notice a member must give before a reserved slot starts — for example, a rule that an aircraft cannot be booked less than two hours before departure, giving dispatch time to confirm airworthiness and the member time to prepare. The booking horizon (also called the advance-booking window or booking ceiling) is the opposite bound: the furthest point in the future a member may reserve, such as no more than 30 days ahead. Together they frame the period during which a slot is actually reservable.
The operational reason to set these per booking type is that different missions have different planning needs. A renter taking a Cessna 172 for a local flight might be allowed to book up to 14 days out with two hours of lead time; a multi-day hour-building trip or a checkride might need a longer horizon and more lead time so that examiners and aircraft can be coordinated; a maintenance reservation might bypass the horizon entirely. Applying a single global window to every mission type either starves long-lead activities of planning room or lets short-notice bookings crowd out members who plan ahead.
Why It Matters for Flight Schools
Lead time and booking horizon are core levers for balancing two competing goals: giving members flexible, self-service access to the schedule, and protecting the operator's ability to plan, maintain, and fairly allocate a finite fleet. Set the horizon too far out and a handful of members lock up prime weekend slots months in advance; set it too short and members cannot plan training blocks or cross-countries. Set lead time too short and dispatch loses the buffer needed to validate documents, balances, and airworthiness before a flight; set it too long and genuine last-minute availability goes unused.
Clubs and schools that tune these windows by booking type — rather than imposing one rule on everyone — tend to see higher utilization and fewer access complaints, because the rules match how each kind of flying is actually planned.
How Aviatize Handles This
Aviatize lets you set booking lead time and booking horizon independently for each flight or event type, rather than forcing one global rule. A solo training slot, an instructor-led lesson, a club rental, and a maintenance block can each carry their own minimum notice and advance-booking limit, and those limits are enforced automatically the moment a member tries to book through the Aviatize Connect app. Because the windows live in the same configurable rule set as the validation checks, a booking is only offered when it is genuinely bookable — no manual policing, and no slots reserved outside the rules you set.
Frequently Asked Questions
- What is the difference between booking lead time and booking horizon?
- Booking lead time is the minimum notice a member must give before a slot starts — it protects the buffer dispatch needs to validate documents, balances, and airworthiness. Booking horizon is how far into the future a member may reserve — it controls how far ahead the calendar opens. They are independent limits and are best set separately, and per booking type.
- Can I set different booking windows for different flight types?
- Yes. In Aviatize, booking lead time and booking horizon are configured per flight or event type, so a local rental, a solo training slot, a checkride, and a maintenance block can each have their own minimum notice and advance-booking limit rather than sharing one global rule.
- Why would a flight school limit how far in advance members can book?
- A booking horizon keeps access fair and the fleet plannable. Without it, a few well-organized members can lock up prime weekend slots months ahead, leaving everyone else to compete for what is left. Capping the horizon spreads access across the membership and keeps the calendar realistic.