Digital records quality
Digital records index review for the engine-module file
Scanning an engine records file is not the same as making it usable. This review evaluates the digital records index for an engine or module file against the source material: whether each scan is legible and searchable, whether its metadata ties it to the right serial number and event, and whether the indexed image matches the paper or system record it claims to represent. It is run when a digitized file will be relied on for a transfer, shop-visit review, or day-to-day continuing-airworthiness work. The result is an exception list of index entries that cannot retrieve, cannot be trusted, or cannot be tied to the asset.
When this review is needed
- A scanning project has finished and the paper is about to go to deep storage or destruction, making this the last cheap moment to catch bad scans.
- A counterparty will work from the digital file in a data room and every unretrievable document will become a query.
- Two records systems were merged after an acquisition or CAMO change and the combined index has never been validated.
- Day-to-day users report that searches miss documents they know exist, which signals metadata rot rather than missing records.
The problem
Digitization projects are scoped by page count, so quality problems concentrate where the source material was hardest: faded thermal paper from test cells, oversized disk sheets folded into binders, multi-part shop travelers stapled out of order. The index inherits whatever the scanning operator typed on a deadline, which means serial numbers with transposed digits, events dated by scan date instead of event date, and module documents filed under the parent engine. The file looks complete in the dashboard and fails in the first real search.
What gets reviewed
- A structured sample of index entries resolved to their images and judged for legibility and completeness
- Metadata fields checked for accuracy: serial number, document type, event date, and module assignment
- Search behavior tested with the queries a transfer review or shop-visit reconciliation would actually run
- Scans compared against surviving source paper or system records for fidelity where available
- Module-level filing checked so documents follow the module serial, given engine module swaps
- Coverage of the index measured against the file's known contents, including test-cell and disk-sheet material
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 index entry retrieves an image that is legible end to end, including stamps and signatures
- Metadata on the sample matches the document face, with event dates from the document rather than the scan batch
- Documents for a swapped module are indexed to the module serial and not stranded under a former parent engine
- Multi-page records are complete and in order, with no pages absorbed into a neighboring document
- Searches by serial number, document type, and date window return the records a manual pull confirms exist
Evidence normally required
- Access to the digital records system and its index export
- The surviving source material: paper binders, shop packages, or the originating systems
- The engine and module serial-number history, including swap dates
- The scanning project's conventions, if documented, for naming and metadata
- A list of the file's known high-value documents to test coverage against
Common discrepancies
- Test-cell printouts scanned from faded thermal paper that are present in the index yet unreadable in the image
- Event dates populated with the scan-batch date, which destroys chronological search across the whole batch
- Module documents indexed under the engine that carried the module years ago, invisible to a search on the current serial
- A stapled shop traveler split across two index entries, each looking complete on its own
What is at stake
An index that cannot retrieve a document is operationally identical to a missing document, except the team believes it has it and finds out otherwise mid-transaction. Data-room reviews price this in: unretrievable evidence gets treated as absent, and remediation happens under counterparty deadlines instead of internal ones. If the paper was destroyed after scanning, a bad scan is no longer a quality issue but a permanent gap.
How the work runs
Profile the index
Map document classes, metadata conventions, and volumes, and identify the high-risk source material.
Sample and resolve
Pull a stratified sample of entries, retrieve each image, and grade legibility, completeness, and metadata accuracy.
Test real retrieval
Run the searches that transfers and shop reviews depend on and compare results against manual pulls.
Specify corrections
Deliver the exception list and a correction spec while the source material is still accessible.
What the buyer receives
- An exception list of index entries that fail retrieval, legibility, metadata, or fidelity checks
- A quality assessment by document class showing where the index can be relied on and where it cannot
- A correction specification the scanning vendor or records team can execute against
Who uses the output
- Records managers deciding whether the paper can be released to storage or destruction
- Teams preparing the digital file for a data room or records transfer
- CAMO staff who need search results they can act on without manual re-verification
How the work fits into the transaction or program
Index quality is upstream of every other source review on this file: an LLP trace, a shop-visit reconciliation, or a binder check all assume the index can produce documents on demand. Running this review first means later reviews measure the records, and this review runs cheapest immediately after scanning, while the source paper still exists to correct against.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA guidance in AC 120-78 addresses electronic recordkeeping and what makes a digital record acceptable, while AC 43-9c frames the underlying content expectations; on the EASA side, Regulation 1321/2014 requires records be kept in a manner that ensures legibility and accessibility for their retention periods. None of these fix an index format, so the review tests against the practical standard: can the organization produce a legible, attributable record when the authority or counterparty asks.
Regulatory limits
The review evaluates the digital index and its fidelity to source. It does not rule on whether the underlying maintenance was performed or properly certified, does not constitute acceptance of an electronic recordkeeping system by any authority, and does not make airworthiness determinations from the records it samples.
What this review does not cover
- Rescanning or metadata correction itself, which follows as remediation
- Legal advice on record retention or destruction of source paper
- Review of the substantive maintenance content beyond fidelity to source
Specific to this review
- The window for cheap correction closes when the paper leaves the building: after that, every bad scan is a reconstruction project instead of a rescan.
- Scan-batch dating is the single most destructive common defect because it corrupts every chronological search silently, without any entry looking wrong on its own.
- Module swaps defeat naive indexing schemes: a disk sheet filed under the engine that hosted the module in 2019 is effectively lost to a 2026 search on the module serial.
- Sampling has to be stratified by source difficulty, since a random sample dominated by clean laser-printed pages will overstate the quality of the thermal-paper and oversized material where the risk lives.
Sources
Federal Aviation Administration. FAA acceptance criteria for electronic recordkeeping systems and electronic signatures.
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
The vendor certified 99 percent scan accuracy. Why review it again?
Vendor accuracy figures usually measure page capture, not retrievability. A page can be captured perfectly and still be unfindable because its metadata points to the wrong serial or date. This review tests the index the way it will actually be used, which is by search, under deadline, by someone who was not present at scanning.
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.