After the records move
Maintenance-program source reconciliation for lessors after records migration
When a lessor migrates records into a new repository, digitizes a paper archive, or re-indexes a returned aircraft's files, the maintenance-program status can detach from the documents that once supported it. This reconciliation re-ties every element of that status, the governing revision, each escalated interval, and each bridge from a prior operator, to a locatable source document in the new structure. A records specialist runs it after the migration settles and before the next remarketing effort or audit relies on the data. Output is a findings list showing exactly which status entries lost their source and where the recovered document now lives.
When this review is needed
- A returned aircraft's records were scanned and loaded into the lessor's repository and the index has never been proven against the originals.
- The asset is being remarketed and prospective lessees will pull program documents from the new system.
- A repository change split the program file across folders and staff can no longer find escalation approvals on demand.
- An upcoming lessor audit or portfolio review will test whether status data traces to source.
The problem
Migration projects are judged on volume moved, so an aircraft's program file can arrive complete on paper yet unusable in practice: revisions filed under the wrong ATA chapter, escalation letters buried in general correspondence, bridging analyses left in a prior batch that never uploaded. Status spreadsheets keep circulating unchanged, which hides the break until someone actually needs the document behind a number.
What gets reviewed
- Index-to-document verification for the maintenance-program section of the migrated records
- Governing program revisions located and matched to the revision the status data cites
- Escalation approvals and their supporting reliability submissions traced into the new structure
- Bridging analyses from each operator in the aircraft's history located and legibility-checked
- Task due list entries sampled against the source records the new index points to
- Orphaned documents in the migrated set identified and mapped back to status entries
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 entry in the program index resolves to a legible document, no placeholder pages or duplicate scans
- The revision the due list runs on exists in the repository and matches the one the status report names
- Every escalated interval in the status data has its approval letter findable through the new index
- Sampled last-done references open the correct work package rather than a neighboring scan batch
- Documents present in the repository but absent from the index are surfaced rather than silently ignored
Evidence normally required
- The migrated or re-indexed records set with its current index
- Maintenance-program status report and task due list in use
- Pre-migration index or shipping manifest, if one exists
- Delivery and redelivery document lists from the most recent lease
- Access to the original scans or paper archive for legibility disputes
Common discrepancies
- Escalation approvals present as scans but indexed under correspondence, invisible to anyone searching by task
- A program revision that exists only as a transmittal letter, with the revision content itself never uploaded
- Due-list entries pointing at a document reference scheme from the old repository that no longer resolves
- Two scan batches of the same event with different legibility, only the worse one indexed
What is at stake
The break surfaces at the worst moment, typically when a prospective lessee's technical team requests the approval behind an escalated interval during remarketing. Producing it late, or failing to, stalls the campaign and casts doubt on the rest of the records. Meanwhile any decision made from the unverified status, maintenance forecasting or reserve calculations included, inherits the same uncertainty.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Freeze the baseline
Capture the status report, due list, and current index as the reconciliation reference.
Walk the index
Resolve each program-section index entry to its document and grade legibility and completeness.
Trace status to source
Work the due list and escalation register back through the index to the approving documents.
Fix and document
Deliver the corrected index, the unresolved findings, and the repository fix specification.
What the buyer receives
- A reconciled index for the program section, entry by entry
- A findings list of status elements whose source could not be located, with a recovery action for each
- A short data-fix specification the records team can apply to the repository
- A verification memo suitable for the next audit or remarketing data room
Who uses the output
- Lessor technical-records teams correcting the repository before the next handover
- Remarketing teams assembling a data room a lessee's reviewers can actually navigate
- Portfolio and audit functions evidencing that migrated status data traces to source
How the work fits into the transaction or program
Reconciliation sits between the migration project and any event that consumes the records: remarketing, delivery to a new lessee, or an audit. It closes the loop the migration opened, and its findings list feeds directly into gap remediation where a source document turns out to be genuinely missing rather than misfiled.
Jurisdiction-specific considerations
Lessor portfolios mix regimes, so the same repository may hold FAA-operated aircraft whose program basis lives in operator specifications and EASA aircraft whose basis is a CAMO-managed program under Regulation 1321/2014. Reconciliation has to respect which regime's document types anchor each aircraft's status, since an index scheme tuned to one will misfile the other.
Regulatory limits
This work establishes where documents are and whether they support the recorded status. It does not approve programs or escalations, does not re-perform bridging analyses, and makes no airworthiness determination. Regulatory acceptance of the program remains with the operating CAMO and its authority.
What this review does not cover
- Executing the migration or scanning work itself
- Recovering documents from prior operators, which is handled as gap remediation
- Building or revising the maintenance program
Specific to this review
- Digitization vendors index by document appearance, and an escalation approval looks like ordinary correspondence, which is why program approvals are among the most frequently misfiled items in scanned lessor archives.
- Status spreadsheets survive migrations untouched, so the data can look continuous even when half its source references no longer resolve.
- The cheapest time to reconcile is immediately after migration, while the pre-migration index and the scanning vendor's batch logs still exist.
- A lessee's technical reviewers judge records quality by retrieval speed; a complete but unfindable approval reads the same as a missing one during remarketing.
- Aircraft between leases have no operating CAMO watching the program file day to day, so the lessor's reconciliation is the only integrity check the records get during that window.
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
The migration vendor certified 100 percent of pages transferred. Why reconcile?
Page counts prove volume, not meaning. A complete page set can still leave escalation approvals unfindable, revisions filed as correspondence, and due-list references pointing at the old repository's numbering. Reconciliation tests whether the status data still connects to its evidence, which is what the next auditor or lessee will test.
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.