Skip to content

Life-limited parts

Tracing LLP status through a maintenance-control system export

Exported LLP status sheets state remaining life; this review tests whether the source records can prove it. It is run for maintenance control and fleet teams whenever an operator transfer or maintenance-system change makes the export authoritative. Each life-limited part's cycle accumulation is rebuilt across operators, module builds, and shop visits, then matched against release certificates and disk sheets. Every part comes back with a trace grading, each break located to the event that caused it, and a recovery path proposed.

When this review is needed

  • A transfer counterparty has asked for back-to-birth substantiation of the exported LLP sheet.
  • An engine or APU changed hands mid-life and its cycle history spans systems that no longer talk to each other.
  • A module swap during a shop visit left doubt about which disks carry which history.
  • Remaining-life figures drive an upcoming removal plan and the numbers have never been proven from source.

The problem

LLP status sheets summarize what the system believes, and the system believes whatever was keyed at the last data load. Cycle counts assembled across two or three operators, a module exchange, and a shop visit can carry a silent discontinuity that the export smooths over. The person signing the transfer package inherits that discontinuity without knowing it exists.

What gets reviewed

  • Cycle accumulation for each LLP rebuilt from birth or from the last fully documented zero point
  • Operator-to-operator handoffs checked for continuity of counts and counting basis
  • Module build records reconciled with disk sheets and the released configuration
  • Release certificates matched to each installation event in the part's history
  • Exported remaining-life figures recomputed and compared against the rebuilt trace

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

  • Cycle totals are continuous across every operator boundary in the part's history
  • Each installation in the trace has a matching release document with agreeing part and serial numbers
  • Disk sheets from shop visits agree with the module build and the export's current configuration
  • The counting basis, flight cycles versus reference cycles, is consistent or correctly converted
  • No remaining-life figure on the export exceeds what the rebuilt trace supports

Evidence normally required

  • The LLP status sheet export with the system's life-tracking parameters
  • Engine, APU, and airframe logbooks covering the part's service history
  • Shop-visit packages, module build records, and disk sheets
  • Release certificates for each installation event
  • Prior-operator utilization statements where history crosses operators

Common discrepancies

  • A cycle-count step change at an operator handoff that no document explains
  • A disk whose sheet history and system history diverge after a module exchange
  • Remaining life computed against the wrong life-limit revision
  • An installation event with a release certificate for the right part number and the wrong serial

What is at stake

A break in an LLP trace collapses the part's remaining life to the most conservative reading, or to zero if no defensible accumulation can be built. On an engine, one unsupported disk can strand the whole module economically, and the argument arrives precisely when the aircraft or engine is supposed to be moving.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Baseline the export

Fix the LLP sheet version and extract each part's claimed life and configuration.

02

Rebuild each trace

Assemble the accumulation history from logbooks, shop records, and release documents.

03

Locate the breaks

Pin each discontinuity to a specific handoff, build, or data load.

04

Grade and hand off

Issue per-part gradings, worksheets, and the recovery plan for open breaks.

What the buyer receives

  • A per-part trace grading with each break located to the event that caused it
  • Rebuilt accumulation worksheets a counterparty reviewer can follow
  • A recovery plan naming the shop, operator, or archive likely to hold each missing link

Who uses the output

  • Maintenance control defending the LLP sheet in the transfer package
  • Fleet management planning removals against proven rather than assumed life
  • Asset managers quantifying exposure on parts with unrecoverable breaks

How the work fits into the transaction or program

The LLP module of an export review runs deepest because its evidence spans the aircraft's whole trading history. Its rebuilt traces feed the operator-transfer status package, inform the release-document and shop-visit reviews covering the same events, and give the removal plan a defensible basis.

Jurisdiction-specific considerations

14 CFR 91.417 requires current status of life-limited parts, and FAA Order 8130.21 governs the release documentation the trace leans on. EASA's Regulation (EU) 1321/2014 imposes equivalent continuing-airworthiness record duties. Traces that cross regimes must handle certificates and counting conventions from both without gaps at the boundary.

Regulatory limits

The review reconstructs and grades documentary traces. It does not declare any part serviceable or airworthy, does not issue or amend release certificates, and does not decide whether a part may remain in service; those determinations stay with the certificate holders and authorities.

What this review does not cover

  • Physical inspection or serial-number verification on the part itself
  • Life-limit engineering analysis or limit revision requests
  • Commercial negotiation over parts with failed traces

Specific to this review

  • Most trace breaks are created at data loads, when a new system accepts summary totals and the source documents stay archived at the old operator.
  • A module exchange is the highest-risk event in an LLP history because disk-level identity can silently swap between records.
  • Counting-basis mismatches, cycles versus reference cycles, produce traces that look continuous while being wrong.
  • The cost of recovering a broken trace roughly doubles each time the responsible shop or operator recedes another transaction into the past.

Sources

Frequently asked questions

What happens when a break simply cannot be closed?

The review documents the break, states what the trace supports up to it, and quantifies the conservative position. Whether the part is then re-lifed conservatively, removed, or traded with disclosure is a commercial and engineering decision made by the operator with its authority and counterparties; the review's job is to make that decision informed.

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.