Skip to content

Scanned records at return

Digital records index quality assessed across the redelivery binder sources

Most redeliveries now hand over a digital records set, and its index determines whether anyone can actually use it. This assessment measures the digital index against the binder sources: whether each scan is legible, searchable, tied to this airframe, and faithful to the source record it represents. Lessors receiving a digital handover and operators producing one both use it in the weeks before acceptance. The deliverable is a file-level quality report plus an exception list of scans that cannot serve as usable records.

When this review is needed

  • The lease specifies digital delivery of records and the parties never agreed what quality means.
  • A scanning contractor produced the set and the operator is about to hand it over untested.
  • The incoming CAMO will work exclusively from the digital set while the physical binder goes to archive.
  • Early sampling has already turned up unreadable stamps or certificates scanned without their reverse sides.

The problem

Scanning projects optimize for throughput, and the person feeding the scanner is never the person who will search for a specific FAA Form 8130-3 three years later. Ink stamps, thermal paper, and double-sided certificates come through as gray rectangles, batch numbers replace meaningful filenames, and the manifest the scanning run produced quietly diverges from the records index the binder claims to follow.

What gets reviewed

  • A structured sample of files tested for legibility, completeness, and capture of both sides of two-sided documents
  • Index metadata checked: aircraft identity, document type, date, and revision fields populated and accurate
  • Text searchability verified for document classes where retrieval matters, such as certificates and status lists
  • The digital index reconciled against the binder index and the return-condition annex structure
  • File integrity basics: no truncated files, duplicated content under different names, or empty placeholders
  • Traceability of each sampled file back to an identifiable source record

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 release certificate is readable down to the signature, stamp, and certificate number
  • Files carry the aircraft serial number or registration in metadata so exports and merges keep their linkage
  • A search for a known document, such as a specific work order, retrieves it by content or metadata within the set
  • Every digital index entry resolves to exactly one current file, with superseded scans marked
  • Signature-bearing documents meet the standard in the agreed records specification or applicable electronic-records guidance

Evidence normally required

  • The digital records set and its index or manifest
  • The binder index and the lease's records-delivery specification
  • A seed list of known documents to use as search and retrieval probes
  • Scanning project documentation, including resolution and naming conventions, where it exists

Common discrepancies

  • Certificates scanned single-sided with the release statement sitting on the missing reverse
  • Metadata populated by folder inheritance, so hundreds of files carry the wrong document type
  • An OCR layer absent entirely, leaving the set browsable but unsearchable
  • The scanning run's manifest treated as the records index despite never being reconciled to it

What is at stake

A digital set that cannot be searched pushes every future question back to the physical archive, if that archive still exists. Illegible release certificates function as missing ones in the next transaction. Where the digital index and the binder index disagree, both lose authority, and the receiving party discounts the whole handover accordingly.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Agree the standard

Fix the quality bar from the lease specification and applicable guidance before testing begins.

02

Sample by stratum

Test files across document classes, scanning batches, and binder sections.

03

Reconcile the indexes

Map the digital manifest to the binder index and log every divergence.

04

Deliver the worklist

Report quality by section and hand over a prioritized rescan list while sources are still reachable.

What the buyer receives

  • A quality report scored by section, with the sampling basis stated
  • An exception list of unusable or unfaithful files, each mapped to its source record
  • A rescan and remediation worklist ordered by acceptance impact

Who uses the output

  • Lessor teams deciding whether the digital set satisfies the delivery specification
  • Operator records staff directing rescans while source documents remain accessible
  • The incoming CAMO planning how it will ingest and rely on the set

How the work fits into the transaction or program

The digital index check pairs with the binder index review: one proves the paper container, the other proves its electronic shadow. It belongs in the window while physical records are still on hand, because rescanning after the archive ships multiplies the cost of every exception it would have caught.

Jurisdiction-specific considerations

FAA guidance on electronic recordkeeping, including AC 120-78 for electronic signatures and records and AC 43-9C for maintenance record content, shapes what a digital record must preserve to stand in for paper. EASA-context handovers work from Part-M record requirements and the receiving CAMO's system expectations. Where the aircraft changes registry, the set is tested against the stricter of the two expectations rather than the current one alone.

Regulatory limits

The assessment does not certify the digital set as legally equivalent to the source records, does not approve any electronic recordkeeping system, and makes no airworthiness findings. It measures usability and fidelity so the parties know what the handover actually contains.

What this review does not cover

  • Scanning or rescanning work itself
  • Selection or implementation of records-management software
  • Content review of the underlying maintenance records, which the record-type reviews cover

Specific to this review

  • Legibility failures cluster by ink and paper type, so a sample stratified by document class finds more real problems than a random sample of equal size.
  • The reverse side of release certificates is the highest-value scan in the set and the most commonly omitted one.
  • Once the physical archive ships to storage, the unit cost of fixing one bad scan can exceed what scanning the entire original box cost.
  • Digital sets that pass a ten-file demonstration at handover still fail at scale, because quality varies by scanning operator and by week, and only structured sampling exposes that.
  • Metadata errors propagate silently: a wrong registration in one batch header misfiles every document in the batch, and only a linkage check across the set catches it.

Sources

Frequently asked questions

The lease just says records will be delivered in electronic format. What standard applies then?

Silence in the lease pushes the question to usability: can the receiving CAMO and the next buyer's diligence team read, search, and trust the files. Applicable guidance on electronic records supplies a defensible floor, and agreeing a written standard with the counterparty before scanning starts is far cheaper than arguing about gray rectangles at acceptance.

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.