Import acceptance
Life-limited part traceability review for import acceptance
An import acceptance LLP traceability review confirms that each life-limited part carries the record chain the importing authority requires as the aircraft enters its register. It is run for the team preparing the import, before the acceptance review, on the airframe and engine LLPs whose remaining life the importing authority will trace to source. The work follows part history through shop visits, matches installations to release certificates, and reconciles accumulated cycles against the status sheet under the importing authority's back-to-birth expectation. You receive a traceability view keyed to the LLP status sheet, a gap list isolating each chain break, and a request set for the missing history behind them.
When this review is needed
- An aircraft is being imported and the importing authority will trace each LLP to its original release.
- The importing authority's back-to-birth expectation exceeds what the LLP file was maintained to satisfy on export.
- Engine LLPs passed through module builds abroad where the release certificate stayed with the shop.
- An acceptance review is scheduled and the team needs to know which parts lack birth-to-current history.
The problem
Import acceptance is often where an LLP's back-to-birth chain is tested most strictly, and the importing authority may expect a fuller history than the aircraft was maintained to abroad. A status sheet can show healthy remaining life while a mid-life release certificate never crossed the border with the aircraft. The team preparing the import has to rebuild the chain to the importing authority's standard and find the breaks before the acceptance review does.
What gets reviewed
- Part history followed through each installation, removal, and shop visit to the original release
- Release certificate located for every build that carried or reset the part's cycle basis
- Accumulated cycles reconciled between the status sheet, the logbooks, and the last shop report
- Serial numbers on the status sheet matched to the parts installed per the removal history
- Trace depth tested against the importing authority's back-to-birth expectation
- Chain breaks isolated to the specific build or border crossing where history goes dark
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 LLP traces to a release certificate at every build that changed its cycle basis
- Accumulated cycles agree between the status sheet and the airframe or engine cycle history
- The serial number on the status sheet matches the installation record for its position
- The trace depth meets the importing authority's back-to-birth expectation, not only the exporting one
- Each chain break is pinned to a named build or transfer rather than left as a general shortfall
Evidence normally required
- The LLP status sheet for the airframe and engines
- Release certificates and shop-visit reports for prior module builds
- Airframe and engine logbooks showing installation and removal history
- The importing authority's back-to-birth expectation for LLP trace
- Disk sheets or back-to-birth records assembled under the exporting register
Common discrepancies
- An engine LLP whose trace breaks at a module build abroad with no release certificate transferred
- A back-to-birth history that satisfied the exporting register but not the importing one
- A status-sheet cycle count that disagrees with the last shop report for the same part
- A serial number that does not match the removal record for the position it occupies
What is at stake
An LLP the importing authority cannot trace to source may have to be treated as zero-life or replaced, which converts a records gap into a shop event on the acceptance timeline. Where a mid-life certificate is unrecoverable, the part's remaining life becomes indefensible and the import either slips or proceeds on a conservative assumption the importing owner carries.
How the work runs
Set the importing standard
Establish the back-to-birth depth the importing authority expects for each LLP.
Walk the part history
Follow each LLP through its installation, removal, and shop-visit record to the original release.
Reconcile the cycles
Confirm accumulated life on the status sheet against the logbooks and the last shop report.
Pin and request the breaks
Isolate each chain break to a named build or crossing and raise the document request that closes it.
What the buyer receives
- A traceability view keyed to the LLP status sheet, marking each part traced or broken
- A gap list identifying the exact build or crossing where each chain break occurs
- A document request set for the release certificates and shop reports needed to close the breaks
Who uses the output
- Continuing-airworthiness leads defending LLP remaining life to the importing authority
- Asset managers weighing whether a broken trace means replacement or a discount on import
- Records teams recovering the missing release evidence before the acceptance review
How the work fits into the transaction or program
The LLP trace review runs with the release document and AD strands of the import package and often carries the longest recovery lead, because a broken chain can force a shop event. It is started early so the importing authority's back-to-birth expectation is met before the acceptance review tests the engines it depends on.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
How far back an LLP must be traced varies between FAA, EASA, and TCCA, and the importing authority's expectation can exceed the depth the exporting file was built to. The review works to the importing authority's back-to-birth standard and flags where the transferred history falls short of it.
Regulatory limits
The review verifies the LLP record chain and reconciles the cycle basis against the importing authority's expectation. It does not certify a part, set its remaining life on an authority's behalf, return it to service, or grant import acceptance.
What this review does not cover
- Physical inspection, teardown, or re-life of any life-limited part
- Issuing or replacing a release certificate for a part
- Any airworthiness determination on the parts installed
Specific to this review
- The importing authority can demand a deeper back-to-birth trace than the exporting file was maintained to, so trace depth is tested against the importing standard first.
- A mid-life release certificate often stays with the shop that performed the build abroad, so it is the first document to chase across the border.
- Once a break forces a zero-life assumption, recovering the certificate later rarely reverses it, so the breaks are hunted before the acceptance review.
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.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Frequently asked questions
The LLP trace passed on export. Why re-check it for import?
The importing authority can expect a deeper back-to-birth history than the exporting register accepted, and a mid-life release certificate may never have crossed the border with the aircraft. The review rebuilds the chain to the importing standard and finds the breaks before the acceptance review, when a zero-life assumption would still be avoidable.
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.