Records & evidence
Life-limited part traceability review
A life-limited part traceability review verifies that each LLP on an aircraft or engine has a continuous, supported history from its current status back to the origin required by the contract or program. It is used before a purchase, a lease return, or an engine transaction. It checks time and cycle accumulation, release documentation, and removal and installation evidence. You receive a per-part trace, a list of breaks in the chain, and the evidence needed to close them.
When this review is needed
- An engine or aircraft is being bought, sold, or returned and the LLP trace drives value.
- A status list shows LLP life remaining that has not been checked against source documents.
- A part changed hands at a shop visit and the release and removal evidence needs confirming.
- A transaction requires back-to-life trace and the chain has to be reconstructed.
The problem
LLP status is usually read from a tracking system or a one-page status list. The list states life remaining, but the documents that justify it are spread across shop visits, prior operators, and release paperwork. A single missing release or an inconsistent cycle count can put a part's remaining life in question and force conservative assumptions that cost real money.
What gets reviewed
- Each life-limited part by part number and serial number
- Time-since-new and cycles-since-new accumulation across operators and shop visits
- Release documentation at each change of custody
- Removal and installation evidence linking the part to the asset
- The required trace origin defined by the contract or program
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 LLP traces from current status to the required origin without an unexplained gap
- Time and cycle history is internally consistent across logbooks, shop reports, and status lists
- Each change of custody carries a valid release certificate appropriate to the jurisdiction
- Removal and installation entries reconcile with the recorded serial numbers
- The status list life remaining is supported by the underlying source documents
Evidence normally required
- LLP status list with part and serial numbers
- Engine and module shop-visit reports
- Release certificates for each part at each change of custody
- Logbooks or digital records showing accumulation and installation history
Common discrepancies
- A release certificate missing at a prior shop visit
- Cycle counts that disagree between the status list and the shop report
- A part whose trace cannot be carried back to the required origin
- Installation evidence that does not match the recorded serial number
What is at stake
A part with broken traceability may have to be treated as having less usable life than the status list claims, or pulled early. On an engine transaction that difference is large, and it is far cheaper to identify before the deal closes than after.
Move from findings to resolution
Move from findings to a documented resolution path.
What the buyer receives
- A per-part traceability record showing the chain and any break
- A list of missing or inconsistent documents by part
- A recommended path to close each gap or quantify its effect on usable life
Who uses the output
- Acquisition and asset teams pricing the engine or aircraft
- Records teams assembling the trace package for a transaction
- Engineering deciding how to treat a part with an incomplete chain
How the work fits into the transaction or program
The review supports a pre-purchase, a redelivery, or an engine sale by turning a status list into a supported trace. It feeds the data room and the discrepancy register for the larger transaction.
Jurisdiction-specific considerations
A release accepted in one jurisdiction is not automatically accepted in another. Where a part has moved across authorities, the trace has to show release documentation that the receiving authority will accept.
Regulatory limits
The review confirms traceability and consistency of the records. It does not certify the part, determine remaining life on the authority's behalf, or replace the approvals required to install or operate it.
What this review does not cover
- Physical inspection or measurement of the part
- Re-certification or re-life of a part
- Any airworthiness determination
Specific to this review
- Back-to-life trace is a contractual and traceability expectation that is often described loosely as back-to-birth; the underlying requirement is a supported, continuous history.
- A single missing release at a shop visit can force a conservative life assumption that is expensive on an engine transaction.
- Status-list life remaining and source-document evidence are checked as two separate things, because they frequently disagree.
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 Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Is back-to-birth a regulatory requirement?
Back-to-birth is industry shorthand. The trace origin is usually set by the contract or the engine program, and it rests on the underlying release and accumulation evidence rather than a single uniformly named regulation.
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.