Continuity of record
Logbook continuity across an owner-managed aircraft's history
A logbook-continuity review reads the airframe, engine, and APU logbooks of a managed aircraft end to end and tests whether the record advances without unexplained breaks. Entry dates and utilization must progress coherently, provider transitions must show orderly handovers, and removal or installation events must mirror across the books. It is performed for the owner representative before a sale or management change, and it delivers a continuity map with every break located, characterized, and ranked by its effect on status credibility.
When this review is needed
- Several management providers have kept the books over the years, each with different habits and formats.
- Hours or cycles jump between consecutive entries with no operational explanation on record.
- Paper logbooks were partially transcribed into an electronic system and neither version is complete on its own.
- Engine or APU books fail to mirror airframe events at removal and installation dates.
The problem
Continuity failures accumulate quietly. A provider change skips a closing entry, a book sits forgotten at a completion center for a season, an electronic migration captures most of the paper and never quite all of it. None of it looks alarming in the moment, and nobody reads the books end to end until a buyer's reviewer does exactly that.
What gets reviewed
- Entry-by-entry progression of dates and utilization through each book
- Provider transition points checked for closing and opening entries
- Cross-book consistency at every engine and APU removal or installation
- Total-time and cycle statements reconciled against supporting records
- Completeness of paper-to-electronic transcription where systems changed
- Statements covering lost or reconstructed records reviewed for an adequate basis
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
- Utilization never decreases, and jumps correspond to documented flight activity
- Each change of management provider shows an orderly handover within the books
- Engine hours and cycles at removal match the airframe book for the same date
- Electronic records reproduce every paper entry for the period they claim to cover
- Totals carried on current status reports equal the figure the logbooks actually support
Evidence normally required
- Complete airframe, engine, and APU logbooks, originals or full scans
- Exports from any electronic records system used during ownership
- Flight logs or trip records that evidence utilization
- Handover inventories and correspondence from provider transitions
- Current status reports stating total time and cycles
Common discrepancies
- A silent gap that coincides exactly with a change of management provider
- An engine book recording an installation the airframe book never mentions
- Status-report totals several hours adrift of what the summed entries support
- Reconstructed pages inserted without any statement of the basis for reconstruction
What is at stake
Utilization credibility underpins every other record on the aircraft. Program status, LLP cycles, and engine value all key to logged hours and cycles, so a break in the books invites recalculation against the least favorable plausible assumption, and the discount lands on the whole asset rather than on the gap alone.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Index every book
Page through airframe, engine, and APU books building a dated index of entries and utilization figures.
Reconcile utilization
Cross-check the index against flight activity, cross-book events, and status-report totals.
Characterize the breaks
Classify each discontinuity as benign, explainable with evidence, or open.
Deliver the map
Hand over the continuity map, reconciliation statement, and ranked exceptions.
What the buyer receives
- A continuity map per book with every break located and characterized
- A utilization reconciliation statement across books, flight records, and status reports
- A ranked exception list ordered by effect on the credibility of current status
Who uses the output
- The owner representative pre-empting the buyer's own logbook read-through
- The incoming provider setting opening totals in its tracking system
- Appraisers whose valuation rests on logged utilization
How the work fits into the transaction or program
Continuity is the spine the rest of the owner-managed file review hangs on. Program status, task-card evidence, and shop-visit history all reference logged time, so a break found here propagates into every sibling exception list, and fixing the spine first keeps the other reviews honest.
Jurisdiction-specific considerations
FAA rules define what an owner must keep and require the records to transfer to the buyer at sale, and AC 43-9C describes what an acceptable reconstruction of lost records looks like. EASA continuing-airworthiness rules impose comparable retention and pass the records along when the operator or CAMO changes. A reconstruction accepted by one authority can still draw a market discount in the other regime, and the review flags where that risk sits.
Regulatory limits
No airworthiness determination is made, no total time is certified, and no reconstruction is sanctioned on any authority's behalf. Recreating lost records is a process the owner runs with the authority; this review locates the breaks, documents them, and scopes what a rebuild would take.
What this review does not cover
- Physical verification of hour meters or cycle counters
- Forensic document examination of suspect entries
- Rebuilding lost logbooks, which the findings scope but other work performs
Specific to this review
- An absence of entries only means something against expected activity, so continuity review needs flight records; without them a quiet book and a broken book look identical.
- Most breaks sit at ownership or management boundaries, so date-sorting the transition events first surfaces the majority of exceptions in the least time.
- APU books break more often than engine books because APU changes get handled casually on privately operated aircraft.
- A total-time discrepancy of even a few hours between the books and the status report draws diligence attention out of all proportion to its size.
- Scanned logbooks hide missing pages well; page-count and sequence checks against the physical binding are tedious and worth it.
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
We found a gap from years ago. How bad is that?
It depends entirely on what the gap covers. A quiet period supported by flight records is explainable and usually survives diligence with a note. A break spanning a heavy inspection or an engine change needs the surrounding evidence assembled before anyone else asks, and the review scopes exactly that package.
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.