Logbook continuity
Bombardier CRJ family logbook-continuity records review
This review tests whether a CRJ's airframe, engine, and APU logbooks form an unbroken record from delivery to today, with no gap where hours, cycles, or maintenance history went unrecorded. It fits a team evaluating, transferring, or maintaining one tail, and it follows each logbook set through every volume change and operator handover. The work confirms utilization entries run continuous, that maintenance events tie to their release paperwork, and that the running totals reconcile across all four record streams. You receive an exception list of continuity breaks, a source map for the affected periods, and a closure plan for that airframe.
When this review is needed
- A CRJ is changing hands and the buyer needs the logbooks proven continuous from delivery forward.
- An engine or APU has been swapped and its logbook has to be reconciled to the airframe history.
- A logbook volume changed at an operator handover and the totals across the seam are in doubt.
- The tail's total time and cycles feed a pricing model that needs a defensible source.
The problem
A CRJ that has flown for two decades across several operators carries logbooks in many volumes, some paper, some scanned, some transcribed into a tracking system that then became the record everyone quotes. Every volume seam and operator change is a place where a cycle count can jump, an engine can arrive with a logbook that starts mid-life, or a period of utilization can go unrecorded entirely. The totals look authoritative until someone reconciles them line by line.
What gets reviewed
- Airframe utilization entries checked continuous from delivery through the current total
- Engine logbooks reconciled to the airframe at each installation and removal
- APU logbook continuity confirmed across swaps and operator changes
- Maintenance entries tied to the release paperwork that should accompany them
- Running totals cross-checked across logbooks, status lists, and any tracking system
- Volume-change and operator-handover seams examined for jumps or missing periods
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
- Utilization entries run continuous with no unexplained gap in hours or cycles
- Each engine and APU logbook reconciles to the airframe at its installation date
- A running total at a volume seam carries forward without a step change
- Maintenance entries reference the release documents that support them
- The logbook totals agree with the status lists and the tracking system, not any one source alone
Evidence normally required
- The complete airframe logbook set across all volumes
- Engine and APU logbooks with installation and removal history
- Component logbooks for time-controlled units where held
- Status lists and any tracking-system export of totals
- Release paperwork for the maintenance events entered in the logbooks
Common discrepancies
- A cycle count that jumps across a logbook volume seam with no bridging entry
- An engine logbook that begins mid-life with no history for the earlier period
- A stretch of utilization present in the tracking system but absent from the paper logbook
- A maintenance entry with no release document behind it
What is at stake
A break in logbook continuity puts every time-based status in doubt, because AD compliance, life-limited part life, and check intervals are all measured from totals the logbooks are supposed to prove. A gap discovered at a transaction forces a conservative assumption the owner pays for, and a break that cannot be closed can strand remaining life on an engine or a component that the records can no longer support.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Line up the streams
Assemble the airframe, engine, and APU logbooks in order across all volumes.
Test the seams
Check every volume change and operator handover for a jump or missing period.
Reconcile the totals
Cross-check running totals across logbooks, status lists, and the tracking system.
List the breaks
Record each continuity gap and order it by effect on time-based status.
What the buyer receives
- An exception list of continuity breaks by logbook stream and period
- A source map for each disputed period showing what supports and what is missing
- A closure plan ordered by which breaks most affect time-based status
Who uses the output
How the work fits into the transaction or program
Logbook continuity is the base every time-based CRJ record is measured from, so this review usually sits under the program, AD, and life-limited work and confirms the totals they rely on. Its exception list feeds the reconstruction a data room needs and the bridging a component or engine transaction requires.
Aircraft-specific considerations
CRJ tails accumulate cycles fast on short regional sectors, so the cycle count is the number most likely to disagree across a seam and the one buyers scrutinize hardest. Engine and APU changes are frequent on this type, which multiplies the installation and removal reconciliations, and long service lives mean many logbook volumes and at least one transcription into a tracking system to reconcile against.
Jurisdiction-specific considerations
FAA and EASA differ on logbook retention and on how continuity is evidenced across a register change, so a CRJ moving between systems is checked for the entries the receiving authority will expect, and periods that satisfied the prior system but not the receiving one are flagged.
Regulatory limits
The review confirms whether the logbooks are continuous and reconciled and identifies where they break. It does not reconstruct missing history on its own authority, correct a logbook, or determine that the aircraft is airworthy.
What this review does not cover
- Making or correcting logbook entries
- Reconstructing utilization that was never recorded anywhere
- Any airworthiness determination on the aircraft
Specific to this review
- On a CRJ the cycle count is the continuity figure most likely to break, because short sectors accumulate cycles far faster than hours.
- Volume seams and operator handovers are where continuity fails, since a fresh logbook rarely restates the closing total of the last one cleanly.
- When the tracking system and the paper logbook disagree, the paper entry is the record and the export is only a convenience, so the review reconciles to the source.
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 tracking system shows continuous totals. Why check the paper logbooks at all?
A tracking system is a transcription, and transcriptions inherit and hide the very gaps this review looks for. The paper logbook is the source of record, so continuity is proven against it and the tracking export is treated as a convenience to reconcile, not as evidence in itself.
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.