LLP traceability
Boeing 737 MAX life-limited part traceability records review
This review traces the life-limited parts on a Boeing 737 MAX back through their part history to a supported origin, testing the LLP status sheet against the documents behind it. It runs when the aircraft or its engines are valued, transferred, or separated for sale, run by or for the party pricing the life. It covers the status sheet, each part's shop-report and release-certificate history, the cycle accumulation between events, and the trace back toward birth. You receive an exception list per part, a source map from the status sheet to the release evidence, and a closure plan for the parts whose trace breaks.
When this review is needed
- An engine is coming off a 737 MAX for separate sale and its LLP trace sets the price.
- A buyer will accept remaining life only where it traces to a release document, not a summary.
- A module build combined disks from different histories and the trace has to survive the join.
- The status sheet was carried between operators and the cycle counts need reconciling across the transfers.
The problem
An LLP status sheet states remaining life to a single cycle, and that number is worth exactly what its trace can prove. On a 737 MAX engine the disks and spools may have moved through shop visits and module builds that each add a document to chase, and the point where the trace most often breaks is a module build where a part joined from a history the current file does not carry. A status sheet that reconciles internally can still fail the moment a buyer asks for the release certificate behind a given part.
What gets reviewed
- The LLP status sheet reconciled to the part records behind each line
- Shop-report and module-build history for each life-limited part
- Release certificates supporting each part's installation and cycle basis
- Cycle accumulation between recorded events checked for continuity
- The back-to-birth trace tested to a supported origin per part
- Parts joined at a module build checked for a carried-across history
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
- Remaining life on the status sheet traces to a release document, not the summary alone
- Cycle accumulation is continuous across shop visits with no unexplained reset or gap
- Each part's serial and part number reconcile across shop reports and release certificates
- A part joined at a module build carries a history that reaches its own origin
- The status sheet's totals agree with the airframe and engine cycle records
Evidence normally required
- The LLP status sheet for the airframe and each engine
- Shop-visit reports and module-build records for the life-limited parts
- Release certificates and disk sheets supporting the parts
- Airframe and engine cycle records for cross-checking accumulation
- Prior LLP trace work or a back-to-birth file if one exists
Common discrepancies
- A disk whose trace breaks at a module build where it joined from another history
- Remaining life stated on the status sheet with no release certificate behind it
- A cycle-count discontinuity across a shop visit that no report explains
- A serial or part number that shifts between the status sheet and the shop report
What is at stake
A life-limited part whose trace cannot reach a supported origin is priced at its worst defensible life or set aside, which moves real value off the asset. A break at a module build can taint the parts around it, and reconstructing a trace after an engine has separated for sale is far harder than confirming it while the records still sit together.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the status sheet to source
Match each life-limited part on the sheet to the shop reports and release certificates behind it.
Test cycle continuity
Check that cycle accumulation runs continuously across every recorded shop visit.
Chase the trace to origin
Follow each part back toward birth and flag where a module build breaks the history.
Report the breaks
Deliver the per-part exception list, source map, and closure plan.
What the buyer receives
- An exception list per life-limited part graded by where the trace breaks
- A source map from the status sheet to the release evidence per part
- A closure plan for the parts whose origin the file cannot yet reach
Who uses the output
- Asset managers pricing remaining life against what the trace can support
- Records teams assembling the release evidence behind the status sheet
- Trading teams preparing an engine for separate sale on documented life
How the work fits into the transaction or program
LLP trace is where the most concentrated value in a 737 MAX file sits, and it depends on shop-visit and release records that scatter as parts move. This review pulls that history back together and tests it to origin, so the status sheet a transaction relies on carries the evidence behind every cycle it claims.
Aircraft-specific considerations
The 737 MAX engine's life-limited parts turn on the module build and part-number standard embodied at delivery and refreshed at each shop visit, so configuration control drives the trace as much as the cycle math. A disk that is physically sound but joined at a build from a history the current file does not carry is the classic 737 MAX trace break, and it surfaces exactly when an engine is being separated for its documented life.
Jurisdiction-specific considerations
FAA and EASA both require life-limited part trace, and a 737 MAX engine crossing between them needs its release evidence in a form the receiving authority recognizes, so dual-release status on the supporting certificates is checked rather than presumed.
Regulatory limits
This review tests the trace and the evidence behind the status sheet. It does not set a part's life on an authority's behalf, certify a life-limited part, or make any airworthiness determination.
What this review does not cover
- Setting or re-lifing any life-limited part
- Issuing a release certificate for any part
- Any airworthiness determination on the engine or airframe
Specific to this review
- A module build is the single most common place a 737 MAX LLP trace breaks, because a part can join from a history the current file never received.
- Remaining life is only worth its release evidence, so a status sheet that reconciles internally can still fail when the certificate behind a part is missing.
- Once an engine separates for sale, rebuilding a trace is far harder than while the disk sheets and shop reports still sit with the airframe file.
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
The status sheet adds up. Why trace each part to a release document?
A status sheet that reconciles internally still relies on the release evidence behind each part. A buyer will pay for remaining life only where it traces to a document, so a part that adds up on the sheet but has no certificate behind it prices at its worst defensible life until the trace is closed.
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.