In brief
AD tracking software must control three different decisions: whether an AD applies to the exact product, how compliance was accomplished, and whether another action is due. Automation can accelerate research and calculation, but accountable review and source evidence must remain explicit.
Airworthiness Directive tracking is not a list of document numbers with green checkmarks. A defensible system must prove why each directive does or does not apply, what action was taken, and whether any recurring requirement is still controlled.
The FAA describes ADs as legally enforceable rules issued under 14 CFR part 39 to correct unsafe conditions in aircraft, engines, propellers, and appliances. The status therefore needs accountable technical review, current source data, and retrievable maintenance evidence.
The three decisions in AD tracking
| Decision | Question | Required evidence |
|---|---|---|
| Applicability | Does this AD apply to this exact product and configuration? | Make, model, serial, part, modification, effectivity, prior action |
| Compliance | What approved action satisfied the requirement? | Method, maintenance entry, work package, incorporated service information |
| Recurrence | Is another action due, and when? | Last accomplishment, interval, utilization, calendar, terminating action |
A system that automates only the next-due date leaves the hardest applicability and evidence questions unresolved.
Current source and revision control
Software should ingest or reference current AD source material from authoritative systems, including the FAA Dynamic Regulatory System. It must preserve:
- AD number and amendment.
- Effective date.
- Product and model applicability.
- Revision or correction history.
- Superseded and superseding relationships.
- Incorporated material and service information.
- Compliance times and thresholds.
- Alternative method of compliance references.
Do not overwrite an older decision when an AD changes. Retain the status history, reviewer, source version, and reason for the new conclusion.
Applicability is configuration-aware
Model and serial range can narrow the candidate set, but applicability may also depend on:
- Installed engine, propeller, appliance, or component.
- Part and serial number.
- Prior modification or repair.
- Software or hardware configuration.
- Service bulletin embodiment.
- Manufacturing or installation date.
- Operating environment or event.
- Whether a terminating action was previously accomplished.
The software needs a reliable aircraft and component configuration baseline. If the baseline is incomplete, “not applicable” may simply mean the system lacks the data needed to decide.
Compliance-method control
For an applicable AD, capture:
- Exact paragraph or requirement.
- Method of compliance.
- Incorporated service document and revision.
- Date and aircraft or component utilization.
- Maintenance entry and approving person.
- Work order, task card, inspection result, or parts evidence.
- Repair or disposition of findings.
- Terminating-action status.
- Any AMOC and its scope.
Avoid free-text entries such as “complied with” without the source necessary to understand what was actually performed.
Recurring AD calculation
Recurring actions can depend on:
- Calendar time.
- Flight hours.
- Cycles, landings, starts, or another utilization counter.
- Time since an event or installation.
- Repetitive inspection findings.
- Grace, credit, or threshold provisions.
- Multiple intervals within one AD.
The calculation engine should show its work: last event, interval, rule, input utilization, result, and evidence. Users should be able to see which input change moved a due date.
AMOC and exception handling
An Alternative Method of Compliance is not a general waiver. The system should record:
- Approval document.
- Applicable AD and paragraphs.
- Affected products or serial numbers.
- Conditions and limitations.
- Approval authority and date.
- Required follow-up.
Exceptions should enter a controlled queue with ownership and due dates. A missing work package should not silently convert into a completed status.
Fleet workflow and review
For a fleet, use role-based workflow:
- System identifies a candidate AD.
- Qualified reviewer evaluates applicability.
- Reviewer records reason and source.
- Applicable action enters planning.
- Maintenance evidence is received.
- A second review confirms compliance and next due.
- Exceptions remain open until evidence supports closure.
- Management sees fleet exposure and aging.
Measure overdue reviews separately from overdue maintenance. Both matter, but they represent different control failures.
Integration requirements
AD tracking should connect with:
- Aircraft and component configuration.
- Flight-hour and cycle utilization.
- Maintenance planning and work orders.
- Digital aircraft records.
- Parts and component history.
- Service bulletin tracking.
- Reliability and defect systems.
- Fleet dashboards and notifications.
An API that imports utilization but cannot export the source-linked status may still create a data trap.
Vendor demonstration checklist
Ask the vendor to demonstrate:
- A serial-specific applicability decision.
- A component AD based on installed part number.
- A superseding AD.
- A recurring AD with multiple intervals.
- A terminating action.
- An AMOC with limited scope.
- A missing or conflicting maintenance entry.
- Reviewer history and audit trail.
- Source document retrieval.
- Fleet-wide exposure report.
- Data export and migration.
Use your own difficult examples. A polished demo on a simple one-time AD does not prove the system can handle your fleet.
Sources and further reading
Common questions
Frequently asked questions
What does Airworthiness Directive tracking software do?
It helps identify potentially applicable ADs, record applicability decisions, document methods of compliance, calculate recurring next-due actions, manage revisions and supersedure, and link each status to maintenance evidence.
Can software determine AD applicability automatically?
Software can narrow candidates using make, model, serial number, part, and configuration data. Final applicability may depend on installed equipment, modification state, prior actions, or AD-specific conditions requiring qualified review.
Are Airworthiness Directives mandatory?
FAA Airworthiness Directives are legally enforceable rules issued under 14 CFR part 39. Owners and operators are responsible for compliance with applicable AD requirements.
What records should support an AD status?
Support should identify the AD and revision, applicability decision, compliance method, date and utilization at accomplishment, maintenance entry or work package, recurring next due, and any approved AMOC.
Keep researching
Related aircraft guides
Run maintenance from connected evidence
Know what is due—and open the record that proves it.
Radar connects maintenance status, component history, compliance work, and source records across every tail in the fleet.
