A320 family logbooks
Airbus A320 family logbook continuity records review
This review checks that the airframe, engine, APU, and component logbooks for an Airbus A320 family aircraft form an unbroken record of utilization and maintenance from origin to date. It is run for a lessor, operator, or manager evaluating or transferring an A320 family asset whose logbooks have passed through several operators. The work follows the continuity file for gaps in dates, hours, cycles, and custody, and reconciles the running totals across the books. You receive a supported exception list, a source map of the continuity breaks, and a closure plan for the specific serial number.
When this review is needed
- A tail with several prior operators is being sold and the logbooks have to show unbroken history.
- Running hours and cycles disagree between the logbooks and the status list.
- A change of custody left a stretch of the record thin and a buyer wants it explained.
- An engine or APU was swapped and its logbook has to bridge onto the airframe history.
The problem
An A320 family aircraft carries airframe, engine, APU, and component logbooks that have to line up across every operator that held it, and continuity breaks where custody changed. A stretch of missing entries, a running total that jumps between volumes, or an engine book that does not bridge onto the airframe at installation all leave the utilization history open to question. The books can look complete page by page while the totals across them do not close.
What gets reviewed
- Airframe logbook continuity from origin through the current entry
- Engine and APU logbooks bridged onto the airframe at each installation and removal
- Running hours and cycles reconciled across logbook volumes and the status list
- Custody changes checked for the entries that should carry across each transfer
- Component logbooks reconciled to their installation and removal history
- Utilization entries checked for internal consistency at rate and interval
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 carry forward continuously across every logbook volume
- Engine and APU book totals bridge onto the airframe at installation and removal
- The logbook running totals reconcile to the current status list
- Each change of custody shows the entries that should have carried across it
- Utilization rates between entries are internally consistent with the operation
Evidence normally required
- Airframe, engine, APU, and component logbooks or their digital equivalents
- The logbook continuity file assembled for the tail
- The current time and cycle status list
- Installation and removal records for the engines and APU
- The custody and ownership history for the aircraft
Common discrepancies
- A stretch of missing entries across a change of custody
- Running totals that jump between two logbook volumes
- An engine book that does not bridge onto the airframe at installation
- Logbook totals that disagree with the status list a buyer will price against
What is at stake
A logbook history that does not close undermines every status derived from hours and cycles, including LLP life and the maintenance program status. A break at a change of custody is hard to reconstruct once the prior operator's records team has moved on, and a buyer will discount the whole asset for a utilization record it cannot rely on.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the chain
Order the airframe, engine, APU, and component books along the custody history of the tail.
Follow the totals
Carry hours and cycles across every volume and reconcile them to the status list.
Bridge the swaps
Confirm engine and APU books join the airframe at each installation and removal.
List the breaks
Flag each continuity gap and total discrepancy and plan its reconstruction.
What the buyer receives
- A supported exception list of the continuity breaks and total discrepancies
- A source map showing where the record breaks against custody and installation history
- A closure plan to reconstruct or reconcile the broken stretches
Who uses the output
- Asset managers relying on a defensible utilization history to price the tail
- Records teams reconstructing the continuity file before a transfer
- Continuing-airworthiness teams confirming hours and cycles feed status correctly
How the work fits into the transaction or program
Logbook continuity is the foundation the utilization-derived statuses rest on, so this review runs before LLP, program, and modification status are trusted on the tail. Its exception list drives reconstruction of the broken stretches while the prior operators are still reachable, and the reconciled totals anchor the time and cycle figures the whole records file depends on.
Aircraft-specific considerations
A320 family aircraft trade frequently and accumulate cycles fast under short-sector operation, so a given tail often carries a long chain of custody with several logbook handovers, each a place continuity can break. Engine and APU swaps are common, which makes the bridge between component and airframe books a recurring point of discrepancy, so the review weights the checks toward custody changes and installation events.
Jurisdiction-specific considerations
Logbook conventions and required entries differ between FAA and EASA operators, so a book maintained under one system may not carry the entries the other expects across a transfer. The review notes where a continuity break coincides with a register change and where the receiving system will need entries reconstructed to its own convention.
Regulatory limits
The review confirms the logbooks form a continuous, internally consistent utilization and maintenance record. It does not certify hours and cycles on an authority's behalf, reconstruct maintenance that was not recorded, or determine that the aircraft is airworthy.
What this review does not cover
- Physical verification of hours and cycles against the aircraft
- Reconstructing maintenance that was never recorded in the books
- Any airworthiness determination tied to the utilization history
Specific to this review
- Continuity almost always breaks at a change of custody, not in the middle of one operator's tenure.
- Logbooks can look complete page by page while their running totals fail to close across volumes.
- An engine or APU book that does not bridge onto the airframe at installation orphans the utilization it carries.
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
Why do logbook gaps cluster around ownership changes?
A change of custody is where records physically move between organizations, so entries get dropped, volumes get split, and totals restart. The review concentrates on those handovers because a stretch that looks thin in the middle of one operator's tenure is far less common than a break at the boundary between two.
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.