FAA to TCCA transition
FAA to TCCA maintenance program records transition review
This review reads an aircraft's FAA-side maintenance program history and asks whether it will bridge cleanly onto a Canadian operator's program. It is run for the receiving side, or the party selling into it, before the program status transfers. The work traces each approved revision and task escalation to its source, tests any prior bridging against the intervals now flown, and expresses the current status so a Canadian reader can evaluate it without the outgoing operator present. You receive an evidence map keyed to the bridging questions, a gap list of program elements that will not carry as recorded, and a request set for the studies and approvals still missing.
When this review is needed
- A US-registered aircraft is moving onto a Canadian operator's program and its history has to bridge to it.
- A buyer wants the program record set read before it commits to bridging the tail onto its Canadian program.
- Escalated intervals were justified under the FAA operator and the study behind them has to travel.
- A redelivery is imminent and the program status has to stand without the outgoing operator's context.
The problem
A maintenance program that ran under an FAA operator is built on that operator's revisions, its escalation studies, and any bridging done at earlier transfers, all of which read naturally inside the team that maintained them. Moving the aircraft onto a Canadian program means that history has to be legible to a receiving team that never saw it, and task intervals earned by a reliability program, revisions approved under one authority, and old bridging all have to hold up when someone else picks them up cold.
What gets reviewed
- Each approved program revision traced to the approval behind it
- Task escalations checked against the study or engineering basis claimed
- Prior bridging analyses read for whether they still match the intervals flown
- Current task status reconciled to the revision the aircraft is actually on
- Source references confirmed to resolve to retrievable documents
- Program status expressed so a Canadian reader can evaluate it independently
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
- Every interval flown is anchored to a revision that carries a formal approval, not an interim draft
- Each extended interval points to an engineering or reliability basis that sits in the file
- Any earlier bridging still matches the tasks and intervals the aircraft runs today
- Program status figures line up with the recorded utilization and the last checks accomplished
- Citations under each program line lead to a document that can actually be pulled
Evidence normally required
- The approved program in force with the full sequence of its revisions
- The engineering and reliability studies behind any interval extension
- Earlier bridging work performed when the tail last changed programs
- A current task status showing where the aircraft stands against the program
- The check history evidencing what was done against each program task
Common discrepancies
- An extended interval whose justification is referenced yet absent from the file
- A revision the aircraft has been flown to that carries no approval on record
- Earlier bridging that has fallen out of step with the intervals now in force
- Program status numbers that do not agree with the most recent check record
What is at stake
A program history that cannot be reconstructed from the records leaves the receiving operator with intervals it cannot defend and escalations it may have to reset to a conservative baseline. That means unplanned tasks at the first check, a program that reads as unsupported to the receiving authority, and a bridging exercise that stalls while the study behind an escalated interval is chased down after the fact.
How the work runs
Gather the program record
Collect the approved program in force, its revision chain, and the status flown against it.
Anchor revisions and extensions
Link every revision to its approval and every extended interval to the study that earned it.
Re-test earlier bridging
Measure any prior bridging against the intervals in force now and note where it has slipped.
Frame for the receiving side
Put the status in terms a Canadian reader can judge and set out what is still outstanding.
What the buyer receives
- An evidence map tying each program element to the bridging question it answers
- A gap list of elements that will not carry onto the Canadian program as they stand
- A prioritized request for the studies and approvals that still have to be pulled
Who uses the output
- Continuing-airworthiness staff planning how the tail joins their Canadian program
- Asset managers estimating the program rework the move will demand
- Records staff building the program file the receiving operator will sign off
How the work fits into the transaction or program
The work happens before the receiving operator starts bridging, so the FAA-side history reads clearly before anyone tries to map it across. The gap list sets the recovery agenda, and the evidence map anchors the program portion of the import file.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
A Canadian operator structures its program and its reliability oversight on its own lines, unlike the FAA operator that built the history. The review marks the FAA-side constructs, such as an interval extended on that operator's reliability record, that the receiving operator has to re-justify in its own terms rather than adopt as translated.
Regulatory limits
The review states what the program records will and will not support. It stops short of approving a program, authorizing an interval, or issuing an airworthiness finding. Whether the program bridges and is accepted stays with the receiving operator and TCCA.
What this review does not cover
- Writing or amending the receiving operator's program
- Running the reliability study that would justify an interval extension
- Any acceptance or airworthiness call on the tail or its program
Specific to this review
- An extended interval is the item most likely to fail here, since the number rides in the status while the justification that earned it stays behind with the outgoing operator.
- Earlier bridging silently expires as intervals move, so a prior analysis is re-tested against today's tasks rather than the ones it was written against.
- A revision can be flown for years with no approval on file, a gap that appears only when the receiving team calls for the document that authorized it.
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
How is this different from the maintenance program review for an EASA to FAA move?
The evidence types are similar, but the receiving system is Canadian and the constructs that need re-justifying are the FAA operator's, not an EASA CAMO's. The review is scoped to how a Canadian operator organizes its program, so the bridging questions and the flagged constructs are specific to this direction of transfer.
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.