Registry change
Maintenance program records review for a registry change
A registry-change maintenance program review confirms that the program the aircraft has been maintained to can be reconciled with the program it will move onto, and that the evidence supports the bridge. It is run for the team preparing the transition, before handover, on the approved program revisions, task escalations, and source-document links the receiving authority will test. The work traces the current program to its approved basis, checks the escalations and bridging analyses, and identifies where the outgoing intervals do not map cleanly onto the receiving program. You receive a program status view keyed to the maintenance program record, a bridging gap list, and a request set for the missing program evidence.
When this review is needed
- An aircraft is changing register and the receiving authority requires the maintenance program bridged to its own basis.
- The current program carries task escalations that the receiving side will re-examine against the source document.
- Program revisions were applied over the years without a consolidated trail to the approved basis.
- A handover date is fixed and the team needs to know where the outgoing intervals will not map to the new program.
The problem
A maintenance program is a living document, and a registry change asks whether every escalation, revision, and deviation on it can be defended to a new authority. Intervals that were approved under the outgoing program do not automatically transfer, and the source-document trail behind an escalation is exactly the thing that goes thin over years of revisions. The team preparing the transition has to show that the program the aircraft flew and the program it will fly are the same story, task by task.
What gets reviewed
- The current program traced to its approved revision and the basis behind it
- Task escalations checked against the source document or sampling that justified them
- Bridging analysis between the outgoing intervals and the receiving program
- Repetitive and threshold tasks reconciled to current time and cycle status
- Deviations and short-term extensions confirmed to be closed or carried with a basis
- Tasks whose intervals do not map cleanly onto the receiving program isolated for bridging
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 program in use traces to an approved revision rather than an uncontrolled working copy
- Each task escalation cites the source document or reliability basis that justified it
- Next-due data for repetitive tasks reconciles to current hours and cycles
- Bridging between the outgoing and receiving intervals is explicit for every mapped task
- Open deviations or extensions carry a stated basis and a close-out path
Evidence normally required
- The approved maintenance program and its revision history
- Task escalation justifications and source-document references
- Any prior bridging analysis and the receiving program for interval mapping
- Current total time and cycles for next-due reconciliation
- Deviation and extension records against the program
Common discrepancies
- A task escalation with no source-document basis retrievable behind it
- A repetitive task whose next-due data does not reconcile to current cycles
- An interval that does not map cleanly between the outgoing and receiving programs
- An open extension carried on the program with no close-out basis recorded
What is at stake
A program that cannot be bridged leaves the receiving side unable to set the next-due picture, so tasks get pulled forward to a conservative interval and checks land early and expensive. An escalation with no source-document basis can be rolled back on the new register, compressing the maintenance schedule the moment the aircraft transfers.
How the work runs
Trace the current program
Confirm the program in use maps to an approved revision and its documented basis.
Test the escalations
Check each escalated interval against the source document or reliability data that justified it.
Map the bridge
Reconcile the outgoing intervals against the receiving program and flag the tasks that do not translate.
Project the next-due
Set the next-due picture on the receiving program and list the evidence still to recover.
What the buyer receives
- A program status view tying the current program to its approved basis
- A bridging gap list mapping outgoing tasks to the receiving program and flagging the mismatches
- A document request set for the escalation justifications and program evidence still needed
Who uses the output
- Continuing-airworthiness leads bridging the program to the receiving authority's basis
- Maintenance planners projecting the next-due picture on the new program
- Records teams recovering the source-document trail behind the escalations
How the work fits into the transaction or program
The program review anchors the transition's forward-looking side, where the AD, LLP, and modification strands settle the aircraft's past. Its bridging gap list tells the receiving planners which tasks land early on the new program, so the maintenance schedule after the change is set on evidence rather than a conservative guess.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA, EASA, and TCCA approve maintenance programs on different bases, and ICAO Annex 6 sets the floor both build on. An escalation defensible under the outgoing program may need its source-document basis re-shown for the receiving one, and the review flags where the two programs diverge.
Regulatory limits
The review reconciles the program records and maps the bridge to the receiving program. It does not approve a maintenance program, grant an escalation, set intervals on an authority's behalf, or determine that the aircraft is airworthy under either program.
What this review does not cover
- Authoring, revising, or approving the maintenance program
- Granting or approving a task escalation or interval extension
- Any airworthiness determination under the outgoing or receiving program
Specific to this review
- Approved intervals do not transfer with the aircraft; the receiving program sets them, so an escalation without a defensible basis compresses the schedule after the change.
- The source-document trail behind an escalation is the first thing to thin over years of revisions and the first thing the receiving authority asks for.
- Bridging is a task-by-task translation, not a copy, so mismatched intervals are the transition items that decide when the next check lands.
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
Will our escalated intervals carry over to the new register?
Not automatically. The receiving authority sets the program the aircraft moves onto, and an escalation has to be defensible on that basis or it can be rolled back. The review checks each escalation against its source-document justification and maps the bridge so the receiving planners set the next-due picture on evidence.
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.