Logbook continuity
Logbook continuity review against the shop-visit source file
Logbooks summarize what the shop-visit file proves, and the two must agree. This review reads the airframe, engine, and APU logbook entries made around the visit against the underlying package: the entry's description of work versus the workscope, the release-to-service statement, the times and cycles quoted, and the continuity of the book itself across the event. It is completed for quality, CAMO, or lessor teams during acceptance. Gaps, contradictions, and continuity breaks return as a documented finding list.
When this review is needed
- The visit is complete and the logbook entry must be verified before the books return to circulation.
- Books changed custody around the event and the sequence of entries needs confirmation.
- Times and cycles in the entry were drawn from estimates during the visit and require reconciliation.
- A previous continuity break in these books makes each new entry a point of scrutiny.
The problem
Logbooks travel separately from work packages, and shop visits are exactly where they diverge. The entry is often drafted from the workscope before the final build settles, times and cycles are keyed from the induction estimate, and the book may sit in an office while the visit runs, accumulating a silent gap between the last operational entry and the maintenance entry. Every one of those shortcuts is invisible until someone reads the book against the package.
What gets reviewed
- The visit's logbook entries located, dated, and sequenced against surrounding entries
- Work description in each entry compared with the accomplished workscope in the package
- Release-to-service statements checked for required content, signatory, and approval reference
- Times and cycles quoted in entries reconciled with utilization records and the package data
- Continuity across the event: custody, storage, and any entries made by parties other than the shop
- Consistency between airframe, engine, and APU books where the visit touched more than one
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 entry describes the work at a level that the package substantiates, without overstating scope
- Release statements carry the certifying organization's approval reference and authorized signature
- Total time and cycle figures agree between the entry, the package, and the utilization trail
- No unexplained interval exists between the last pre-visit entry and the visit entry
- Engine and APU book entries align with the airframe book where events overlap
Evidence normally required
- Airframe, engine, and APU logbooks covering the visit period
- The visit's accomplishment summary and release documentation
- Utilization records bracketing induction and return to service
- Custody or transmittal records for the books around the event
Common discrepancies
- An entry drafted from the planned workscope that omits work added or deleted mid-visit
- Times and cycles carried from induction estimates and never updated to actuals
- A release statement missing the approval reference or signed by an unidentifiable stamp
- A quiet gap where the books sat unattended between the last flight and the maintenance entry
What is at stake
Logbooks are the first documents any buyer, lessor, or authority opens, and a visit entry that disagrees with its package casts doubt over both. Continuity questions spread backward: a gap around one event invites re-examination of the whole book, and an incorrect release statement in the entry can put the validity of the return to service itself in question. Corrections made years later look worse than the errors they fix.
How the work runs
Stage the books and package
Gather all affected logbooks and the verified source package for the visit.
Read entries against evidence
Compare each entry's scope, figures, and release statement with the package.
Assess continuity
Examine the sequence and custody of entries across the event window.
Document the findings
Issue the per-book finding list and the continuity statement for the record.
What the buyer receives
- A finding list per book, each item citing the entry and the source document it conflicts with
- A corrected-figures memo for times, cycles, and dates the source file supports
- A continuity statement describing the book's condition across the event, for the permanent file
Who uses the output
- Records custodians returning the books to circulation after the visit
- CAMO leads whose continuing-airworthiness record references these entries
- Asset and transition managers preparing the books for the next review by a counterparty
How the work fits into the transaction or program
The logbook check closes the loop the other source-file reviews open: after the cards, releases, and status lists have been verified, this review confirms the books tell the same story. It is deliberately last in sequence, because a verified package is the standard the entries are judged against.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Requirements under 14 CFR 91.417 and 91.419 govern what US records must contain and how they transfer with the aircraft, while EASA's Part-M continuing-airworthiness record system distributes similar content across the operator's records. Entry conventions differ enough between the systems that a book maintained under one can look deficient to a reviewer trained in the other, so findings distinguish true gaps from format differences.
Regulatory limits
The review compares documents and reports differences; it does not make or amend logbook entries, issue release-to-service statements, or rule on the validity of a certification already made. Corrections to books are executed by authorized persons under the operator's or shop's procedures.
What this review does not cover
- Reconstructing missing historical entries predating the visit
- Executing corrections or making entries in any book
- Assessing entries unrelated to the shop-visit period under review
Specific to this review
- The interval while books sit in an office during a long visit is a common false alarm; a custody note in the file resolves it, and its absence turns a non-event into a permanent question.
- Entries that overstate the workscope are as damaging as ones that omit work, because they certify accomplishments the package cannot back.
- Estimated induction times that harden into the release entry create a utilization discontinuity that compounds in every later calculation.
- Multi-book consistency is checked less often than entry accuracy, yet engine books disagreeing with the airframe book is among the most frequent findings.
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 shop drafted the logbook entry. Is it not their responsibility?
The shop certifies its own work, and the books belong to the operator or owner, who carries the long-term consequence of a defective entry. Reviewing the entry at acceptance is the only point where corrections cost nothing but a redraft.
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.