Logbook continuity
Boeing 737 MAX logbook continuity records review
A Boeing 737 MAX logbook-continuity review confirms the airframe, engine, and APU logbooks tell one unbroken story from entry into service to the review date. It is run by or for a party evaluating, transferring, or holding a specific tail. Utilization figures, maintenance entries, and custody handoffs are reconciled so time and cycles carry forward without a break, a duplicate, or a volume that goes missing at an operator change. You receive a supported exception list of every discontinuity, a source map across the logbook set, and a plan to close or document each break.
When this review is needed
- A tail has passed through more than one operator and no one has confirmed the logbooks run without a gap at each handoff.
- An engine or APU serial has changed and the time and cycle history has to follow the unit, not the position.
- A buyer's status figures do not reconcile with the logbook totals and the difference has to be located.
- A logbook volume is suspected missing across a period the utilization record cannot otherwise explain.
The problem
Logbooks are the primary record every status figure ultimately rests on, and they break most often at the seams between owners. A volume gets left behind at an operator change, an engine swap detaches accumulated time from the airframe entry, or a period of utilization appears in a tracking system but not in any book. The MAX is young enough that the full history should be present, which makes a genuine break stand out and worth locating rather than assuming.
What gets reviewed
- Airframe logbook continuity from entry into service to the review date, volume by volume
- Engine logbooks reconciled to the serials currently installed and their accumulated time and cycles
- APU logbook continuity across any unit changes
- Utilization reconciled between the logbooks and the operator's tracking record
- Custody handoffs at each operator change checked for a missing or duplicated volume
- Time and cycle totals carried forward without an unexplained step
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 figures at each volume boundary match the opening figures of the next volume
- Installed engine and APU serials trace to the accumulated time and cycles claimed for them
- Utilization in the logbooks reconciles with the tracking record over the same periods
- No operating period appears in tracking without a corresponding logbook entry
- Each operator handoff shows a continuous record rather than a break or a re-baselined total
Evidence normally required
- The full airframe logbook set, all volumes, in sequence
- Logbooks for the installed engine and APU and any relevant removed units
- The operator's utilization or tracking history
- Delivery and transfer records marking each change of custody
- Engine and APU installation and removal records
Common discrepancies
- A logbook volume missing across a period the utilization record still covers
- An engine time total that does not carry across a swap between airframes
- A utilization step between operators that neither book explains
- A duplicated entry period where two volumes overlap at a handoff
What is at stake
A discontinuity in the logbooks undermines the time and cycle basis for AD applicability, life-limited part life, and every interval built on hours or cycles. If the break sits at an operator change, the party that could supply the missing volume may be hard to reach, and a status taken on trust across that gap becomes an exception the next buyer prices against.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Sequence the volumes
Order the airframe, engine, and APU logbooks and mark every boundary and custody handoff.
Reconcile the figures
Confirm closing and opening totals match across boundaries and that unit time follows the serial.
Cross-check utilization
Compare the logbook record against the tracking history for the same periods.
Log the breaks
Record each discontinuity, its location, and whether it can be recovered or must be documented.
What the buyer receives
- A supported exception list of every discontinuity with its location in the logbook set
- A source map showing how the airframe, engine, and APU records reconcile
- A plan to recover the missing volume or document the break where recovery is not possible
Who uses the output
- Records teams establishing a defensible time and cycle basis before the next milestone
- Asset managers confirming the utilization history supports the value they carry
- Buyers verifying that status figures rest on continuous logbooks rather than a tracking summary
How the work fits into the transaction or program
Continuity sits under every other records review, because AD, life-limited part, and interval status all inherit their hours and cycles from the logbooks. This review runs early so a discontinuity is found before status work is built on top of it, and its exception list feeds recovery or a documented fallback while the prior operator is still reachable.
Aircraft-specific considerations
The 737 MAX entered service recently, so a complete logbook set from delivery should exist and a real gap is unusual enough to warrant tracing to its cause rather than accepting. Because the family relies on avionics and software configuration recorded alongside utilization, the review confirms that engine and APU changes carried their time histories cleanly rather than re-baselining at the swap.
Jurisdiction-specific considerations
FAA recordkeeping and EASA continuing-airworthiness both require the utilization and maintenance history to be retrievable and consistent, but they present it differently, so the review flags where a logbook set built for one register will need reformatting or supplementary evidence for the other.
Regulatory limits
The review reconciles the logbooks and locates discontinuities. It does not certify the accumulated time, return the aircraft to service, or make an airworthiness determination on the basis of the utilization history.
What this review does not cover
- Reconstructing utilization that was never recorded in any system
- Physical inspection or verification of installed serials
- Any airworthiness or status approval built on the logbook figures
Specific to this review
- Logbooks break most often at custody handoffs, so each operator change is the first place a continuity review looks.
- An engine or APU swap can detach accumulated time from the airframe entry, so unit time is traced to the serial, not the position.
- Because the MAX fleet is young, a missing volume is anomalous rather than expected, which makes it worth recovering instead of writing off.
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
Is a tracking-system total enough if a logbook volume is missing?
A tracking summary is a convenience layer over the logbooks, not a substitute for them. If a volume is missing, the underlying entries cannot be verified, so the review treats the period as a break to recover or document rather than trusting the summary across it.
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.