Back-to-birth before export
Life-limited part trace review for operators preparing an aircraft export
This review establishes, part by part, whether the life-limited parts on an exporting operator's aircraft carry the trace the receiving registry will demand. It examines the LLP status sheet, back-to-birth histories, release certificates, and cycle-accumulation records for every listed part on the airframe, engines, and APU before the export airworthiness application goes in. Records specialists work from the operator's own files outward during export preparation. Maintenance leadership gets a part-by-part trace ledger, a gap sheet rating each hole by recoverability, and a retrieval plan sequenced against the export date.
When this review is needed
- An export airworthiness application is planned and the LLP files have never been tested to back-to-birth standard.
- The aircraft changed operators in its past and the trace for earlier segments was inherited, never verified.
- A receiving registry or buyer has signaled it will require certificate-supported histories for every part.
- Engine or APU parts were swapped in service and the supporting paper is scattered across shop and pool sources.
The problem
LLP documentation is only as strong as its weakest ownership segment, and an aircraft that has traded twice carries trace assembled by three different records organizations. Status sheets summarize what the underlying certificates and shop documents must actually prove, and the gap between summary and source tends to surface exactly when a receiving registry asks for back-to-birth substantiation on a single disk.
What gets reviewed
- Every part on the LLP status sheet for airframe, engines, and APU, with no sampling
- Back-to-birth cycle history across each ownership and operation segment
- Release certificates at each installation, matched to part and serial number
- Shop-visit documents where limits were reset or parts were reworked
- Cycle-accumulation records covering the current operator's tenure, including ferry and test flights
- Non-incident statements where the receiving side or the transaction requires them
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
- Summed segment cycles equal the status-sheet total for each part, with no unexplained jumps
- Each installation event has a release certificate whose part and serial numbers match the status entry
- Operator transition points hand cycles across without overlap or gap between the two record sets
- Remaining-life figures use the correct limit for the part's dash number and the engine's thrust rating
- Current-tenure accumulation reconciles with the aircraft's flight log totals
Evidence normally required
- The current LLP status sheet for airframe, engines, and APU
- Part history cards or trace files for each listed part
- Release certificates and shop documents held in the operator's records
- Flight and utilization logs for the current operating period
- Prior-operator contact points for segments the operator's files do not cover
Common discrepancies
- A cycle gap at an operator transition years back, invisible on the summary sheet
- A release certificate on file whose serial number differs from the installed part by one transposed digit
- Remaining life computed against the wrong thrust rating's limit
- Ferry-flight cycles absent from the accumulation record
What is at stake
A part that cannot be traced to the standard the receiving side expects is treated as though its life were unknown, and the commercial answer is replacement or a steep concession. Trace holes discovered after the export application is filed cost more to fix than the same holes found during preparation, because prior operators and shops respond slowly once the aircraft is no longer their problem.
How the work runs
Build the ledger frame
Load every status-sheet part and lay out its claimed segments and totals.
Substantiate each segment
Match certificates, shop documents, and histories to every segment of every part.
Rate the gaps
Classify each hole by recoverability, likely holder, and export impact.
Run retrieval
Issue requests, log returns into the ledger, and report standing against the export date.
What the buyer receives
- A part-by-part trace ledger showing each part's substantiated history
- A gap sheet rating every hole by recoverability and likely source
- A retrieval plan with owners and dates sequenced against the export timeline
Who uses the output
- The director of maintenance deciding what to fix before the application
- Records staff executing the retrieval plan
- Transaction counterparts who will rely on the trace at delivery
How the work fits into the transaction or program
LLP trace is usually the longest-lead item in export preparation, so this review starts before the rest of the records package is assembled. Its gap sheet drives the retrieval effort, and its ledger becomes the substantiation file handed to the receiving registry and any buyer's team behind it.
Start with a single asset
Reconcile maintenance tracking against the underlying records.
Jurisdiction-specific considerations
Registries differ in how far back substantiation must reach: some accept documented life since new on the current summary standard, while others expect certificate-supported back-to-birth for every segment. FAA-side files lean on 14 CFR 91.417 retention and FAA Form 8130-3 releases; EASA-side files are built around EASA Form 1 under Regulation 1321/2014. The review applies the stricter of the operator's standard and the destination's.
Regulatory limits
The review documents part histories. It does not approve parts for installation, extend or determine life limits, certify cycle counts the records cannot support, or issue any element of the export approval.
What this review does not cover
- Physical inspection or serial-number verification on wing
- Sourcing replacement parts for unrecoverable trace
- Negotiating trace standards with the buyer or registry
Specific to this review
- Trace failures cluster at ownership transitions because each records organization assumed the previous one had closed its segment.
- A single reworked part can carry two legitimate release certificates; the review keeps both linked so neither looks like a discrepancy later.
- Ferry and acceptance flights add cycles that operators often book late, and receiving registries do check the final weeks of accumulation.
- Recoverability drops sharply once a shop archives past its retention period, which is why the gap sheet is sequenced by source fragility rather than part value.
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
Our status sheet is current. Why is a full-trace pass needed for export?
The status sheet asserts totals; the export process tests whether documents behind those totals exist. A current sheet built over an inherited gap still fails when the receiving registry pulls the segment certificates, so the review verifies the source layer the sheet summarizes.
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.