Recurring ADs Have No Grace Period, and That Distinction Grounds Aircraft

Scheduled inspections often carry a tolerance window. Recurring Airworthiness Directives do not. Overfly one by a single flight hour and the aircraft is legally unairworthy.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Compliance

|

A Tolerance That Doesn't Exist

Ask a line technician how much room there is on a phase inspection and you'll get a number. Most approved maintenance programs carry an inspection tolerance, commonly ten percent or ten hours on an hourly task and a flat window of days on a calendar task, and crews internalize it. A trip that pushes a check a few hours past nominal feels routine because, for that task, it is. The program authorizes the slack, and using it is fully legal.

The trouble is that the same instinct quietly bleeds onto a class of requirement that carries no slack at all. A recurring airworthiness directive (AD) is due exactly when it is due. There is no built-in window, no soft margin, no catching it at the next event. Fly past the compliance time by one flight hour or one calendar day and the aircraft is unairworthy under federal regulation, and it stays that way until the directive is satisfied or a deviation is formally approved. The gap between how those two line items behave, both sitting on the same status report, both counting down in the same units, is where otherwise disciplined flight departments get caught. This piece is about closing that gap before it scrubs a trip or, worse, surfaces during a ramp check.

ADs Are Regulation, and the Operator Holds the Bag

An AD is not a manufacturer recommendation and not an industry best practice. The FAA issues ADs under 14 CFR Part 39, and Part 39 states plainly that no person may operate a product to which an AD applies except in accordance with that AD. That framing matters because it changes who is exposed and how badly. Under 14 CFR 91.403, the owner or operator is primarily responsible for keeping the aircraft in an airworthy condition, which expressly includes compliance with every applicable AD. Not the mechanic who turned the wrench, not the management company, not the avionics shop that did the last database upload. The certificate holder.

A Director of Maintenance can delegate the labor and the tracking, but the regulatory responsibility for the aircraft being legal to dispatch sits with the operator, and a signed work order from a vendor does not move that line. When a recurring AD is overflown, the enforcement exposure, the insurance friction, and the residual-value haircut at resale all land on the same party. A logbook with an open AD finding is exactly what a sharp pre-purchase inspection (PPI) is built to surface, and a buyer's technical rep will price the discovery in. This is why ADs sit at the top of the airworthiness hierarchy. An inspection program can be tailored, escalated, or replaced with an FAA-accepted alternative. An AD becomes mandatory the moment its applicability matches your serial number, engine, appliance, or installed STC, and it stays mandatory regardless of how well the rest of the program is run.

One-Time Directives Versus the Ones That Never Close

The first distinction a records system has to make is whether a directive is one-time or recurring, because they age completely differently over the life of the airframe. A one-time AD is satisfied once and discharged. You perform the required inspection, modification, or replacement, document the method of compliance, and the directive is closed for that aircraft permanently. Many recurring ADs also offer a terminating action: an optional or required modification that, once embodied, ends the otherwise repetitive requirement. Install the redesigned part or incorporate the service bulletin (SB) the AD references, log it correctly against the AD, and the repeating inspection drops off the open-items list for good. Terminating actions are worth chasing precisely because they convert a perpetual liability into a closed entry and remove a recurring drag on dispatch reliability.

A recurring AD never closes on its own. It establishes an initial compliance threshold and then a repeat interval, and that interval persists for the operational life of the affected component or structure until a terminating action is incorporated. Inspect a structural area every 1,200 flight hours. Functionally check a system every 24 calendar months. Re-torque or re-examine a fitting at a fixed cadence indefinitely. Every time you comply you reset the clock and, in the same motion, create the next due point. Miss that reset in your tracking and the aircraft keeps flying toward a wall nobody is watching, which is a very different failure mode from a part wearing out. Nothing breaks. The number is simply wrong.

Due When Due, Full Stop

