Life-limited parts
Life-limited part traceability review of the shop-visit source file
When an engine or APU leaves the shop, the LLP status sheet states cycles consumed and life remaining for every tracked part. This review follows each of those figures back through the source file: release certificates, module build records, disk sheets, and prior-operator history. It is done at or just after closeout by a records specialist working for the accepting quality team or the lessor. What comes back is a part-by-part account of where the trace holds and where the cycle history breaks.
When this review is needed
- An engine shop visit installed or re-installed LLPs and the outgoing sheet must be defensible.
- Parts moved between modules or serial numbers during the build and the tracking has to follow.
- A lessor requires back-to-birth traceability before the asset returns to the portfolio.
- Remaining-life figures drive an upcoming valuation, sale, or lease pricing decision.
The problem
Cycle figures travel more easily than the records behind them. A disk that has passed through two operators and a module swap carries its history in scattered releases and shop reports, and the status sheet printed at closeout simply totals whatever the tracking system holds. If one segment of that history has no document behind it, the sheet looks clean while the part's remaining life rests on an unverifiable number.
What gets reviewed
- Every part on the LLP status sheet matched to a release document for its latest installation
- Cycle totals recomputed across operator history and compared to the sheet
- Module build and strip records checked for parts that changed position during the visit
- Disk sheets and prior shop reports read for consistency with the claimed accumulation
- Serial-number continuity confirmed where parts were replaced, swapped, or re-identified
- Life-remaining calculations checked against the current published life limit
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 installation event in the part's history carries a matching removal from the previous position
- FAA Form 8130-3 or EASA Form 1 entries agree with the part number and serial number in the build records
- Cycle counts across consecutive segments add up without unexplained jumps or resets
- Utilization sources for each operator period exist and cover the full interval
- The life limit applied on the sheet is the current one for the part's dash number
Evidence normally required
- The outgoing LLP status sheet from the visit
- Release certificates for every LLP installed or re-certified during the build
- Module assembly and disassembly records, including disk sheets
- Prior shop-visit reports and operator utilization statements covering the part's history
Common discrepancies
- A cycle segment at a prior operator with no utilization record to anchor it
- A part re-identified to a new dash number without the paperwork tying the histories together
- Sheet totals that disagree with the sum of the documented segments by a small, unexplained margin
- A release certificate that covers the part but not the position it was actually built into
What is at stake
A broken cycle trace converts directly into money. Counterparties price an LLP with an unsupported segment as if the missing cycles were consumed, or reject the part outright at redelivery. Because the gap usually sits with a prior operator or a shop visit years back, each month of delay makes the record harder to recover and the conservative assumption harder to escape.
How the work runs
Bound the part list
Take the outgoing sheet and fix the set of parts, positions, and life limits under review.
Rebuild each history
Assemble releases, build records, and utilization data into a dated segment chain per part.
Test the arithmetic
Recompute cycles across the chain and compare against the sheet's totals and remaining life.
Deliver the trace map
Report supported figures, breaks, and the named document that would close each one.
What the buyer receives
- A part-by-part trace map showing each documented segment and each break
- An exception register with the specific missing document named for every break
- A verified restatement of remaining life for the parts the file fully supports
Who uses the output
- Lessor asset managers pricing the engine's green time and LLP stub value
- Quality leads deciding whether the outgoing sheet enters the permanent record as is
- Records teams preparing the file for the next transaction or redelivery
How the work fits into the transaction or program
LLP trace work sits alongside the AD and release-document reviews run on the same closeout file, but it reaches further back in time than either. The exception register it produces typically becomes the longest-running item on the post-visit action list, which is exactly why it is opened first.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA guidance under Order 8130.21 shapes what a domestic release must state, while an EASA Form 1 carries its own certification wording, and many parts alternate between the two systems across their lives. Lessor return conditions often demand back-to-birth continuity that neither regulator strictly requires, so the review distinguishes regulatory sufficiency from the contractual standard the sheet must meet.
Regulatory limits
The output describes documentary support for the life figures; it does not certify a part serviceable, approve continued use of a part with a broken trace, or set the disposition. Life-limit decisions remain with the operator, the CAMO, and the type-certificate holder's published limits.
What this review does not cover
- Physical inspection or measurement of any part
- Recovering records from prior operators, beyond drafting the specific requests
- Opinions on whether a part with a broken trace may remain in service
Specific to this review
- Most cycle-trace breaks are created at module swaps, where a part changes position and the paperwork follows the module rather than the disk.
- A status sheet can be internally consistent and still wrong, because tracking systems inherit whatever opening balance was keyed at induction.
- Two identical parts with equal remaining life can differ sharply in value if one carries a documented history and the other carries a reconstructed one.
- Requests for prior-operator records succeed far more often within months of the visit than years later, when fleets and archives have moved on.
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
Does every LLP need back-to-birth records?
Regulators require that life status be substantiated, and lessor agreements usually go further and demand an unbroken documentary chain from new. The review reports against both standards separately, so an operator can see what satisfies the authority even where a contract demands more.
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.