Dash 8 logbooks
De Havilland Dash 8 logbook continuity records review
This review checks that the airframe, engine, and APU logbooks for a De Havilland Dash 8 form an unbroken record from entry into service to today, with utilization and maintenance entries that carry across every volume and operator change. It reads the logbook continuity file for missing books, gaps at custody changes, and utilization that does not reconcile between the airframe and its major components. A records specialist runs it before a transaction or a register change where an intact history is required. You receive a supported exception list, a source map of the logbook run, and a closure plan for the breaks.
When this review is needed
- A Dash 8 is being sold and the buyer requires an intact logbook history with no missing volumes.
- The aircraft has changed operators several times and the books were handed over piecemeal.
- Utilization in the logbooks has to reconcile with the status lists before diligence opens.
- A register change requires a continuous maintenance history the receiving authority accepts.
The problem
The logbooks are the spine of the records: every status list ultimately reconciles back to them. On a Dash 8 that has passed through several operators, a logbook volume goes missing at a handover, utilization entries stop and restart across a custody change, or the airframe hours in the book disagree with the engine and APU books. A gap in the run is more than a missing document. It marks a stretch of the aircraft's life that cannot be accounted for, and it undermines everything computed downstream.
What gets reviewed
- Airframe, engine, and APU logbooks checked as a continuous run with no missing volumes
- Utilization entries reconciled across the airframe and its major components
- Custody changes checked for breaks in the entry sequence
- Component logbooks tied to the airframe history at install and removal
- Opening entries in each new volume reconciled to the closing of the last
- Maintenance entries checked for continuity across operator transitions
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
- The logbook run is continuous with each volume's opening tied to the prior close
- Airframe, engine, and APU utilization reconcile at every point they should agree
- No entry sequence breaks unexplained at a change of operator or custody
- Component logbooks align with the airframe record at install and removal
- Every referenced logbook volume is present in the continuity file
Evidence normally required
- The airframe, engine, and APU logbooks in full
- Component logbooks for major installed items
- The status lists that reconcile back to the logbooks
- Custody and operator-change history for the tail
- Utilization records supporting the logbook entries
Common discrepancies
- A missing logbook volume across a change of operator
- Airframe hours in the book that disagree with the engine or APU record
- An entry sequence that stops and restarts without an explanation
- A component logbook that does not align with the airframe install record
What is at stake
A missing logbook volume forces a reconstruction from secondary records if it can be done at all, and a buyer prices the uncertainty steeply. Utilization that does not reconcile across the airframe, engine, and APU books puts every derived status figure in doubt, and a register change can stall until the receiving authority is satisfied the history is continuous.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Lay out the run
Order the airframe, engine, and APU volumes and confirm none are missing from the sequence.
Tie the volumes
Reconcile each volume's opening entry to the close of the one before it.
Reconcile utilization
Check that airframe, engine, and APU hours and cycles agree where they should.
Flag the breaks
Record missing volumes and unexplained gaps with the evidence needed to close them.
What the buyer receives
- A supported exception list of missing volumes and continuity breaks
- A source map of the logbook run across the aircraft's life
- A closure plan for reconstructing or accounting for the gaps
Who uses the output
- Records teams confirming the logbook spine before status work rests on it
- Asset managers pricing the uncertainty behind a broken history
- Buyers and authorities requiring a continuous maintenance record
How the work fits into the transaction or program
Logbook continuity is the foundation the AD, LLP, and program reviews all reconcile back to, so it is checked before those are relied on. Its exception list drives the reconstruction of missing volumes while prior operators can still supply copies, and its source map anchors every utilization figure the rest of the file depends on.
Aircraft-specific considerations
Dash 8 tails change operators often across regional markets, so the logbook run typically spans several custody changes and each handover is a candidate for a missing volume. High-cycle regional utilization also means the books fill and roll over faster than on a long-haul asset, multiplying the volumes that have to be present and continuous.
Jurisdiction-specific considerations
FAA and EASA differ on how a continuous maintenance history is demonstrated at a register change, so a Dash 8 crossing that boundary needs its logbook run presented to satisfy the receiving authority. The review notes where the continuity evidence will need supplementing for the receiving system.
Regulatory limits
The review confirms the logbook history is continuous and internally consistent. It does not reconstruct maintenance that was never recorded, recreate a missing volume as an authority, or make an airworthiness determination on the aircraft.
What this review does not cover
- Recreating a missing logbook volume as an official record
- Reconstructing maintenance that was never performed or recorded
- Any airworthiness determination on the aircraft
Specific to this review
- The logbook run is the spine every status list reconciles back to, so a gap in it undermines figures computed far downstream.
- The change of custody between operators is where a Dash 8 logbook volume most often goes missing, because the handover was rushed.
- Utilization that reconciles across the airframe, engine, and APU books is the fastest test of whether the history is real or patched together.
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
One logbook volume is missing but the status lists look complete. Is that a problem?
Yes. The status lists reconcile back to the logbooks, so a missing volume is a stretch of the aircraft's life that cannot be independently verified. A buyer or a receiving authority will treat the gap as uncertainty and price or condition acceptance around it. The review documents the break and the plan to reconstruct it from secondary records where possible.
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.