Life-limited parts at transition
LLP traceability tested against the import and export records package
Life-limited parts carry the highest document burden in any registry change, because a single unaccountable cycle can void a part's remaining life. This review tests the LLP status sheet against the import and export package: every part's identity, its release documents, and a cycle history that must hold together from new to now. Transition leads and acquiring teams commission it while the export application and registry-change files are in preparation. The output is a part-by-part trace verdict, with the exact break point named wherever a history fails.
When this review is needed
- The importing authority or its inspector has asked how remaining life on the status sheet was established.
- An engine or landing gear passed through shops and operators whose records arrive in different formats and languages.
- The status sheet came out of the current operator's system and the underlying trace has never been assembled as a package.
- A part's remaining life sits close to the next shop-visit boundary, so a conservative reading would change the maintenance plan the buyer is pricing.
The problem
LLP evidence is a chain, and a chain is judged at its weakest link: a module built at a shop visit whose disk sheet never followed the engine, a prior operator that logged hours but never cycles, a release certificate covering the assembly but none of the parts inside it. Status sheets present one confident number per part, and assembling the paper behind each number is where transitions stall.
What gets reviewed
- Each LLP on the status sheet identified by part number, serial number, and current position
- Release documentation checked at every installation event in the part's history
- Cycle accumulation reconstructed operator by operator, with conversion assumptions made explicit
- Module and assembly build records checked where parts moved between engines or gear legs
- Non-incident and service statements verified where the part class requires them
- Status-sheet arithmetic recomputed from the reconstructed history rather than accepted from the summary
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
- The identity chain holds: part and serial numbers agree across releases, shop reports, and the status sheet without unexplained renumbering
- Every custody transfer is covered by an authorized release document appropriate to its time and place, such as an FAA Form 8130-3 or EASA Form 1
- Cycle counts match at each transfer boundary: what a shop received equals what the previous operator dispatched
- Utilization sources behind the counts exist, whether operator logs, shop findings, or fleet-average substantiation with its basis stated
- Remaining life on the status sheet equals the limit minus the reconstructed accumulation, under the limit in the current airworthiness limitations data
Evidence normally required
- The LLP status sheets for engines, APU, and landing gear
- Release certificates and shop-visit reports across each part's life
- Prior-operator utilization records or their accepted substitutes
- Module build and disk-sheet records from shop visits
- Current life limits from the applicable airworthiness limitations data
Common discrepancies
- A cycle history that runs clean until a module swap at a mid-life shop visit, after which the trace rests on a summary the shop no longer holds source data for
- Hours recorded where cycles were required, with a conversion factor applied later and its basis undocumented
- A release certificate for the assembled module standing in for the piece-part releases the importing side expects
- Status-sheet remaining life computed against a superseded limit that was later reduced
What is at stake
A break in cycle history gets read conservatively: consumed life becomes whatever cannot be excluded, and remaining life shrinks to what can be proven. On engine parts that reading can pull a shop visit forward by thousands of cycles, which reprices the deal. An authority that finds one broken trace tends to widen its sampling, and the package's other sections inherit the doubt.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the part population
Freeze the status sheets and confirm the installed configuration they describe.
Assemble each chain
Gather releases, shop reports, and utilization records into a per-part history.
Test the boundaries
Verify identity and cycle continuity at every transfer, build, and shop-visit event.
Issue verdicts
Deliver per-part results, the exception list, and the reconstruction memo.
What the buyer receives
- A part-by-part trace verdict: proven, proven with stated assumptions, or broken at a named event
- The exception list for the authority-response evidence file, with the failing document identified per part
- A reconstruction memo recording the sources and arithmetic behind each verified history
Who uses the output
- Transition leads deciding what to fix, substantiate, or disclose before submission
- Acquiring teams and their advisors pricing remaining life against proven trace
- The receiving CAMO loading verified part histories into its tracking system
How the work fits into the transaction or program
LLP trace runs alongside the AD and release-document reviews because they share sources: the shop-visit report that proves a cycle count often also proves an AD closure and carries the release certificate. Sequencing them together means each source document is pulled once and read three ways, which matters when the archive is a prior operator on another continent.
Jurisdiction-specific considerations
FAA and EASA both demand traceable life status, but their documentary habits differ: dual-release certificates smooth movement between the two systems, while single-authority releases from third registries need case-by-case reading. Guidance such as FAA Order 8130.21 shapes how release forms are completed, and importing authorities vary in what they accept as substantiation where operator logs are gone.
Regulatory limits
The review does not extend, restore, or certify part life, does not approve substantiation methods, and makes no installation or airworthiness decisions. It states what the package proves about each part's history and where the proof stops.
What this review does not cover
- Physical inspection or borescope verification of installed parts
- Negotiating substantiation methods with the authority
- Sourcing replacement parts or pricing life shortfalls
Specific to this review
- Cycle-count mismatches at custody boundaries are usually clerical, one side counting from a different reference flight, and resolving the reference resolves the mismatch without any loss of life.
- The disk sheet from a module build is the document most often absent from third-hand engine records, and the shop that built the module is the only realistic recovery path.
- Fleet-average substantiation accepted by one authority years ago does not automatically carry to the importing authority, which can reopen a history everyone considered settled.
- Parts near their limit attract inspection focus, so ordering the review by remaining-life margin, tightest first, matches the order the authority will read in.
- Landing-gear LLPs break trace more often than engine LLPs, because gear overhauls route through more independent shops and their records travel less reliably than engine shop-visit packages.
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.
Frequently asked questions
One part has a two-year gap in operator records. Is its life automatically lost?
Not automatically. Authorities accept substantiation in defined circumstances, such as documented fleet-average utilization for the gap period with a conservative margin. What the review establishes is exactly what the gap is, what evidence borders it, and which substantiation route is plausible, so the conversation with the authority starts from specifics rather than from a missing folder.
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.