Continuity diligence
Logbook continuity checked against the data-room uploads
Airframe, engine, and APU logbooks establish the continuous story of an aircraft, and this review tests that story using the scans a seller places in the data room. It looks for breaks between volumes, unexplained gaps in entries, and periods where custody, utilization, or program changes hide inside a discontinuity. Buy-side teams run it during the diligence window, before the exception schedule settles. The deliverable is a continuity map with sourced exceptions the deal team can price or push back on.
When this review is needed
- The index lists logbook volumes by date range and the ranges do not join.
- The aircraft spent time in storage or with a short-lived operator and those months are thin in the record.
- Total time and cycle figures in the specification need anchoring to logbook entries rather than to a status export.
- An engine or APU arrived on the aircraft mid-life and its earlier logbook history must be present and legible.
The problem
Logbooks fail quietly. A volume ending in March and a successor opening in June looks fine in a folder listing, and only a page-level read shows the missing quarter. Scans compound the problem: pages skipped at the copier, bindings that hid entries, volumes uploaded under the wrong asset. The person who could explain a gap left the operator years ago, and the deal timetable does not wait for archive searches.
What gets reviewed
- Volume date ranges assembled into a single timeline per asset: airframe, each engine, and the APU
- Entry-level review at volume boundaries and around custody or operator changes
- Utilization progression checked for steps, reversals, or implausible accumulation
- Storage entries examined for preservation and depreservation records
- Cross-checks between logbook totals and the specification or status exports posted in the room
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
- Each volume's closing totals carry into the opening entries of its successor
- No calendar period lacks entries without an explanation the room supports, storage included
- Times and cycles progress monotonically and match utilization reports where both exist
- Custody and registry changes appear in the entries where the deal history says they occurred
- Engine and APU logbooks cover the units currently installed, serial numbers verified
Evidence normally required
- All uploaded logbook volumes for airframe, engines, and APU
- The aircraft specification or summary the seller represents
- Utilization statements covering the ownership periods
- Storage and preservation records, where the history includes parking
- Registry and ownership chronology from the deal documents
Common discrepancies
- A quarter of flying absent between volumes, unexplained in Q&A
- Depreservation entries with no matching preservation record, leaving a storage period undocumented
- An installed engine whose early volumes belong to a different serial number
- Totals in the specification that outrun the last certified logbook entry
What is at stake
A continuity break at a custody change can conceal an incident, an unrecorded storage period, or a maintenance-program lapse, and each of those reprices the asset when it eventually surfaces. Hours and cycles that cannot be anchored to continuous entries weaken every downstream status, from LLP life to check forecasting, and some registries will question the record at transfer.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the timeline
Assemble volume date ranges for airframe, engines, and APU into one coverage picture per asset.
Read the boundaries
Examine entries at volume joins, custody changes, and claimed storage periods page by page.
Anchor the totals
Reconcile hour and cycle progression against utilization statements and the represented specification.
Map and report
Issue the continuity map with breaks classified and the volume requests that would close them.
What the buyer receives
- A continuity map per asset showing covered periods, breaks, and their significance
- Exception entries referencing volume, page, and folder for the diligence schedule
- A targeted Q&A set asking for the specific volumes or explanations that would close each break
Who uses the output
- Transaction managers weighing continuity breaks against price and conditions
- Technical teams anchoring time and cycle status for downstream reviews
- Registry and legal advisors preparing for deregistration and transfer questions
How the work fits into the transaction or program
Continuity is the spine the other record reviews hang from: LLP traces, AD status, and program history all assume the hours and cycles are real. This review usually runs first or in parallel with the status reviews, and its continuity map tells the rest of the diligence which periods deserve suspicion.
Jurisdiction-specific considerations
14 CFR 91.417 and 91.419 govern which records transfer with a US aircraft and what a new owner must receive, while EASA continuing-airworthiness rules under Regulation 1321/2014 set retention duties on the operator and CAMO. Aircraft that crossed registries mid-life often show format changes at the boundary, and the review reads each era against the regime it was kept under.
Regulatory limits
Mapping continuity is documentary work. The review issues no airworthiness determination, does not validate registry status, and cannot certify total time or cycles; it reports what the posted volumes support and where they fall short.
What this review does not cover
- Forensic authentication of handwriting or ink on questioned entries
- Reconstruction of missing volumes from third-party sources
- Legal opinion on title, liens, or registry matters
Specific to this review
- Most continuity breaks cluster at operator transitions, because the departing operator's archive and the arriving operator's system rarely overlap cleanly.
- Storage periods are the classic false gap: a parked aircraft generates few entries legitimately, but preservation records must still exist for the gap to be benign.
- Scanned logbooks lose the physical cues a hardcopy inspection would catch, torn pages and replaced bindings among them, so scan-based review flags candidates for physical follow-up.
- A specification quoting totals beyond the last certified entry usually means the seller extrapolated from utilization reports, which is a representation and never evidence.
- Engine and APU books deserve equal page-level attention because their continuity carries the LLP and hard-time story; a clean airframe book proves nothing about the powerplants.
Sources
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
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.
Frequently asked questions
A three-month gap sits between two logbook volumes. Is the deal in trouble?
Gaps have benign explanations, storage being the usual one, but benign must be shown through preservation records, utilization statements, or a credible Q&A answer with documents attached. The continuity map classifies each break by what would close it, so the deal team can price the ones that stay open.
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.