Unbroken books
Airframe, engine, and APU logbook continuity review before a transaction
Logbook continuity means an unbroken chain of entries from delivery to today across the airframe, engine, and APU books, with utilization figures that carry consistently from one entry to the next. This review reads the books end to end before an operator's sale or lease return and identifies every break: missing periods, custody handoffs without closing entries, and time or cycle steps that jump without explanation. It runs early in transaction preparation because continuity defects take the longest of any records finding to repair. What comes back is a break register with the surrounding evidence needed to bridge or explain each gap.
When this review is needed
- The aircraft changed hands or management companies in its past and nobody has proven the books across those seams.
- Engines or the APU swapped between airframes and their books must stand alone through each installation period.
- A sale process is starting and the broker warns that this buyer profile reads logbooks page by page.
- Utilization reporting moved from paper to electronic at some point and the transition period was never reconciled.
The problem
Books accumulate under many hands: line stations, management companies, engine shops, and prior owners each wrote their portion under their own conventions. A period covered only by a summary insert, an engine book that restarts after a shop visit without carrying totals forward, or a custody change marked by nothing except a change of handwriting all read as continuity breaks to a buyer's reviewer. Operators rarely discover these until an external reader works the books cover to cover, which is precisely what a transaction triggers.
What gets reviewed
- Airframe logbook read entry to entry from earliest available record to current date
- Engine and APU books proven through every removal, shop visit, and reinstallation
- Utilization figures carried across entries and checked against independent sources such as flight logs
- Custody and operator changes matched to proper closing and opening entries
- Periods covered by summaries, transcriptions, or replacement books identified and risk-graded
- Component book alignment where major assemblies moved between aircraft
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 calendar gap exceeds the operator's entry frequency for that period of operation
- Time and cycle totals reconcile arithmetically across consecutive entries and across book volumes
- Every engine and APU installation period in the airframe book matches the corresponding assembly book
- Shop-visit exit entries carry the same totals the shop's records certify
- Replacement or transcribed volumes are identified as such and anchored to surviving originals
Evidence normally required
- All airframe, engine, APU, and relevant component logbooks, original or certified images
- Flight logs, utilization reports, or ACARS-derived data for independent hour and cycle checks
- Shop-visit reports and engine or APU disk sheets for total verification at overhaul points
- Prior transaction records marking custody changes
- The current status summary the books must ultimately support
Common discrepancies
- An engine book restarted at a shop visit with totals reset instead of carried forward
- Months of operation evidenced only by a management company's summary letter, no underlying entries
- Airframe cycles diverging from the flight log during a period of short-sector operation
- A custody change with no closing entry, leaving two parties' entries interleaved for weeks
What is at stake
Continuity doubts attack the numbers everything else depends on. If total time or cycles cannot be carried confidently across a gap, the counterparty discounts LLP remaining life, questions AD compliance timing, and prices the whole asset defensively. Severe breaks push buyers toward the most conservative assumption available, and reconstructing a period after the fact costs multiples of what preventing the doubt would have.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the books
Work each volume chronologically, logging every gap, restart, and custody seam.
Reconcile the numbers
Carry time and cycle totals across entries and check them against independent utilization sources.
Bridge what can be bridged
Assemble shop reports, flight logs, and prior-transaction records that explain each break.
Grade and disclose
Rank residual breaks by valuation impact and prepare the disclosure position for the data room.
What the buyer receives
- A break register locating every continuity defect by book, page, and date range
- A bridging file of independent evidence assembled for each explainable break
- A severity grading distinguishing cosmetic breaks from those that threaten utilization totals
Who uses the output
- Directors of maintenance and records leads sequencing repairs before the data room opens
- Sale or redelivery teams deciding what to disclose proactively versus defend on request
- The counterparty's reviewers, eventually, who receive bridged books instead of raw gaps
How the work fits into the transaction or program
Logbook continuity is the foundation layer of transaction records work: AD timing, LLP life, and program status all inherit their credibility from the utilization chain the books establish. Running this review first lets its bridging evidence support every downstream workstream, and its severity grading tells the project which other reviews can proceed in parallel.
Jurisdiction-specific considerations
FAA-registered aircraft rest on 14 CFR 91.417 records, and 91.419 obliges a seller to transfer them at sale, so continuity defects become a direct transfer-obligation problem at closing. EASA-managed aircraft carry equivalent continuing-airworthiness record expectations through the CAMO. Aircraft that spent time on multiple registers need each era's books read against the convention of the register that governed it.
Regulatory limits
This review characterizes documentary continuity and assembles bridging evidence. It does not certify total time or cycles, does not recreate or replace logbook entries, and does not determine airworthiness. Where a gap cannot be bridged, the review states the exposure; how to disposition it belongs to the operator, the counterparty, and their authorities.
What this review does not cover
- Forensic authentication of handwriting or suspected altered entries
- Negotiating price adjustments for unbridgeable gaps
- Physical inspection of the aircraft or assemblies
Specific to this review
- Shop-visit exits are the most frequent continuity failure point because the shop's paperwork and the operator's book are written by different organizations days apart.
- Independent utilization sources, flight logs and engine-trend data, can bridge a book gap convincingly, but only if collected before the operating records themselves are archived or discarded.
- Buyers grade a bridged gap and an undisclosed gap very differently; the same break costs far less when it arrives pre-explained in the data room.
- APU books break more often than engine books because APU removals are treated as routine component changes and escape the ceremony that engine swaps receive.
- Replacement volumes issued after a lost or damaged book are legitimate records, but only while the anchor documents that justified their opening totals stay with the books; separated anchors turn a lawful replacement into an apparent gap.
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 are already scanned into the data room. Does the review use scans or originals?
Scans serve for the first read, but continuity questions often turn on physical details: binding, page sequence, ink changes, and whether a page was inserted later. Breaks flagged from scans get confirmed against originals before they enter the register, which avoids raising false findings with the counterparty.
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.