Airframe, engine, and APU logbook continuity at import and export

When this review is needed

• The aircraft has passed through several operators and no single team has read the logbooks end to end.
• Total time or cycles in the export application come from a tracking system rather than the logbook record.
• A storage period, incident, or operator collapse sits in the aircraft's history and its documentation is untested.
• Some logbook entries are in a language or format the importing authority is unlikely to accept as delivered.

The problem

Every operator keeps logbooks its own way, and each handover splices the styles together: paper into digital, one language into another, entry conventions changing mid-book. Totals get restated at transitions with the reconciliation living in an email long deleted. The current owner sees a stack of books; the importing authority sees a chronology it will test for the one break the seller did not know about.

What gets reviewed

• Entry-by-entry chronology review of the airframe logbook across the ownership history available
• Engine and APU logbooks for the currently installed units, including installation and removal entries
• Hours and cycles progression, tested for monotonic accumulation and against the status summaries
• Custody and operator changes, matched to the transfer documentation at each transition
• Storage, preservation, and reactivation periods and their required entries
• Alignment of logbook totals with the figures on the draft export application

What gets validated

• No unexplained gap exists between consecutive entries relative to the aircraft's known activity
• Hours and cycles never decrease, and step changes are supported by a documented reconciliation
• Each currently installed engine and the APU has an installation entry consistent with its removal from the prior position
• Operator and custody changes in the books match the bills of sale, lease records, or transfer letters available
• Totals quoted in the export application and status summaries agree with the logbook progression at the same date

Evidence normally required

• All airframe, engine, and APU logbooks, paper or digital, covering the traceable history
• Status summaries and utilization reports current at package assembly
• The draft export application and registry-change file with the totals being declared
• Transfer documents marking operator and ownership changes
• Storage and preservation records for any inactive periods

Common discrepancies

• A months-long silence in the airframe book covering a storage period that has no preservation entries
• Hours restated at an operator change with no surviving reconciliation for the difference
• An installed engine whose logbook lacks the installation entry for its current position
• Entries in a language requiring certified translation the timeline has not budgeted for

What is at stake

A continuity break discovered by the authority undermines the numbers everything else in the package depends on. Total time feeds the maintenance status, cycles feed LLP life, and custody history feeds the credibility of the whole file, so an unexplained gap forces reconstruction work under transfer deadline pressure and can push the registry date while affidavits, translations, or prior-operator statements are assembled.

How the work runs

What the buyer receives

• A continuity map of the logbook record showing verified spans, breaks, and restatements
• An exception list for every gap, with the reconstruction route available for each
• A totals reconciliation between logbooks, status summaries, and the export application

Who uses the output

• Transition leads declaring totals to the authority with evidence behind them
• Records teams commissioning translations, affidavits, or prior-operator confirmations
• The importing operator's CAMO anchoring its utilization records to a verified starting figure

How the work fits into the transaction or program

Continuity findings ripple outward: a corrected total time changes the maintenance status, a corrected cycle count changes LLP remaining life, and a custody gap changes what the modification and repair histories must independently prove. This review therefore runs early, so the rest of the package is built on numbers that hold.

Jurisdiction-specific considerations

Records retention and transfer at sale sit under 14 CFR 91.417 and 91.419 on the FAA side, while EASA-managed aircraft carry continuing-airworthiness records under Regulation 1321/2014, and the two regimes differ in what they expect a logbook to contain versus what may live in operator systems. A transfer between them often exposes information that exists but sits in the wrong place for the destination's habits.

Regulatory limits

The review characterizes the logbook evidence as found. It does not certify total time or cycles, does not create or reconstruct logbook entries, and does not determine whether the record satisfies any authority's import requirements. Declarations to authorities remain the responsibility of the applicant.

What this review does not cover

• Creation of replacement or reconstructed logbook entries
• Certified translation services, which are arranged separately once needs are identified
• Verification of flight activity against external sources such as movement databases

Specific to this review

• Continuity breaks cluster at operator changes rather than random points; the handover weeks are where entries stop while responsibility is ambiguous.
• An authority reads the logbooks before the summaries, so a package whose books contradict its status sheets fails in the first hour of review.
• Translation and notarization of foreign-language entries routinely takes longer than teams expect and is one of the most common late-timeline surprises.
• A restated total is survivable if the reconciliation survives with it; the undocumented restatement is what converts into a permanent asset-value discount.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits