Logbook continuity
Airbus A350 family logbook-continuity records review
This review confirms that the airframe, engine, and APU logbooks for an Airbus A350 family aircraft run without a break from entry into service to the review date. It is run by or for a lessor, operator, or manager who needs the utilization and maintenance history to hold together across every volume and every change of custody. It reads the logbooks as one continuous record, checking that hours and cycles carry forward correctly, that no volume starts on a figure the prior volume did not end on, and that engine and APU changes are logged where the airframe record expects them. You receive a continuity map, a list of breaks and unexplained jumps, and a plan to close each one.
When this review is needed
- A serial number has passed through more than one operator and the logbook set has to be proven continuous before a deal.
- An engine or APU was changed and the airframe logbook needs to show the removal and installation cleanly.
- Hours and cycles quoted on a status list do not reconcile with the logbook totals.
- A logbook volume was reopened or reissued and the continuity across the seam is in question.
The problem
Logbooks are the spine every other status hangs from, and continuity fails at the seams: the end of one volume and the start of the next, a change of operator, an engine or APU swap. An A350's utilization accrues fast on long-haul rotations, so a small carry-forward error compounds into a totals gap that then contradicts the AD and life-limited status built on those totals. The break is usually silent until someone reconciles the whole set end to end.
What gets reviewed
- Airframe logbook read as a continuous series with each volume's opening figure matched to the prior close
- Engine logbooks continuous across shop visits, changes, and the airframe on which each engine ran
- APU logbook continuity including removals, installations, and utilization while installed
- Hours and cycles carried forward correctly across every volume seam and custody change
- Removal and installation entries present in the airframe record for each engine and APU event
- Breaks and unexplained jumps carried onto an exception list with the bridging evidence identified
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
- Each logbook volume opens on the exact figure the preceding volume closed on
- Airframe hours and cycles at the review date agree with the engine and APU records for time installed
- Every engine and APU change shows a matched removal and installation across the relevant books
- No utilization period is counted twice or skipped across a change of operator
- Reissued or reopened volumes state the basis for the seam and preserve the running totals
Evidence normally required
- The complete airframe logbook set across all volumes
- Engine logbooks for each installed and previously installed engine
- The APU logbook and its removal and installation history
- Current time and cycle status lists to reconcile against the books
- Transfer records covering any change of operator during the aircraft's life
Common discrepancies
- A volume that opens on a figure the prior volume never reached
- An engine change logged in the engine book but missing from the airframe record
- Utilization double-counted across the seam where one operator handed off to the next
- APU hours that cannot be reconciled to the periods the unit was installed
What is at stake
A logbook set that does not run continuously undermines every figure derived from it. Time and cycle totals become disputable, life-limited part remaining life loses its footing, and a counterparty who finds the break prices the uncertainty or stalls the transaction until it is explained. A gap that spans a change of custody is the hardest to close, because the records that would bridge it sit with an operator no longer in the picture.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the full series
Gather every airframe, engine, and APU volume and export so the record can be read end to end.
Match the seams
Confirm each volume opens on the figure the prior one closed on and each change is logged both ways.
Reconcile totals to status
Check the running hours and cycles against the status lists that quote them.
Map and plan the breaks
Record every discontinuity and name the bridging evidence that would close it.
What the buyer receives
- A continuity map showing the logbook set as one running history
- A list of breaks, seams, and unexplained jumps with the evidence each needs
- A plan to bridge each discontinuity to a documented close
Who uses the output
- Records teams proving the utilization history holds before it anchors other status
- Asset managers relying on continuous totals to price the serial number
- Diligence teams confirming the logbook set runs unbroken across operators
How the work fits into the transaction or program
Continuity is the foundation the rest of the records file stands on, so this review runs early. Once the logbooks are proven continuous, the time and cycle totals they carry become the reliable base for AD applicability, life-limited standing, and the redelivery status that later reviews depend on. Any break it finds feeds remediation while the bridging records may still be recoverable.
Aircraft-specific considerations
The A350's long-haul mission drives high utilization per volume, so carry-forward arithmetic matters more here than on a short-cycle type, and a seam error grows quickly. Trent XWB engine changes and APU events add cross-book reconciliation points, and the aircraft's electronic technical-log practice means continuity often has to be proven across a mix of paper volumes and digital exports rather than a single physical series.
Regulatory limits
The review establishes whether the logbook record is continuous and internally consistent. It does not certify the utilization figures to an authority, return the aircraft to service, or make any airworthiness determination based on the totals it reconciles.
What this review does not cover
- Reconstructing utilization for a period no logbook or export covers
- Auditing the individual maintenance events recorded within the logbooks
- Any airworthiness determination drawn from the reconciled totals
Specific to this review
- Continuity almost always fails at a seam: a volume change, an engine or APU swap, or a change of operator, not in the middle of a book.
- High long-haul utilization makes a small carry-forward slip compound into a totals gap that then contradicts life-limited status.
- A gap spanning a change of custody is the hardest to bridge because the records that would close it sit with a party no longer involved.
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
What counts as a continuity break in a logbook set?
A break is any point where the record does not run cleanly across a seam: a volume that opens on a figure the previous one never reached, an engine or APU change missing from the airframe book, or utilization that is counted twice or skipped when the aircraft changed operators. The review flags each break and identifies the record that would bridge 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.