Airbus A220 family logbook continuity records review

When this review is needed

• A buyer needs the logbook trail proven continuous from entry into service before pricing the tail.
• The aircraft passed between operators and the utilization has to reconcile across the handover.
• An engine or APU was swapped and its logbook has to bridge onto the airframe record cleanly.
• The logbooks moved from paper to a digital record and the continuity across that change was never checked.

The problem

Logbook continuity is the spine every status figure hangs on, and a break in the spine undermines everything above it. Utilization and maintenance entries have to run unbroken across airframe, engine, APU, and component books, but a custody change, an engine swap, or a move to a digital record is where a page goes missing or a figure stops agreeing between books. The totals still look reasonable, so the discontinuity hides until someone reconciles the entries across the seam and finds the trail does not actually connect.

What gets reviewed

• Airframe utilization traced unbroken from entry into service to the current total
• Engine and APU logbooks reconciled to the airframe across installs and removals
• Component logbooks checked for continuity across their recorded history
• Utilization figures reconciled across airframe, engine, and APU books for the same periods
• Custody changes examined as the points where continuity most often breaks
• Continuity breaks flagged where entries are missing or figures do not agree across books

What gets validated

• Airframe hours and cycles run continuously with no unexplained gap in the entries
• Engine and APU utilization reconciles to the airframe across every install and removal
• Utilization for the same period agrees across the airframe, engine, and APU books
• Each custody change carries a clean handover with entries continuing across it
• The move from paper to digital, where it occurred, preserved the entries across the change

Evidence normally required

• The airframe, engine, APU, and component logbooks or their digital equivalents
• Utilization and maintenance entries across the logbook set
• Install and removal records for the engines and APU
• Custody and operator history for the tail
• Any prior continuity file or logbook index maintained for the aircraft

Common discrepancies

• An airframe utilization gap across a change of operator with no bridging entry
• Engine hours that do not reconcile to the airframe over an installed period
• An APU logbook that stops at a swap and never resumes on the current unit
• Entries lost in the move from paper logbooks to a digital record

What is at stake

A logbook break forces conservative assumptions about the period it covers, which can pull maintenance forward or cast doubt on the utilization every LLP and interval is calculated from. At a sale a discontinuity becomes a discount or a hold while the missing entries are chased, and reconstructing a logbook period after the operator who flew it has moved on is among the hardest records tasks there is.

How the work runs

What the buyer receives

• A supported exception list of continuity breaks across the logbook set
• A source map reconciling utilization across the airframe, engine, and APU books
• A closure plan to recover or reconstruct the missing logbook periods for the tail

Who uses the output

• Records teams proving logbook continuity before a sale or a lease event
• Asset managers confirming the utilization every status figure rests on
• Buyer diligence teams verifying the trail runs unbroken from entry into service

How the work fits into the transaction or program

Logbook continuity is the foundation the AD, LLP, and program reviews all build on, because their status figures come from the utilization the logbooks record. This review confirms that foundation is unbroken before the rest of the file is relied on, so a buyer prices from a proven utilization history and a receiving operator inducts on a trail that actually connects.

Aircraft-specific considerations

A220 tails are recent enough that a continuous logbook trail back to entry into service is realistic to prove, which raises rather than lowers the expectation that it exists. Many A220 records are digital from early in the aircraft's life, so the continuity risk sits less in aged paper and more at operator handovers and at any migration between record systems. The review concentrates on those seams, where a young fleet's logbook trail is most likely to break.

Jurisdiction-specific considerations

FAA and EASA maintain different expectations for how utilization and maintenance entries are recorded and retained, so a logbook set built under one system and moving to the other may show entries the receiving side records differently. The review notes where the logbook trail will need reformatting or supplementary entries to satisfy the receiving system's continuity expectations.

Regulatory limits

The review reconciles the logbooks for continuity and internal agreement. It does not make an entry, certify utilization, or determine airworthiness. Confirming the trail is continuous is an evidence check, not an attestation of the maintenance the entries record.

What this review does not cover

• Making or amending any logbook entry
• Physical inspection or verification of the aircraft's utilization
• Any airworthiness determination on the aircraft

Specific to this review

• Logbook continuity is the spine every status figure hangs on, so a break there propagates into AD, LLP, and interval calculations.
• Totals can look reasonable while the entries behind them do not actually connect across a seam.
• On a young A220 the continuity risk concentrates at operator handovers and system migrations, not in aged paper.
• Reconstructing a logbook period after the operator who flew it has moved on is among the hardest records tasks there is.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits