Cross-border engine transfer
Maintenance-program records review for engine transfer
This review checks that an engine's maintenance-program records will map onto the receiving operator's program before the engine transfers across a border. It is run by or for the transferring party ahead of shipment. It covers approved program revisions, task escalations, the bridging analysis to the receiving program, and the source references behind the intervals the engine has been run to. You receive a program status mapped to the receiving side, a list of intervals that will not bridge as written, and a request set for the escalation and bridging sources to recover.
When this review is needed
- An engine maintained under one program is transferring to an operator that runs a different one.
- Shop-visit intervals were escalated and the basis has to travel with the engine.
- A bridging analysis to the receiving program exists but its source data is not in the file.
- The next shop visit is priced against intervals the receiving operator may not accept.
The problem
An engine has been maintained to a program whose intervals and escalations made sense to the operator that set them. The receiving operator runs its own program, so the engine's task history has to bridge to those intervals rather than carry across unchanged. An escalated shop-visit interval with no analysis attached, or a bridge that points to source data the file never included, becomes a question the receiving side resolves conservatively, which pulls the next shop visit forward.
What gets reviewed
- Approved program revisions with the revision governing at transfer identified
- Task and shop-visit escalations paired with their authorizing analysis
- Bridging analysis from the engine's program to the receiving operator's program
- Source references behind the intervals the engine has been run to
- Program status at transfer reconciled to the tracking output
- Intervals that will not bridge as written flagged for the receiving side
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 escalated interval traces to the analysis and approval that granted it
- The bridging analysis maps the engine's tasks onto the receiving program's intervals
- Bridging references point to documents present in the file
- Program status agrees with the tracking system it was drawn from
- Intervals the receiving operator is unlikely to accept are identified before transfer
Evidence normally required
- The engine's maintenance program and revision history
- Escalation analyses and their approvals
- The bridging study to the receiving operator's program
- Current program status from the tracking system
Common discrepancies
- An escalated shop-visit interval with no analysis in the file
- A bridging study that cites source data missing from the package
- Program status run against a superseded program revision
- An interval accepted at origin that the receiving program does not support
What is at stake
An interval the receiving operator will not accept resets to a shorter default, which can advance an expensive shop visit and reprice the engine after the transfer was agreed. If the escalation basis is unrecoverable, the receiving side has no choice but the conservative interval, and the cost of that reset lands on whoever holds the engine next.
How the work runs
Fix the governing revision
Identify the program revision at transfer and confirm status was run against it.
Trace the escalations
Pair each escalated interval with the analysis and approval behind it.
Bridge to the receiving program
Map the engine's tasks onto the receiving operator's intervals and flag the gaps.
Request the sources
List intervals that will not bridge and the escalation and bridging documents to recover.
What the buyer receives
- A program status mapped onto the receiving operator's program
- A list of intervals that will not bridge as written
- A document request set for the escalation and bridging sources to recover
Who uses the output
- Continuing-airworthiness leads bridging the engine onto the receiving program
- Records teams recovering escalation and bridging sources before shipment
- Asset managers weighing whether a reset interval advances the next shop visit
How the work fits into the transaction or program
This review runs before the engine ships, so a weak interval or bridge is found while the origin holder still has the source. Its findings drive the recovery that must finish before transfer, and the mapped status becomes the basis the receiving operator plans the next shop visit against.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA, EASA, and TCCA frame program acceptance differently, and a receiving operator on another register may not accept an escalation its authority never approved. The review notes where an interval or escalation basis will need additional support before the receiving program will run to it.
Regulatory limits
This review maps program records onto the receiving program. It does not approve the maintenance program, set intervals on an authority's behalf, or make an airworthiness determination. Acceptance of the program rests with the receiving operator and its authority.
What this review does not cover
- Authoring or approving the maintenance program
- Setting or approving shop-visit intervals
- Any airworthiness determination on the engine
Specific to this review
- An engine's intervals do not carry across unchanged; the task history bridges to the receiving program, and the escalations are where the bridge strains.
- An unrecoverable escalation basis forces a conservative interval, which can pull an expensive shop visit forward after the transfer was priced.
- A bridging study is only as usable as the source data it cites, and that data is the item most often absent from the transfer file.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Can the receiving operator just keep our intervals?
Only where its program and authority support them. Escalated intervals in particular have to bridge to the receiving program, and any the receiving side will not accept reset to a shorter default. The review finds those before transfer so the reset does not surprise the next shop-visit plan.
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.