Logbook continuity
Logbook continuity review against the continuing-airworthiness source file
This review tests the airframe, engine, and APU logbook chain against the records the CAMO already holds: status reports, airworthiness-review working notes, maintenance-program references, and the open-item log. A records analyst walks each logbook period, confirms the entries line up with what the source file says the aircraft was doing at the time, and flags every interval the file cannot vouch for. It is usually commissioned while a continuing-airworthiness baseline is being rebuilt or challenged. The continuing-airworthiness manager receives an exception list keyed to specific logbook periods, ready to disposition.
When this review is needed
- A new CAMO has taken over the aircraft and inherited logbooks with unexplained intervals between entries.
- An airworthiness review is approaching and the reviewer will read the logbooks side by side with the CAMO status reports.
- Utilization totals in the CAMO system drifted away from the logbook figures after a data migration or operator change.
- A redelivery clause demands continuous logbook coverage and the operator wants each break explained before the lessor asks.
The problem
Logbook breaks rarely announce themselves. A period with no entries can mean the aircraft was parked, or it can mean a custody change, a utilization step, or a maintenance-program switch that nobody recorded in the book. The CAMO file usually knows which of these happened, but the knowledge sits in status reports and open-item logs that were never cross-read against the logbooks, so the same gap gets rediscovered and re-argued at every review.
What gets reviewed
- Entry-by-entry continuity across the airframe, engine, and APU logbooks for the review period
- Each logbook interval matched to the utilization and status picture in the CAMO reports for the same dates
- Custody and operator changes traced through airworthiness-review notes and program references
- Carried-forward totals checked where a logbook volume closes and the next one opens
- Open-item log entries examined for deferrals or events that explain a quiet period in the books
- A period-by-period verdict on whether the source file supports the continuity claim
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
- Hours and cycles at each logbook entry reconcile with the utilization figures the CAMO reported for that month
- No logbook volume transition drops or restates carried-forward totals without a supporting note in the file
- Every operator or custody change visible in the source package has a corresponding logbook handover entry
- Periods without logbook entries are covered by storage, parking, or transfer evidence in the CAMO records
- Engine and APU logbook timelines stay consistent with the airframe book across removals and reinstallations
Evidence normally required
- Airframe, engine, and APU logbooks or certified digital copies for the review period
- CAMO status reports and utilization summaries covering the same dates
- Airworthiness-review working notes and any prior review findings
- The open-item log and maintenance-program references in force during the period
- Records of custody transfers, storage entries, or lease transitions if held separately
Common discrepancies
- A quiet logbook period that the CAMO file explains as storage, but with no preservation entries to close the loop
- Carried-forward hours restated at a volume change with no reconciliation anywhere in the source package
- An engine logbook that continues under a new operator while the airframe book shows no handover
- Utilization steps in the CAMO reports that never made it into the books as amending entries
What is at stake
A gap left unexplained hardens into a traceability defect. Airworthiness reviewers treat unsupported logbook intervals as open findings, lessees inherit them as redelivery exposure, and every downstream status figure that spans the gap carries a question mark. Reconstructing the explanation years later costs far more than reading it out of the source file while the file is still complete.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the period map
Lay out the logbook timeline for airframe, engine, and APU books and mark every interval, transition, and volume change.
Read the source file against it
Match CAMO status reports, review notes, and open-item entries to each logbook period.
Isolate unsupported intervals
Flag every period where the books and the file disagree or where neither says anything.
Issue the exception list
Deliver period-keyed exceptions with the evidence found, the evidence missing, and a suggested disposition.
What the buyer receives
- An exception list keyed to specific logbook periods, each with the source evidence found or missing
- A continuity map showing which intervals the CAMO file supports and which it does not
- Recommended disposition for each exception, from a simple cross-reference entry to targeted retrieval
Who uses the output
- The continuing-airworthiness manager preparing the airworthiness status baseline
- Records staff who must annotate or amend the logbooks before the next review
- Fleet managers deciding whether a redelivery or remarketing timeline is realistic
How the work fits into the transaction or program
The logbook continuity check is normally the first record type read in a CAMO source-file review, because every other status claim ultimately hangs off the utilization chain the logbooks carry. Its exception list feeds the airworthiness status baseline and tells the modification, weight and balance, and deferred-maintenance reviews which periods to treat with suspicion.
Jurisdiction-specific considerations
Under 14 CFR 91.417 and 91.419 the records travel with the aircraft at transfer, so a US-registered asset with prior owners often has continuity questions concentrated at each sale date. EASA-registered aircraft managed under Part-CAMO carry the parallel obligation through the CAME and the airworthiness review cycle, which means the source file itself is the artifact the reviewer will test. Dual-register histories need the gap explained under both retention regimes, not just the current one.
Regulatory limits
The review reports what the source file does and does not support. It does not certify the aircraft airworthy, sign an airworthiness review, approve data, or amend a logbook on anyone's behalf. Disposition of each exception stays with the continuing-airworthiness manager and, where required, the competent authority.
What this review does not cover
- Physical inspection of the aircraft or verification of installed hardware
- Reconstruction of missing logbook entries or drafting of replacement pages
- Assessment of maintenance quality behind the entries that do exist
Specific to this review
- Most continuity exceptions cluster at ownership and CAMO transitions, because the party writing the last entry and the party writing the next one were never the same organization.
- A logbook gap backed by storage evidence in the CAMO file is a footnote; the same gap without it becomes a diligence finding that can stall a transaction.
- Volume changes are a quiet failure point: carried-forward totals get retyped, and a single transposed digit propagates into every later status report.
- Engine and APU books drift out of sync with the airframe book whenever a removal spans a reporting period, so cross-book checks catch errors that single-book reads miss.
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 logbooks look complete. Why read them against the CAMO file at all?
Complete-looking books can still contradict the file. An entry chain with no visible breaks may sit over a custody change or a utilization restatement the CAMO recorded elsewhere, and it is the disagreement between the two sources, invisible from either alone, that surfaces at the airworthiness review.
What happens to gaps the source file cannot explain?
They go on the exception list with a stated recovery path, typically retrieval from a prior operator or shop, or a documented fallback if the evidence is gone. The review does not paper over them; it makes them explicit so the baseline is honest.
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.