Here is the operational heart of it. A scheduled inspection task usually carries a defined plus-or-minus window written into the approved maintenance program, and because the program is an FAA-accepted document, the tolerance is part of what was accepted. A recurring AD carries no comparable allowance unless the directive itself grants one in its own text. Read the language and the difference is obvious. An AD will say something like "within 100 hours time-in-service" and "thereafter at intervals not to exceed 100 hours." That "not to exceed" is a ceiling, not a target with margin around it. There is no implied ten percent and no quiet rounding. If the next inspection falls due at 4,820.0 flight hours and the aircraft lands at 4,820.1, compliance was not met, the aircraft was operated past the AD limit, and under Part 39 every leg flown after that point is its own finding.

Operators trip on this for a structural reason, not a competence one. The two requirements live side by side on the status report and look identical at a glance. Both show a next-due value, both count down in hours or months, and both get a green, amber, or red flag from the same software. But one is governed by an approved program that includes tolerance and the other by federal regulation that does not. Treating them as the same kind of number is the single most common path to an inadvertent violation inside an otherwise clean operation, and it is almost never a decision anyone made on purpose.

AMOC Is the Only Legal Way to Move the Interval

When a recurring AD's interval genuinely does not fit an operation, the answer is not to stretch it on the line and hope. The answer is an Alternative Method of Compliance (AMOC). An AMOC is the formal mechanism for doing something other than exactly what the AD prescribes, which can include flying a different interval or using a different procedure to achieve the same level of safety. The non-negotiable part is that an operator cannot self-grant one. An AMOC must be approved in writing by the cognizant FAA office, typically the Aircraft Certification Office responsible for the directive, or it must already be authorized within the body of the AD itself. Some ADs name a manufacturer's document or a specific office as a pre-approved AMOC source; absent that, you are submitting a request and waiting on a written approval that references your situation.

There is no version of this where a DOM extends a recurring AD on their own signature and stays compliant. The interval is the interval until an authority with jurisdiction says otherwise, in writing, for your aircraft. That is also why the tracking has to be right well in advance: the relief valve is slow and formal by design, and it cannot be reached for at the last minute on a ramp with a principal already in the car.

The Learjet That Didn't Go

A Learjet operator carried an hours-based structural AD on the airframe, a recurring inspection with a fixed flight-hour interval. The aircraft came back from a multi-leg trip with the logbooks squared away for the legs flown, but nobody reconciled cumulative airframe time against the AD's next-due value once the trip closed out. The compliance point had been crossed by roughly eight flight hours somewhere in the back half of that itinerary, and no one knew it.

The discovery came the morning the principal wanted to launch. A pre-departure status check flagged the AD as past due. With no tolerance to invoke and no AMOC on file, there was no legal dispatch and no quick fix. The inspection the AD requires is not a thirty-minute task; it meant opening structure for access, performing the inspection, and obtaining the return-to-service (RTS) sign-off before the aircraft could fly again. The same-day trip was scrubbed and chartered out, and the department then spent days documenting how an aircraft had flown eight hours in an unairworthy condition without anyone catching it in real time. Nothing had failed mechanically. The structure was almost certainly fine. The failure was purely one of reconciliation: a next-due number that never got updated against actual times after the last trip, and no system forcing the comparison before the next departure.

What an Audit-Ready AD Entry Actually Shows

The defense is documentation discipline, because a recurring-AD record is not only proof you did the work. It is proof you know precisely when the next obligation falls and against which revision. A complete entry shows three things without anyone having to reconstruct them from scattered sign-offs:

  • Method of compliance, citing the specific AD paragraph, service bulletin, or procedure used, so an auditor can confirm you did what the directive required rather than something adjacent.

  • AD number and revision, because directives get amended and superseded, and compliance against a stale revision is not compliance against the one in force.

  • The next-due value, stated in both flight hours and calendar terms wherever the AD uses both, so the reset point is explicit and impossible to overfly by accident.

When those three elements are captured cleanly on every recurring AD across the fleet, the next-due value becomes the number every pre-departure check measures against, and the eight-hour overfly stops being possible. When they live in loose logbook entries and a tracking spreadsheet that only updates when someone remembers, the wall is always out there somewhere in the dark. Getting compliance status into one place where the method, the revision, and the next-due are queryable together is the difference between catching an AD the week before it comes due and finding it the morning of a scrubbed trip. The directive gives you no grace. The records have to carry that load instead.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free

Recurring ADs Have No Grace Period, and That Distinction Grounds Aircraft

