EASA to TCCA import
EASA to TCCA modification and STC status transition review
This review checks whether the modification and STC status on an EASA-registered aircraft will satisfy Transport Canada on import. A records specialist runs it before the acceptance package is submitted, from the importing side. It works through the service-bulletin records, STC files, and configuration lists that establish what has been embodied, confirms the approval data behind each change and its effectivity for the serial number, then isolates the modifications a Canadian reviewer will question because their approval basis needs validation. You receive a modification status map tied to approvals, a gap list keyed to the import questions, and a document request set for the STC and approval files that are missing.
When this review is needed
- An EASA aircraft with an accumulated modification history is being imported to Canada and each embodied change has to be validated for the receiving authority.
- STCs were embodied under European approval and their acceptance on the Canadian register has to be established.
- The modification status report and the installed configuration disagree on what is actually embodied.
- A service bulletin was recorded as embodied at a revision that a Canadian reviewer will want confirmed.
The problem
Modification status is where an airframe's configuration history is most likely to have drifted from its approval basis, because changes are embodied under STCs, service bulletins, and minor modifications spread across operators and shops. Each embodiment was approved on data valid at the time, but the record of that data and its effectivity for the specific serial number is exactly what fragments. On import, Transport Canada asks how each modification was approved and whether its acceptance carries to the Canadian register, and an STC embodied years ago may need validation that was never contemplated when it was fitted.
What gets reviewed
- Embodied modifications and STCs reconciled to the recorded effectivity for this serial number
- The approval data behind each embodied change confirmed present and portable
- STC acceptance on the Canadian register assessed for each embodied STC
- Service-bulletin embodiments checked at the recorded revision against source
- The modification status report reconciled to the installed configuration
- Modifications structured so a Canadian reviewer can follow each to its approval basis
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 modification carries approval data appropriate to the change and the serial number
- Effectivity on every embodied change matches the serial number and its configuration history
- Each embodied STC has a path to acceptance on the Canadian register or is flagged for validation
- Service-bulletin embodiments are recorded at a revision the source documents support
- The installed configuration reflects every modification the status report claims and no more
Evidence normally required
Common discrepancies
- An embodied STC with no clear path to acceptance on the receiving register
- A modification recorded against effectivity that does not apply to this serial number
- A service bulletin recorded as embodied at a revision the records do not support
- A modification present in the configuration that the status report never captured
What is at stake
A modification whose approval cannot be traced or validated becomes an open item on the import, and an STC that does not carry to the receiving register may require validation or, if that fails, removal before the aircraft can be accepted. Reconstructing an STC file or arranging validation late in an import is slow and expensive, and an unrecorded modification discovered during acceptance can stall the whole package until its basis is established.
How the work runs
Assemble the embodied set
Gather the STCs, service bulletins, and modifications the records claim for the serial number.
Confirm data and effectivity
Check each change carries appropriate approval data and applies to this aircraft.
Test STC acceptance
Identify which STCs carry to the receiving register and which need a validation path.
Build the gap and request set
Log each unsupported change and name the file that closes it for the reviewer.
What the buyer receives
- A modification status map tying each embodied change to its approval basis
- A gap list organized around the modification questions the Canadian import raises
- A document request set for the STC and approval files to recover
Who uses the output
- Importers assembling the modification evidence in the TCCA acceptance package
- Engineering deciding how to treat an STC that does not carry to the receiving register
- Asset managers pricing the exposure of any modification that may need validation
How the work fits into the transaction or program
Modification-status review runs with the repair-approval and configuration work, since an STC, a repair, and an equipment change all bear on the configuration a Canadian reviewer examines. Its status map becomes the modification evidence Transport Canada reviews, and its gap list drives the STC-validation and file-recovery work that has to close before the aircraft can be accepted.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
An STC approved under one authority does not automatically hold on another register, so the review distinguishes modifications whose acceptance carries across from those that need a validation path before Transport Canada will accept them. Effectivity matters as much as approval here, because a change valid on the type can still be recorded against a serial number it never applied to, and the import is where that mismatch surfaces.
Regulatory limits
This review confirms and organizes modification evidence and identifies which changes need validation. It does not approve a modification, grant or validate an STC, or determine that the aircraft is in an airworthy configuration, all of which rest with Transport Canada and the approval holders.
What this review does not cover
- Obtaining or validating an STC on the receiving register
- Developing or approving new modification data
- Any airworthiness determination on the modified configuration
Specific to this review
- An STC valid under EASA does not automatically hold on the Canadian register, so the review separates modifications that carry across from those needing a validation path.
- Effectivity is where modification records break most often on import: a change can be genuine yet recorded against a serial number it never applied to.
- An unrecorded modification found during acceptance is harder to clear than a recorded one, because its approval basis has to be established from scratch under deadline.
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 STC embodied under EASA carry to the Canadian register automatically?
Not automatically. Approval by one authority does not bind another register, so each embodied STC needs a path to acceptance validated for Transport Canada, or the modification may require validation or removal. The review sorts the modifications that carry across from those that need that path before the import package goes out.
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.