AD and SB Compliance Tracking for Small Flight Schools: How It Should Actually Work

Airworthiness directives are legally mandatory, they recur on schedules that do not line up with your annual, and they are tied to a mix of calendar dates, flight hours, and cycles. That combination is exactly what a busy flight school gets wrong. Not because anyone is careless, but because tracking a recurring AD due at every 100 hours of tach time across a six-aircraft fleet is genuinely hard to do on paper. Here is how a real compliance system should be structured.

Know the difference between what you are tracking

An airworthiness directive is issued by the FAA and is mandatory. A service bulletin is issued by the manufacturer and is usually advisory, though your operating rules or an AD can make a specific SB mandatory. Both need to be on your radar, but you must never treat an SB as optional just because the manufacturer's language is softer, and you must never let an AD slip because it was buried in an SB reference. The first job of any tracking system is to hold both, clearly labeled, with their compliance basis attached.

The three clocks every AD runs on

This is the part paper handles worst. A directive can be due on a calendar interval, on a flight-hour interval, or on cycles, and recurring ADs reset each time you comply. A calendar AD due every 12 months is easy. A recurring AD due every 100 hours of time in service is the trap, because it drifts against your 100-hour inspection and your annual and never lines up cleanly. If your aircraft flies more than 100 hours between annuals, and a training aircraft absolutely does, you will hit that recurring AD several times a year on a schedule nothing else shares.

The only reliable way to track an hour-based AD is to compute the next-due value from the same time source you actually record after every flight. If you are recording tach time on a rental, your hour-based AD compliance has to run off tach. If you have not sorted out which clock you bill and track on, our explainer on Hobbs versus tach time is worth reading first, because using the wrong clock silently corrupts your AD next-due math.

Next-due, not last-done

A tracking system built around last-compliance dates is backwards. What you need on the wall every morning is next-due, sorted by urgency, in the unit that matters. The mechanic and the chief instructor should be able to see at a glance that N12345 is 6.4 tach hours from a recurring AD and 22 hours from its 100-hour, so it should not go out on today's four-hour cross-country. That single view is what prevents the last-minute scrub and, worse, the inadvertent overflight of a compliance limit. This is the core of how our Maintenance module presents fleet status: every aircraft, every open directive, computed to next-due against the live time source.

Compliance has to link to the aircraft's actual status

An AD that is past due should not be a note in a binder. It should ground the airplane. The cleanest operations connect compliance directly to airworthiness status, so that an overdue directive or an open squawk that touches airworthiness makes the aircraft unavailable to schedule. When maintenance and scheduling share the same data, you cannot book a flight in an aircraft the maintenance side has grounded. We wrote about why that shared-data model matters in dispatch board versus spreadsheet; AD compliance is the highest-stakes example of it.

Keep the paper trail an inspector will ask for

For every AD, you need to be able to show the directive number, the method of compliance, the date and time in service at compliance, the signature of the person who returned the aircraft to service, and the next-due if it recurs. That record is what an IA wants at annual and what an FSDO inspector wants to see. Storing it alongside the aircraft's other maintenance records, rather than in a separate AD binder that lives in one person's office, is what keeps it retrievable under pressure.

A workflow that holds up

Here is the loop that works. When a new AD is issued against a type in your fleet, you record it once with its applicability and its compliance basis. The system computes next-due for each affected tail. After every flight, your recorded time updates and the next-due recalculates. As an aircraft approaches a limit, it surfaces on the fleet status view before it becomes urgent, so maintenance can plan the compliance work into a slow day instead of grounding a revenue aircraft on a Saturday. When the work is done, one entry records compliance and resets the recurrence. Nothing lives in a human's memory, and nothing depends on someone remembering to check a binder.

The schools that get this right are not the ones with the biggest maintenance staff. They are the ones who stopped tracking compliance in a place separate from where they track flight time, and let the two talk to each other. If you are mapping out what a modern setup looks like end to end, see what a modern flight school tech stack looks like.