Scheduled inspections often carry a tolerance window. Recurring Airworthiness Directives do not. Overfly one by a single flight hour and the aircraft is legally unairworthy.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Compliance

|

A Tolerance That Doesn't Exist

Ask a line technician how much room there is on a phase inspection and you'll get a number. Most approved maintenance programs carry an inspection tolerance, commonly ten percent or ten hours on an hourly task and a flat window of days on a calendar task, and crews internalize it. A trip that pushes a check a few hours past nominal feels routine because, for that task, it is. The program authorizes the slack, and using it is fully legal.

The trouble is that the same instinct quietly bleeds onto a class of requirement that carries no slack at all. A recurring airworthiness directive (AD) is due exactly when it is due. There is no built-in window, no soft margin, no catching it at the next event. Fly past the compliance time by one flight hour or one calendar day and the aircraft is unairworthy under federal regulation, and it stays that way until the directive is satisfied or a deviation is formally approved. The gap between how those two line items behave, both sitting on the same status report, both counting down in the same units, is where otherwise disciplined flight departments get caught. This piece is about closing that gap before it scrubs a trip or, worse, surfaces during a ramp check.

ADs Are Regulation, and the Operator Holds the Bag

An AD is not a manufacturer recommendation and not an industry best practice. The FAA issues ADs under 14 CFR Part 39, and Part 39 states plainly that no person may operate a product to which an AD applies except in accordance with that AD. That framing matters because it changes who is exposed and how badly. Under 14 CFR 91.403, the owner or operator is primarily responsible for keeping the aircraft in an airworthy condition, which expressly includes compliance with every applicable AD. Not the mechanic who turned the wrench, not the management company, not the avionics shop that did the last database upload. The certificate holder.

A Director of Maintenance can delegate the labor and the tracking, but the regulatory responsibility for the aircraft being legal to dispatch sits with the operator, and a signed work order from a vendor does not move that line. When a recurring AD is overflown, the enforcement exposure, the insurance friction, and the residual-value haircut at resale all land on the same party. A logbook with an open AD finding is exactly what a sharp pre-purchase inspection (PPI) is built to surface, and a buyer's technical rep will price the discovery in. This is why ADs sit at the top of the airworthiness hierarchy. An inspection program can be tailored, escalated, or replaced with an FAA-accepted alternative. An AD becomes mandatory the moment its applicability matches your serial number, engine, appliance, or installed STC, and it stays mandatory regardless of how well the rest of the program is run.

One-Time Directives Versus the Ones That Never Close

The first distinction a records system has to make is whether a directive is one-time or recurring, because they age completely differently over the life of the airframe. A one-time AD is satisfied once and discharged. You perform the required inspection, modification, or replacement, document the method of compliance, and the directive is closed for that aircraft permanently. Many recurring ADs also offer a terminating action: an optional or required modification that, once embodied, ends the otherwise repetitive requirement. Install the redesigned part or incorporate the service bulletin (SB) the AD references, log it correctly against the AD, and the repeating inspection drops off the open-items list for good. Terminating actions are worth chasing precisely because they convert a perpetual liability into a closed entry and remove a recurring drag on dispatch reliability.

A recurring AD never closes on its own. It establishes an initial compliance threshold and then a repeat interval, and that interval persists for the operational life of the affected component or structure until a terminating action is incorporated. Inspect a structural area every 1,200 flight hours. Functionally check a system every 24 calendar months. Re-torque or re-examine a fitting at a fixed cadence indefinitely. Every time you comply you reset the clock and, in the same motion, create the next due point. Miss that reset in your tracking and the aircraft keeps flying toward a wall nobody is watching, which is a very different failure mode from a part wearing out. Nothing breaks. The number is simply wrong.

Due When Due, Full Stop

Here is the operational heart of it. A scheduled inspection task usually carries a defined plus-or-minus window written into the approved maintenance program, and because the program is an FAA-accepted document, the tolerance is part of what was accepted. A recurring AD carries no comparable allowance unless the directive itself grants one in its own text. Read the language and the difference is obvious. An AD will say something like "within 100 hours time-in-service" and "thereafter at intervals not to exceed 100 hours." That "not to exceed" is a ceiling, not a target with margin around it. There is no implied ten percent and no quiet rounding. If the next inspection falls due at 4,820.0 flight hours and the aircraft lands at 4,820.1, compliance was not met, the aircraft was operated past the AD limit, and under Part 39 every leg flown after that point is its own finding.

