Continuity checks
Logbook continuity review inside a component-history source file
A logbook continuity review establishes whether the airframe, engine, and APU logbooks in a component-history source file run unbroken across the period the subject part was installed. The reviewer walks the entries in date order on each aircraft the component flew on, comparing utilization steps, custody changes, and maintenance events against the part's serial-number history. It is performed as part of a serialized-component trace review, before the file supports a sale, exchange, or lease event. The deliverable is a continuity map with every break, overlap, and unexplained jump logged as an exception.
When this review is needed
- The component flew on several airframes and nobody has confirmed the logbooks cover every installed period end to end.
- Hours and cycles claimed for the part rest on utilization figures whose logbook basis has never been walked.
- An operator change mid-history left a period where two logbook systems ran in parallel or neither did.
- A counterparty has asked how a three-month silence in the engine logbook squares with the part's claimed time on wing.
The problem
Logbooks are continuous by design, so any silence in them is information. A missing quarter can conceal a lease to another operator, a storage period that changed the maintenance basis, or utilization that was never rolled into the component's totals. Teams building a component trace tend to pull the entries that mention the part and skip the stretches in between, which is precisely where the problems live.
What gets reviewed
- Logbook coverage on every airframe, engine, and APU position the component occupied, mapped against its fitment dates
- Utilization steps at each installation and removal reconciled with the part's hour and cycle claims
- Custody and operator changes located in the entries and matched to the serial-number history
- Maintenance-program transitions visible in the logbooks checked for effect on the component's tracking basis
- Entry sequences examined for backdating, overlapping volumes, and rewritten pages
- Storage and preservation periods verified as documented rather than inferred from silence
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 installed period of the component falls outside the date range of an available logbook volume
- Hour and cycle figures at each fitment event agree between the logbook, the movement record, and the trace summary
- Every custody change in the serial-number history has a corresponding entry or transfer document
- Gaps between volumes are bridged by closing and opening totals that reconcile
- Entries around each removal and installation are contemporaneous with the event they record
Evidence normally required
- Airframe, engine, and APU logbooks, or certified digital equivalents, for each host aircraft
- The component's serial-number history and fitment record
- Utilization reports covering the installed periods
- The removal and installation records held in the component-history source file
- Transfer, storage, or preservation documentation for any period out of service
Common discrepancies
- An installed period that begins before the earliest available logbook volume for the host aircraft
- Closing totals in one volume that do not match the opening totals of the next
- A custody change evident from the entries that never made it into the component's stated history
- Utilization accrued during a wet-lease period absent from the part's hour and cycle totals
What is at stake
If a break in the logbooks goes unnoticed until a counterparty finds it, the component's hour and cycle figures lose their foundation, and with them the remaining-life arithmetic on anything life-tracked nearby. Reconstructing a gap after the fact means chasing a prior operator's archive under deal pressure, and gaps that cannot be reconstructed force conservative assumptions that come straight off the asset's value.
How the work runs
Build the fitment timeline
Fix the dates the component was installed on each host aircraft from the serial-number history.
Walk the logbooks
Read entries in date order across each installed period, noting totals, custody events, and silences.
Reconcile utilization
Tie logbook utilization steps to the hour and cycle figures the trace claims for the part.
Map and report
Deliver the continuity map and exception log with reconstruction priorities.
What the buyer receives
- A continuity map plotting logbook coverage against the component's fitment timeline
- An exception log of breaks, overlaps, and unreconciled totals with their trace impact stated
- A reconciled utilization statement for the component across its documented installed periods
- Recommendations on which gaps merit reconstruction effort and from whom
Who uses the output
- Records leads deciding whether the trace file can stand on the current logbook set
- CAMO staff validating the utilization basis behind the component's life tracking
- Asset managers weighing gap reconstruction cost against transaction impact
How the work fits into the transaction or program
Continuity is the skeleton of a component trace: task cards, releases, and shop reports all hang their dates on it. Running this review early in the source review sequence pays off, because a continuity break found late invalidates cross-checks already performed against the affected period.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
14 CFR 91.417 obliges the owner to keep records of total time in service and to transfer them with the aircraft, so a break often traces to a transaction where 91.419 transfer duties were handled loosely. EASA-managed aircraft add the CAMO's continuing-airworthiness record set, which can fill a logbook silence if the CAMO archive is reachable, a possibility this review flags rather than assumes.
Regulatory limits
The review measures documentary continuity. It makes no finding on airworthiness, does not certify hour or cycle totals as correct, and does not recreate missing logbook entries; reconstruction, where attempted, is a separate effort with the organizations that generated the original records.
What this review does not cover
- Reconstruction of missing volumes or entries
- Verification of flight-log data against operational systems
- Continuity checks on aircraft the component never flew on
Specific to this review
- The riskiest silences sit at ownership boundaries: the weeks between a sale closing and the new operator's first entry are where utilization most often goes unrecorded.
- Overlapping volumes are as telling as gaps, since two books covering the same dates usually mean a rewrite, and the differences between them are worth reading line by line.
- APU logbooks break continuity far more often than airframe books because APU swaps are treated as routine component changes rather than events worth a careful entry.
- A logbook gap during a storage period is only benign if preservation records exist; without them, the trace cannot show the calendar-limited items were protected.
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 component's own paperwork is complete. Why do the host aircraft logbooks matter?
The part's hours and cycles were accrued by the aircraft it was bolted to, so its totals are only as good as the host's utilization record. A clean stack of release certificates cannot show how much the part flew between them; the logbooks can, and a counterparty will read them for exactly that.
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.