Cross-border engine transfer
AD-status review for a cross-border engine transfer
This review verifies that an engine's AD compliance status will satisfy the receiving authority before the engine transfers across a border. It is run by or for the transferring party ahead of shipment. It covers applicability for the receiving register, accomplishment records, and the method-of-compliance evidence behind each closed AD, then checks that status against the mandatory set the receiving authority applies. You receive an AD-by-AD acceptance read, a list of items the receiving side will treat as open, and a request set for the accomplishment evidence that must be recovered.
When this review is needed
- An engine is moving to a register whose AD set differs from the one it was maintained under.
- An AD was closed by a method the receiving authority may not treat as compliant.
- Accomplishment evidence behind a closed AD is not in the engine file.
- The receiving authority mandates an AD the current register never made applicable to this engine.
The problem
An AD status list reads as compliant against the authority that issued it. Cross a border and the receiving authority applies its own mandatory set, which may include directives the origin register never called out, or may treat a method of compliance the origin accepted as insufficient. A status line marked closed against one authority is not closed against another until the accomplishment evidence supports the receiving side's expectation, and that evidence is often what the file lacks.
What gets reviewed
- Applicability of the receiving authority's AD set to this engine build
- Accomplishment records for each AD the status list marks closed
- Method-of-compliance evidence read against the receiving authority's expectation
- Directives mandatory on the receiving register but not on the origin flagged
- AD status reconciled to the engine's actual configuration and part standing
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 AD carries accomplishment evidence behind it, rather than a status-list entry alone
- The method of compliance recorded is one the receiving authority accepts
- AD applicability reflects the engine's build standard, not a generic type list
- Directives mandatory on the receiving register but absent from the origin status are identified
- AD status agrees with the configuration and part records for the engine
Evidence normally required
- The engine AD status list from the origin register
- Accomplishment records and method-of-compliance evidence
- The receiving authority's applicable AD set for the type
- Configuration and part records establishing the engine build standard
Common discrepancies
- An AD closed on the status list with no accomplishment record behind it
- A method of compliance the origin accepted but the receiving authority does not
- A directive mandatory on the receiving register that the origin never applied
- AD applicability drawn from a type list that does not match the engine build
What is at stake
An AD the receiving authority treats as open holds the engine until it is accomplished or its compliance is proven. If the method of compliance is the issue, the engine may need rework that was never planned, and if the accomplishment record is simply missing, the transferring party is chasing a shop for evidence while the receiving fleet waits for the engine.
How the work runs
Rebuild applicability
Establish the receiving authority's applicable AD set against the actual engine build.
Test each closure
Confirm accomplishment evidence and method of compliance for every AD marked closed.
Compare mandatory sets
Flag directives mandatory on the receiving register but absent from the origin status.
Request the evidence
List open items and the accomplishment records needed to close them for the receiving side.
What the buyer receives
- An AD-by-AD read of what the receiving authority will accept as closed
- A list of directives the receiving side will treat as open
- A document request set for the missing accomplishment and compliance evidence
Who uses the output
- Continuing-airworthiness teams clearing the engine's AD position for the new register
- Records teams recovering accomplishment evidence before the engine ships
- Asset managers weighing whether receiving-side rework affects the transfer plan
How the work fits into the transaction or program
This review runs before the engine transfers, so an AD gap is found while the origin holder still has access to the shops and records that can close it. Its open-item list drives the accomplishment work and evidence recovery that must clear before the receiving authority will treat the engine as compliant.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA, EASA, and TCCA maintain their own mandatory AD sets, and an engine compliant on one register can carry open items on another. The review reads the origin status against the receiving authority's applicable set specifically, flagging both extra directives and methods of compliance that will not carry across.
Regulatory limits
This review reads AD status against the receiving authority's mandatory set. It does not accomplish an AD, grant compliance, or make an airworthiness determination on the engine. Whether an AD is satisfied on the receiving register rests with that authority and the accepting operator.
What this review does not cover
- Accomplishing any airworthiness directive
- Physical inspection or shop work on the engine
- Any airworthiness determination on the engine's AD position
Specific to this review
- A closed status line proves nothing to the receiving authority without the accomplishment record behind it.
- The receiving register can mandate directives the origin never applied, so a clean origin status is not a complete one.
- A method of compliance accepted at origin can be rejected at the receiving side, turning a closed AD back into rework.
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.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
The engine's AD status is clean at origin. Why would the receiving authority disagree?
Each authority applies its own mandatory set. The receiving register may mandate a directive the origin never applied, or may not accept the method used to close one. The review reads the status against the receiving side's set so those differences surface before the engine ships.
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.