Operator certificate transfer
Maintenance program records for an operator AOC transfer
This review establishes whether the maintenance program records for an aircraft will bridge onto a new operator's program at a certificate transfer. It is run before handover, for the transferring party, so the maintenance program status is defensible before the receiving side maps it to its own tasks. The work checks approved program revisions, task escalations, and the bridging analysis against the source documents each task derives from. You get a program evidence map, a gap list of tasks whose next-due basis will not survive the bridge, and a document request set for the revisions and escalation approvals the receiving operator needs.
When this review is needed
- An aircraft is moving to a new operator certificate and the receiving side will map its task status onto a different program.
- Tasks were escalated under the sending program and those escalations have to be justified before the bridge.
- The two operators derive intervals from different program bases and the next-due figures will not translate one to one.
- The bridging analysis has to be built before the receiving side will set the aircraft's entry status.
The problem
A maintenance program status is meaningful only against the program that produced it, and a transfer moves the aircraft to a program built on different assumptions. Task intervals, escalations, and sampling that were approved under the sending program do not carry over intact, and the next-due dates that looked settled shift the moment they are re-based. Without a bridging analysis that ties each task back to its source document, the receiving side cannot tell an accepted escalation from an unsupported one.
What gets reviewed
- Approved program revisions confirmed as the basis for the current task status
- Task escalations matched to the analysis and approval that authorized them
- The bridging analysis reconciling sending-program tasks with the receiving program
- Next-due status re-based where the two programs derive intervals differently
- Source-document references confirmed for tasks whose basis the receiving side will check
- The program status ordered so the receiving operator can build entry status from it
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
- Task status derives from an approved program revision rather than an informal working list
- Each escalation is backed by the analysis and approval that authorized the longer interval
- The bridging analysis accounts for every task the receiving program requires at entry
- Next-due figures re-based between programs reconcile against utilization and last accomplishment
- Tasks trace to their source documents where the receiving side will verify the basis
Evidence normally required
- The approved maintenance program and its revision history
- The current task status and next-due list for the aircraft
- Escalation analyses and the approvals granting the extended intervals
- The receiving operator's program and its entry requirements, where available
- Source documents underlying the tasks, from the type program to modification-driven items
Common discrepancies
- A task status built on a working list rather than the approved program revision
- An escalation carried forward with no analysis or approval to justify the interval
- A next-due figure that does not re-base cleanly onto the receiving program
- A task with no traceable source document to support its basis at the bridge
What is at stake
A task whose next-due basis will not bridge lands as a dispute at exactly the point the receiving operator is setting entry status. Escalations that cannot be justified default to the conservative interval, which can pull checks forward and force work the transfer did not budget for. If the bridging analysis is thin, the whole entry status is negotiated line by line under time pressure instead of read from a settled map.
How the work runs
Fix the program basis
Confirm the approved revision the current task status derives from and set it as the bridge starting point.
Justify the escalations
Match each extended interval to the analysis and approval that authorized it.
Build the bridging analysis
Reconcile sending-program tasks with the receiving program and re-base next-due figures where they differ.
Deliver map, gaps, and requests
Hand over the program evidence map, the ranked gap list, and requests for the missing revisions and approvals.
What the buyer receives
- A program evidence map tying task status to its revision and source documents
- A gap list of tasks whose next-due basis will not survive the bridge, ranked by schedule effect
- A document request set for the revisions and escalation approvals still needed
Who uses the output
- Asset managers judging the schedule exposure hidden in the program bridge
- Receiving-operator continuing-airworthiness staff setting the aircraft's entry status
- Records leads assembling program revisions and escalation approvals before handover
How the work fits into the transaction or program
This review sits directly ahead of the receiving operator building entry status. It settles the escalations and next-due bases that would otherwise be argued at induction, and it hands the receiving side a bridging analysis it can build its own program entry from rather than rebuild from scratch.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
A transfer between FAA and EASA operators can move the aircraft onto a program with a different source basis and a different escalation practice. The review reconciles the sending-program tasks to the framework the receiving operator answers to, so intervals that were approved under one regime are re-based rather than assumed to carry over.
Regulatory limits
The review reports what the program records and their approvals support. It does not approve a maintenance program or any escalation, set the receiving operator's intervals, and does not replace the receiving operator's or authority's approval of the program the aircraft enters.
What this review does not cover
- Approving a maintenance program or any task escalation
- Setting intervals for the receiving operator's program
- Performing any maintenance task or check
Specific to this review
- A program status only means something against the program that produced it, so a transfer re-bases every next-due figure the moment the aircraft moves.
- Escalations that cannot be justified default to the conservative interval, which pulls checks forward and adds unplanned work at entry.
- Without a bridging analysis, the receiving side cannot distinguish an approved escalation from an unsupported one, and the whole entry status turns into a negotiation.
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
Both operators run approved programs. Why can't the task status just move across?
The two programs are built on different intervals, escalations, and sources, so a next-due figure approved under one does not translate directly to the other. The review re-bases each task and justifies the escalations, so the receiving operator can set entry status from a bridge that holds rather than argue it line by line.
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.