Aircraft logbooks
Airframe logbook records review
An airframe logbook review is for lessors, airlines, and acquisition teams who need a continuous, supported airframe history rather than a status summary. It runs before a purchase, a lease return, or a registry change. It reconstructs the airframe record from delivery to current status, checking entry continuity, total time and cycles, recorded major repairs and alterations, and the operator and program changes the airframe has passed through. You receive a continuity timeline, a register of gaps and inconsistencies, and the entries needed to close them.
When this review is needed
- An airframe is being bought, sold, or returned and the buyer needs the history reconstructed, not just a status sheet.
- An aircraft has moved between operators or registries and the logbook continuity across those handovers is unconfirmed.
- Recorded total time or cycles on a status list have not been checked against the entries that should build them.
- A major repair or alteration appears on a summary sheet but its airframe logbook entry is missing.
The problem
An airframe logbook is supposed to be the unbroken narrative of the aircraft, but in practice it is a stack of books, supplements, and digital extracts assembled across operators and decades. Entries go missing at handovers, time and cycles drift between the books and the status list, and major repairs appear in one record but not the logbook. The status sheet reads clean while the history that should justify it has holes.
What gets reviewed
- Airframe logbook entries from delivery to current status, including supplements and digital extracts
- Continuity of entries across operator, base, and maintenance-program changes
- Total time in service and total cycles reconciled across books and status lists
- Major repairs and alterations recorded against the airframe with their approval references
- Registry changes and the records handed over at each one
- Periods of storage, lease, or sub-lease reflected in the airframe history
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
- Logbook entries form a continuous record with no unexplained break across the airframe history
- Total time and cycles are internally consistent across logbooks, summaries, and status lists
- Each major repair and alteration recorded against the airframe cites its approval reference
- Operator and program transitions show the records handed over rather than a silent gap
- Registry changes are reflected with the transfer of records expected at each one
- Dated entries follow a coherent sequence without overlaps or impossible jumps in time
Evidence normally required
- Airframe logbooks, supplements, and any digital record extracts
- Major repair and alteration records with their approval references
- Current total time and cycle status and the summaries that build it
- Operator and maintenance-program transition documentation
- Registry and ownership transfer records where applicable
- Storage and reactivation records for any out-of-service periods
Common discrepancies
- A logbook gap that opens at an operator or registry change and is never bridged
- Total time or cycles that disagree between the logbooks and the status list
- A major alteration listed on a summary sheet with no corresponding airframe logbook entry
- Dated entries that overlap or jump in a way the history cannot support
- A storage period with no record of preservation or return-to-service condition
- Approval references missing for a recorded major repair to the structure
What is at stake
An airframe with a broken logbook history is harder to value, harder to re-register, and harder to defend in a transaction. Missing continuity can force reconstruction work, conservative assumptions on accumulated time, or a discount, and gaps that cross an operator change are the slowest to close.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the books
Gather all airframe logbooks, supplements, and digital extracts and order them across the aircraft's life.
Reconstruct the timeline
Build a continuous history and reconcile time and cycles against the status list and summaries.
Mark the breaks
Register each gap, overlap, or inconsistency with the operator or registry change it sits at.
Bridge or quantify
Recommend the entries needed to bridge each gap or quantify its effect on the airframe history.
What the buyer receives
- A reconstructed continuity timeline of the airframe from delivery to current status
- A register of logbook gaps and inconsistencies with the record each touches
- A recommended path to bridge each gap or quantify its effect on the history
Who uses the output
- Asset and acquisition teams valuing the aircraft and its history
- Records teams assembling the airframe narrative for a data room
- Continuing-airworthiness staff confirming the history supports the current status
How the work fits into the transaction or program
The review turns a stack of books into a defensible airframe narrative, so continuity gaps surface before they are inherited at a transaction. It anchors the wider records audit and gives the engine and APU reviews a consistent airframe time and cycle baseline to reconcile against.
Jurisdiction-specific considerations
An airframe that has changed registry carries the recordkeeping expectations of more than one authority across its life. The review checks that the records handed over at each registry change support the history the current authority and the next operator will rely on.
Regulatory limits
The review confirms that the airframe history is continuous, internally consistent, and traceable. It does not certify the airframe, determine accumulated life on the authority's behalf, or make an airworthiness determination.
What this review does not cover
- Physical inspection or survey of the airframe
- Reconstruction of missing history beyond identifying the gap and the evidence needed
- Any airworthiness determination or re-registration approval
Specific to this review
- Airframe time and cycles read from a status list and the same figures built from logbook entries are checked as two separate things, because handovers and re-keying make them drift.
- The highest-risk airframe gaps cluster at operator and registry changes, where one party's records end before the next party's begin.
- A major alteration recorded in a summary but absent from the airframe logbook is a continuity finding, even when an approval reference exists elsewhere.
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). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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
Is a status list the same as an airframe logbook history?
No. A status list summarizes current condition; the logbooks are the history that should support it. The review reconstructs the history and checks whether it actually backs the status the list reports.
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.