Logbook continuity
Logbook continuity review across the lease-transition records file
Logbooks are the spine of an aircraft's history, and a continuity break anywhere in them puts every dependent record in doubt. This review reads the airframe, engine, and APU logbooks delivered in a lease-transition records file for unbroken sequence: dates, utilization figures, custody changes, and release entries that follow one another without gaps or overlaps. Where the sequence breaks, the review establishes what the break conceals by testing it against utilization statements and correspondence in the file. The transition lead receives a continuity map and an exception list for every interval the logbooks cannot account for.
When this review is needed
- The incoming operator's review found a date gap in an engine logbook and wants the full set walked before acceptance.
- Books were rebuilt or transcribed after a system migration and the originals' continuity was never re-verified.
- An APU or engine spent time off-wing during the lease and its book does not obviously cover the removal period.
- Total-time figures at transition differ between the logbooks and the status summaries by more than rounding.
The problem
Logbook problems hide in plain sight because books are read for their entries, never for their silences. A gap of six weeks between entries looks like a quiet aircraft until the utilization statements show four hundred hours flown across it. Transition files add a second layer: books transcribed, rebuilt, or migrated during the lease read smoothly and prove nothing unless the source records came along.
What gets reviewed
- Entry sequence in each book checked for date order, gaps, overlaps, and utilization continuity
- Total time and cycles accumulated through the entries reconciled to the transition status figures
- Custody and operator changes located in the books and matched to the transition record
- Off-wing periods for engines and the APU bounded by removal and installation entries
- Transcribed or rebuilt sections identified and tested against the source records that fed them
- Breaks already queried in acceptance correspondence consolidated rather than re-raised
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
- No unexplained interval exists between consecutive entries in any book
- Utilization figures step consistently upward and match the delivered statements at sampled dates
- Each operator change shows closing and opening entries that agree on time and cycles
- Engine and APU books cover every position change the airframe book and status data imply
- Rebuilt sections declare themselves as such and cite the records they were built from
Evidence normally required
- Airframe, engine, and APU logbooks or certified digital equivalents
- Utilization statements and monthly reports for the lease term
- The transition status summary with total time and cycles
- Removal and installation records for engines and the APU
Common discrepancies
- A silent gap of weeks between entries during which the aircraft demonstrably flew
- An engine book that skips a loan to another airframe the status data reveals
- Opening entries after an operator change that restate totals differing from the closing entries before them
- A transcription that compressed several source entries into one, dropping the release references
What is at stake
A continuity break contaminates everything dated inside it: AD compliance, task accomplishment, and LLP accumulation in that window all lose their anchor. Total-time disputes reprice the asset directly, since hours and cycles drive maintenance-value calculations on both sides of the table. Breaks that cross custody changes are the hardest to repair later, because each former custodian holds only its own side of the seam.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Sequence the entries
Read each book end to end for date order, gaps, overlaps, and utilization steps.
Plot the utilization
Test entry intervals against statements and status data to expose silent gaps.
Probe the breaks
Investigate each break for what it conceals: custody changes, off-wing periods, or transcription loss.
Map and report
Deliver the continuity map with exceptions bounded by date and utilization on both sides.
What the buyer receives
- A continuity map per book marking verified spans and unexplained intervals
- An exception list with each break bounded by dates and utilization on both sides
- A reconciliation of logbook totals to the transition status summary
Who uses the output
- Transition leads who need every break bounded before totals are argued
- Records teams targeting the custodian on each side of a broken seam
- Both parties' technical staff, who anchor the other record reviews to the continuity map
How the work fits into the transaction or program
Logbook continuity is reviewed first when sequencing allows, because every other strand dates its evidence against the books. A verified continuity map lets the AD, LLP, and program reviews anchor their calculations; a broken one tells them exactly which windows to treat as unproven.
Jurisdiction-specific considerations
Retention and transfer rules frame this review. 14 CFR 91.417 sets what an FAA operator keeps and for how long, and 14 CFR 91.419 obliges transfer to a purchaser at sale; a lease transition is not a sale, so the lease itself must do the work 91.419 does not. EASA-managed aircraft carry continuity through the CAMO's continuing-airworthiness records under Regulation (EU) 1321/2014, which changes where the review looks but not what it needs to find.
Regulatory limits
The review establishes documentary continuity, no more. It does not certify total time or cycles, does not validate or recreate logbook entries, and does not determine airworthiness; a verified continuity map is evidence for those decisions, not the decision itself.
What this review does not cover
- Certification of total time and cycle figures
- Reconstruction or re-creation of missing logbook entries
- Legal interpretation of lease record-transfer clauses
Specific to this review
- The costliest breaks are quiet ones: books that resume cleanly after a gap look continuous until utilization is plotted against them.
- Engine and APU books break more often than airframe books because off-wing custodians rarely write in the operator's book.
- Overlapping entries are rarer than gaps and worse: two books claiming the same period with different figures leave no conservative side to default to.
- Because lease transitions fall outside the sale-transfer rule in 14 CFR 91.419, continuity at handover is only as strong as the lease clause that governs records delivery.
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
The books were digitized mid-lease. Is that automatically a finding?
Not by itself. A migration becomes a finding when the digital record cannot demonstrate its lineage: source books that were not retained, batches scanned without index control, or entries keyed in with no image behind them. Where lineage is intact, the review verifies it once and moves 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.
Talk through the aircraft, records, evidence, deadline, and next useful step.