767 logbook continuity
Boeing 767 family logbook continuity records review
This review confirms that a Boeing 767's airframe, engine, APU, and component logbooks run without a break across the aircraft's life and every change of operator. It is run for a lessor, airline, or asset manager working a specific 767 tail through diligence or a records clean-up. The work checks utilization and maintenance entries for continuity, confirms no volume or period is missing, and reconciles the running totals against the status records. You receive a continuity assessment across the logbook set, an exception list of gaps and unexplained jumps, and a closure plan for the missing volumes.
When this review is needed
- A 767 that has passed through several operators is entering diligence and the logbooks must run without a gap.
- A logbook volume covering an ownership change cannot be found and the utilization jumps across it.
- An engine or APU was swapped and its logbook does not pick up cleanly from the removal record.
- A buyer wants the running totals reconciled against the status records before pricing.
The problem
The logbooks are the continuous narrative every other record is measured against, and a break in them undermines the totals downstream. On a 767 that has served for decades under several operators, custody has changed hands more than once, and a missing volume or a period where utilization jumps without an entry leaves a hole the status figures paper over. The set can also span paper and digital systems, which is where a period quietly drops out.
What gets reviewed
- Airframe, engine, APU, and component logbooks checked for continuous coverage
- Utilization entries confirmed to run without an unexplained jump
- Maintenance entries continuous across each change of custody
- Engine and APU logbooks reconciled to their removal and installation records
- Running totals reconciled against the status and utilization records
- Missing volumes or periods logged as open items with the totals at risk
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
- The logbook set covers the aircraft's life without a missing volume or period
- Utilization runs continuously with no jump that lacks a supporting entry
- Each change of custody carries entries on both sides without a break
- Engine and APU logbooks reconcile to the removal and installation history
- Running totals in the logbooks agree with the status records they support
Evidence normally required
- The airframe, engine, APU, and component logbooks or their digital equivalents
- The logbook continuity file or index
- Removal and installation records for engines and the APU
- The current utilization and status records
- Records of prior operators and custody transfers
Common discrepancies
- A missing logbook volume across a change of ownership
- A utilization jump with no entry to support the increase
- An engine logbook that does not pick up cleanly from its installation record
- Running totals in the logbooks that disagree with the status records
What is at stake
A logbook gap forces a total to be estimated across it, and an estimated total is priced below a verified one because a buyer cannot confirm what happened in the missing period. Recovering a lost volume means going back to the operator who held it, and once that operator has moved on the gap may have to be carried as a documented estimate rather than closed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Index the set
Assemble the airframe, engine, APU, and component logbooks and map their coverage across the aircraft's life.
Check continuity
Confirm utilization and maintenance entries run without a missing volume or unexplained jump.
Reconcile the totals
Tie the running totals to the status records and the removal and installation history.
Flag the gaps
List missing volumes and periods with the totals at risk and the operator who could supply each.
What the buyer receives
- A continuity assessment across the airframe, engine, and APU logbook set
- An exception list of gaps, missing volumes, and unexplained jumps
- A closure plan identifying the operator who can supply each missing volume
Who uses the output
- Asset managers reading utilization confidence into the value of the tail
- Records teams recovering missing volumes before the file goes to a buyer
- Continuing-airworthiness staff confirming the totals the status rests on
How the work fits into the transaction or program
Logbook continuity underpins every total the status records carry, so this review sets the confidence level for the LLP, AD, and utilization figures a transaction turns on. Gaps it finds route into remediation while the prior operator can still be reached, and any period that cannot be recovered is carried as a stated estimate into the baseline.
Aircraft-specific considerations
A 767 that has flown for decades has usually changed operators more than once, and each transfer is a point where a logbook volume can be lost. Freighter conversion is another custody event on many tails, and the logbook set often spans older paper volumes and later digital records, so continuity has to be checked across both media.
Jurisdiction-specific considerations
Logbook format and retention differ between an FAA operator and an EASA CAMO, so a 767 that has served under both carries a mixed set, and a period logged under one system may need reformatting or supporting evidence under the other. The review notes where the continuity file will need rework for the receiving register.
Regulatory limits
The review confirms the logbooks run continuously and reconcile with the status records. It does not recreate maintenance history, certify utilization figures, or make an airworthiness determination on the aircraft.
What this review does not cover
- Recreating utilization or maintenance history that was never recorded
- Physical inspection of the aircraft or its components
- Any airworthiness determination on the aircraft
Specific to this review
- Each change of operator on a long-served 767 is a point where a logbook volume can drop out, so custody transfers are checked first.
- A logbook set that spans paper and digital systems can quietly lose a period at the seam between the two media.
- A utilization jump with no supporting entry means a total has to be estimated across it, and estimated totals price below verified ones.
- Freighter conversion is a custody event on many 767 tails and a common place for a logbook handover to have a break.
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
What happens when a logbook volume cannot be recovered?
The period it covered is carried as a documented estimate, with the totals at risk stated plainly and the basis for the estimate recorded. That is more defensible at a transaction than a silent jump in the numbers, and it lets the buyer price the uncertainty rather than discover it later.
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.