Skip to content

Back-to-birth trace

Life-limited part traceability for an EASA to FAA transition

Life-limited parts carry the most expensive records risk in an EASA to FAA transfer, because a broken trace converts remaining life into scrap value. This review tests each tracked part's story: birth record, every operating interval, cycle accumulation arithmetic, shop-visit evidence at each module build, and the release certificates that will face US acceptance rules. It is carried out by a records specialist during transition preparation, using the LLP status sheet as the index. The owner receives a part-by-part evidence map, a gap list weighted by life at stake, and document requests to the shops and operators holding the missing intervals.

When this review is needed

  • The buyer's engine specialist has requested back-to-birth trace for every disk and shaft, and the file has never been assembled part by part.
  • Engines or landing gear changed hands through exchanges, leases, or shop swaps and the interval records live in several archives.
  • Cycle accounting crossed operators with different counting conventions and nobody reconciled the totals.
  • The LLP status sheet was inherited from a tracking-system migration and its source documents were never re-verified.

The problem

An LLP status sheet states remaining life to the cycle, but the number is only as good as the chain behind it: the birth certificate, the release at every shop visit, the recorded cycles in every installation interval, and the arithmetic joining them. Engines that passed through exchanges and multiple operators scatter that chain across organizations that owe the current owner nothing. US-side reviewers work the chain link by link, and one undocumented interval anywhere in a part's life breaks the whole trace.

What gets reviewed

  • Back-to-birth documentation assembled for each LLP on the status sheet: engines, APU, and landing gear
  • Cycle accumulation recomputed across every installation interval and reconciled with airframe utilization
  • Shop-visit reports and module build records checked for continuity at each disassembly and rebuild
  • Release certificates for each part movement assessed against US acceptance rules at transfer
  • Non-incident and accident-history statements collected where the receiving side requires them
  • Status-sheet arithmetic verified: limits, cycles consumed, and remaining life per part number and dash

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 part's documented intervals join without gaps from birth record to current position
  • Cycles claimed per interval match operator utilization records, with counting-convention conversions shown
  • Every change of custody has a release certificate whose serial number matches the part and the build records
  • Module build sheets account for each tracked part entering and leaving every shop visit
  • The life limit applied matches the current type-certificate data and airworthiness limitation for that part and dash number

Evidence normally required

  • LLP status sheets for engines, APU, and landing gear
  • Shop-visit reports, module build records, and disk sheets
  • Release certificates covering each part movement: Form 1, 8130-3, dual release, or predecessor documents
  • Operator utilization and cycle records for each installation interval
  • Prior trace packages, non-incident statements, and tracking-system extracts

Common discrepancies

  • An interval documented only by a tracking-system line, with the underlying operator records never obtained at the exchange
  • Cycle totals that ignore a counting-convention change, understating consumption by a few hundred cycles
  • A disk that entered a shop visit on one build sheet and exited on another with no linking record
  • Release certificates that will draw US-side questions because the issuing organization held EU-only approval

What is at stake

A part with a broken trace is treated as if its history were unknown, and for a life-limited part that means removal or a deep discount, regardless of how much book life remains. On a high-time engine set, two or three untraceable disks can move the transaction economics more than every other records issue combined. Recovery gets harder with time as shops close and archives purge, so gaps found at the buyer's audit are the costliest kind.

How the work runs

01

Index every tracked part

Build the part list from status sheets and confirm limits and dash numbers against current type data.

02

Assemble each chain

Order birth records, releases, build sheets, and interval records into a continuous history per part.

03

Recompute the life

Recalculate cycles consumed across intervals, converting counting conventions explicitly.

04

Report by value at risk

Deliver the evidence map and a gap list ranked by remaining-life value, with targeted requests.

What the buyer receives

  • A part-by-part evidence map from birth record to present position
  • A gap list weighted by remaining-life value at risk, separating recoverable from likely-unrecoverable items
  • Document requests to the specific shops, lessors, and operators holding each missing interval

Who uses the output

  • Buyer and seller engine specialists agreeing what the trace actually supports
  • Asset managers quantifying LLP exposure in the transaction
  • The incoming US operator's records team, which inherits the trace file as its baseline

How the work fits into the transaction or program

LLP trace intersects the release-document review, since the same certificates prove both custody and acceptability, and the AD review where directives set inspection or life constraints on tracked parts. In an EASA to FAA transition it is usually the longest-running strand, so it starts at the first sign of a transaction and its interim findings feed the negotiation before the review is even complete.

Start with a single asset

Confirm the status list matches the underlying evidence.

Jurisdiction-specific considerations

Both systems impose life limits through the type design and require records proving consumption, with FAA-side retention expectations anchored in 14 CFR 91.417 and part status governed by the airworthiness limitations. The transfer-sensitive issue is document acceptability: intervals evidenced by EU-only releases or national predecessor certificates get read under the bilateral's acceptance rules, and FAA Order 8130.21 practice shapes what US reviewers expect a release to show. The review notes, part by part, where the evidence is solid but the certificate form will still prompt questions.

Regulatory limits

The review establishes what the records prove. It does not certify remaining life, does not approve any part for continued service or installation, does not adjudicate counting-convention disputes between operators, and makes no airworthiness determination. Life-limit compliance remains the operator's obligation under the airworthiness limitations.

What this review does not cover

  • Physical part inspection, dataplate reading, or borescope verification
  • Engine or landing-gear condition assessment and workscope planning
  • Negotiating trace-related price adjustments, beyond supplying the evidence basis

Specific to this review

  • Trace quality is binary in practice: a part is either fully traceable or it is negotiated as untraceable, so partial recoveries only pay off when they complete a chain.
  • Counting conventions are the silent killer in cycle arithmetic; a part that flew short-cycle operations under one operator and was tracked on full-flight cycles by the next can be off by a meaningful fraction of its life.
  • Exchange transactions are where intervals vanish, because the paperwork duty fell between the outgoing and incoming custodians and neither archived the other's records.
  • The order of work matters: verify the status-sheet arithmetic first, because a computation error can manufacture an apparent trace gap that no document request will ever close.

Sources

Frequently asked questions

What does back-to-birth actually require, document by document?

For each part: the original release from manufacture, a release certificate for every subsequent custody change, records placing the part in each engine or gear position with dates, and operator cycle records for every interval, all joining without gaps. A summary sheet, however tidy, is an index to this file rather than a substitute for it.

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.