Registry transition
Records from Canada mapped for FAA conformity and import review
This page serves operators, brokers, airlines preparing for sale or lease placement to a US operator. EE reviews TCCA export C of A, STC list mapped to FAA acceptance status, AME-signed maintenance releases and tests whether the file proves the status claimed in the summary. Any gap tied to STCs assumed valid on the N-register without checking acceptance, expiry timing, copy status, or acceptance basis is logged. The output is a requirement matrix, source-record exception register, and handover index for the next reviewer.
The problem
what an FAA import of a Canadian aircraft turns on: conformity to the FAA type design, acceptance of Canadian STCs under the US-Canada bilateral, and a CAR 571 maintenance release chain the FAA reviewer can follow.
What gets reviewed
- Build a requirement-by-requirement matrix for tcca to faa aircraft records transition.
- Test whether TCCA export C of A proves the condition claimed in the summary.
- Separate acceptable records from items that need CAMO, owner, maintenance, or authority action.
- Check timing risk for inspections, ARC or C of A status, deferrals, and calendar-limited tasks.
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
- The matrix passes when each requirement has one named record and one owner.
- Reject a summary line when the supporting certificate, work package, or approval cannot be produced.
- Timing is open if an inspection, ARC, C of A, or deferral expires before transfer completion.
- Close a finding only with dated evidence, not with a verbal confirmation or index note.
Evidence normally required
Common discrepancies
- STCs assumed valid on the N-register without checking acceptance.
- CAR-format releases.
- metric records misread during conformity review.
- The file treats the TCCA export C of A as closed without enough support.
What is at stake
Canadian STCs assumed valid on the N-register without checking acceptance, and CAR-format releases and metric records misread during conformity review.
How the work runs
Frame TCCA FAA
Confirm the exact event, affected file set, buyer role, and decision standard before any ad status is treated as sufficient.
Trace Transition Aircraft
Walk the named evidence from index entry to source artifact and mark where the trail supports, conflicts with, or fails to answer the page-specific question.
Sort Mapped Conformity
Group exceptions by closure route: document retrieval, data correction, engineering disposition, authority response, or contractual decision.
Package Review Registry
Deliver the exception list, evidence map, and owner sequence in a form that can move directly into remediation, submittal cleanup, or transaction negotiation.
What the buyer receives
- C-reg to FAA records transition requirement matrix
- Source-record exception log
- Acceptance question list
- Handover package index
How the work fits into the transaction or program
The decision is what an FAA import of a Canadian aircraft turns on: conformity to the FAA type design, acceptance of Canadian STCs under the US-Canada bilateral, and a CAR 571 maintenance release chain the FAA reviewer can follow; TCCA export C of A, the Canadian STC list mapped to FAA acceptance status, AME-signed maintenance releases, and AD status covering Transport Canada directives. The evidence set centers on TCCA export C of A, the Canadian STC list mapped to FAA acceptance status, AME-signed maintenance releases, and AD status covering Transport Canada directives. The likely weak points are canadian STCs assumed valid on the N-register without checking acceptance, and CAR-format releases and metric records misread during conformity review. Handoff: buyer technical advisor, sale or lease placement to a US operator, Records from Canada mapped for FAA conformity and import.
Start with a single asset
Organize records and a discrepancy register for diligence.
Regulatory limits
This work is a records and evidence review only. EE does not approve maintenance programs, issue airworthiness certificates, make compliance findings, or guarantee that a registry, buyer, lessor, or authority will accept the file.
Specific to this review
- Aircraft status at the transfer date controls this review more than any older audit snapshot.
- FAA import context changes what evidence is persuasive even when the status heading looks familiar.
- A summary gains value only when the release, approval, inspection, or utilization record behind it can be found.
- c-reg-to-n-acceptance-map is the page-specific risk that drives the request list and closure plan.
- The scope uses the TCCA FAA Records Transition question as the control point, so the review stays tied to Sale or lease placement to a US operator and the buyer decision behind it.
- The evidence starts with AD status and follows Aircraft Canada Mapped Conformity references until every exception has a source location and a reason code.
- The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
- The timing matters for buyer technical advisor: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
- The boundary control keeps Import Review Registry Importing questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
- The handoff value comes from C-reg to FAA records transition requirement matrix; it gives the next reviewer a precise map instead of another broad request for a better file.
Sources
Transport Canada. Canadian airworthiness, maintenance records (CAR 605/571), and Airworthiness Directive requirements (CAR 593).
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Frequently asked questions
What makes this transitions review different from a general file audit?
The scope is tied to tcca faa records transition and to the decision named in the request. A general audit can list weak records; this pass ranks the gaps by whether they block sale or lease placement to a us operator or can be closed later without changing the decision.
What evidence has to be available before this work starts?
The starting point is ad status, the current status source, and any index or matrix that tells reviewers where the supporting artifact should live. Missing inputs are logged as findings rather than filled with assumptions.
Who decides whether an open item is acceptable?
The review explains what the evidence supports and gives buyer technical advisor a closure path. Acceptance remains with the buyer, operator, authority, delegated engineer, or authorized person responsible for the underlying airworthiness or certification decision.
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.