Engine AD position
Airworthiness Directive status review for the engine-module records file
This review verifies each line of an engine-module AD status list against the shop reports, work scopes, and accomplishment records that are supposed to stand behind it. It resolves applicability down to module and part level, checks supersedure, and separates terminating action from repetitive compliance. Engine records leads run it before a records transfer or after a shop visit, while the shop's paperwork is still easy to obtain. What it returns is a per-AD evidence map for the engine trace support file, with each unsupported closure named and located.
When this review is needed
- The engine is transferring and the receiving party will audit the AD list against source records.
- A shop visit just closed and the status list must absorb what the shop actually did.
- Modules were swapped at the last build and part-level applicability has not been re-run since.
- A superseded AD still shows on the list and nobody can say which revision the evidence answers.
The problem
Engine AD lists are maintained at the engine level while compliance actually happens at module and part level. Every shop visit that mixes modules or introduces serviceable parts changes which serial numbers the list is really speaking for, and the accomplishment evidence scatters across shop reports, subcontractor releases, and test-cell paperwork that was never filed against the AD it satisfied.
What gets reviewed
- Every AD on the list resolved for applicability against the modules and part serials actually installed
- Closure evidence located for each complied-with line: shop report section, SB accomplishment, or dedicated compliance record
- Supersedure chains checked so each line answers the current revision
- Repetitive requirements confirmed as tracked with method, interval, and last-done point
- Terminating actions verified against the specific configuration that terminates them
- Parts introduced at builds screened for AD history that arrived with them
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Each closed line cites evidence that exists, is legible, and describes the required action
- No line answers a superseded revision while the current revision adds requirements
- Method of compliance on the list matches the method the evidence shows
- Part-level ADs are evaluated against installed serials, and the evaluation postdates the last build
- Repetitive items show a next-due point derived from documented accomplishment, and none is marked closed
Evidence normally required
- The current AD status list at engine and module level
- Shop-visit reports and work scopes for the visits the list relies on
- Module build sheets and installation history establishing what is installed now
- SB accomplishment records where SBs serve as the compliance method
- Test-cell and subcontractor documentation referenced by the shop reports
Common discrepancies
- A complied-with line whose only support is its own row in a previous status list
- An AD evaluated at engine level while the affected part number sits in a swapped-in module
- Compliance recorded against an SB revision that the shop report shows was only partially embodied
- A repetitive inspection shown as terminated by a modification the build sheets do not confirm
What is at stake
An AD line that cannot be evidenced holds up the whole engine at transfer, because AD status is the first thing a receiving reviewer tests and the least negotiable. If a closure was recorded against a part that has since rotated out, or a repetitive requirement was marked terminated, the correction can require reopening shop records from organizations with no remaining duty to answer.
How the work runs
Rebuild applicability
Establish installed modules and part serials from build sheets and installation history, and resolve each AD against that configuration.
Pull the evidence
Locate the accomplishment record behind every closed line in shop reports, SB records, and compliance documents.
Test the hard cases
Work supersedure chains, partial embodiments, terminating actions, and repetitive tracking where lists most often fail.
Map and report
Issue the per-AD evidence map, the unsupported-closures list, and the corrected applicability baseline.
What the buyer receives
- A per-AD evidence map linking every line to its source document and page
- An unsupported-closures list with the responsible organization and recovery route for each
- A corrected applicability baseline reflecting the modules and parts actually installed
Who uses the output
- Engine records leads assembling the trace support file for a transfer
- Receiving reviewers at lessors, operators, or shops who audit the list
- Program managers pricing the risk of unresolved lines before a deal date
How the work fits into the transaction or program
AD substantiation anchors the engine-module records source review, since LLP trace and release-document findings frequently resolve or worsen an AD question. Its evidence map becomes the AD chapter of the engine trace support file, and its unsupported-closures list usually drives the first round of document requests to prior shops.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
For FAA purposes, 14 CFR 39 makes each AD binding as written, and 91.417 requires records of method, date, and next action. EASA operators track ADs within continuing-airworthiness management under Regulation 1321/2014, and engines that have served under both regimes may hold compliance records addressed to either authority's directives, which do not always map one to one for the same unsafe condition.
Regulatory limits
The review establishes what the records demonstrate. It does not determine airworthiness, does not approve alternative methods of compliance, and does not decide applicability questions that belong to the design-approval holder or the authority; unresolved applicability is reported as unresolved.
What this review does not cover
- Physical inspection of modules or parts
- Performing or arranging AD accomplishment work
- AMOC applications or other correspondence with the authority
Specific to this review
- A status list inherits credibility from nothing; a line copied forward across three transfers has exactly the evidentiary weight of the original document, which may never have existed.
- Part-level applicability resets at every module build that introduces outside serials, so an AD evaluation is only as current as the newest build sheet.
- Marking a repetitive AD closed is one of the most common list defects and one of the most alarming to a receiving reviewer, because it suggests the tracking method, and everything downstream of it, is wrong.
- When an SB is the compliance method, the shop report must show the SB's full work scope; partial embodiment recorded as compliance is a defect that survives until someone reads the report against the bulletin.
- Supersedure quietly invalidates clean evidence: a perfectly documented closure of the prior revision can still leave the current revision's added requirements open.
Sources
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The list came from a reputable operator's system. Why would it need substantiation?
System quality governs how the list was maintained, and the weak point is what entered it: closures keyed from summaries, applicability run before the last build, evidence filed under the shop visit rather than the AD. Substantiation checks the join between the list and its sources, which no tracking system checks for itself.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.