Operators trip on this for a structural reason, not a competence one. The two requirements live side by side on the status report and look identical at a glance. Both show a next-due value, both count down in hours or months, and both get a green, amber, or red flag from the same software. But one is governed by an approved program that includes tolerance and the other by federal regulation that does not. Treating them as the same kind of number is the single most common path to an inadvertent violation inside an otherwise clean operation, and it is almost never a decision anyone made on purpose.

AMOC Is the Only Legal Way to Move the Interval

When a recurring AD's interval genuinely does not fit an operation, the answer is not to stretch it on the line and hope. The answer is an Alternative Method of Compliance (AMOC). An AMOC is the formal mechanism for doing something other than exactly what the AD prescribes, which can include flying a different interval or using a different procedure to achieve the same level of safety. The non-negotiable part is that an operator cannot self-grant one. An AMOC must be approved in writing by the cognizant FAA office, typically the Aircraft Certification Office responsible for the directive, or it must already be authorized within the body of the AD itself. Some ADs name a manufacturer's document or a specific office as a pre-approved AMOC source; absent that, you are submitting a request and waiting on a written approval that references your situation.

There is no version of this where a DOM extends a recurring AD on their own signature and stays compliant. The interval is the interval until an authority with jurisdiction says otherwise, in writing, for your aircraft. That is also why the tracking has to be right well in advance: the relief valve is slow and formal by design, and it cannot be reached for at the last minute on a ramp with a principal already in the car.

The Learjet That Didn't Go

A Learjet operator carried an hours-based structural AD on the airframe, a recurring inspection with a fixed flight-hour interval. The aircraft came back from a multi-leg trip with the logbooks squared away for the legs flown, but nobody reconciled cumulative airframe time against the AD's next-due value once the trip closed out. The compliance point had been crossed by roughly eight flight hours somewhere in the back half of that itinerary, and no one knew it.

The discovery came the morning the principal wanted to launch. A pre-departure status check flagged the AD as past due. With no tolerance to invoke and no AMOC on file, there was no legal dispatch and no quick fix. The inspection the AD requires is not a thirty-minute task; it meant opening structure for access, performing the inspection, and obtaining the return-to-service (RTS) sign-off before the aircraft could fly again. The same-day trip was scrubbed and chartered out, and the department then spent days documenting how an aircraft had flown eight hours in an unairworthy condition without anyone catching it in real time. Nothing had failed mechanically. The structure was almost certainly fine. The failure was purely one of reconciliation: a next-due number that never got updated against actual times after the last trip, and no system forcing the comparison before the next departure.

What an Audit-Ready AD Entry Actually Shows

The defense is documentation discipline, because a recurring-AD record is not only proof you did the work. It is proof you know precisely when the next obligation falls and against which revision. A complete entry shows three things without anyone having to reconstruct them from scattered sign-offs:

  • Method of compliance, citing the specific AD paragraph, service bulletin, or procedure used, so an auditor can confirm you did what the directive required rather than something adjacent.

  • AD number and revision, because directives get amended and superseded, and compliance against a stale revision is not compliance against the one in force.

  • The next-due value, stated in both flight hours and calendar terms wherever the AD uses both, so the reset point is explicit and impossible to overfly by accident.

When those three elements are captured cleanly on every recurring AD across the fleet, the next-due value becomes the number every pre-departure check measures against, and the eight-hour overfly stops being possible. When they live in loose logbook entries and a tracking spreadsheet that only updates when someone remembers, the wall is always out there somewhere in the dark. Getting compliance status into one place where the method, the revision, and the next-due are queryable together is the difference between catching an AD the week before it comes due and finding it the morning of a scrubbed trip. The directive gives you no grace. The records have to carry that load instead.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free

Recurring ADs Have No Grace Period, and That Distinction Grounds Aircraft

