EASA to TCCA import
EASA to TCCA maintenance program records transition review
This review checks whether an EASA-registered aircraft's maintenance program records will bridge cleanly to the receiving operator's Canadian program on import. A records specialist runs it before the acceptance package is submitted, from the importing side. It works through the approved program revisions the aircraft was maintained under, the task escalations and variations applied to it, and the source documents behind them, then builds the bridging picture a Canadian operator and Transport Canada will examine. You receive a program status map, a bridging gap list keyed to the import questions, and a document request set for the revision and escalation evidence that is missing.
When this review is needed
- An EASA aircraft is being imported to Canada and its maintenance history has to bridge to the receiving operator's program.
- The aircraft was maintained under a CAMO-controlled program whose task intervals differ from the Canadian program it is entering.
- Task escalations and variations were applied that a Canadian reviewer will want justified against source.
- The last-accomplished status of program tasks has to be established before the aircraft flies under Canadian oversight.
The problem
Two operators rarely maintain an aircraft under the same program, so an import is a bridging exercise, not a copy. The EASA aircraft carries a task history built under an approved program with its own intervals, escalations, and variations, and the receiving Canadian operator's program sets different ones. The record of when each task was last accomplished, and on what interval basis, is what has to survive that translation, and escalations applied years ago under a CAMO can be exactly the entries whose source justification is hardest to produce on demand.
What gets reviewed
- The approved program revisions the aircraft was maintained under, confirmed against the task history
- Task escalations and variations checked against their source justification
- Last-accomplished status established for the tasks that bridge to the Canadian program
- Bridging points identified where the EASA intervals and the Canadian program diverge
- Source-document references confirmed for the program basis relied on
- The program status structured so the receiving operator can map it to its own program
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 task's last-accomplished status is supported by the accomplishment record behind it
- Task escalations and variations trace to a source justification the receiving operator can rely on
- The program revision the aircraft was maintained under matches the approved revision on file
- Bridging points where intervals diverge are identified and no task is left unmapped
- No program task shows a last-accomplished basis that the records cannot substantiate
Evidence normally required
- The approved maintenance program and its revision history for the aircraft
- The task accomplishment history and last-done status
- Escalation and variation approvals with their source justification
- The receiving operator's Canadian program for interval mapping
- CAMO or continuing-airworthiness records controlling the program
Common discrepancies
- A task escalation applied without the source justification on file
- A last-accomplished status that cannot be reconciled to an accomplishment record
- A program task whose interval does not map cleanly to the Canadian program
- A program revision the aircraft was maintained under that differs from the approved revision of record
What is at stake
An aircraft inducted on an unbridged history carries hidden task or interval gaps that surface at the first check under the Canadian program, sometimes as a task already overdue by the receiving intervals. If an escalation cannot be justified against source, the receiving operator may have to revert the task to its baseline interval, which can pull maintenance forward and disrupt the induction schedule the import was planned around.
How the work runs
Fix the program basis
Confirm the approved program revisions and the task history the aircraft was maintained under.
Test the escalations
Check each escalation and variation against its source justification.
Map the bridge
Compare the aircraft's intervals to the receiving program and flag where they diverge.
Build the gap and request set
Log each unbridged or unsupported task and name the evidence that closes it.
What the buyer receives
- A program status map with last-accomplished status per task
- A bridging gap list mapping the aircraft's history to the receiving program
- A document request set for the revision and escalation evidence to recover
Who uses the output
- Importers assembling the program evidence in the TCCA acceptance package
- Continuing-airworthiness teams bridging the aircraft onto the receiving operator's program
- Maintenance planners sequencing the induction around any task the bridge pulls forward
How the work fits into the transaction or program
Maintenance-program review sits at the point of induction, between the exporting operator's release and the first check under the Canadian program. Its bridging gap list drives the interval-mapping work the receiving operator has to complete, and it feeds directly into the induction planning that the AD and life-limited part positions also inform.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
The receiving Canadian operator maintains under its own approved program, so the aircraft's EASA task history has to bridge to those intervals rather than transfer unchanged. Escalations approved under the exporting CAMO do not automatically carry to the receiving program, so the review establishes which task positions survive the bridge and which revert to a baseline interval the Canadian operator sets.
Regulatory limits
This review bridges and reconciles the program records so the receiving operator can map the aircraft onto its program. It does not approve a maintenance program, accept an escalation on the operator's behalf, or make an airworthiness determination, which rest with the receiving operator and Transport Canada.
What this review does not cover
- Authoring, approving, or revising the receiving operator's maintenance program
- Accomplishing or signing off any program task
- Any airworthiness determination on the aircraft
Specific to this review
- A task escalation approved under the exporting CAMO does not carry to the receiving program on its own, so the review establishes which positions survive the bridge and which revert to baseline.
- The bridge, not the copy, is the work: a task shown current under EASA intervals can already be overdue against the receiving Canadian program's shorter interval.
- Escalation source justification is the hardest program evidence to produce late, because it was filed once at approval and rarely carried forward with the aircraft.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Can we carry the aircraft's EASA program status straight onto the Canadian operator's program?
No. The receiving operator maintains under its own approved program, so the task history has to bridge to those intervals. Escalations approved under the exporting CAMO may not carry across, and a task shown current under the old intervals can already be overdue under the new ones, which is exactly what the bridging review surfaces before induction.
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.