After the migration
Tying the airworthiness review file back to sources after an MRO records migration
When an MRO migrates, scans, or re-indexes its records, this review tests whether the airworthiness review file still ties back to real source documents. Records control or quality teams commission it after the system change, before the next audit or customer handover exercises the file. Each certificate, finding disposition, and status reference in the file is traced to the document now holding it in the new structure. The output names every entry whose source went missing, was mis-filed, or lost legibility in the move, with a route to restore each link.
When this review is needed
- A records system cutover moved the airworthiness review file into a new folder and metadata structure.
- Paper review evidence was scanned and the originals are scheduled for offsite storage or destruction.
- An audit is approaching and nobody has sampled the migrated file against the legacy system.
- Customer aircraft are due for handover and the review evidence must be produced from the new index.
The problem
Migrations preserve counts, and counts lie. A folder that reports the right number of files can still hold the wrong revision, an unreadable scan, or a document indexed under another aircraft. The airworthiness review file is where this bites hardest, because its entries cite specific dispositions and status revisions, and a citation that resolves to the wrong document fails an audit as surely as a missing one.
What gets reviewed
- Review certificates and their issue records traced into the new index
- Finding dispositions matched to the documents that now carry the closing evidence
- Status report revisions cited by reviews located in their migrated form
- Legibility and completeness sampling across the scanned review evidence
- Metadata fields, aircraft assignment, and date attribution on migrated review records
- Legacy-system references that no longer resolve after the cutover
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
- A sampled review entry retrieves its source document through the new index alone, without legacy-system help
- Scanned dispositions are complete, legible, and include every page and signature the original carried
- Migrated metadata assigns each review record to the correct aircraft, date, and review cycle
- Certificate copies in the new system match the issued originals in revision and content
- Documents cited by more than one review resolve consistently wherever they are referenced
Evidence normally required
- Access to the new records system and, while it survives, the legacy structure
- The airworthiness review files for the affected aircraft or customer fleet
- Migration mapping tables, batch logs, or vendor completion reports
- The scanning specification and any quality-control sampling already done
Common discrepancies
- Multi-page dispositions truncated during scanning, with signature pages absent
- Review evidence indexed to the wrong tail number after a batch mapping error
- Cited status report revisions overwritten by later versions during the load
- Legacy shortcuts and cross-references that resolve to nothing in the new system
What is at stake
If broken links surface during an audit or a customer handover, the finding lands on the MRO's quality system, and the fix happens under scrutiny with the legacy system possibly already retired. Once original paper is destroyed, an illegible or mis-indexed scan becomes the only record, and reconstruction may no longer be possible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Stratify the sample
Build a sample across aircraft, review cycles, and migration batches, weighted toward known-risk batches.
Trace entry to source
Retrieve each sampled entry's source document through the new index and judge completeness and legibility.
Classify the failures
Sort defects into re-scan, re-index, legacy retrieval, and reconstruction cases with owners.
Close out with evidence
Deliver the reconciliation report and sampling record for the migration close-out file.
What the buyer receives
- A reconciliation report listing each review entry with a broken or doubtful source link
- Corrective actions per item: re-scan, re-index, retrieve from legacy, or reconstruct
- A sampling record the quality system can cite as migration verification evidence
Who uses the output
- Quality leadership answering for migration integrity at the next audit
- Records control staff executing the re-scan and re-index corrections
- Program managers confirming customer files are producible before handover
How the work fits into the transaction or program
This reconciliation belongs in the migration close-out, after the load completes and before legacy access or original paper disappears. Findings feed the correction queue while sources still exist, and the sampling record becomes part of the evidence that the quality system accepted the migration.
Jurisdiction-specific considerations
Retention duties under 14 CFR 91.417 and EU Regulation 1321/2014 follow the record whatever medium it lives in, so a migration that degrades retrievability degrades compliance even though no document was deliberately discarded. Mixed customer fleets mean the migrated file usually has to satisfy FAA and EASA expectations at once.
Regulatory limits
The reconciliation verifies that records survived a system change intact. It does not perform airworthiness reviews, approve the records system, certify the migration for regulatory purposes, or make any finding about the airworthiness of the aircraft the records describe.
What this review does not cover
- Executing the migration or operating the records system
- Wholesale re-scanning, which is scoped separately once the defect rate is known
- Review of record types outside the airworthiness review file
Specific to this review
- The reconciliation window closes when legacy access is switched off; after that, a doubtful record can no longer be compared against what it replaced.
- Batch scanning errors cluster: one mis-fed box can corrupt hundreds of pages, so sampling is stratified by batch rather than spread evenly.
- OCR quality on old thermal-paper certificates is poor enough that text search cannot be trusted as the retrieval path for early review evidence.
- Auditors increasingly ask for migration verification evidence itself, so the sampling record has value beyond the defects it finds.
Sources
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 the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
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 already reported 100 percent file counts. Why sample again?
Counts confirm that files moved, nothing else. They do not confirm the file is legible, attributed to the right aircraft, or the revision the review cited. Those are the failures audits find, and only document-level sampling detects them.
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.