Definition
Maintenance tracking is a bookkeeping problem before it is an engineering one. Every requirement is a rule of the form *this task, on this item, every N of this unit*, and the work is keeping an accurate current value for every counter and comparing it against every limit.
The counters do not agree with each other, which is the source of most of the difficulty.
**Flight hours** may be measured against a Hobbs meter, a tach reading, or airborne time, and the three diverge — a tach under-reads against Hobbs at low power settings, and which one a given limit is written against is a matter of the manual, not of preference. **Cycles** count take-off and landing pairs and drive structural and some component limits. **Calendar time** runs regardless of use, which is why a lightly flown aircraft is not a lightly maintained one. **Landings** are counted separately where a limit is written against them.
The items being tracked form a hierarchy. The airframe carries inspections and structural limits; engines and propellers carry their own intervals and overhaul periods; components carry life limits, overhaul intervals and, where serial-controlled, an individual history that moves with the part between aircraft. Above all of these sit **Airworthiness Directives**, which are mandatory and may be one-off or recurring, and **Service Bulletins**, which may be advisory or made mandatory by an AD or by the operator's own programme.
What makes this genuinely hard is not any single limit but the interaction. A component removed from one aircraft and fitted to another carries its accumulated time with it and lands on a different set of counters. A recurring AD compliant at one inspection becomes due again against a counter that is still moving. An overhaul resets some values and not others.
The consequence of getting it wrong is not a maintenance problem but an airworthiness one. An aircraft flown past a limit was not airworthy for those flights, and the finding is retrospective: the flights already happened, were already billed, and in a training context were already logged towards licences. There is no way to unfly them.
The forecasting dimension matters as much as the compliance one. Knowing an inspection is due in eighty hours is only useful alongside knowing the aircraft flies forty hours a month, because that is what converts a limit into a date and a date into a schedule decision.
Why It Matters for Flight Schools
For a school, the value of tracking is forecast rather than record. A system that tells you an inspection was due yesterday has documented a problem; one that tells you it falls due in three weeks at current utilisation lets you move bookings while they are still movable.
The common failure is a tracking system fed by hand from a different system of record. Hours entered separately into billing, the logbook and the tracking spreadsheet will diverge, and the one that is wrong is discovered at audit rather than in use. The discrepancy is rarely large; it only has to be large enough to put a flight on the wrong side of a limit.
The second failure is treating tracking as the maintenance organisation's job alone. The counters are driven by flying, which the school controls, so a forecast that does not reflect how the aircraft is actually being scheduled is a forecast against the wrong denominator.
How Aviatize Handles This
Aviatize tracks maintenance status per aircraft — instructions, Airworthiness Directives, Service Bulletins and open squawks — and limits an aircraft's availability to the schedule at the point its status requires it, rather than earlier than necessary or later than is safe. Because the flight records that move the counters and the bookings that will move them next are in the same system, what an aircraft is due is read against how it is actually being flown.
Work is planned as work orders and work packs with tasks assigned to technicians, who record time, parts and tools used from a tablet, and that record feeds both the compliance trail and the invoice. Aviatize is the record and the scheduling control around it; the approved maintenance programme, the airworthiness determination and the certification of work remain the operator's and the certifying organisation's.
Frequently Asked Questions
- What does aircraft maintenance tracking involve?
- Keeping a current value for every counter an aircraft and its components are measured against — flight hours, cycles, landings and calendar time — and comparing each against every applicable limit, so inspections, overhauls, life limits and recurring Airworthiness Directives are planned before they fall due rather than found afterwards.
- Why do flight hours and tach time disagree?
- They measure different things. A tachometer reading accumulates at a rate tied to engine speed and under-reads relative to a Hobbs meter at low power settings, while airborne time differs from both. Which counter a limit is written against is set by the maintenance manual, so tracking against the wrong one can put an aircraft past a limit while the paperwork appears to show compliance.
- What happens if an aircraft flies past a maintenance limit?
- It was not airworthy for those flights, and the finding is retrospective — the flights have already happened, already been billed, and in training already been logged towards licences. Rectifying the maintenance does not undo that, which is why tracking errors are treated as airworthiness events rather than administrative ones.
- What makes component tracking harder than airframe tracking?
- Components move. A part removed from one aircraft and fitted to another carries its accumulated time and history with it onto a different set of counters, and serial-controlled items must be tracked individually rather than by type. Overhauls reset some values and not others, so the arithmetic is per item rather than per aircraft.