777 family logbooks
Boeing 777 family logbook continuity records review
This review checks that the airframe, engine, and APU logbooks on a Boeing 777 family aircraft form an unbroken record of utilization and maintenance with no missing volumes or unexplained gaps. It is run for a lessor, airline, or asset manager evaluating, transferring, or holding a specific tail. The work reads the logbook continuity file across volumes, confirming utilization carries forward and every custody change is bridged. You receive a supported exception list, a source map of the continuity chain, and a closure plan for the serial number under review.
When this review is needed
- A 777 has passed through several operators and the logbook set has to be confirmed continuous across every handover.
- A logbook volume appears to be missing and the utilization has to be reconstructed across the gap.
- A buyer wants the airframe, engine, and APU books proven unbroken before pricing the asset.
- An engine or APU was swapped and its book has to bridge to the airframe record.
The problem
The logbooks are the spine every other record hangs from, and on a widebody the airframe, engines, and APU each carry their own continuous history. A missing volume, a utilization figure that jumps between books, or a custody change that was never bridged breaks the spine, and everything built on it, status, life, and configuration, loses its footing. These breaks hide at the seams between volumes and operators, which is exactly where a buyer looks.
What gets reviewed
- The airframe logbook set confirmed continuous across all volumes
- Engine logbooks bridged to the airframe record across every installation and removal
- The APU logbook reconciled to the airframe utilization
- Utilization figures confirmed to carry forward without a jump between volumes
- Custody and operator changes bridged with a clean handover entry
- Component logbooks reconciled where they carry their own utilization
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 logbook volume is missing across the airframe, engine, or APU history
- Utilization carries forward across each volume boundary without an unexplained jump
- Engine and APU time and cycles bridge to the airframe record at each install and removal
- Every custody or operator change is bridged with a handover entry
- Component logbooks reconcile to the airframe where they carry their own hours and cycles
Evidence normally required
- The airframe, engine, and APU logbooks or their digital equivalents
- The logbook continuity file for the tail
- Installation and removal records for engines and the APU
- Utilization and status reports for reconciliation
- Handover records from prior operators
Common discrepancies
- A logbook volume missing across a change of operator
- A utilization figure that jumps between two volumes with no explaining entry
- An engine book whose time does not bridge to the airframe at its installation
- An APU logbook that cannot be reconciled to the airframe utilization
What is at stake
A break in logbook continuity forces a reconstruction of the utilization across the gap, and where the reconstruction cannot be made, a conservative assumption the owner carries. An engine or APU book that does not bridge to the airframe leaves its time and cycles in doubt, and a missing volume discovered at sale can stall the deal until it is found or the gap is formally accepted.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Lay out the volumes
Order the airframe, engine, and APU logbooks and confirm no volume is missing.
Check utilization flow
Confirm hours and cycles carry forward across each volume boundary without a jump.
Bridge the swaps and handovers
Confirm engine and APU books bridge to the airframe and every custody change is entered.
List the exceptions
Flag missing volumes and continuity breaks and sequence the reconstructions.
What the buyer receives
- A supported exception list of continuity breaks and missing volumes
- A source map of the logbook chain across the airframe, engines, and APU
- A closure plan sequencing which volumes or bridges to recover before the next milestone
Who uses the output
- Records teams reconstructing utilization across a continuity break
- Asset managers confirming the logbook spine before the file is priced
- Buyers verifying the airframe, engine, and APU history is unbroken before closing
How the work fits into the transaction or program
Logbook continuity is the foundation the status, life, and configuration records all rest on, so this review runs first when a file is assembled for a deal or an induction. The exception list drives reconstruction of the utilization across any break while the prior operators can still be reached, and the confirmed continuity chain underpins every other review in the transaction.
Aircraft-specific considerations
A 777 accumulates long-sector utilization, so its logbook hours run high relative to cycles, and the engines and APU carry substantial independent histories that have to bridge cleanly to the airframe at each swap. A tail that has moved between operators carries more volume boundaries and more custody changes where the continuity can break, so the review is scoped to this serial number's actual operator history rather than a family template.
Jurisdiction-specific considerations
FAA and EASA both require a continuous maintenance and utilization record, but a 777 that has operated across both systems may carry logbooks kept to different conventions, and the continuity has to hold across the change of recordkeeping practice as well as the change of operator.
Regulatory limits
The review confirms the logbook set is continuous and reconciled. It does not reconstruct maintenance that was never performed, certify the utilization, or determine that the aircraft is airworthy.
What this review does not cover
- Reconstructing maintenance or entries that were never recorded
- Physical inspection of the aircraft or its components
- Any airworthiness determination on the aircraft
Specific to this review
- Continuity breaks concentrate at operator handovers, because a missing volume or an unbridged book is easiest to lose when custody changes.
- On a 777 the engine and APU books carry independent histories that must bridge to the airframe, so a swap is a common point where time and cycles fall out of step.
- A utilization jump between volumes is often a transcription error rather than a real gap, but it has to be reconciled before the figures downstream can be trusted.
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 if a logbook volume is missing?
The utilization and maintenance across the gap are reconstructed from status reports, work orders, and prior-operator records where possible. Where the volume cannot be recovered, the break is carried as a documented exception with the basis used, so the buyer sees it rather than inheriting a silent gap.
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.