Logbook continuity across a scanned records archive

When this review is needed

• Physical logbooks were scanned across multiple sessions or vendors and no one has confirmed the volumes join up.
• An aircraft changed hands and the delivered archive mixes scans of different generations and quality.
• Utilization totals in the maintenance system disagree with what the books appear to show.
• An engine or APU arrived with its own scanned records that must be spliced into the aircraft's history.

The problem

Physical logbooks announce their own gaps: a torn page, a missing volume on the shelf. Scans do not. A skipped spread during scanning, a volume digitized out of order, or an engine book filed under the wrong serial number produces an archive that looks whole and is quietly missing months of history. Because logbook entries chain totals forward, one lost span undermines every figure downstream of it.

What gets reviewed

• Volume inventory for airframe, each engine position, and APU, matched against the continuity file
• Page-sequence verification within each scanned volume, including covers and endpapers where totals live
• Carried-forward hours and cycles reconciled across every volume boundary
• Entry date lines checked for unexplained jumps that suggest unscanned spans
• Custody, registration, and maintenance-program changes located and bounded within the record
• Engine and APU installation and removal entries cross-checked against airframe entries

What gets validated

• Every volume the continuity file lists is present in the archive and attributed to the right asset
• Closing totals of one volume equal opening totals of the next, for hours and for cycles
• Sampled page runs are consecutive, with both sides of two-page spreads captured
• Date gaps longer than the asset's known storage or low-utilization periods are explained
• An engine's scanned book covers the periods the airframe record shows it installed

Evidence normally required

• The complete set of scanned logbook volumes for airframe, engines, and APU
• The logbook continuity file or volume register, if one exists
• Current utilization report from the maintenance system for endpoint reconciliation
• Fleet or asset history noting storage periods, registration changes, and engine swaps
• Scan session or vendor batch records, where available

Common discrepancies

• A volume boundary where carried-forward cycles differ from the prior closing figure with no amending entry
• Two-page spreads scanned as single pages, dropping the right-hand entries throughout a volume
• An engine logbook span missing exactly where the engine was at a shop visit under another party's control
• Volumes attributed to the wrong engine serial after a mid-life position swap

What is at stake

A continuity break that surfaces at a transaction becomes a valuation event. Hours and cycles after the break rest on assertion instead of record, remaining life on LLPs inherits the doubt, and a buyer or lessor prices the uncertainty or demands reconstruction from third parties whose cooperation nobody controls. Breaks found early, while the paper or the prior operator is still reachable, are usually fixable; breaks found late often are not.

How the work runs

What the buyer receives

• A continuity map per logbook showing verified spans, gaps, and total-agreement points
• A gap register stating each break's location, length, and probable cause
• Endpoint reconciliation between the scanned record and current system utilization

Who uses the output

• Records control leads certifying the archive as the working logbook reference
• CAMO staff whose utilization and life tracking depend on the chained totals
• Transaction teams presenting continuity to a buyer, lessor, or auditor

How the work fits into the transaction or program

Continuity is the spine the other archive reviews hang from. LLP status, AD compliance intervals, and check due-times all reference hours and cycles that are only as good as the chained logbook record, so this review typically runs first when an archive's quality is in question, and its continuity map becomes the timeline against which the other record types are read.

Jurisdiction-specific considerations

14 CFR 91.417 requires records of total time in service and 91.419 obliges a seller to transfer them, which makes the scanned books the buyer's evidence of everything time-based. EASA's Regulation 1321/2014 continuing-airworthiness record requirements carry the same weight for airworthiness reviews, where an ARC signatory will want the utilization chain shown, not asserted.

Regulatory limits

Output is a factual account of what the scanned volumes contain and where they break. The review does not certify hours or cycles as correct, does not extend or validate any maintenance interval, and does not amount to an airworthiness review or determination under any regime.

What this review does not cover

• Reconstruction of missing spans from third-party sources, beyond specifying what is needed
• Verification of individual maintenance entries beyond their role in the continuity chain
• Appraisal or valuation conclusions from the continuity findings

Specific to this review

• The highest-risk pages in any logbook scan are the first and last of each volume, where carried-forward totals live; they are also the pages most often lost to covers sticking together on the scanner.
• Cycle discrepancies at volume boundaries are more consequential than hour discrepancies for LLP-heavy assets, since part life retires on cycles.
• Storage periods legitimately produce long date gaps, so the review needs the asset's parking history to avoid flagging phantom breaks.
• Mid-life engine position swaps are where wrong-serial attribution errors concentrate, because both books pass through the records office in the same week.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits