Logbook continuity checks for a modification-baseline source file

When this review is needed

• Logbook volumes arrived from a prior operator with date ranges that do not quite meet, and modifications fall inside the gap.
• An engine swap mid-lease means the logbook that recorded a mod may have left the aircraft with the removed engine.
• The baseline claims embodiment dates the logbooks were never checked to confirm.
• A registry transfer replaced the logbook format and nobody verified the carry-over entries against the old volumes.

The problem

Logbooks accumulate across operators, registries, and record-keeping styles, and the seams between eras are where continuity fails. One era summarizes checks in a single line, another lists every task; one operator logged mods in the airframe book, another only in the mod status report. When a modification's embodiment date has to be pinned down years later, the entry may sit in a volume that stayed behind at a previous lessee, or inside a summarized check entry that never named the mod at all.

What gets reviewed

• Date-range continuity across every airframe, engine, and APU volume in the file
• A logbook entry located for each modification the baseline claims as embodied
• Custody and operator changes matched to transfer documentation
• Utilization steps at each seam, checked against hours and cycles claimed either side
• Summarized check entries expanded against the underlying work-package records
• Volumes referenced by other records but absent from the file, logged as missing

What gets validated

• Consecutive entries leave no unexplained calendar gap during periods the aircraft was active
• Embodiment entries name the modification and date consistently with the SB or STC record in the source file
• Engine and APU logbook histories align with the removal and installation record for each position
• Hours and cycles at each custody seam carry across without an unexplained step
• Entries made after a registry change reconcile with the closing figures of the prior registry's volumes

Evidence normally required

• All available airframe, engine, and APU logbook volumes or certified digital equivalents
• The modification status report and embodiment evidence from the source package
• Removal and installation history for engines and APU
• Transfer, lease, and registry-change documentation covering custody seams
• Utilization statements for the periods around each suspected gap

Common discrepancies

• A months-long silence in an otherwise dense logbook, coinciding with storage that no entry declares
• Embodiment recorded in the mod status report while the corresponding logbook entry names only a check number
• An engine logbook whose early volumes followed a removed engine and were never recovered
• Carry-over totals after a registry change that differ from the closing totals of the old volumes

What is at stake

An embodiment claim without a logbook entry behind it invites the question of whether the work entered the aircraft's record at all, and that question spreads doubt to neighboring claims. Buyers and auditors treat continuity breaks as risk concentrations: whatever happened inside the gap must be assumed unfavorable until shown otherwise, and that assumption is priced accordingly.

How the work runs

What the buyer receives

• A continuity map showing every volume, seam, and gap across the three logbook streams
• An exception list pairing each unsupported embodiment claim with the specific missing entry or volume
• A recovery plan naming the custodian most likely to hold each absent volume

Who uses the output

• Configuration managers anchoring embodiment dates in the baseline
• Records leads negotiating volume recovery with prior operators and lessors
• Technical buyers weighing continuity risk ahead of a transaction

How the work fits into the transaction or program

Continuity work anchors the rest of the modification-baseline review in time. Task-card and status-report findings both resolve against embodiment dates, and those dates are only as reliable as the logbook chain that carries them, so this strand typically runs early and its map is reused by every other strand.

Jurisdiction-specific considerations

Retention duties diverge: 14 CFR 91.417 and 91.419 govern which records transfer with a US-registered aircraft and for how long they must be kept, while Regulation 1321/2014 places continuing-airworthiness records with the operator or CAMO under its own retention clock. Aircraft that crossed between systems often show exactly one weak seam per crossing, and that is where the review concentrates.

Regulatory limits

The review documents the state of the logbook chain. It does not certify continuity to any authority, does not determine airworthiness, and does not recreate or backfill logbook entries; a gap that cannot be closed from source is reported as a gap.

What this review does not cover

• Creation of substitute or reconstructed logbook entries
• Authentication of signatures or forensic document examination
• Chasing volumes beyond the custodians identified in the recovery plan

Specific to this review

• Storage periods are the leading benign explanation for logbook silence, but only an entry or a storage certificate makes the explanation usable in a baseline.
• Engine logbooks fail continuity differently than airframe books because the engine's travel between aircraft multiplies the custody seams.
• A summarized check entry is not itself a defect; it becomes one when the underlying work package that would expand it has been purged.
• The cheapest moment to fix a seam is immediately after the custody change that created it, while both parties still answer their mail.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits