AD Deadlines Explained: Flight Hours, Cycles, and Calendar Limits

An Airworthiness Directive isn't just a yes/no on applicability — it comes with a clock. Sometimes several clocks at once. Miss the moment they run out and a compliant aircraft becomes a non-compliant one, often without anything visibly changing. Understanding how AD deadlines are expressed, and how to compute the next due point per aircraft, is what keeps a fleet ahead of them instead of reacting to them.

This article covers one-time versus recurring ADs, the three ways deadlines are measured, how they combine, and how the maintenance programme interacts.

One-time vs recurring ADs

The first distinction is whether the AD is done once or forever:

• One-time ADs require an action by a deadline. Once complied with, the requirement is satisfied and closes.
• Recurring ADs require an action to be repeated at intervals — a repetitive inspection, for example. Complying once does not close them; it resets the clock to the next occurrence. Treating a recurring AD as closed after the first compliance is one of the most common and most consequential record errors.

Everything about deadline management flows from getting this classification right per directive.

The three clocks: flight hours, cycles, calendar

AD deadlines are typically expressed against one or more of three measures:

• Flight hours — accumulated hours of operation.
• Flight cycles — takeoff/landing cycles, which matter for fatigue-driven issues.
• Calendar time — elapsed days, months, or years, independent of how much the aircraft flies.

An AD might say "within 100 flight hours," "before 5,000 cycles," "within 12 months," or a combination. Which clock governs depends on the unsafe condition: fatigue tends to be cycle-driven, time-in-service issues hour-driven, and corrosion or age-related conditions calendar-driven.

Whichever comes first, thresholds, and grace

Where an AD specifies more than one measure, the deadline is usually whichever comes first — the earliest of the hour, cycle, or calendar limits. A high-utilisation aircraft may hit a cycle limit long before the calendar one; a low-utilisation aircraft may hit the calendar limit first. That's why the same AD produces different due dates on different tails, and why a fleet-wide "due date" is meaningless without per-aircraft utilisation.

ADs also frequently define the start point for the clock — from the effective date, from a modification, from last compliance for recurring items — and sometimes a compliance window or threshold rather than a single instant. Reading these precisely is the difference between a correct due point and a plausible-looking wrong one.

How the maintenance programme interacts

AD requirements don't live in isolation; they interact with the aircraft's approved maintenance programme (AMP). Recurring AD intervals often need to be scheduled alongside existing maintenance tasks, and the way an operator tracks hours and cycles for the AMP is the same data that drives AD due points. Keeping AD deadlines and the maintenance programme on the same, current utilisation data is what prevents the two from drifting apart.

Computing the next due point per aircraft

Putting it together, the next due point for an AD on a specific aircraft is a function of:

• the AD's measure(s) and interval(s),
• the correct start point,
• the aircraft's current flight hours and cycles,
• the aircraft's utilisation trend (to forecast when hour/cycle limits will be reached),
• and, for recurring items, the date/hours/cycles at last compliance.

Do this per tail and you get a real forecast — not just "this AD is due," but "this aircraft will reach the limit around this date at current utilisation." That forecast is what makes proactive planning possible.

Alerting before it's late

The point of computing due points is to act on them with time to spare. Effective alerting gives configurable lead times ahead of each due point — enough to plan the work into a maintenance slot rather than scramble — and it accounts for the fact that a busy aircraft eats through an hours/cycles margin faster than the calendar suggests. A missed AD deadline is rarely a surprise in hindsight; it's usually a due point that was computed late or not at all.

How Aviagent helps

Aviagent extracts each AD's compliance interval — flight hours, cycles, or calendar — and computes the next due point per aircraft against its actual utilisation, distinguishing one-time from recurring requirements so recurring ADs stay open with their next occurrence. Escalation alerts fire ahead of due dates with configurable lead times, and the determinations are shown with their reasoning for your engineers to confirm. The result is a per-tail deadline picture you can plan against, rather than a static list that quietly goes stale.

FAQ

How are AD deadlines measured? By flight hours, flight cycles, calendar time, or a combination. Where more than one applies, the deadline is normally whichever limit is reached first.

Why does the same AD have different due dates on different aircraft? Because due dates depend on each aircraft's utilisation. A high-cycle aircraft reaches a cycle limit sooner; a low-utilisation aircraft may hit the calendar limit first. Per-tail utilisation is essential.

Do recurring ADs ever close? No — they repeat at intervals. Complying resets the clock to the next occurrence; it doesn't close the requirement. Marking a recurring AD "closed" is a frequent error.

How much lead time should alerts give? Enough to plan the work into a maintenance opportunity rather than react. Lead times should be configurable and should account for utilisation eating into hour/cycle margins faster than calendar time.

See which ADs apply to your fleet — free, in about 30 seconds. Try the free AD lookup, or book a 20-minute walkthrough.

Related reading: Superseded and recurring ADs · Which airworthiness directives apply to your aircraft · Building an audit-ready AD evidence chain.

About the author — Satya Neerupudi is Founder & CEO/CTO of Aviagent and an aeronautical engineer with 25 years in continuing airworthiness at SAS, GE Aviation, Pratt & Whitney, and HAL.