Skip to content

787 logbook continuity

Boeing 787 family logbook continuity records review

This review reads the airframe, engine, APU, and component logbooks for a specific Boeing 787 family aircraft to confirm the utilization and maintenance history runs unbroken from delivery to the current entry. A records specialist runs it for the party trading or inducting the tail, often when the logbooks span several operators. It checks that hours and cycles carry across every volume without a jump, that ownership and operator changes are bridged, and that maintenance entries line up with the events the other records describe. You receive an exception list of continuity breaks, a source map across the logbook set, and a closure plan for the gaps.

When this review is needed

  • A 787 has passed through several operators and the hours and cycles have to carry cleanly across every logbook.
  • A transition between digital and paper record systems left a suspected break in the history.
  • Ownership or operator changes need bridging so the utilization picks up where the prior custodian left off.
  • A buyer wants the logbook set proven continuous before relying on the status built on it.

The problem

The logbooks are the spine every other record hangs from: if the hours and cycles do not carry unbroken across each volume, every status figure built on them is suspect. Continuity breaks tend to appear where custody changed, where a digital system replaced paper, or where a logbook volume was opened without carrying the closing totals of the last one. On a 787 that has moved between operators, the same total time can be stated three ways across three systems, and none of them agrees at the seam.

What gets reviewed

  • Airframe hours and cycles carried continuously across every logbook volume
  • Engine and APU logbooks reconciled to the airframe utilization at each seam
  • Ownership and operator changes bridged so no utilization is lost at handover
  • Transitions between paper and digital record systems checked for a clean carry-over
  • Maintenance entries in the logbooks aligned with the events the other records describe
  • Component logbooks reconciled to the airframe for installed time and cycles

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

  • Closing totals in each logbook volume match the opening totals of the next
  • Engine and APU utilization reconciles to the airframe hours and cycles at each transfer
  • Utilization carries across every ownership and operator change without a lost interval
  • The seam between paper and digital records preserves the running totals
  • Logbook maintenance entries correspond to the events recorded in the task and shop records

Evidence normally required

  • The complete airframe, engine, and APU logbook set for the tail
  • The logbook continuity file or running utilization summary
  • Ownership and operator transfer records covering the aircraft's history
  • Any digital-record extracts that replaced or supplement the paper logbooks
  • Component logbooks for the major installed items

Common discrepancies

  • A logbook volume opened without the closing totals of the prior volume carried across
  • Engine or APU utilization that does not reconcile to the airframe at an operator change
  • A gap in utilization at a custody change where a prior operator's entries were never transferred
  • A total-time figure stated differently across the paper logbook and the digital system

What is at stake

A break in continuity means the total time and cycles cannot be proven, and a buyer who cannot trust the utilization discounts every life-limited and time-controlled figure that depends on it. Rebuilding a continuous history after custody has changed hands several times is slow and sometimes impossible, so the gap becomes a conservative assumption the owner pays for at the next transaction.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Lay out the volumes

Order the airframe, engine, APU, and component logbooks and identify every seam and custody change.

02

Carry the totals

Confirm closing and opening totals match across each volume, system, and transfer.

03

Reconcile across records

Align logbook maintenance entries with the events the task and shop records describe.

04

List the breaks

Locate each continuity gap and sequence the utilization to reconstruct or bridge.

What the buyer receives

  • An exception list of continuity breaks located to the volume and seam
  • A source map across the airframe, engine, APU, and component logbooks
  • A closure plan for the utilization to reconstruct and the seams to bridge

Who uses the output

  • Records teams proving an unbroken history before status is built on the logbooks
  • Asset managers confirming the total time and cycles a valuation rests on
  • Buyer and lessor teams verifying the utilization spine before diligence goes deeper

How the work fits into the transaction or program

Logbook continuity is checked early because every other 787 records review, from LLP trace to program status, assumes the hours and cycles are sound. This review either confirms that spine or locates the breaks that have to be bridged first, and its reconciliation feeds the weight-and-balance, modification, and LLP work that all read utilization from the same logbooks.

Aircraft-specific considerations

787s were delivered into operators that record utilization electronically, so a logbook history for this type often spans a paper handover from delivery, a digital operator system, and any interim custodian, with a seam at each transition. Because the type entered service relatively recently, the whole life is usually recoverable, but only if each seam is bridged while the prior operator's system is still accessible. The review is scoped to this serial number's custody chain rather than a generic logbook template.

Jurisdiction-specific considerations

FAA and EASA operators format logbook entries and retain records differently, so at a register change the review notes where the utilization history has to be re-presented to satisfy the receiving system's recordkeeping.

Regulatory limits

The review confirms the logbook history is continuous and internally consistent. It does not certify the utilization figures, return the aircraft to service, or make an airworthiness determination on the aircraft.

What this review does not cover

  • Physical inspection of the aircraft or its recording systems
  • Reconstructing utilization that was never recorded by any operator
  • Any airworthiness determination on the aircraft

Specific to this review

  • Continuity almost always breaks at a seam, a new volume, a custody change, or a paper-to-digital switch, rather than in the middle of a record kept by one operator.
  • Every life-limited and time-controlled figure inherits the logbook's continuity, so a break here quietly undermines the rest of the file.
  • A 787's relatively recent entry into service means the full history is usually still recoverable, but the window closes as each prior operator's system is retired.

Sources

Frequently asked questions

Where do continuity breaks usually turn up on a 787?

Almost always at a seam rather than inside a stretch of records kept by one operator. The common ones are a new logbook volume opened without the prior closing totals, an operator change where utilization was not carried across, and the switch from a paper delivery record to an operator's digital system.

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.