ATR 72 digital index
ATR 72 digital records index quality review
This review checks whether an ATR 72's digital records index actually points to the documents its status lines claim. It reads the scan sets, the metadata fields, the OCR layer, and the file-naming scheme against a sample of the source paperwork the index describes. A records specialist runs it when an operator or lessor has migrated a paper library into a viewer and needs to trust what the index returns. You receive a supported exception list, a source map tying index entries to the underlying evidence, and a closure plan scoped to this serial number.
When this review is needed
- A paper library for an ATR 72 has just been scanned and loaded into a records viewer that nobody has verified yet.
- A diligence team keeps hitting index entries that open the wrong scan or no scan at all.
- The asset is being marketed and the buyer will search the index rather than the shelves.
- Two indexing passes by different vendors have to be merged into one library for this tail.
The problem
A digital index is only as good as the link between each entry and the page it claims to describe. On an ATR 72 that has passed through regional operators, scans arrive in mixed batches, metadata fields get filled by whoever ran the scanner that week, and the OCR layer often fails on handwritten Franco-Italian task-card entries. The result is an index that looks complete in a viewer but returns the wrong document, a rotated image, or a dead reference the moment someone tries to cite it.
What gets reviewed
- The metadata schema and how consistently each field is populated across the scan sets
- OCR text quality against the underlying image, including handwritten and stamped entries
- File-naming and folder logic measured for collisions, duplicates, and orphaned files
- A sampled reconciliation of index entries to the source documents they point to
- Coverage of the required record classes for this ATR 72 serial number
- Rotated, cropped, or illegible scans flagged for rescan against the original
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 opens the exact document it names, at the correct revision and page range
- Metadata date, part number, and record-type fields match the content of the linked scan
- The OCR layer returns searchable text on the record classes diligence teams query most
- No two index entries resolve to the same file while a referenced file has no entry
- Every AD and LLP status line in the index maps to a retrievable supporting scan
Evidence normally required
- The digital records index and the viewer or export it runs in
- The scan sets with their metadata fields as loaded
- A retrievable sample of the original paper or PDF source documents
- The status lists the index is meant to support for this ATR 72
- Any indexing standard or naming convention the library was built to
Common discrepancies
- Metadata date fields populated from the scan date rather than the document date
- OCR that silently fails on handwritten regional task-card entries, leaving them unsearchable
- Duplicate scans of the same work order indexed under two different record types
- Index lines that reference a source document the library does not actually contain
What is at stake
If the index is trusted without checking, a diligence question that should resolve to a document instead reopens a manual search through thousands of pages under a deadline. Status lines that reference a missing or mislabeled scan read as gaps even when the paper exists, and an unreliable index depresses the price a buyer will pay because they cannot verify anything quickly.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the schema
Map the metadata fields and naming logic the index was built on before sampling any entry.
Sample entry to source
Open a spread of index lines and confirm each opens the document it names at the right revision.
Test the OCR layer
Search the record classes diligence uses most and check where the text layer actually returns hits.
Log the exceptions
Record broken, duplicate, and mislabeled entries and sequence the rescan and re-index work.
What the buyer receives
- A supported exception list of broken, duplicate, and mislabeled index entries
- A source map linking sampled index entries to their underlying documents
- A closure plan sequencing rescans, re-indexing, and metadata correction
Who uses the output
- Records teams deciding which parts of the index they can rely on today
- Asset managers judging whether the library supports a fast diligence pass
- Buyers who will search the index rather than the physical files
How the work fits into the transaction or program
Index verification comes after scanning and before anyone treats the digital library as the working copy. Its exception list and source map feed the re-indexing work and set up every later status review on this ATR 72, since AD, LLP, and release checks all depend on the index returning the right page.
Aircraft-specific considerations
An ATR 72 records library leans on propeller, landing-gear, corrosion, and regional-operation evidence more heavily than a narrowbody file, and much of that history was created at line stations where scanning discipline varied. Franco-Italian document formats and handwritten cards defeat generic OCR profiles, so the index for this family needs its searchable-text coverage checked on exactly those record classes rather than assumed from an overall page count.
Jurisdiction-specific considerations
The same index has to serve both FAA and EASA readers, who look for different retention structures and status presentations. The review notes where the naming and metadata will need adjustment for whichever system the receiving operator uses.
Regulatory limits
The review assesses whether the index resolves to the correct documents. It does not make any airworthiness determination, approve or restore the status the documents record, and it does not substitute for the receiving operator's own acceptance of the library.
What this review does not cover
- Re-scanning the source documents or operating the scanning equipment
- Building or licensing the records viewer the index runs in
- Any airworthiness determination on the aircraft or its records
Specific to this review
- A viewer showing a full folder tree can still hide dead links, because a missing scan looks identical to a present one until someone opens it.
- OCR coverage is usually strong on typed release paperwork and weak on the handwritten cards that carry the maintenance history, so an overall page count overstates searchability.
- Merging two indexing passes is where most collisions appear, because each pass had its own naming logic and neither expected a second one.
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 scanning is already done. What does verifying the index add?
Scanning produces images; the index is what makes them findable and citable. Verification confirms each index entry opens the right document with usable metadata and searchable text, which is what a diligence team or a buyer actually relies on. Broken links and failed OCR are invisible in the viewer until someone tries to use 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.