On a fleet of 15 to 40 aircraft, missing an applicable Airworthiness Directive is a legal violation. FAA Part 39 and EASA Part 21 subpart J ADs are mandatory, and a compliance gap creates airworthiness exposure even when the aircraft has a current certificate. Tracking sounds simple in theory, but mixed maintenance histories and components with individual time-since-new requirements make it difficult in practice.
How airworthiness directives work
An airworthiness directive comes from an airworthiness authority and targets a type design, appliance type, or part number. It mandates corrective action within a specified compliance window, expressed as a calendar date, flight-hours threshold, or flight-cycles threshold. Emergency ADs generally require immediate or near-term action, often within days or a small number of flight hours. Normal ADs allow wider windows, sometimes months or thousands of flight hours.
An AD can require a one-time action or recur every X hours, cycles, or months. Recurring ADs are harder to control because each affected component on each aircraft needs an accurate compliance record and projected next-due date. That date moves whenever the aircraft flies.
In a mixed-age fleet, aircraft can hold different statuses for the same AD when an alternative method of compliance exists or some have incorporated the design change that supersedes it. Maintaining that distinction across 25 aircraft with varied maintenance histories is beyond what one person can reliably sustain in a spreadsheet.
The AD applicability determination problem
First determine whether an AD applies to the particular aircraft. The apparent process is simple: find ADs for the aircraft type and assess each one. Actual applicability may depend on the installed part number, covered serial number range, airframe modification status, or the operator's maintenance program.
An AD for a part number may not affect every aircraft of that type if some operators installed a later version. An AD covering serial numbers N1500 to N2200 excludes serial N2201. If the required modification was already incorporated before the AD was issued, the operator may demonstrate compliance through that prior action.
The CAMO or responsible maintenance organization makes the determination. Fleet planning needs, for every tail, the applicable AD list, current status, and projected next-due dates. That data feeds scheduling. If recent AD applicability has not been assessed or records were not updated after a recent check, scheduling is based on incomplete information.
Where manual AD tracking fails
Manual fleet-level tracking most often fails through an inaccurate projected due date, not a completely missed deadline. Suppose an AD recurs every 600 flight hours and the last action occurred at 14,200 airframe hours. The next due point is projected at 14,800 hours. If utilization rises 15% during the following quarter, that date moves earlier.
Next-due dates calculated from a fixed utilization rate drift as actual flying changes. The error builds over a quarter or year. When a planner updates everything using current utilization, items once months away may be weeks away, while others must move into the immediate queue from the deferred backlog.
The second failure mode is more immediate. A new AD is published for an aircraft type, but applicability to individual fleet members and the compliance-window calculation occur after publication. Without active, systematic monitoring, planning may first learn of an applicable AD from an auditor or check pilot, not from the planning function.
How AD compliance fits scheduled maintenance
An AD due at 14,800 flight hours can fit inside a scheduled C-check, making it a planning opportunity as well as a compliance requirement. A C-check at 14,850 hours can include the AD in its work package. At 15,200 hours, the AD needs a separate hangar visit beforehand, adding mobilization cost and aircraft downtime.
Experienced planners make these judgments intuitively for the ADs they actively manage. The harder task is applying them consistently to the full AD register across the fleet. A system containing compliance windows and planned maintenance can find ADs suitable for bundling into scheduled visits instead of separate actions. Across a 25-aircraft fleet, the hangar mobilization savings accumulate over a year.
The reverse case matters too. If a C-check is planned while several AD windows close within a few months, moving the check slightly earlier may combine the work into one visit. Otherwise, the aircraft may return for AD work soon after the check. A manual planner may spot this for top-priority items; a system with the complete AD register applies the check consistently across all items.
What Tailsight handles, and what it does not
Tailsight treats AD deadlines as scheduling constraints and highlights clashes between projected compliance windows and planned maintenance. It alerts planners when an AD is expected to fall during a period with no scheduled hangar visit and flags the issue for resolution. It imports compliance records from the MRO system and projects next-due dates using actual flight-record utilization.
Tailsight is not a certified maintenance recordkeeping system. The authoritative AD compliance record remains in the CAMO or MRO records system. Tailsight reads it for scheduling. Applicability decisions, sign-off for completed AD work, and maintenance release remain in the organization's certified system. We are not presenting scheduling support as certified recordkeeping. Keeping them separate avoids creating another compliance risk.
The integration closes the gap between an AD record showing the next action due in 11 weeks and a flight plan that leaves the aircraft unavailable for maintenance for 9 of those 11 weeks. The scheduling system exposes this gap, which the records system alone cannot. Finding it is scheduling's role. Fixing it belongs to maintenance planning, and recording the fix belongs to records. Connecting those functions while keeping their responsibilities separate is what makes the process reliable.