Program status at transfer
Maintenance program records in import, export, and registry-change packages
Before a registry change, the maintenance program status in the transfer package has to trace to an approved program, and this review confirms that it does. It compares the task due list against the program revision actually approved for the exporting operator, verifies check history and escalations against their approvals, and flags every interval that has drifted from the approved basis. Records specialists run it during import, export, or registry-change preparation, ahead of the authority filing. The transition lead receives an exception list keyed to the source document behind each unsupported line.
When this review is needed
- The importing operator is building a bridging analysis and needs certainty about which program revision the status was computed against.
- An export application quotes check compliance the seller's team has not verified against completion evidence.
- Escalations or short-term extensions were used in the final months of operation and the approvals need to be located.
- The registry change moves oversight between FAA and EASA and the program approval trail must be shown to the receiving authority.
The problem
Maintenance program status is generated by the operator's tracking system, and the system reflects whatever intervals were loaded into it. Over years of program revisions, escalations, and fleet-level changes, loaded intervals drift away from the approved document. At export, the status summary looks authoritative precisely because it is machine-printed, yet nobody has recently checked that its basis matches the approval letter that governs it.
What gets reviewed
- The task due list, sampled against the intervals in the approved program revision
- Check history and completion evidence for the checks the status claims as accomplished
- Escalations, tolerances, and short-term extensions used, together with their approvals
- Airworthiness limitation and ICA tasks, verified against the controlling documents rather than the tracking system alone
- The program approval trail: approval letters, revision history, and the operator or CAMO holding the approval
- Utilization figures feeding the due calculations, cross-checked to the aircraft records
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 revision cited on the status header is the revision the approval on file actually covers
- Sampled task intervals in the due list match the approved program document line for line
- Every claimed check completion is backed by a work order, certificate of release to service, or equivalent closure evidence
- Each escalation or extension applied within the review window carries its approval or is flagged
- ALS and ICA task tracking agrees with the current revision of the controlling limitation documents
Evidence normally required
- The current maintenance program document with its approval letter and revision record
- A full task due list export from the tracking system, with the basis data visible
- Check completion records for the checks inside the review window
- Escalation and extension files, including approvals and supporting justifications
- The draft export or import package and any questions already received from the authority
Common discrepancies
- A due list computed against a newer program revision than the one the approval letter covers
- ALS tasks tracked at intervals that lag a revision of the limitations document
- A short-term extension used near the end of operation with no approval evidence in the file
- Check completions asserted on the status that have no closure record in the delivered package
What is at stake
If the receiving authority or the importing operator's CAMO finds the due list computed on a basis the approval does not cover, the whole status loses credibility at once. Bridging work restarts from source documents instead of the summary, the transfer timeline absorbs the delay, and tasks that seemed comfortably inside their intervals may prove overdue on the approved basis.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the approved basis
Establish the exact program revision, approval, and limitation documents that govern the status.
Sample the due list
Compare tracked intervals and due calculations against the approved documents, weighting ALS and high-consequence tasks.
Verify claimed compliance
Trace check completions, escalations, and extensions to their closure and approval evidence.
Report for the bridge
Deliver the exception list and verified basis statement in a form the bridging analysis can consume.
What the buyer receives
- A line-referenced exception list mapping each unsupported status entry to its missing or conflicting source
- A verified statement of which program revision and approval govern the status as delivered
- Inputs the importing operator's team can carry straight into the bridging analysis
- A prioritized retrieval list for approvals and completion evidence still to be located
Who uses the output
- The importing operator's CAMO or planning group building the bridge to the new approved program
- Transition leads answering authority questions on program compliance
- Technical-records managers on the exporting side closing gaps while the previous operator is still reachable
How the work fits into the transaction or program
Program status is the spine the rest of the transfer package hangs on: task cards prove the checks it claims, the deferral log carries its open items, and the logbooks carry its utilization. This review runs early in the package sequence because a shifted program basis changes what every other record set has to prove.
Jurisdiction-specific considerations
FAA operators hold their program under Part 121 or 135 with the associated operations specifications, while EASA operators manage theirs through an approved AMP under Part-CAMO, and ICAO Annex 6 shapes what third-country authorities ask for at import. The review reads the status against the framework it was approved under, then flags what the destination framework will ask to see.
Regulatory limits
Nothing in this review approves a maintenance program, amends one, or determines compliance with it. It establishes what the delivered evidence supports and where it conflicts. Program approval remains with the competent authority, and compliance determinations remain with the operator and its CAMO.
What this review does not cover
- Writing or revising the bridging analysis itself
- Recommending program escalations or interval changes
- Auditing the operator's tracking-system configuration beyond the sampled evidence
Specific to this review
- Interval drift between the tracking system and the approved document is a slow defect: it accumulates through revisions and rarely announces itself until a transfer forces a line-by-line comparison.
- A due-list snapshot ages quickly during a drawn-out export; a status printed at deal signing can be materially wrong by the registry date.
- Authorities compare the revision cited on the status header with the approval letter before they look at any individual task, so a header mismatch undermines the package immediately.
- The importing operator's bridging analysis inherits every error in the exported status, which is why receiving CAMOs increasingly ask for source verification rather than the summary alone.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
Can the importing operator not simply rebuild the status on its own program?
It will, through the bridging analysis, but the bridge starts from the exporting status. If that status rests on an unverified basis, every bridged interval inherits the doubt. Verifying the source once, before transfer, costs far less than discovering the drift after the aircraft is flying under the new program.
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.