Fleet Planning

A fleet plan answers four questions, and they interact.

**Composition** — which types, and how the training pipeline is served. A school running PPL through CPL needs a trainer, something for complex and instrument work, and possibly a multi-engine aircraft used for few hours but required for the syllabus. The multi is the instructive case: it may fly under a hundred hours a year and cannot be removed without losing the course, so it is a syllabus obligation carried as a capacity asset.

**Size** — how many of the core trainer. This is where fleets are most often wrong, because the tempting reference point is peak demand. A fleet sized for the best weekend of the year carries idle fixed cost through every other week, and fixed cost per hour is what a low-utilisation aircraft destroys.

**Ownership basis** — outright purchase, finance, operating lease, or **leaseback**, where an owner's aircraft is operated by the school. Leaseback shifts capital cost off the school and brings scheduling and maintenance obligations to an owner with their own expectations; it is cheaper in cash and more expensive in control.

**Timing** — when to add and when to retire. Both have lead times measured in months, and demand signals arrive later than the decisions need to be made.

The arithmetic that binds these is **break-even utilisation**. An aircraft's fixed costs divided by its contribution per hour gives the hours per year at which it stops losing money. Adding a tail adds its fixed cost immediately and its hours gradually; the new aircraft also takes hours from the existing fleet rather than serving purely new demand, so the marginal tail is usually the least utilised. A fleet plan that assumes the new aircraft flies at fleet-average utilisation from month one will be wrong in a predictable direction.

**Availability is part of capacity.** An aircraft is only bookable when airworthy, so a plan built on calendar days rather than serviceable days overstates what the fleet can deliver — typically by more than owners expect, because unscheduled downtime is dominated by parts lead time rather than labour.

The softer constraint is instructors. Adding aircraft without adding instructors moves the bottleneck rather than removing it, and a school can find itself paying fixed costs on a tail that nobody is available to teach in.

For an owner, the discipline is to size against sustainable utilisation and solve peak demand with scheduling policy rather than with metal. Booking windows, fair-share rules and priced cancellation are far cheaper than an extra airframe, and they can be changed in a week.

The common error after that is treating utilisation as a fleet average. A fleet at a comfortable average can contain one tail carrying the others and one nobody wants to book, and the average conceals exactly the decision worth making.

The third is planning capacity in aircraft alone. Instructor availability, and the hours instructing consumes beyond flying, cap what a fleet can deliver just as firmly as serviceability does.

Aviatize reports utilisation per aircraft from the bookings and flights actually recorded, not as a fleet-wide average, so the tail carrying the fleet and the one nobody books are both visible — which is the distinction a fleet decision turns on. Because maintenance status and the schedule share a system, the hours a tail flew can be set against the time it was held out of service, giving serviceable-day capacity rather than calendar-day capacity.

Billing records what each aircraft actually earned against the rate structure configured for it, and for a multi-location operation the same metrics compare across sites. Aviatize supplies the measured inputs — utilisation, availability, revenue and cost per tail; the fleet decision, the ownership basis and the acquisition timing remain the operator's.