FAA to TCCA transition
FAA to TCCA modification status transition review
This review reads an aircraft's modification and STC status for a move onto the Canadian register and asks whether each change's approval will be recognized on import. It is run for the receiving side, or the seller preparing the handover, before the modification status report transfers. The work ties each SB embodiment and STC to its approval data and effectivity, and identifies STCs whose Canadian standing needs to be established rather than assumed. You receive an evidence map keyed to the import questions, a gap list of modifications whose approval will not travel as recorded, and a request set for the STC and approval files still to be recovered.
When this review is needed
- A US-registered aircraft is importing into Canada and its STC and modification approvals have to be recognized by TCCA.
- An FAA STC is embodied whose Canadian validation has not been confirmed.
- A service bulletin is shown embodied but the revision and effectivity are not tied to the serial number.
- The modification status report has to be reconciled to the approval files before the register changes.
The problem
A modification status report lists what has been changed, but the import turns on whether each change carries an approval the receiving authority recognizes. An FAA STC embodied on the aircraft is not automatically valid on the Canadian side, a service bulletin shown embodied may be recorded at the wrong revision, and a modification approval accepted under one authority can need a separate validation under the other. The report reads settled while the approval underneath a given change is exactly what has to be re-established.
What gets reviewed
- Each embodied STC tied to its approval and its standing on the Canadian side
- Service bulletin embodiment recorded at the correct revision and effectivity
- Modification approvals checked for whether they are recognized on import
- The configuration list reconciled to the modification and effectivity history
- Change-impact of a modification on AD applicability and other status noted
- Modifications whose approval will not travel identified and listed for follow-up
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 embodied STC has an approval and a confirmed or flagged Canadian standing
- Service bulletin embodiment cites the revision and effectivity for the serial number
- Modification approvals are present, not merely referenced in the status report
- The configuration list reconciles to the modification and effectivity history
- Modifications with no recognized basis on import are flagged, not assumed accepted
Evidence normally required
- The modification and STC status report with effectivity
- STC files and their approval documentation
- Service bulletin embodiment records and revision history
- Approval and substantiation data for embodied modifications
- The configuration list or type-design reference for the serial number
Common discrepancies
- An embodied FAA STC with no confirmed Canadian standing
- A service bulletin shown embodied but recorded at the wrong revision
- A modification approval referenced in the status report but not present in the file
- A configuration list that does not reconcile to the modification history
What is at stake
A modification whose approval is not recognized on import becomes an open item: the change is embodied, the aircraft flies with it, but the basis TCCA needs is missing. An STC without a confirmed Canadian standing can force a validation exercise or, failing that, removal of the modification. A service bulletin recorded at the wrong revision can misstate the configuration the rest of the file rests on, and the error surfaces at the least convenient point in the import.
How the work runs
Tie each change to approval
Link every STC and embodiment to its approval data and effectivity.
Test Canadian standing
Establish which approvals are recognized on import and which need validation.
Mark the unrecognized changes
Identify modifications lacking a recognized basis and request the STC and approval files.
What the buyer receives
- An evidence map linking each modification to its approval and effectivity
- A gap list of modifications whose approval will not travel as recorded
- A request set for the STC files and approval data still to be recovered
Who uses the output
- Continuing-airworthiness teams settling the modification status for the Canadian register
- Acquisition teams sizing the STC validation an import could require
- Records staff recovering the STC and approval files the import will demand
How the work fits into the transaction or program
The review reads the modification status before the import, so changes without a recognized Canadian basis are known while there is time to validate or plan for them. Its gap list drives the recovery and validation, and its evidence map forms the modification section of the Canadian import package.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
An FAA STC is not automatically valid on a Canadian-registered aircraft, and a modification approval may need a separate validation on the receiving side. The review distinguishes changes whose approval is recognized from those that need Canadian standing established, so the importer sees which modifications are a filing question and which need validation.
Regulatory limits
The review assesses the modification records and reports the gaps. It does not approve or validate an STC, grant any approval, or make an airworthiness determination. Recognition of a modification's approval rests with the receiving operator and TCCA.
What this review does not cover
- Validating or approving an STC or any modification
- Developing modification or substantiation data
- Any airworthiness determination on the modified configuration
Specific to this review
- An FAA STC embodied on the aircraft does not carry automatic recognition on the Canadian side, so a change that looks approved can still need validation established.
- A service bulletin recorded at the wrong revision misstates the configuration the rest of the file depends on, and the error can propagate into AD applicability.
- The status report often reads settled precisely because the approval underneath a change is referenced rather than filed, which hides the gap until someone asks for the file.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Federal Aviation Administration. STC application process, certification basis, and continued airworthiness obligations of an STC holder.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Does an FAA STC stay valid once the aircraft is on the Canadian register?
Not automatically. An FAA STC often needs its Canadian standing established through validation before the receiving authority relies on it. The review flags STCs in that position so the importer can plan the validation, but it does not validate or approve any STC itself.
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.