Logbook continuity
Logbook continuity review for airframe, engine, and APU records at redelivery
Logbooks are the one record set whose value lies in having no gaps, and this review walks them entry by entry to prove it. Covering airframe, engine, and APU volumes in the redelivery binder, the reviewer checks chronological continuity, carried-forward hour and cycle totals at every volume change, and the presence of entries for each check, shop visit, custody transfer, and major event the rest of the source set says occurred. Lessors typically commission it as binder assembly begins. The deliverable is a continuity map with every break, mismatch, and silent period located precisely.
When this review is needed
- The aircraft has passed through several operators or registries and no single party has ever verified the logbooks across all of them.
- Digital records were introduced partway through the aircraft's life and the paper-to-electronic transition point has never been audited.
- An engine or APU spent time off wing, on lease or in storage, and its logbook must account for the detached period.
- A prior operator's entries are in another language or format and the binder must present them coherently to the incoming party.
The problem
Every operator keeps logbooks its own way: different volumes, different entry granularity, sometimes different units for the same counters. Each transition splices another style onto the stack, and splices are where continuity dies. A closing total in one volume that does not match the opening total in the next, a shop visit the engine records elsewhere but the logbook never mentions, six quiet months during a registry change. None of it is visible until someone reads the volumes end to end, which is precisely the work operators defer until a return forces it.
What gets reviewed
- End-to-end chronological reading of airframe, engine, and APU logbook volumes in the binder
- Verification of carried-forward hours and cycles at every volume transition and operator change
- Cross-check of logbook entries against check records, shop-visit packages, and installation or removal events in the source set
- Identification of silent periods and their correlation with storage, transition, or off-wing intervals
- Review of entries recording major repairs and alterations for the detail recordkeeping rules require
- Assessment of any reconstructed volumes and the evidence offered behind the reconstruction
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
- Opening totals of each volume equal the closing totals of its predecessor for hours, cycles, and landings where tracked
- Every engine and APU removal, installation, and shop visit evidenced elsewhere in the binder has a corresponding logbook entry
- Operator and registry transitions show closing and accepting entries on both sides of the change
- Entries for major repairs and alterations identify the work, the data, and the certifying organization
- Periods without entries are explained by documented storage or off-wing status rather than left open
Evidence normally required
- All airframe, engine, and APU logbook volumes, original or certified digital equivalents
- Utilization summaries and hour-cycle statements for the lease term and prior custody periods
- Check completion certificates and shop-visit release documents for correlation
- Records of registry changes, storage programs, and off-wing intervals
- Any reconstruction affidavits or replacement volumes with their supporting evidence
Common discrepancies
- A carried-forward cycle total that jumps or drops at a volume change, traceable to a units or counter confusion between operators
- Engine shop visits fully documented in the powerplant records yet never entered in the engine logbook
- A custody transfer where the receiving operator's first entry predates the delivering operator's last, leaving overlapping and contradictory records
- Reconstructed volumes supported by an affidavit alone, with none of the underlying secondary evidence attached
What is at stake
Logbook breaks attack the asset's value directly, because the logbook is the record a future buyer's counsel and the next registry will ask for first. A silent period invites the assumption that something unrecorded happened in it, and rebutting that assumption after the fact requires affidavits and secondary evidence that never fully restore confidence. At redelivery, a break found by the counterparty rather than the presenter becomes leverage across the entire negotiation.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Lay out the custody timeline
Establish operators, registries, storage periods, and off-wing intervals before opening a single volume.
Read the volumes end to end
Verify chronology and carried-forward totals across every transition for each logbook.
Correlate against events
Test the logbooks against checks, shop visits, and movements documented elsewhere in the binder.
Map and hand over
Deliver the continuity map, mismatch schedule, and entry-gap list to both records teams.
What the buyer receives
- A continuity map per logbook showing every volume, transition, break, and silent period on one timeline
- A mismatch schedule for carried-forward totals with the arithmetic shown
- An entry-gap list of events evidenced in the source set but absent from the logbooks
Who uses the output
- Asset managers defending the aircraft's value story into the next transaction
- Records leads at the returning operator drafting corrective entries while the certifying organizations are still reachable
- The incoming operator's registry and CAMO teams preparing their own acceptance filings
How the work fits into the transaction or program
Logbook continuity is the frame the other reviews hang inside: utilization totals verified here feed the program-status recomputation, shop visits correlated here anchor the engine package review, and custody chronology established here settles which operator owes which missing record. It is usually sequenced early for exactly that reason.
Jurisdiction-specific considerations
For FAA-registered aircraft, 14 CFR 91.417 defines what must be kept and 91.419 obliges the seller or transferor to hand the records over, while EASA-side continuity duties flow through Part-CAMO under Regulation (EU) 1321/2014. Aircraft that migrated between regimes mid-life often show entry styles that satisfied each authority in turn yet leave translation-era ambiguities the review has to resolve document by document.
Regulatory limits
The review reports on continuity and consistency of the logbook record. It does not create or certify logbook entries, does not validate reconstructions on behalf of any authority, and offers no determination that the aircraft is airworthy or eligible for any registry.
What this review does not cover
- Making corrective or bridging entries in the logbooks themselves
- Forensic authentication of handwriting, inks, or paper
- Registry filings or interactions with aviation authorities
Specific to this review
- Breaks cluster at custody changes because the delivering operator stops caring one day before the receiving operator starts, and that single administrative day can become a permanent hole.
- Hour and cycle mismatches at volume transitions frequently trace to one operator counting touch-and-go landings differently than the next, an error that compounds silently for years.
- An off-wing engine keeps its own history while the airframe logbook goes quiet about it; reviewers reconstruct the pairing timeline to prove the quiet period is benign.
- Reconstructed logbooks are accepted in practice only to the extent secondary evidence backs each reconstructed period, and an affidavit without that evidence moves almost no acceptance team.
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
One early volume is lost and the aircraft is twenty years old. How bad is that?
It depends on what surrounds the hole. A lost volume bracketed by consistent totals, with check certificates, shop records, and utilization statements covering the same period, can be substantiated well enough for most counterparties. The review defines the affected window exactly and inventories the secondary evidence, which is the difference between a managed disclosure and an open-ended doubt.
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.