Logbook continuity
ATR 72 airframe, engine, and APU logbook continuity review
This review confirms that the ATR 72 airframe, engine, and APU logbooks form an unbroken history with no missing volumes, gaps in time and cycle accrual, or entries that contradict each other. A records specialist runs it during acquisition, before redelivery, or whenever a change of custody makes the utilization record uncertain. It traces total time and cycles forward through every logbook, reconciles them against status lists and shop reports, and locates the points where continuity breaks. You receive a continuity map, a list of gaps with their probable cause, and the source references that either close or bound each break.
When this review is needed
- An ATR 72 has passed through several operators and the logbook set has never been continuity-checked end to end.
- An engine or APU came back from a shop visit and the returned logbook has to splice cleanly into the airframe history.
- A buyer needs total time and cycles proven from source rather than accepted from a tracking summary.
- A logbook volume is suspected missing and the time it should cover has to be bounded.
The problem
Continuity is the spine every other record hangs from, and it breaks quietly. A logbook volume goes missing during a lease transfer, a shop returns an engine with its own book that does not reconcile to the airframe, or a period of operation under a foreign register leaves a stretch where entries thin out. On an ATR 72 that has moved between regional operators, these breaks stack up, and each one puts the total time and cycle figure into question.
What gets reviewed
- Airframe total time and cycles traced continuously across every logbook volume
- Engine and APU logbooks spliced into the airframe timeline at each installation and removal
- Utilization entries reconciled against status lists and shop-visit reports
- Periods of operation under a prior or foreign register identified and bounded
- Missing or suspected-missing volumes located and the interval they cover estimated
- Contradictory time or cycle entries flagged and resolved to the most supported figure
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
- Time and cycle totals carry forward without an unexplained jump between logbook volumes
- Each engine and APU installation reconciles to the airframe entry that records it
- Utilization in the logbooks agrees with the totals on current status lists
- A suspected-missing volume is confirmed present or its covered period is bounded
- Where two entries disagree, the review states which figure the evidence supports and why
Evidence normally required
- The complete airframe, engine, and APU logbook set, physical or scanned
- Current time and cycle status lists for the aircraft and its engines
- Shop-visit reports for engine and APU events during the period reviewed
- Any prior continuity file or handover record from an earlier transfer
Common discrepancies
- A logbook volume missing across a change of operator, leaving a bounded but unproven interval
- An engine returned from shop whose book does not reconcile to the airframe installation entry
- Total time that steps up between volumes with no accounting entry explaining the jump
- A period under a foreign register where utilization entries are sparse or absent
What is at stake
A break in logbook continuity puts the burden of proof on the current owner to show what happened during the gap. Unbounded, it undermines LLP life calculations, AD applicability, and inspection intervals, all of which count from a time base the gap makes uncertain. At sale, an uncontinuous logbook history is one of the fastest ways to lose value on a turboprop.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Lay out the timeline
Order every logbook volume for airframe, engine, and APU and mark the spans each covers.
Trace time and cycles
Carry totals forward through the volumes and reconcile them to status lists and shop reports.
Locate the breaks
Identify missing volumes, unexplained steps, and contradictions, and bound each interval.
Reference the resolution
Cite the source that closes each break or record the limit where none exists.
What the buyer receives
- A continuity map showing the unbroken spans and the breaks in the logbook history
- A gap list with each break's probable cause and the interval it covers
- The source references that close each break or define its bounds
Who uses the output
- Records teams establishing a defensible time and cycle base for the asset
- Asset managers pricing the exposure a continuity gap creates at sale
- CAMO leads relying on a proven time base for interval and life tracking
How the work fits into the transaction or program
Logbook continuity comes first because everything downstream counts from the time base it establishes. Once the history is proven unbroken, LLP life, AD status, and inspection intervals can be trusted; where a break remains, it is bounded and carried as a known limit into the baseline, the data room, or the redelivery file.
Aircraft-specific considerations
The ATR 72 runs high daily cycles on short regional legs, so cycle accrual outpaces flight-hour accrual and continuity errors surface first in the cycle count. Frequent engine and propeller shop visits in this operation mean the airframe-to-component logbook splice is a common break point, and the review checks each installation entry against the returning shop book.
Jurisdiction-specific considerations
An ATR 72 that operated under both FAA and EASA registers carries logbook conventions from each, and a transfer between them is a frequent site of a missing volume. The review notes where continuity has to be reconstructed to the receiving system's recordkeeping rather than the register the entries were made under.
Regulatory limits
The review establishes what the logbooks support about continuity and utilization. It does not certify the time and cycle figures on any authority's behalf, does not reconstruct maintenance that was never recorded, and makes no airworthiness determination.
What this review does not cover
- Recreating logbook entries for a period no source record covers
- Certifying total time or cycles for a regulatory filing
- Any airworthiness determination based on the reconstructed history
Specific to this review
- On a high-cycle turboprop the cycle count breaks before the hour count, so continuity errors show up there first.
- The airframe-to-engine logbook splice at each shop visit is the most common single break point in this family.
- A bounded gap is worth far more at sale than an unbounded one, because it converts an open question into a defined limit.
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 to a period where a logbook volume is genuinely missing?
The review bounds it: it establishes the time and cycle range the missing volume must cover using the entries on either side, so the gap becomes a defined limit rather than an open question. That bounded figure is what the baseline and any transaction carry forward.
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.