Scheduled inspections often carry a tolerance window. Recurring Airworthiness Directives do not. Overfly one by a single flight hour and the aircraft is legally unairworthy.

Israel Slodowitz

Israel Slodowitz

Founder of Radar

Compliance

|

A Tolerance That Doesn't Exist

Ask a line technician how much room there is on a phase inspection and you'll get a number. Most approved maintenance programs carry an inspection tolerance, commonly ten percent or ten hours on an hourly task and a flat window of days on a calendar task, and crews internalize it. A trip that pushes a check a few hours past nominal feels routine because, for that task, it is. The program authorizes the slack, and using it is fully legal.

The trouble is that the same instinct quietly bleeds onto a class of requirement that carries no slack at all. A recurring airworthiness directive (AD) is due exactly when it is due. There is no built-in window, no soft margin, no catching it at the next event. Fly past the compliance time by one flight hour or one calendar day and the aircraft is unairworthy under federal regulation, and it stays that way until the directive is satisfied or a deviation is formally approved. The gap between how those two line items behave, both sitting on the same status report, both counting down in the same units, is where otherwise disciplined flight departments get caught. This piece is about closing that gap before it scrubs a trip or, worse, surfaces during a ramp check.

ADs Are Regulation, and the Operator Holds the Bag

An AD is not a manufacturer recommendation and not an industry best practice. The FAA issues ADs under 14 CFR Part 39, and Part 39 states plainly that no person may operate a product to which an AD applies except in accordance with that AD. That framing matters because it changes who is exposed and how badly. Under 14 CFR 91.403, the owner or operator is primarily responsible for keeping the aircraft in an airworthy condition, which expressly includes compliance with every applicable AD. Not the mechanic who turned the wrench, not the management company, not the avionics shop that did the last database upload. The certificate holder.

A Director of Maintenance can delegate the labor and the tracking, but the regulatory responsibility for the aircraft being legal to dispatch sits with the operator, and a signed work order from a vendor does not move that line. When a recurring AD is overflown, the enforcement exposure, the insurance friction, and the residual-value haircut at resale all land on the same party. A logbook with an open AD finding is exactly what a sharp pre-purchase inspection (PPI) is built to surface, and a buyer's technical rep will price the discovery in. This is why ADs sit at the top of the airworthiness hierarchy. An inspection program can be tailored, escalated, or replaced with an FAA-accepted alternative. An AD becomes mandatory the moment its applicability matches your serial number, engine, appliance, or installed STC, and it stays mandatory regardless of how well the rest of the program is run.

One-Time Directives Versus the Ones That Never Close

The first distinction a records system has to make is whether a directive is one-time or recurring, because they age completely differently over the life of the airframe. A one-time AD is satisfied once and discharged. You perform the required inspection, modification, or replacement, document the method of compliance, and the directive is closed for that aircraft permanently. Many recurring ADs also offer a terminating action: an optional or required modification that, once embodied, ends the otherwise repetitive requirement. Install the redesigned part or incorporate the service bulletin (SB) the AD references, log it correctly against the AD, and the repeating inspection drops off the open-items list for good. Terminating actions are worth chasing precisely because they convert a perpetual liability into a closed entry and remove a recurring drag on dispatch reliability.

A recurring AD never closes on its own. It establishes an initial compliance threshold and then a repeat interval, and that interval persists for the operational life of the affected component or structure until a terminating action is incorporated. Inspect a structural area every 1,200 flight hours. Functionally check a system every 24 calendar months. Re-torque or re-examine a fitting at a fixed cadence indefinitely. Every time you comply you reset the clock and, in the same motion, create the next due point. Miss that reset in your tracking and the aircraft keeps flying toward a wall nobody is watching, which is a very different failure mode from a part wearing out. Nothing breaks. The number is simply wrong.

Due When Due, Full Stop

Here is the operational heart of it. A scheduled inspection task usually carries a defined plus-or-minus window written into the approved maintenance program, and because the program is an FAA-accepted document, the tolerance is part of what was accepted. A recurring AD carries no comparable allowance unless the directive itself grants one in its own text. Read the language and the difference is obvious. An AD will say something like "within 100 hours time-in-service" and "thereafter at intervals not to exceed 100 hours." That "not to exceed" is a ceiling, not a target with margin around it. There is no implied ten percent and no quiet rounding. If the next inspection falls due at 4,820.0 flight hours and the aircraft lands at 4,820.1, compliance was not met, the aircraft was operated past the AD limit, and under Part 39 every leg flown after that point is its own finding.

