How to digitize aircraft logbooks for a records audit.

A records audit reads the logbooks against the regulation — 14 CFR 91.417, 43.9, 43.11, and the entries required by 91.421 for a rebuilt engine, among others. The auditor traces AD compliance, STC continuity, 337s, and the paper trail behind each major alteration. That work is only as good as the scan.

Poor scans force re-work: illegible tach entries, half-cropped 337s, missing back sides of yellow tags. Good scans let the audit close findings instead of chasing them.

1. Capture requirements

Scan at 300 DPI minimum, 400 DPI for hand-written logbook pages. Color, not grayscale — stamp ink, red-line annotations, and highlighter change meaning. Output as searchable PDF (OCR applied) when the scanner supports it; otherwise deliver PDF and rely on the audit to OCR downstream.

• 300 DPI floor for typed pages; 400 DPI for handwriting and small stamps.
• Color mode, not grayscale — ink color often carries meaning.
• Include the full page edge to edge — no cropped margins.
• Every logbook page, not just the ones with entries. Blank pages prove continuity.
• Front and back of each 337, yellow tag, 8130-3, and STC permission letter.
• Straight, not skewed — a phone camera at an angle loses the bottom line.

2. File organization

One PDF per logbook, named for what it is. Auditors read across airframe, engine, and propeller books simultaneously — the file names have to make that possible without opening every document.

• 01_Airframe_Logbook_N12345.pdf — full airframe book.
• 02_Engine_Logbook_Left_N12345.pdf — left engine, if applicable.
• 03_Propeller_Logbook_N12345.pdf — propeller.
• 04_Form_337s_N12345.pdf — every 337 in chronological order.
• 05_AD_Compliance_Record_N12345.pdf — status list plus source entries.
• 06_STC_Documents_N12345.pdf — permission letters, ICAs, and flight manual supplements.
• 07_Weight_Balance_N12345.pdf — every W&B revision, latest last.
• 08_Yellow_Tags_and_8130s_N12345.pdf — parts traceability.
• 09_Miscellaneous_N12345.pdf — anything that doesn't fit above.

3. Traceability: 337s and AD compliance

A 337 is only as good as its data basis. When you scan the 337 packet, capture the referenced STC letter, ICA, or approved data on the same pass — not later, not "if we can find it." A missing data-basis document is one of the most common records findings.

For AD compliance, the goal is a compliance record that ties each AD to a specific logbook entry and, where applicable, a recurring interval. Scan the summary list and every logbook entry it references. If the previous owner tracked ADs by memory, say so — the audit needs to know what is documented versus what is asserted.

4. What not to do

• Do not photograph pages with a phone at an angle — the bottom line goes illegible at 300 DPI-equivalent.
• Do not scan in grayscale to "save space." Storage is free; ink color is evidence.
• Do not skip blank pages between entries. Their existence is part of the continuity record.
• Do not deliver individual JPGs. One PDF per book, page order preserved.
• Do not redact or annotate the scans. The auditor needs the record as it exists.

5. Delivery for an audit

Upload the labeled PDFs to the engagement's secure portal. A complete capture typically fits comfortably under a few hundred megabytes; if a single book is over 100 MB, the scan is likely over-resolution and can be reduced without losing legibility.

Send the physical books when the engagement calls for a bench review of the originals — the digital set is what the audit reads against, and the physical books remain the legal record.