Pre-purchase review
Pre-purchase technical-record review
A pre-purchase technical-record review is the focused document check a buyer runs on one specific aircraft after diligence has narrowed the field to that tail. It is used by acquisition teams, lessors, operators, and management companies preparing to sign. The trigger is a near-final deal where the records package has been delivered for confirmation. It tests the logbooks, AD and LLP status, release paperwork, and repair history against the underlying source records, and separates what is genuinely supported from what is merely asserted. You receive a confirmation memo, an exception list keyed to specific documents, and the closure path for each open item.
When this review is needed
- A single tail has been selected and the seller has handed over the full records package for confirmation.
- The bill of sale is days away and the buyer wants the documents tested before money moves.
- An earlier portfolio screen flagged questions that now have to be resolved on the chosen aircraft.
- A lender or board needs documented confirmation that the records support the transaction.
The problem
By the time a package is delivered for sign-off, momentum favors closing. The status reports read cleanly, but the logbook continuity, the release behind a replaced rotable, or the approval behind a structural repair often goes unexamined under deadline. Signing against an unconfirmed package means the buyer absorbs every soft spot the package contained.
What gets reviewed
- Continuity of the airframe, engine, and APU logbooks across the asset's life
- AD applicability and accomplishment evidence confirmed against source entries
- Life-limited part status traced to release and accumulation documents
- Release certificates for installed and recently replaced components
- Major repairs and alterations checked for their approval basis
- The configuration the records describe against the configuration claimed in the sale
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
- Logbook entries form a continuous record with no unexplained break in custody or time
- Every applicable AD is supported by an accomplishment record matching the stated method
- LLP status reconciles to release certificates and a consistent cycle history
- Installed rotables carry valid release paperwork for the jurisdiction of operation
- Repairs and alterations cite approved or acceptable data held in the records
- The recorded configuration matches what the sale documents represent
Evidence normally required
Common discrepancies
- A logbook gap spanning an operator or maintenance-program change
- An AD marked complete whose accomplishment entry cannot be located
- A replaced rotable installed without a release certificate on file
- A structural repair recorded without the approved data behind it
- LLP cycle history that steps inconsistently between two records
- A configuration claim in the sale that the records do not confirm
What is at stake
A clean-looking package that does not survive a source check leaves the buyer owning unsupported life, missing releases, or unapproved repairs after close. Each of those is harder and costlier to remedy once the seller has been paid and released.
How the work runs
Establish continuity
Walk the logbooks end to end and confirm an unbroken record before testing any status claim.
Confirm against source
Match AD, LLP, release, and repair claims to the documents that are supposed to justify them.
List exceptions
Record each item that the source check does not support, keyed to the exact document or entry.
Set closure terms
Assign a closure path and owner for each exception so it can be resolved before signature.
What the buyer receives
- A confirmation memo stating what the records support and what they do not
- An exception list tied to the specific documents and entries at issue
- A closure path and responsible party for each exception ahead of signing
Who uses the output
- Acquisition teams clearing the records condition before sign-off
- Continuing-airworthiness staff planning to take the aircraft onto their system
- Lenders and boards requiring written confirmation of the records position
How the work fits into the transaction or program
The review sits between diligence and signature. Diligence sets price across candidates; this confirms the chosen tail's package before the bill of sale and hands clean inputs to whatever induction or registry work follows.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
On older or much-modified airframes, logbook continuity and repair approval history carry more weight than on a young aircraft, where release completeness and LLP accuracy dominate. The depth of the review is set against the asset's age and modification standard.
Jurisdiction-specific considerations
If the aircraft will change registry on or after purchase, the records have to support the receiving authority's basis. A release valid where the aircraft sits today is not guaranteed to satisfy the authority the buyer intends to operate under.
Regulatory limits
The review confirms that the records are complete, consistent, and traceable to source. It does not appraise the aircraft, replace technical acceptance, make an airworthiness determination, or warrant that any authority will accept the asset.
What this review does not cover
- Physical inspection or operational test of the aircraft
- Drafting or negotiation of the purchase and sale agreement
- Any regulatory approval or airworthiness sign-off
Specific to this review
- At sign-off the package is usually read once for completeness; this review reads it a second way, against the source entries that are supposed to support it.
- Deal momentum near the bill of sale is itself a risk, because the pressure to close discourages testing the documents that close the deal.
- Logbook continuity is checked as its own line item, since a break in custody can undermine an otherwise clean status report.
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). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How does this differ from acquisition diligence?
Diligence works across candidate aircraft to set price and conditions. This review is the deep confirmation on the one tail you have chosen, testing its delivered package against source before the bill of sale.
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.
Walk through your situation with an engineer who has done this work.