FAA to TCCA transition
FAA to TCCA life-limited part traceability transition review
This review reconstructs the traceability behind each life-limited part for a move onto the Canadian register and asks whether the back-to-birth chain will satisfy TCCA import. It is run for the receiving side, or the seller readying the handover, before the LLP status sheet transfers. The work follows each part's history through its shop reports, release certificates, and cycle-accumulation records, and confirms the running total ties to source rather than to a tracking summary alone. You receive an evidence map keyed to the import questions, a gap list of parts with broken or thin trace, and a request set for the missing history.
When this review is needed
- A US-registered aircraft is importing into Canada and its LLP trace has to hold back to birth for TCCA.
- An engine has passed through several shops and the cycle history has to be rebuilt from the reports.
- The LLP status sheet shows remaining life the importer wants tied to source before it relies on it.
- A part changed hands at a module build and the trace has to be confirmed across the event.
The problem
A life-limited part is only as good as the unbroken chain from birth to the current cycle count, and that chain lives across birth records, every shop visit, and each release the part has carried. On a US to Canadian import the receiving side wants that chain proven, not summarized, and the status sheet's running total is exactly where trace tends to detach from source. A number that matches the tracking system can still rest on a shop report nobody has and a module build the file does not fully explain.
What gets reviewed
- Each life-limited part traced from birth record through every shop visit to the current count
- Cycle accumulation reconciled to utilization rather than the tracking summary alone
- Shop reports and release certificates confirmed present at each change of custody
- Module builds checked for whether the part trace survives the event
- Remaining life tied to source documents the receiving import will accept
- Parts with broken or thin trace identified and listed for recovery
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 cycle count traces to source records, not the status sheet in isolation
- Birth records or an accepted equivalent are present for each life-limited part
- Release evidence is present at every change of custody in the part's history
- Cycle accumulation reconciles with the airframe or engine utilization history
- Parts whose trace breaks are flagged rather than carried at their claimed life
Evidence normally required
- The LLP status sheet with current cycle counts and remaining life
- Birth records or the earliest available trace for each part
- Shop-visit reports and disk sheets across the part's history
- Release certificates carried at each installation and removal
- Utilization history for cycle-accumulation reconciliation
Common discrepancies
- A part whose trace breaks at a module build with no report to bridge it
- A cycle count that agrees with the tracking system but not with the utilization history
- A life-limited part with no birth record and no accepted equivalent on file
- A shop visit in the history with no release certificate to support it
What is at stake
A part whose trace breaks cannot carry its recorded remaining life into the import, so the conservative assumption is that its life resets or that it is unusable until the chain is rebuilt. That can strand real remaining cycles on an otherwise good part, and on an engine several broken traces can dominate the import's cost, because each one has to be closed to a source the receiving side accepts.
How the work runs
Lay out the part histories
List each life-limited part and assemble its birth record, shop reports, and releases.
Follow the chain to source
Trace each part from birth through every custody change to the current cycle count.
Reconcile the counts
Check cycle accumulation against utilization and flag totals that rest only on the tracking system.
Flag the breaks
Identify parts with broken or thin trace and request the missing shop and release records.
What the buyer receives
- An evidence map linking each part to its back-to-birth trace
- A gap list of parts with broken or incomplete traceability
- A request set for the shop reports and release records still to be recovered
Who uses the output
- Continuing-airworthiness teams clearing LLP status for the Canadian register
- Acquisition teams valuing remaining life that the trace can actually support
- Records staff recovering the shop and release history the import will require
How the work fits into the transaction or program
The review rebuilds the trace before the import, so parts whose chain breaks are known while shops are still reachable and remaining life can still be defended. Its gap list drives the recovery, and its evidence map forms the LLP section of the Canadian import package.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
TCCA import expects a life-limited part's history proven back to birth, and a US-side status sheet that satisfied day-to-day tracking is not the same as a proven chain. The review works to the standard the receiving side applies, tying each count to source rather than accepting the running total the tracking system carried.
Regulatory limits
The review reconstructs and tests the traceability and reports where it breaks. It does not set a part's life on an authority's behalf, certify remaining cycles, or make an airworthiness determination. Acceptance of the LLP status rests with the receiving operator and TCCA.
What this review does not cover
- Setting or re-lifing any life-limited part
- Physical inspection or re-certification of a part
- Any airworthiness determination on the life-limited parts
Specific to this review
- The running total on a status sheet is where trace most often detaches from source, because the number keeps moving while the document behind it stays static.
- A module build is the classic break point: the part is real and installed, but the report that carries its trace across the build is the piece that goes missing.
- A broken trace can strand genuine remaining cycles, because the conservative assumption on import is worth less than the life the part actually has.
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
Why rebuild the trace when the status sheet already shows remaining life?
The status sheet shows a number, but a Canadian import wants that number proven back to source. Where the chain breaks, the recorded remaining life cannot be relied on, which is why the review ties each count to birth records, shop reports, and releases rather than to the tracking summary.
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.