Logbook continuity
Logbook continuity traced through the engine-module records file
A logbook continuity review establishes that the engine's documented life runs unbroken from entry to entry, with every gap explained by the file. It is run for owners, lessors, and receiving operators whenever an engine file transfers or a continuity question surfaces during diligence. Log entries are read against installation and removal history, utilization statements, and shop records, so each custody change and each step in hours and cycles is anchored to evidence. Breaks the file cannot explain are returned as dated, located exceptions.
When this review is needed
- An engine spent time off wing or in storage and the log is silent for the period.
- Logbooks were migrated to a digital system and the paper originals are being retired.
- Diligence flagged a utilization step between two entries that nobody can currently explain.
- A mid-life engine assembled from modules of different origins needs its combined history shown coherent.
The problem
Engine logs are written by whoever holds the engine at the time, and engines change hands more often than aircraft. Each operator, shop, and lessor writes in its own convention, and the joins between custodians are where entries go missing, utilization resets, and module histories detach from the assembled engine. Reading one logbook cover to cover reveals almost none of this; the breaks appear only against the installation and shop records.
What gets reviewed
- Entry-by-entry sequence of the engine log against removal and installation history
- Utilization steps between consecutive entries tested for arithmetic and plausibility
- Custody and registry changes located and matched to transfer documentation
- Module histories aligned with the assembled engine's log across build changes
- Storage, preservation, and transport periods matched to their supporting records
- APU and airframe log references crossed where the engine history depends on them
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
- Consecutive entries carry utilization figures that reconcile with the operator's stated flying in the period
- Every removal in the installation history has a corresponding log closure, and every installation an opening entry
- No period of claimed operation lacks an accountable custodian in the file
- Module serial changes recorded at shop visits appear in the assembled engine's log record
- Preservation entries exist for storage periods long enough to require them
Evidence normally required
- Engine and module logbooks, paper or digital, covering the full claimed life
- Removal and installation history from all operators in the chain
- Utilization statements or reports for the periods in question
- Shop-visit records marking module changes and utilization at induction and release
- Transfer, storage, and transport documents for off-wing periods
Common discrepancies
- A silent log across a period the installation history shows the engine flying on wing
- Utilization at shop induction that disagrees with the last operator log entry by a round number, suggesting a transcription slip
- Module logs that stop at a build change without cross-reference into the assembled engine record
- Storage periods with no preservation entries, leaving the engine's condition through the gap unsupported
What is at stake
An unexplained continuity break gets priced as if the worst happened during it. Hours and cycles claimed across the gap are discounted, LLP status computed through the gap inherits the doubt, and a buyer's reviewer will anchor negotiations on the break long after the parties thought the file was settled.
How the work runs
Assemble the timeline
Lay every log entry, installation event, and shop record onto one dated sequence for the engine and its modules.
Test the steps
Check utilization arithmetic and custody accountability across each pair of consecutive entries.
Classify the breaks
Separate explained gaps, curable gaps, and true breaks, with the evidence that would cure each.
Deliver the continuity map
Issue the mapped history, the reconciled utilization line, and the exception entries for the trace file.
What the buyer receives
- A continuity map of the engine's documented life with every break located and classified
- Exception entries for the trace file, each stating what evidence would cure the break
- A reconciled utilization line from first entry to current status
Who uses the output
- Receiving operators and their CAMO accepting the engine's history
- Lessors defending claimed hours and cycles at transaction
- Records teams deciding which archives to chase while prior custodians are still responsive
How the work fits into the transaction or program
Continuity is the spine the rest of the file hangs on: LLP status, program status, and AD compliance all assume the utilization line is real. This review therefore runs early in a full file review, and its reconciled utilization line becomes the reference the program and LLP reviews compute against.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA record expectations flow from 14 CFR 91.417, with 91.419 governing what transfers at sale and AC 43-9C describing entry content. EASA files carry the parallel continuing-airworthiness record obligations of Regulation 1321/2014. Engines that moved between registries often show a format change at the transfer point, and the review treats those seams as high-risk zones rather than assuming equivalence.
Regulatory limits
The review maps and evidences continuity; it does not recreate lost logbooks, certify total time or cycles as an official determination, or rule on airworthiness. Where a gap cannot be closed, the deliverable states the exposure and leaves the operational decision with the responsible operator or authority.
What this review does not cover
- Reconstruction of missing log periods as a substitute record
- Forensic document authentication of suspect entries
- Valuation adjustments arising from continuity findings
Specific to this review
- The joins between custodians hold most continuity defects; entries inside a single operator's tenure are comparatively reliable.
- Round-number utilization steps at handovers deserve suspicion, since real flying rarely lands on even hundreds of hours and cycles.
- Digital migrations create a specific failure: the scanned book is complete but the indexed data was keyed with gaps, so the paper passes review while the system fails it.
- A module's history can be continuous while the assembled engine's is broken, and the reverse; both records need reading together.
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
The engine has a current utilization statement. Isn't that enough?
A current statement gives the endpoint, and continuity review tests the path to it. Two files can show the same closing hours and cycles while one supports them entry by entry and the other bridges a silent year. Counterparties pay for the supported path, so the difference is commercial.
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.