Cross-border engine transfer
Repair-approval review for a cross-border engine transfer
This review confirms that the repairs on an engine carry approved data a receiving authority will recognize before the engine crosses a border. It is run by or for the transferring party ahead of shipment. It covers damage reports, repair dispositions, the approved data each repair relied on, and the return-to-service entries that closed them, read against what the receiving side accepts. You receive a repair map with the approval basis for each entry, a list of repairs whose data will not carry across, and a request set for the substantiation needed to close them.
When this review is needed
- An engine with a repair history is transferring to an authority with different approval expectations.
- A repair was accomplished under data the receiving side may not recognize as approved.
- The substantiation behind a disposition is referenced but not present in the engine file.
- A structural repair on a case or frame drives the receiving operator's acceptance of the build.
The problem
A repair is only as portable as the data that approved it. A shop that dispositioned damage under an approval valid on one register leaves a return-to-service entry that reads clean at home. The receiving authority reads the same repair and asks what data approved it, and if that data is a source the receiving side does not recognize, or was never filed against the repair, the entry that looked closed is suddenly a question the engine cannot ship past.
What gets reviewed
- Damage reports and dispositions for each recorded repair
- Approved data behind each repair read against the receiving authority's acceptance
- Return-to-service entries tied to the repair and its approval basis
- Structural repairs on cases and frames traced to substantiation the receiving side recognizes
- Repairs whose approval basis will not carry across flagged for re-substantiation
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 repair references the approved data it was accomplished under
- The approval basis is one the receiving authority recognizes for the part
- Return-to-service entries tie to the repair and the data that closed it
- Structural repairs carry substantiation, rather than a disposition note alone
- The repair map reconciles with the engine's current configuration and part standing
Evidence normally required
- The engine repair and alteration records
- Damage reports and repair dispositions
- Approved data or substantiation referenced by each repair
- The receiving authority's expectation for repair approval on the type
Common discrepancies
- A repair accomplished under data the receiving authority does not recognize
- A disposition that references substantiation missing from the engine file
- A structural repair closed on a note with no approved data attached
- A return-to-service entry with no repair record explaining what was done
What is at stake
A repair the receiving authority will not accept can force the engine to be re-inspected, the repair re-substantiated, or in the worst case the affected part replaced. Substantiation held by the repairing shop and never filed becomes hard to recover once the engine has moved and the transaction has closed, which turns a paperwork gap into a physical one.
How the work runs
Assemble the repair map
List each repair with its damage report, disposition, and return-to-service entry.
Read the approval basis
Check the data behind each repair against what the receiving authority recognizes.
Test the structural repairs
Confirm case and frame repairs carry substantiation the receiving side will accept.
Flag and request
List repairs whose basis will not carry across and request the substantiation to close them.
What the buyer receives
- A repair map showing the approval basis behind each entry
- A list of repairs whose data will not carry to the receiving authority
- A document request set for the substantiation needed to close each item
Who uses the output
- Engineering deciding how to treat a repair the receiving side will not accept
- Records teams recovering substantiation before the engine ships
- Asset managers weighing whether re-substantiation affects the transfer economics
How the work fits into the transaction or program
This review runs before transfer, so a repair with a weak basis is found while the repairing shop is still reachable. Its findings drive the substantiation recovery and, where data cannot be recovered, the engineering call on whether the repair holds for the receiving register.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
What counts as approved repair data differs across FAA, EASA, and TCCA, and a repair accepted on one register can require its own acceptance on another. The review flags repairs whose approval basis is jurisdiction-specific so the receiving side's expectation is known before the engine moves.
Regulatory limits
This review reads repair records against the receiving authority's acceptance of approved data. It does not approve a repair, develop repair data, or make an airworthiness determination on any repaired part. Acceptance of a repair rests with the receiving authority.
What this review does not cover
- Developing or approving repair or alteration data
- Physical inspection or re-inspection of any repair
- Any airworthiness determination on a repaired part
Specific to this review
- A return-to-service entry reads clean at home but proves nothing to the receiving side without the approved data behind it.
- Structural repairs on cases and frames draw the closest receiving-side scrutiny, because their substantiation is what re-establishes the build.
- Substantiation held only by the repairing shop is the item most likely to become unrecoverable once the engine has transferred.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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 repairs all have return-to-service entries. Isn't that sufficient?
A return-to-service entry records that the repair closed; it does not prove the data that approved it will be accepted elsewhere. The receiving authority reads the approval basis, so the review checks that each repair's data carries to the receiving register 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.