Register to source
Non-routine register source reconciliation for operators
Once an operator's records pass through a scanning program, a system migration, or a re-indexing effort, the non-routine register can point at cards, dispositions, and corrective-action evidence that no longer sit where the references say. This reconciliation walks the register line by line and re-establishes the path from each entry to its signed card and the engineering behind it in the new structure. Records leadership typically schedules it before the next authority audit or lease event consumes the data. It produces a corrected reference set and a short list of entries whose evidence is genuinely gone rather than mislocated.
When this review is needed
- A scanning project digitized years of check packages and register references were never updated to the new image locations.
- The maintenance system changed and non-routine identifiers were renumbered or truncated in the mapping.
- Auditors previously accepted paper retrieval and will now test the electronic path for the first time.
- A lease return is a year out and the team wants register integrity proven before external reviewers rely on it.
The problem
The register is a list, and lists migrate easily; the evidence behind each line does not. Dispositions filed as engineering correspondence land in a different scan batch than the cards they authorize, corrective-action attachments get flattened into multi-hundred-page PDFs, and renumbered identifiers quietly break the join between the register and the card images. Everything looks orderly until someone requests one specific closed defect and the trail dead-ends.
What gets reviewed
- Register entries sampled across check events, defect classes, and scan or migration batches
- Each sampled entry resolved to its card image, disposition, and corrective-action evidence in the current system
- Identifier mapping between old and new numbering schemes verified
- Multi-document closures, card plus engineering plus attachments, checked for co-location or valid cross-reference
- Deferral records reconnected to the register entries they authorized
- A census of register lines whose evidence cannot be located by any path
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 register entry chosen at random resolves to its complete closure evidence within the documented retrieval procedure
- Old-format non-routine numbers map one-to-one to new identifiers with no collisions
- Engineering dispositions referenced by sampled cards exist as retrievable documents, none as broken pointers
- Scanned card images carry the pages the paper card had, verified against batch page counts where available
- Entries marked closed in the register never resolve to cards that are unsigned or still open
Evidence normally required
- The non-routine register in its current and, if available, pre-migration form
- Access to the records system, scan repositories, and any surviving legacy references
- Scanning batch manifests and migration mapping tables
- Engineering and deferral logs for the covered period
- The operator's documented retrieval procedure
Common discrepancies
- Register references built on a folder naming convention the scanning vendor did not replicate
- Dispositions digitized into a general correspondence archive with no defect number in the metadata
- Identifier truncation during migration merging two different defects into one reference
- Attachment pages, photos and measurement sheets, dropped during PDF flattening
What is at stake
Dead-end references accumulate silently and then all surface in the same week, usually the week an auditor or lessor starts sampling. Each failed retrieval forces a manual archaeology exercise through scan batches and old folder trees, and items that cannot be reconnected get treated as undocumented defects even though the work was done and signed. Confidence in the whole register erodes from a handful of failures.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map the identifiers
Reconstruct the numbering translation between the pre-migration register and the current system.
Sample and resolve
Pull register entries across batches and defect classes and follow each to its closure evidence.
Repair the joins
Build corrected references and metadata for every entry that resolved by a nonstandard path.
Isolate true gaps
Document entries with no surviving evidence path and hand them to remediation.
What the buyer receives
- A repaired cross-reference table from register entry to current document locations
- A census of unresolvable entries, each with the search paths already exhausted
- Metadata correction batches ready to load into the records system
- A retrieval demonstration script usable at the next audit
Who uses the output
- Records and document-control staff loading the corrected references
- Continuing-airworthiness management demonstrating register integrity to auditors
- Redelivery project teams inheriting a register they can sample without surprises
How the work fits into the transaction or program
Reconciliation converts a migration from finished-on-paper to finished-in-practice. It runs after the technical cutover and before external reliance, and its unresolvable-entry census hands off cleanly to gap remediation, where recovery from MROs or paper archives is pursued item by item.
Jurisdiction-specific considerations
Both regimes expect defect-rectification evidence to remain producible: FAA record rules under 14 CFR 91.417 and the operator equivalents on one side, EASA continuing-airworthiness record requirements under Regulation 1321/2014 on the other. Neither regime cares whether a failure to produce stems from loss or from mislocation; the operational duty is retrieval, which is exactly what this reconciliation tests and repairs.
Regulatory limits
The work repairs references and proves retrieval. It does not re-open or re-certify defect closures, does not create substitute engineering, and makes no finding about the airworthiness significance of any defect. Entries that stay unresolvable are reported as documentation gaps for the operator and its CAMO to disposition.
What this review does not cover
- Recovering missing documents from third parties, handled as a separate remediation effort
- Judging the technical adequacy of historical dispositions
- Re-platforming or configuring the records system itself
Specific to this review
- Register-to-card joins usually break at identifier boundaries: prefix changes, leading-zero handling, and truncation account for most failed lookups after a migration.
- Photographic attachments are the least likely element to survive digitization because they were often stored physically apart from the card that references them.
- Sampling by scan batch rather than by aircraft finds systematic breaks faster, since a bad batch damages every defect it contains regardless of tail.
- An operator that can demonstrate scripted retrieval of a random register entry tends to see auditors reduce their sample; failed first retrievals have the opposite effect.
- The oldest register lines resolve worst after a migration yet matter most at a transaction, because early-life repairs carry the longest evidence chains; sampling should cover age bands deliberately.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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
Is a full register walk necessary, or does sampling suffice?
Start with a stratified sample across scan batches and identifier eras. Breaks after migrations are systematic rather than random, so a sample that covers each batch and numbering scheme finds the failure patterns, and the full-register repair can then be scripted instead of manual.
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.