Operator transition
Operator-transfer records validation
Operator-transfer records validation confirms that an aircraft's records support a move from one operator's maintenance program onto another. It is run when an asset changes operator while ownership may stay the same, and the receiving operator has to take the aircraft onto its own program and authority. It checks that AD status, repetitive task intervals, and release evidence translate cleanly from the outgoing program to the incoming one. You receive a bridging gap list, a status set restated against the new program, and the items the receiving operator needs closed before acceptance.
When this review is needed
- An aircraft is moving to a new operator and has to be taken onto a different maintenance program.
- The receiving operator's program uses different task intervals than the outgoing one.
- An owner is changing the operator under a management arrangement and needs continuity confirmed.
- The incoming operator's continuing-airworthiness function needs an independent read before bridging.
The problem
Two operators rarely run identical programs. Repetitive inspections fall on different intervals, AD compliance methods may differ, and the outgoing program's status list is written in its own terms. When the receiving operator bridges the aircraft onto its program, mismatches surface as tasks that look overdue, intervals that do not reconcile, or compliance that was satisfied under a method the new program does not recognize. Sorting that out under entry-into-service pressure is slow and disruptive.
What gets reviewed
- The outgoing and incoming maintenance programs and where their requirements diverge
- Airworthiness Directive status and the methods of compliance used to close each directive
- Inspection and repetitive task status mapped from old intervals to new ones
- Modification and service-bulletin status relevant to the receiving program
- Authorized release certificates for components the new operator will rely on
- Time and cycle baselines the bridging will be built from
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 AD is closed by a method the receiving program will accept, or the difference is flagged
- Each repetitive task maps to the incoming intervals with the next-due basis shown
- Component releases are appropriate to the authority the receiving operator holds
- Time and cycle baselines reconcile across both operators' records
- Modification status reflects what the new program assumes is installed
- Status carried from the outgoing tracking system is checked against source documents
Evidence normally required
Common discrepancies
- Repetitive intervals that do not line up between the two programs
- An AD closed under a method the receiving program does not recognize
- Modification status that the new program assumes but the records do not confirm
- Component releases issued under an authority the new operator cannot use directly
- Time and cycle baselines that disagree between the two operators' systems
- Tasks shown complete on the old tracking system with no supporting source entry
What is at stake
An aircraft taken onto a new program with unreconciled status can ground on a task the receiving operator believes is due but the outgoing operator considered complete. Resolving it after the transfer means correspondence between two organizations that have already moved on, and it delays the aircraft earning revenue.
How the work runs
Compare the programs
Identify where the outgoing and incoming maintenance programs diverge on intervals, methods, and assumed configuration.
Map status across
Restate AD, task, and modification status in the receiving program's terms with the next-due basis for each item.
Reconcile baselines
Confirm the time and cycle baselines the bridging is built from agree across both operators' records.
List for closure
Produce the gap and closure list the receiving operator needs cleared before it accepts the aircraft.
What the buyer receives
- A bridging gap list mapped to the receiving operator's program
- A status set restated in the incoming program's terms with next-due bases
- A closure list for the items needed before the receiving operator accepts the aircraft
Who uses the output
- The receiving operator's continuing-airworthiness team building the bridge
- The owner or manager coordinating the transfer between operators
- Records teams reconciling the two programs before entry into service
How the work fits into the transaction or program
The validation runs alongside the receiving operator's bridging work so mismatches are found before the aircraft enters service rather than during it. It feeds the bridging analysis and the entry-into-service records package.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
When the new operator holds a different authority than the outgoing one, compliance methods and release forms that were accepted before are not automatically accepted now. The validation flags where the receiving authority's program will read the same history differently.
Regulatory limits
The validation checks that records support the program transition. It does not approve the maintenance program, perform the bridging on the operator's behalf, or make an airworthiness determination, all of which remain with the operator and its authority.
What this review does not cover
- Building or approving the receiving operator's maintenance program
- Physical inspection or return-to-service tasks
- Any airworthiness determination or program approval
Specific to this review
- The decisive risk in an operator transfer is interval mismatch: a task complete under one program can read as overdue under another with different timing.
- AD compliance is closed by a method, and a method accepted by the outgoing program is not guaranteed acceptable to the incoming one.
- Bridging works from time and cycle baselines, so a baseline disagreement between the two operators propagates into every next-due calculation.
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). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Frequently asked questions
Is this the same as the receiving operator's bridging?
It supports it. Bridging is the receiving operator's task of placing the aircraft on its program. This validation is the independent records check that the history actually supports that bridge, so mismatches are caught before service.
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.