Registry change
Life-limited part traceability review for a registry change
A registry-change LLP traceability review confirms that each life-limited part carries an unbroken record chain the receiving authority will accept when the aircraft moves to a new register. It is run for the team preparing the transition, before the package is handed over, on the airframe and engine LLPs whose remaining life the new register will trace. The work follows part history back through shop visits, matches each installation to its release certificate, and reconciles accumulated cycles against the status sheet. You receive a traceability map keyed to the LLP status sheet, a gap list flagging the breaks that will draw questions, and a request set for the missing history behind them.
When this review is needed
- An aircraft is changing register and the receiving authority will trace each LLP back to its original release.
- Engine LLPs have passed through module builds and shop visits where the trace can break at a disk swap.
- The LLP status sheet has been carried forward across operators without the underlying release certificates being verified.
- A firm handover date is set and the team needs to know which parts lack birth-to-current history before the package goes over.
The problem
A life-limited part is only as good as the paper that proves its cycles, and that paper scatters across every shop visit the part has ever seen. A status sheet can show comfortable remaining life while the certificate that would substantiate a mid-life installation sits in an archive nobody has touched since the last engine build. On a registry change the receiving authority tends to trace the whole chain, and a single missing release breaks the line at exactly the disk that matters.
What gets reviewed
- Part history followed back through each recorded installation, removal, and shop visit
- Release certificate located for every build event that reset or carried the part's cycle basis
- Accumulated cycles reconciled between the status sheet, the logbooks, and the last shop report
- Serial numbers on the status sheet matched to the parts actually installed per the removal history
- Remaining-life figures tested against the correct cycle limit for the part standard fitted
- Chain breaks isolated to the specific build or transfer where the history goes dark
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 LLP traces to a release certificate at every build that changed its installed position
- Accumulated cycles on the status sheet agree with the airframe or engine cycle history at the same date
- The serial number on the status sheet matches the removal and installation record for that position
- Remaining life is calculated against the cycle limit that applies to the part number fitted
- Any break in the chain is pinned to a named build or transfer rather than left as a general shortfall
Evidence normally required
- The current LLP status sheet for the airframe and engines
- Release certificates and shop-visit reports for prior module builds
- Airframe and engine logbooks showing installation and removal history
- Current cycle totals for reconciling accumulated life
- Disk sheets or back-to-birth records where the part history was previously assembled
Common discrepancies
- An engine LLP whose trace breaks at a module build with no release certificate on file
- A status-sheet cycle count that disagrees with the last shop report for the same part
- A serial number that does not match the removal record for the position it occupies
- Remaining life stated against a superseded cycle limit for the part standard installed
What is at stake
An LLP the new register cannot trace may have to be treated as zero-life or pulled for replacement, which turns a records gap into a shop event. Where the missing certificate is genuinely unrecoverable, the part's value collapses and the transition either slips or closes with a conservative assumption the receiving owner carries.
How the work runs
Walk the part history
Follow each LLP back through its installation, removal, and shop-visit record to the original release.
Match builds to certificates
Locate the release evidence for every build that carried or reset the part's cycle basis.
Reconcile the cycles
Confirm accumulated life on the status sheet against the logbooks and the last shop report.
Pin and request the breaks
Isolate each chain break to a named build and raise the document request that would close it.
What the buyer receives
- A traceability map tied to the LLP status sheet, marking each part traced or broken
- A gap list identifying the exact build or transfer where each chain break occurs
- A document request set for the release certificates and shop reports needed to close the breaks
Who uses the output
- Continuing-airworthiness leads defending LLP remaining life to the receiving authority
- Asset managers weighing whether a broken trace means a replacement or a discount
- Records teams recovering the missing release evidence before the package is handed over
How the work fits into the transaction or program
The LLP trace review runs beside the AD, repair, and configuration strands of the registry-change package and feeds the same handover deadline. Because a broken chain can force a shop event, its gap list often drives the longest-lead recovery work in the transition and is started early for that reason.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA, EASA, and TCCA differ in how far back they expect an LLP to be traced and in which release forms they treat as substantiating a build. The review notes where the receiving authority's back-to-birth expectation exceeds what the outgoing file was maintained to satisfy.
Regulatory limits
The review verifies the LLP record chain and reconciles the cycle basis. It does not certify a part, set its remaining life on an authority's behalf, return it to service, or commit the receiving authority to accept the trace as assembled.
What this review does not cover
- Physical inspection, teardown, or re-life of any life-limited part
- Issuing or replacing a release certificate for a part
- Any airworthiness determination on the parts installed
Specific to this review
- The trace almost always breaks at a shop visit, because that is where a part changes position and its certificate leaves with the shop rather than the aircraft.
- A status sheet can show ample remaining life and still fail acceptance, because the number is only defensible if the certificate behind each build survives.
- Once a chain break forces a zero-life assumption, recovering the missing certificate later rarely reverses the decision, so the breaks are hunted before handover.
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
What happens to an LLP whose trace we cannot close?
If the release evidence behind a build is genuinely unrecoverable, the receiving authority may require the part to be treated as zero-life or replaced. The review identifies those parts early so the choice between recovery, replacement, and a documented assumption is made before the handover date, not during acceptance.
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.