Records problem
Logbook gaps in aircraft maintenance records
A logbook gap is a period of an aircraft's life where the maintenance history is missing or unaccounted for, breaking the continuous record a buyer, lessee, or authority expects. This page is for lessors, airlines, and maintenance organizations that have found a hole in a logbook ahead of a transaction, return, or audit. The review reads airframe, engine, and APU logbooks, work-package summaries, AD and SB status, and the time and cycle history, then bounds each gap and reconstructs what it conceals. You receive a gap register with the period, the affected records, and the recovery path for each one.
When this review is needed
- A logbook jumps in date, hours, or cycles and the period in between has no entries behind it.
- An operator or registry change left a stretch of the aircraft's life with no records carried forward.
- Diligence on a purchase or return surfaces a missing volume, a lost book, or an unexplained break in the sequence.
- An authority or audit query asks for entries covering a period that the records do not appear to hold.
The problem
A maintenance history is only as good as its continuity, and a gap puts every status statement that depends on the missing period into question. Total time and cycles are read forward from each entry, so a break leaves the accumulation unverified across the hole. The work done in that period, the inspections signed off, and the components installed all sit behind entries that are not in front of you, and the longer the gap, the more status the rest of the records are asserting without support.
What gets reviewed
- The exact date, hour, and cycle boundaries of each gap in each logbook set
- Airframe, engine, and APU continuity checked independently for breaks
- Time and cycle accumulation across the gap reconciled against entries on either side
- Inspections, checks, and AD compliance that should fall inside the missing period
- Components reported as installed or removed during the unaccounted stretch
- Operator, registry, and maintenance-program changes that coincide with the break
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
- Date, hour, and cycle values are continuous across every logbook handover with no unexplained jump
- Total time and cycles read forward from entry to entry without a step that the records do not justify
- Inspection and check intervals that should have fallen in the period are accounted for on one side or the other
- AD and SB compliance claimed after the gap rests on accomplishment evidence that predates or spans it
- Component installations dated inside the gap are supported by release paperwork held elsewhere
- A change of operator or registry is matched by a documented transfer of records for the period
Evidence normally required
- Airframe, engine, and APU logbooks or their digital equivalents on both sides of the gap
- Work-package and shop-visit summaries covering the period in question
- Current AD and SB status with accomplishment dates
- Time and cycle status as recorded at the start and end of the unaccounted period
- Records transfer or export documentation from any operator or registry change
Common discrepancies
- A jump in hours or cycles between two entries with no work recorded to explain the interval
- A missing logbook volume that covers a defined block of the aircraft's life
- An inspection signed off after the gap whose prior accomplishment falls inside the missing period
- A component shown as installed during the gap with no release certificate in the file
- A registry change where the prior records were never carried over
- Engine history that is continuous while the airframe set has a break, or the reverse
What is at stake
An unbounded gap can force a conservative read of time, cycles, and inspection status across the affected period, and it can stall a redelivery or a sale until the history is reconstructed. Where the gap covers a registry or program change, the next operator may have to rebuild the bridge before the aircraft can move, and recovery from a prior party gets harder once that party has been released.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Bound each gap
Locate every break by date, hours, and cycles across airframe, engine, and APU logbooks and define its exact boundaries.
Map what the gap conceals
List the inspections, AD actions, and component movements that should fall inside the missing period.
Trace recovery sources
Identify where the missing evidence may sit, from prior operators, shops, or registries, and who can supply it.
Register and reconcile
Record each gap with its risk and recovery path, and show what time and cycle status is supported versus assumed.
What the buyer receives
- A gap register stating the bounded period, the affected logbook sets, and what each gap puts at risk
- A per-gap recovery path identifying where the missing evidence may be held and who can supply it
- A reconciled time and cycle view showing what is supported and what remains assumed across each break
Who uses the output
- Records teams reconstructing the history before a transaction or return
- Asset managers pricing the exposure a gap creates
- Continuing-airworthiness staff confirming status that depends on the missing period
How the work fits into the transaction or program
Gap analysis runs early in a records review so the rest of the work knows which status statements rest on a missing period. It feeds the discrepancy register and the recovery plan, and it sits alongside a maintenance-tracking reconciliation and an AD status review that depend on a continuous history to be reliable.
Jurisdiction-specific considerations
Recordkeeping and retention duties differ by authority, so a gap that is tolerable under one regime may block acceptance under another. Where the break coincides with a registry change, the receiving authority will look for evidence that the prior history was transferred, not merely that current status is asserted.
Regulatory limits
This review bounds and characterizes gaps and maps a recovery path. It does not fabricate missing entries, certify the period as compliant, issue an airworthiness determination, or guarantee that an authority will accept a reconstructed history.
What this review does not cover
- Creation of replacement logbook entries for the missing period
- Physical inspection of the aircraft to infer undocumented work
- Any airworthiness determination or regulatory acceptance of the gap
Specific to this review
- A gap is defined by date, hour, and cycle boundaries together, because a break can be invisible in one dimension while plain in another.
- Airframe, engine, and APU continuity are checked separately, since one chain can be intact while another has the break.
- Status read forward from entries means a single missing period can leave every later total time and cycle claim unverified until the gap is bounded.
- A gap that lands on a registry or operator change is treated as a records-transfer question first, before any inference about the work itself.
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.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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
Can a logbook gap be closed without the original entries?
Sometimes. Evidence for the missing period often survives in work packages, shop reports, or a prior operator's files. The review identifies those sources and the path to recover them, while being clear about what cannot be reconstructed.
Does a gap mean the aircraft is not airworthy?
No. It means the records do not currently support the period. The review characterizes what the gap puts at risk so the right party can recover the evidence or quantify the effect; airworthiness remains the operator's and the authority's determination.
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.
Walk through your situation with an engineer who has done this work.