Almost every operation starts the same way: a spreadsheet with the airframe hours, another with component due dates, a folder of PDFs with the ADs and SBs, and one person, usually just one, who knows how it all connects. It works. Until the day it doesn't.
The problem with spreadsheet-based technical tracking is not cosmetic. It is structural: the spreadsheet depends on someone remembering to update it, and aircraft item due dates do not forgive forgetfulness. An overdue inspection that goes unnoticed is not an administrative error. It is an aircraft operating outside airworthiness condition, with all the regulatory, insurance and safety consequences that carries.
The five failure modes of the spreadsheet
1. The hour totals travel separately from the flight. The flight happens, the logbook is filled out, and the spreadsheet hours are updated... when someone remembers. Every interval between the flight and the update is a window in which the calculated due dates are wrong.
2. A component is tracked by more than one unit. Items expire by hours, cycles and calendar, whichever comes first. The typical spreadsheet tracks one unit well and the others poorly. The classic: the component with hours to spare that expired by calendar without anyone noticing.
3. ADs and SBs are not one-time events. Directives have applicability by serial number, initial compliance and, often, repetitive compliance. Tracking this in a spreadsheet row demands an archivist's discipline, and the inspector asks exactly about what falls in the interval between compliances.
4. There is no trail of who changed what. An overwritten cell tells no story. When the question comes up ("was this inspection really extended? by whom?"), the spreadsheet does not answer.
5. The knowledge lives in one person. Vacation, a resignation or simply a weekend, and the operation discovers that technical tracking was, in practice, someone's memory.
If you recognized two or more, the problem is not that your spreadsheet is poorly made. It is that the tool has reached its limit.
What a real CTM needs to have
A Maintenance Tracking system (Controle Técnico de Manutenção) worthy of the name rests on four capabilities:
- Hours and cycles fed by the operation. Entering the flight in the logbook updates airframe, engines and tracked components, with no retyping. It is the only way for due dates to be right always, and not just on the day of the update.
- Component map with multiple control units. Each item with its limits by hours, cycles and calendar, expiring by whichever comes first, with a projection based on the aircraft's actual average utilization ("at the current pace, this item is due in ~45 days").
- Control of directives and bulletins with recurrence. ADs and SBs with applicability, method of compliance, document reference and, when repetitive, the next due date generated automatically after each compliance.
- Alerts with configurable lead time and a complete trail. The system warns in advance, with room to plan the downtime, and records who entered, who changed and on what basis.
The transition: how to migrate without losing (or corrupting) the history
Migrating from a spreadsheet to a structured CTM has a single critical point: the initial snapshot. All future control derives from the starting totals: airframe hours, hours/cycles of each component, status of each AD/SB, date and hour meter of the last inspection of each type. Recommendations from people who have done this many times:
- Freeze a cutover date and close the spreadsheet on that date. A migration with a still-live spreadsheet creates two diverging controls;
- Reconcile the initial snapshot with the physical records (airframe and engine logbooks, latest work orders), not with the spreadsheet itself. If the spreadsheet has accumulated errors, this is the time to find them, not to perpetuate them;
- Validate with whoever performs the maintenance. The shop or the responsible mechanic reviewing the initial snapshot is the best inexpensive audit there is;
- Run the first month with double attention: every alert from the new system checked against the team's expectation. Divergence in this period is gold: it is an error being found before it gets costly.
Where Alis comes in
Alis's CTM was built integrated with the operation from the start: the flight entered in the digital logbook automatically updates airframe and component hours and cycles; the due-date map projects dates based on actual utilization; ADs, SBs and inspections have tracking with recurrence and linked documentation; and alerts arrive with lead time to plan, even showing up in Flight Kit, so the crew knows about technical pending items before the flight, not after.
Want to see your aircraft in this tracking? Talk to Alis. Migrating the initial snapshot is part of onboarding, done together with you.
This article is informational and does not replace the regulations in force, the manufacturer's manuals, or the technical responsibility applicable to the maintenance of your aircraft.