Skip to content

Digitized records

Digital scan-quality review of aircraft records

A digital scan-quality review is for teams about to run a transaction, audit, or handover from a digitized record set rather than the paper. The trigger is a scan set delivered for reliance. It inspects page-level legibility, completeness against expected page counts, orientation and resolution adequate to read part numbers and authority blocks, and fidelity to the originals where both can be compared. You receive a defect log by document, a list of pages that are unreadable, cropped, or absent, and a fidelity note where the scan diverges from the source.

When this review is needed

  • A digital record set has been delivered and a transaction will be run from it instead of from the paper.
  • Scans arrived from several sources and the quality varies across the set.
  • An audit or handover will lean on the digital copies and their fidelity to the originals is unconfirmed.
  • A prior set was rejected for legibility and a rescan needs verifying before it is accepted.

The problem

A scan can be present in the file tree and still carry no evidentiary value. The places a record actually proves something, an inspector stamp, a hand-signed release, a part number in a margin, are exactly the places that go faint, get cropped, or drop a continuation page in a bulk scan. A file-level index counts documents, not readable ones, so a set can look whole while the entries that matter are unusable when a reviewer finally opens them.

What gets reviewed

  • Page-level legibility across the set, including stamps, signatures, and handwritten entries
  • Completeness of each document against its expected page count and any continuation pages
  • Orientation, cropping, and resolution sufficient to read part numbers, dates, and authorizations
  • Color or contrast where it carries meaning, such as ink-stamp authority or marked annotations
  • Fidelity of the scan to the paper original where both are available to compare
  • Skew, double-feeds, and blank inserts that signal a capture fault rather than a document gap

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

  • Stamps, signatures, and handwritten entries are legible at the delivered resolution
  • Each document is present page for page with no dropped, duplicated, or out-of-order pages
  • Part numbers, dates, and authorization references can be read without ambiguity
  • Cropping and orientation do not cut off authority blocks or margins that carry data
  • Where the original is available, the scan reproduces it faithfully without lost annotation
  • Capture faults such as skew, double-feeds, and blank inserts are identified and tied to a document

Evidence normally required

  • The scanned record set and its file index
  • The expected document list or original index for the set
  • A sample of paper originals where available for fidelity comparison
  • Any prior scan-quality notes or rejection history
  • The capture specification or resolution standard the scan was meant to meet

Common discrepancies

  • Authority stamps or signatures too faint to read at the delivered resolution
  • Pages cropped so a part number, date, or authorization block is cut off
  • Documents short a page against their expected count or missing a continuation page
  • Scans that diverge from the paper original where both are available to compare
  • Skewed or double-fed pages that render a critical entry partly unreadable

What is at stake

Relying on a set with unreadable authority blocks or missing continuation pages forces rescans mid-transaction, stalls diligence, or pushes a reviewer back to chasing the paper the digitization was meant to retire. When the originals have already been dispersed, an illegible scan can leave a record effectively lost.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Establish the expected set

Build the document and page-count baseline from the original index and the capture specification the scan was meant to meet.

02

Inspect legibility and completeness

Read every page for stamps, signatures, and part numbers and confirm page-for-page presence against the baseline.

03

Compare to source

Where paper originals are available, test the scans for fidelity and lost annotation.

04

Log defects and rescans

Produce a defect log by document and a rescan list while the originals are still accessible.

What the buyer receives

  • A defect log by document with the page and the type of defect
  • A rescan list of unreadable, cropped, or missing pages
  • A fidelity note where the scan set diverges from the paper source

Who uses the output

  • Records operations teams running or accepting the digitization
  • Diligence and audit reviewers who will work from the digital set
  • Asset teams deciding whether the set can carry the transaction

How the work fits into the transaction or program

The review runs before the digital set is trusted, so rescans happen while the paper originals are still in reach. Its output sets the legibility baseline the indexing review and any later reconciliation depend on.

Jurisdiction-specific considerations

Both the FAA and EASA systems allow electronic recordkeeping, but the digital copy still has to reproduce what the paper proved. Where an authority block or signature carries the authorization, an illegible scan of it is a defect regardless of which system the record will be relied on under.

Regulatory limits

This review confirms the legibility, completeness, and fidelity of a scanned set. It does not approve an electronic recordkeeping system, does not certify the underlying records, and does not make any airworthiness determination from what the scans show.

What this review does not cover

  • Performing the scanning or rescanning itself
  • Approval of an electronic recordkeeping or signature system
  • Judging the airworthiness content of the records being scanned

Specific to this review

  • A scan can be present and still unusable, because faint stamps and cut-off authorization blocks are exactly where a record loses its evidentiary value.
  • The set is checked page for page against expected counts, since a missing continuation page rarely surfaces in a file-level index.
  • Capture faults such as skew and double-feeds are treated as defects in their own right, because they degrade a critical entry without dropping the page count.

Sources

Frequently asked questions

Is a clean file count enough to trust a scanned set?

No. A file count proves documents exist as files, not that they are readable or whole. The review opens the pages, so a faint stamp, a cropped authority block, or a missing continuation page is caught before the set is relied on.

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.

Walk through your situation with an engineer who has done this work.