Operators trip on this for a structural reason, not a competence one. The two requirements live side by side on the status report and look identical at a glance. Both show a next-due value, both count down in hours or months, and both get a green, amber, or red flag from the same software. But one is governed by an approved program that includes tolerance and the other by federal regulation that does not. Treating them as the same kind of number is the single most common path to an inadvertent violation inside an otherwise clean operation, and it is almost never a decision anyone made on purpose.

AMOC Is the Only Legal Way to Move the Interval

When a recurring AD's interval genuinely does not fit an operation, the answer is not to stretch it on the line and hope. The answer is an Alternative Method of Compliance (AMOC). An AMOC is the formal mechanism for doing something other than exactly what the AD prescribes, which can include flying a different interval or using a different procedure to achieve the same level of safety. The non-negotiable part is that an operator cannot self-grant one. An AMOC must be approved in writing by the cognizant FAA office, typically the Aircraft Certification Office responsible for the directive, or it must already be authorized within the body of the AD itself. Some ADs name a manufacturer's document or a specific office as a pre-approved AMOC source; absent that, you are submitting a request and waiting on a written approval that references your situation.

There is no version of this where a DOM extends a recurring AD on their own signature and stays compliant. The interval is the interval until an authority with jurisdiction says otherwise, in writing, for your aircraft. That is also why the tracking has to be right well in advance: the relief valve is slow and formal by design, and it cannot be reached for at the last minute on a ramp with a principal already in the car.

The Learjet That Didn't Go

A Learjet operator carried an hours-based structural AD on the airframe, a recurring inspection with a fixed flight-hour interval. The aircraft came back from a multi-leg trip with the logbooks squared away for the legs flown, but nobody reconciled cumulative airframe time against the AD's next-due value once the trip closed out. The compliance point had been crossed by roughly eight flight hours somewhere in the back half of that itinerary, and no one knew it.

The discovery came the morning the principal wanted to launch. A pre-departure status check flagged the AD as past due. With no tolerance to invoke and no AMOC on file, there was no legal dispatch and no quick fix. The inspection the AD requires is not a thirty-minute task; it meant opening structure for access, performing the inspection, and obtaining the return-to-service (RTS) sign-off before the aircraft could fly again. The same-day trip was scrubbed and chartered out, and the department then spent days documenting how an aircraft had flown eight hours in an unairworthy condition without anyone catching it in real time. Nothing had failed mechanically. The structure was almost certainly fine. The failure was purely one of reconciliation: a next-due number that never got updated against actual times after the last trip, and no system forcing the comparison before the next departure.

What an Audit-Ready AD Entry Actually Shows

The defense is documentation discipline, because a recurring-AD record is not only proof you did the work. It is proof you know precisely when the next obligation falls and against which revision. A complete entry shows three things without anyone having to reconstruct them from scattered sign-offs:

  • Method of compliance, citing the specific AD paragraph, service bulletin, or procedure used, so an auditor can confirm you did what the directive required rather than something adjacent.

  • AD number and revision, because directives get amended and superseded, and compliance against a stale revision is not compliance against the one in force.

  • The next-due value, stated in both flight hours and calendar terms wherever the AD uses both, so the reset point is explicit and impossible to overfly by accident.

When those three elements are captured cleanly on every recurring AD across the fleet, the next-due value becomes the number every pre-departure check measures against, and the eight-hour overfly stops being possible. When they live in loose logbook entries and a tracking spreadsheet that only updates when someone remembers, the wall is always out there somewhere in the dark. Getting compliance status into one place where the method, the revision, and the next-due are queryable together is the difference between catching an AD the week before it comes due and finding it the morning of a scrubbed trip. The directive gives you no grace. The records have to carry that load instead.

Your fleet's records at your fingertips.

Sign up, print a label, and search your first tail within days. Free.

Get Started Free