Logbook continuity
Embraer E-Jet logbook-continuity records review
This review reads the airframe, engine, and APU logbooks for a specific Embraer E-Jet and confirms the utilization and maintenance entries run continuously, with no gap at a change of operator, a volume change, or an engine swap. It is run before a transaction or when an asset's history has passed through several hands and the running totals have to be trusted. It checks that time and cycle figures carry forward without a break, that each logbook volume hands off cleanly to the next, and that maintenance entries reconcile to the status list. You receive an exception list of continuity breaks, a source map across the volumes, and a plan to bridge each gap.
When this review is needed
- An E-Jet is being sold and the buyer needs the running time and cycle totals to trace unbroken to source.
- The aircraft has changed operators and each handoff between logbook custodians has to be checked for a gap.
- An engine or APU was swapped and its logbook has to reconcile with the airframe utilization at the swap.
- Digital records replaced paper volumes at some point and the transition has to be shown to lose nothing.
The problem
Continuity breaks where custody changes. An E-Jet that has moved between regional operators carries logbooks that were closed by one team and opened by another, and the closing figure in one volume does not always match the opening figure in the next. A digital system that replaced paper somewhere in the history may have carried a rounded or a transposed total forward. None of this shows on a status list, which reports a single running number as if the chain behind it were whole.
What gets reviewed
- Airframe total time and cycles traced continuously across every logbook volume
- Each volume handoff checked so the closing figure equals the opening figure of the next
- Engine and APU logbooks reconciled to the airframe at each installation and removal
- Maintenance entries in the logbooks reconciled against the status list they support
- Any paper-to-digital transition confirmed to carry forward the totals without loss
- Utilization gaps across changes of operator identified and bounded
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 and opening totals match at every logbook volume boundary
- Engine and APU accumulated time reconciles with the airframe at each swap
- The running time and cycle totals agree with the status list and any tracking export
- A paper-to-digital transition preserves the totals with no rounding or transposition
- No calendar period passes with utilization but no corresponding logbook entry
Evidence normally required
- The complete set of airframe logbook volumes, paper and digital
- Engine and APU logbooks with installation and removal history
- The current time and cycle status list or tracking export
- The operating and ownership history that establishes the custody changes
- Any continuity file or handoff records assembled at prior transitions
Common discrepancies
- A closing total in one logbook volume that does not match the opening total of the next
- An engine whose accumulated time does not reconcile with the airframe at its installation
- A paper-to-digital handover that carried a transposed or rounded time figure
- A calendar gap where the aircraft flew but no logbook entry records the period
What is at stake
A running total the logbooks cannot support is a number the buyer discounts, because every status computed from it inherits the doubt. A gap at an engine swap can leave the engine's accumulated time in question, which matters directly to its LLP standing and its residual value. A break at a volume handoff that is found late, mid-diligence, reopens the whole utilization history at the worst moment.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the volumes
Assemble the airframe, engine, and APU logbooks in sequence and mark every boundary.
Trace the totals
Follow the running time and cycle figures across each boundary and confirm they carry forward.
Reconcile the swaps
Check engine and APU accumulated time against the airframe at each installation and removal.
Bound the gaps
Identify each continuity break and map the records that could bridge it.
What the buyer receives
- An exception list of continuity breaks with the volume and boundary where each occurs
- A source map tracing the running totals across every logbook volume
- A plan to bridge each gap with the supporting records that close it
Who uses the output
- Asset managers relying on the running totals to price the aircraft and its engines
- Records teams assembling a continuity file the buyer's diligence can verify
- Continuing-airworthiness teams confirming utilization before they compute status
How the work fits into the transaction or program
Logbook continuity underpins every time-driven status the aircraft carries, because AD due-dates, task intervals, and LLP life all compute off the running totals the logbooks establish. The review runs before the totals are relied on, and its exceptions feed the bridging that has to close before a buyer will accept the utilization history.
Aircraft-specific considerations
E-Jets on regional networks accumulate cycles quickly relative to hours, so the cycle count is as load-bearing as the hour count, and a break in cycle continuity at a volume boundary is as consequential as a missing hours figure. Engine changes are common across an E-Jet's service life, and each swap is a point where the engine and airframe utilization have to be reconciled separately, so the review treats every installation and removal as a continuity checkpoint.
Jurisdiction-specific considerations
The recordkeeping expectations for logbook retention and content differ between the FAA framework and EASA continuing-airworthiness rules, so a continuity file built for one register may need reformatting or supplementary entries for the other. The review notes where a volume acceptable in its origin system needs additional support for the receiving one.
Regulatory limits
The review confirms the logbooks run continuously and reconcile to the status list. It does not reconstruct utilization that was never recorded, certify the totals, or make an airworthiness determination based on them.
What this review does not cover
- Reconstructing flight time or cycles that were never logged
- Certifying or endorsing the running totals on an authority's behalf
- Any airworthiness determination derived from the utilization history
Specific to this review
- Continuity almost always breaks at a boundary: a volume change, an operator change, or a paper-to-digital transition, not in the middle of a settled record.
- On a regional jet the cycle count carries as much weight as the hours, so a cycle continuity break is not a lesser finding.
- Every engine swap is a separate continuity checkpoint, because the engine logbook and the airframe have to agree at the installation date independently.
- A paper-to-digital transition can carry a rounded or transposed total forward, and the status list shows a single clean number that hides the discrepancy.
- A running total the logbooks cannot support is a number the buyer discounts, because every AD due-date and LLP life computed from it inherits the same doubt.
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 happens if a total does not carry forward across a volume change?
The gap is bounded and traced to whatever records can reconcile the two figures, such as the entries either side of the boundary or a tracking export from the period. Where the difference cannot be reconciled, it is carried as a documented continuity break with its magnitude stated, which is more defensible than presenting a running total the logbooks do not support.
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.