Operator transition
Operator AOC transfer records review for fleet onboarding
An operator AOC transfer records review checks an aircraft's records against the requirements of the receiving operator's air operator certificate before the aircraft is placed on the new AOC. It is built for lessors, airlines, and acquisition teams moving an aircraft onto a different operator's certificate. It covers the receiving operator's maintenance program, MEL and configuration deviation list, approved data scope, and the records its quality system needs to take the aircraft. You receive an onboarding-readiness view, a gap list against the receiving AOC, and the records each open item needs before the transfer.
When this review is needed
- An aircraft is being placed on a different operator's AOC and its records must satisfy that operator's approvals before induction.
- The receiving operator's maintenance program differs from the program the aircraft has been managed under.
- The aircraft's MEL and configuration baseline must align with the receiving operator's MEL and approved configuration.
- Approved data the aircraft was maintained against needs confirming as acceptable within the receiving operator's approval scope.
The problem
Placing an aircraft on a new operator's AOC means its records must satisfy a certificate that is not the one it was operated under. The receiving operator's maintenance program, its MEL, its approved-data scope, and its quality system each define what the records have to show, and the outgoing operator built the records against a different set of approvals. A task tracked one way under the prior program, a deferral carried against a different MEL, or a repair approved under data the receiving operator cannot use, all surface at induction unless they are checked against the new AOC first.
What gets reviewed
- The receiving operator's approved maintenance program and how it differs from the prior program
- MEL and configuration deviation list status against the receiving operator's MEL
- Approved-data and modification records against the receiving operator's approval scope
- Open deferrals, carried-forward items, and their mapping to the receiving program
- The records the receiving operator's quality system requires to accept the aircraft
- Continuing-airworthiness handover from the outgoing arrangement to the receiving one
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 task and inspection maps to the receiving operator's maintenance program without an orphaned item
- Open deferrals reconcile against the receiving operator's MEL and configuration deviation list
- Repairs and modifications rest on data within the receiving operator's approval scope
- Carried-forward items transfer with a defined due point under the receiving program
- The configuration baseline matches the receiving operator's approved configuration for the type
- The records package meets what the receiving operator's quality system requires to accept the aircraft
Evidence normally required
- The receiving operator's approved maintenance program and MEL
- The aircraft's current maintenance program status and task history
- Open deferral and carried-forward item list with supporting evidence
- Repair and modification records with the approved data they rest on
- The receiving operator's quality-system acceptance requirements
Common discrepancies
- A task tracked under the prior program with no clear equivalent in the receiving program
- A deferral carried against a different MEL than the receiving operator's
- A repair approved under data the receiving operator cannot use within its approval scope
- A carried-forward item that arrives without a due point the receiving program can schedule
- A configuration the receiving operator's approval does not cover without an additional approval
What is at stake
An aircraft whose records do not satisfy the receiving AOC cannot enter service on it, and it sits while the gaps are closed against the new operator's approvals. A deferral that does not map to the receiving MEL or a repair approved under data the new operator cannot accept can force re-work or re-approval at induction, which is slower and more expensive than reconciling the records before the aircraft arrives.
How the work runs
Read the receiving AOC
Establish the receiving operator's maintenance program, MEL, and approved-data scope that the records must satisfy.
Map the records across
Reconcile the aircraft's tasks, deferrals, and approvals against the receiving operator's program and approvals.
Test the open items
Check each deferral, carried-forward item, and repair against the receiving MEL and approval scope.
Register the gaps
List each item the receiving AOC does not yet support and the record it needs before induction.
What the buyer receives
- An onboarding-readiness view against the receiving operator's AOC and approvals
- A gap list with the records each open item needs to satisfy the receiving AOC
- A mapping of the maintenance program and open items from the prior arrangement to the receiving one
Who uses the output
- Continuing-airworthiness teams aligning the aircraft with the receiving program before induction
- Quality staff confirming the records meet the receiving operator's acceptance requirements
- Fleet and asset teams confirming the aircraft can enter service on the new AOC on schedule
How the work fits into the transaction or program
The review precedes induction onto the new AOC so the records are reconciled to the receiving operator's approvals while the outgoing operator and its records remain reachable. It connects to the maintenance-program transition mapping, since the program differences drive most of the open items, and it feeds the induction package the receiving operator acts on.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
An AOC is issued under one authority, so an aircraft moving to an operator certified by a different authority inherits that authority's rules through the operator's approvals. A maintenance program acceptable under one authority is not automatically acceptable under another, and approved data the prior operator relied on may need a bridging assessment before the receiving operator can use it.
Regulatory limits
The review confirms whether the records satisfy the receiving operator's AOC requirements and where they fall short. It does not approve a maintenance program, accept the aircraft onto the AOC, make an airworthiness determination, or grant any approval the receiving operator or its authority must give.
What this review does not cover
- Approval or amendment of the receiving operator's maintenance program
- Acceptance of the aircraft onto the AOC or any return-to-service action
- Physical inspection or conformity survey of the aircraft
Specific to this review
- The records were built against the prior operator's certificate, so an item that was complete under one AOC can be incomplete under another without any change to the aircraft.
- A deferral is checked against the receiving operator's MEL, because a carried item valid under one MEL may not be permitted under the receiving one.
- Approved data is read against the receiving operator's approval scope, since a repair acceptable under the prior operator's approvals can need re-approval to be usable on the new AOC.
- Carried-forward items must arrive with a due point the receiving program can schedule, or they become orphaned tasks at induction.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Transport Canada. Canadian airworthiness, maintenance records (CAR 605/571), and Airworthiness Directive requirements (CAR 593).
Frequently asked questions
Why do complete records still fail when an aircraft changes operator?
Because the records were built against the prior operator's certificate. The receiving operator's program, MEL, and approval scope are different, so an item complete under one AOC can be incomplete under another even though the aircraft has not changed.
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.
Walk through your situation with an engineer who has done this work.