Logbook continuity
Pilatus PC-12 airframe and engine logbook continuity review
This review confirms that the airframe, engine, APU, and component logbooks for a Pilatus PC-12 form a continuous record with no unexplained break in utilization or maintenance entries. A records specialist runs it for an owner or buyer who needs the logbook history to be unbroken before status is drawn from it. It reads the books across ownership changes and volume transitions, checks that time and cycle figures carry forward without a jump, and confirms the entry stream is continuous. You receive an exception list keyed to the gaps, a source map across the logbook set, and a plan to bridge or reconstruct the breaks.
When this review is needed
- A PC-12 is being sold and the buyer will read the logbooks for any unexplained break in the history.
- The aircraft passed through several owners and the logbook volumes may not join cleanly at each handover.
- A logbook volume was replaced or reconstructed and the carry-forward figures have not been confirmed.
- Time and cycle totals on the status lists have to be reconciled back to the logbook entries.
The problem
Logbook continuity is the spine the rest of a PC-12 file hangs on, and it breaks most often at the seams: a change of owner, a new volume, or a period when the aircraft sat and the entries thinned out. A carry-forward figure copied at the top of a new volume can disagree with the bottom of the last one, and a gap in the entry stream can hide a stretch of unrecorded utilization. The books look continuous because each volume reads cleanly on its own, while the joins between them were never checked.
What gets reviewed
- Airframe, engine, APU, and component logbooks read as a set for continuity
- Carry-forward time and cycle figures checked across each volume transition
- The entry stream examined for unexplained gaps in utilization or maintenance
- Ownership handovers checked for a clean join between the outgoing and incoming records
- Replaced or reconstructed volumes confirmed against the figures they carry forward
- Logbook totals reconciled with the status lists built from them
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 figures carry forward across each volume transition without an unexplained jump
- The entry stream is continuous with no silent gap in utilization or maintenance
- Each ownership handover joins the outgoing and incoming records without a break
- A replaced or reconstructed volume agrees with the figures it claims to continue
- Logbook totals reconcile with the AD, LLP, and time status lists drawn from them
Evidence normally required
- The airframe, engine, APU, and component logbooks or their digital equivalents
- The status lists built from the logbook figures for reconciliation
- Ownership and handover records marking the volume transitions
- Any reconstructed or replaced logbook volume and its supporting basis
Common discrepancies
- A carry-forward figure at the top of a new volume that disagrees with the prior volume's close
- A gap in the entry stream across a change of ownership with no bridging record
- A reconstructed volume whose figures cannot be tied to the period it replaced
- Logbook totals that do not reconcile with the status list built from them
What is at stake
A break in logbook continuity puts every time and cycle figure downstream in doubt, because the status lists are only as reliable as the entries they were built from. A buyer treats an unexplained gap as unrecorded time and prices it conservatively, and reconstructing a missing logbook period from third-party sources after a sale has started is slow and rarely complete.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the volumes
Lay out the airframe, engine, APU, and component books in sequence across the ownership history.
Check the seams
Confirm carry-forward figures agree at each volume transition and handover.
Read the stream
Examine the entry stream for unexplained gaps against the utilization pattern.
Reconcile and flag
Tie logbook totals to the status lists and list the continuity breaks to close.
What the buyer receives
- An exception list keyed to each continuity gap in the logbook set
- A source map across the airframe, engine, APU, and component books
- A closure plan to bridge or reconstruct the breaks in the history
Who uses the output
- Asset managers pricing the utilization history the logbooks can prove
- Records teams bridging or reconstructing the logbook gaps before a sale
- Buyers relying on a continuous logbook history behind the status lists
How the work fits into the transaction or program
The continuity review underpins every status view built on the PC-12 file, since AD, LLP, and time status all trace back to logbook entries. It runs before a sale so a break at a volume seam or an ownership handover is found while the records to bridge it can still be gathered, and its exception list drives the reconstruction ahead of diligence.
Aircraft-specific considerations
A PC-12 that has moved between owner-operators tends to accumulate logbook volumes filled by different hands, and continuity of the entry stream across those handovers is where the history most often breaks. Periods of light or seasonal use can thin the entries to the point where a genuine gap is hard to tell from a quiet stretch, so the review reads the utilization pattern alongside the maintenance entries.
Regulatory limits
The review confirms the logbook history is continuous and reconciles with the status lists, and flags where it breaks. It does not recreate maintenance that was never performed, certify the utilization figures, or make an airworthiness determination on the aircraft.
What this review does not cover
- Recreating maintenance or utilization that was never recorded
- Physical inspection of the aircraft
- Any airworthiness determination on the aircraft
Specific to this review
- Logbook continuity breaks most often at the seams between volumes and at ownership handovers, not in the middle of a volume that reads cleanly on its own.
- On a lightly used PC-12 a genuine gap in the entry stream can look like a quiet period, so the utilization pattern has to be read alongside the maintenance entries.
- A carry-forward figure at the top of a new volume is an assertion, not a proof, until it is checked against the close of the volume before it.
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
The logbooks are all present. Why check continuity?
Having every volume is not the same as the volumes joining cleanly. The review checks the carry-forward figures and the entry stream at each seam and handover, because that is where continuity breaks and where a buyer reads unrecorded time.
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.