Operator certificate transfer
LLP traceability records for an operator AOC transfer
This review establishes whether life-limited part traceability will carry an aircraft onto a new operator's certificate. It is performed before handover, for the party moving the aircraft, so the LLP status sheet is unbroken before the receiving side follows each part back. The work walks every life-limited part from its current cycle count to birth through release certificates, shop reports, and cycle-accumulation records. You get an LLP evidence map, a gap list keyed to any break in the trace, and a document request set for the release paper and back-to-birth records that close the breaks.
When this review is needed
- An aircraft is moving to a new operator certificate and the receiving side will trace each LLP back to birth.
- A life-limited part changed hands at a shop visit and its interim cycle history was never consolidated onto the sheet.
- The transfer crosses authorities and the back-to-birth documentation was assembled to a different standard along the way.
- A module build reset the visible cycle count and the pre-build accumulation has to be reconciled.
The problem
Life-limited part trace is unforgiving because a single missing link can invalidate the entire history of a part. Cycles accumulate under one operator, the part moves at a shop visit, a disk is rebuilt into a different module, and each transfer leaves a chance for the count to detach from its source. The status sheet reads clean right up until the receiving operator asks for the release that connects two adjacent lines and finds nothing in between.
What gets reviewed
- Each life-limited part traced from current cycles to birth without a missing link
- Release certificates confirming cycle status at every change of custody
- Shop-visit reports reconciled with the cycles claimed on the status sheet
- Module and disk build records checked where a rebuild reset the visible count
- Cycle-accumulation history tied to the airframe or engine hours it was flown against
- Back-to-birth documentation assembled in the order the receiving side will follow 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
- Every life-limited part traces to birth with no gap between adjacent custody events
- Cycles on the status sheet reconcile with the release certificate at each shop visit
- Serial numbers on the sheet match the shop reports and installation records for the part
- Cycle counts after a module build account correctly for the pre-build accumulation
- Remaining life on the sheet derives from source records, not from the summary line
Evidence normally required
- The LLP status sheet for airframe and engine life-limited parts
- Release certificates issued at each shop visit and change of custody
- Shop-visit and module build reports showing cycle status at exit
- Cycle-accumulation history against airframe or engine utilization
- Contact points at the shops that last handled each traced part
Common discrepancies
- A gap between two custody events with no release to connect the cycle count across it
- A shop report whose exit cycles disagree with the figure carried on the status sheet
- A rebuilt module whose sheet does not account for pre-build cycle accumulation
- Remaining life stated from the summary with no source record to support it
What is at stake
A part whose trace breaks cannot be relied on for the cycles it claims to have left, and the receiving operator will not accept remaining life it cannot follow to birth. The conservative outcome is to treat unproven cycles as consumed, which can pull an expensive part to an earlier removal than its true life supports. On a transfer, that turns a records gap into an unplanned shop visit and a direct hit to the asset's value.
How the work runs
Walk each part to birth
Trace every life-limited part from its current count backward through each change of custody to birth.
Reconcile cycles at each event
Match the sheet against the release and shop report at every shop visit and module build.
Isolate the breaks
Mark each point where the trace stops and identify the release or record that would connect it.
Deliver map, gaps, and requests
Hand over the LLP evidence map, the ranked gap list, and requests to the shops that can supply the missing links.
What the buyer receives
- An LLP evidence map tracing each part to birth with its supporting releases
- A gap list keyed to each break in the trace and ranked by the part's remaining value
- A document request set for the releases and back-to-birth records that close the breaks
Who uses the output
- Asset managers pricing the exposure of any part whose trace is incomplete
- Receiving-operator continuing-airworthiness staff following each LLP to birth
- Records leads assembling back-to-birth evidence before the transfer date
How the work fits into the transaction or program
This review runs before the receiving operator begins its own back-to-birth trace. It closes the breaks that would otherwise force cycles to be written off, and it hands the receiving side an LLP position that reads cleanly from current count to birth without a stop in between.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
When the aircraft crosses between FAA and EASA operators, the back-to-birth file may combine documents assembled to different practices over the part's life. The review checks that each custody event is evidenced to the standard the receiving operator applies, so a trace that was acceptable elsewhere is not first questioned at handover.
Regulatory limits
The review reports what the traceability records support for each life-limited part. It does not certify remaining life, issue release documentation, adjust a cycle count, and does not replace the receiving operator's acceptance of the parts and their remaining life.
What this review does not cover
- Physical inspection or dimensional check of any life-limited part
- Issuing release certificates or back-to-birth statements
- Certifying remaining cycles on any part
Specific to this review
- A single missing custody link can invalidate a life-limited part's whole history, no matter how clean the surrounding lines look.
- When trace breaks, the conservative rule is to count unproven cycles as consumed, which can force an early and expensive removal.
- Module builds are a common break point because the visible cycle count resets while the pre-build accumulation has to be carried forward by paper.
Sources
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
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
One part is missing a release from an old shop visit. Does that really affect its remaining life?
It can. Without the release that carries the cycle count across that visit, the receiving operator cannot follow the part to birth and may treat the unproven cycles as used. The review finds those breaks early so the missing release can be recovered before it costs remaining life.
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.