In brief
A pre-purchase inspection report should identify the aircraft, agreed scope, records reviewed, tests performed, findings, limitations, unresolved questions, and corrective evidence. It should not imply that a buyer-defined pre-buy is a regulatory inspection or guarantees the absence of defects.
Tools for this decision
Run the numbers while you read.
A useful pre-purchase inspection report connects each observation to evidence, follow-up, and the buyer’s negotiated closing rights. A squawk list alone does none of that.
A pre-buy is a buyer-defined diligence process. It is not automatically an annual inspection, conformity inspection, appraisal, or determination that no defect exists. Completing an annual during the transaction requires its own applicable scope, performance, and record entry; calling the work a pre-buy does not satisfy those requirements. The purchase agreement and written work scope should control what the facility examines, what it may open or test, and what happens when a finding appears.
What the download is (and is not)
The download is a five-sheet transaction workspace, not a completed or signed inspection report:
| Downloaded sheet | Purpose |
|---|---|
| Start Here | Workflow and use limitations |
| Scope | Physical inspection, operational test, records review, specialist, exclusions, and decision owner |
| Findings Register | Observation, evidence, open technical question, estimate, seller response, and buyer decision |
| Records Review | Requested evidence, receipt, reconciliation, gap, consequence, and next action |
| Closing Exceptions | Unresolved condition, required evidence, dependency, remedy, and acceptance |
It does not contain aircraft-model inspection instructions, approved maintenance data, return-to-service authority, automatic defect classification, title work, an appraisal, or purchase-agreement remedies. Use the workbook to control inputs to the report structure below; the appropriately qualified facility and specialists remain responsible for their signed technical work.
Report cover and document control
Copy this header into the working report:
``text Report ID and revision: Issue date: Inspection facility and location: Lead inspector and qualifications: Buyer / client: Seller: Aircraft make, model, and series: Registration: Manufacturer serial number: Engine / APU / propeller identities: Inspection arrival date: Inspection completion date: Aircraft hours and cycles at inspection: Purchase agreement / scope reference: Distribution and confidentiality: Revision history: ``
Use manufacturer serial number and installed-component serial numbers, not registration alone. If an engine changes during the transaction, the report should make the identity break unmistakable.
Executive decision page
The first page should let the decision team see the condition of the process without minimizing nuance:
| Status | Count | Decision owner | Required before closing? |
|---|---|---|---|
| Open safety or airworthiness review | |||
| Contractual rejection candidate | |||
| Correction required | |||
| Price, reserve, or escrow decision | |||
| Records exception | |||
| Accepted with monitoring | |||
| Closed with evidence |
Then state:
- Whether every agreed inspection item was completed.
- Material access, disassembly, weather, test-flight, or records limitations.
- Items requiring engineering, manufacturer, maintenance, appraisal, lender, insurer, or legal review.
- Conditions that arose after the inspection cutoff.
- The date and aircraft status through which the report is current.
Avoid a bare “passed” or “failed.” Those words can conceal unresolved exceptions and contractual choices.
Section 1: scope and limitations
``text Agreed physical scope: Agreed records scope: Panels or areas opened: Inspections or tests performed: Engine/APU/propeller specialist work: Avionics and cabin functional checks: Ground run: Test flight: Fluid, filter, or laboratory analysis: Items excluded by agreement: Items not completed and why: Known access or sampling limitations: Reliance on seller-provided statements: Events after inspection not covered: ``
Attach the signed scope. If the purchase agreement defines rejection items or correction standards, cite the section rather than paraphrasing it.
Section 2: aircraft and records received
Inventory what was actually available:
| Record group | Received | Date range | Format/location | Review status | Exception ID |
|---|---|---|---|---|---|
| Airframe logs | |||||
| Engine/APU/propeller logs | |||||
| Work orders and task cards | |||||
| AD and inspection status | |||||
| LLP and component history | |||||
| Repairs, alterations, STCs, Form 337 | |||||
| Weight and balance/equipment | |||||
| Programs and shop visits | |||||
| Damage and corrosion history |
“Logs reviewed” is not enough. Show the boundary of the review and link the aircraft pre-buy records review deliverable.
Section 3: physical inspection results
Organize the body by aircraft system, not inspection chronology:
- Airframe, pressure vessel, structure, and corrosion.
- Flight controls and empennage.
- Landing gear, wheels, brakes, and steering.
- Engines, APU, propellers, and associated systems.
- Fuel, hydraulic, pneumatic, environmental, and ice protection.
- Electrical, avionics, software, and databases.
- Cabin, interior, emergency, and safety equipment.
- Exterior finish, windows, doors, seals, and placards.
For each inspected area record:
``text Scope performed: Reference or inspection data: Condition observed: Measurements / limits: Photograph or test-result IDs: Records reconciliation: Finding IDs: Not inspected / limitation: ``
Do not label a condition within limits unless the applicable data and measurement support that conclusion.
Section 4: finding record
Every finding needs a stable ID and this complete record:
| Field | Instruction |
|---|---|
| Finding ID | Never renumber after issue |
| Aircraft area/article | Include part and serial identity where relevant |
| Objective condition | Describe what was observed, not the negotiated result |
| Discovery method | Visual, functional test, borescope, records review, laboratory |
| Evidence | Photos, measurements, pages, test data |
| Technical reference | Applicable manual, limit, engineering data, or rule |
| Initial classification | Technical review, correction, records, value, monitor |
| Recommended next action | Inspection, engineering, repair, research, estimate |
| Transaction treatment | Seller correction, credit, escrow, acceptance, rejection review |
| Owner and deadline | Named person and date |
| Closure evidence | Work order, entry, test, invoice, or approved disposition |
| Final status | Open, closed, accepted, superseded |
Keep the technical conclusion separate from the buyer and seller’s commercial disposition.
Example finding
``text ID: ENG-004 Area: Right engine, serial [identifier] Condition: Borescope image set shows a condition requiring evaluation under the referenced engine maintenance data. Evidence: Images ENG-004-A through ENG-004-F; borescope report [ID]. Technical action: Qualified engine specialist to evaluate against current data and state continued-service, follow-up, or corrective recommendation. Transaction action: Open pending technical disposition and cost/downtime impact. Owner / due: [name / date] Closure: Attach signed technical disposition and, if corrected, completed work record and post-maintenance test evidence. ``
This example does not diagnose the condition or authorize operation.
Section 5: corrective work and reinspection
For seller-completed work, define the evidence and reinspection process before correction begins:
- Agreed work scope and an appropriately authorized provider.
- Parts, data, and expected record deliverables.
- Completion deadline.
- Buyer access and reinspection rights.
- Functional or operational test.
- Maintenance entry and supporting work package.
- Treatment if work reveals additional findings.
- Treatment if the aircraft is flown after correction and before delivery.
“Corrected” should never be a checkbox without closure evidence.
Section 6: records, value, and financing consequences
Create a cross-functional register:
| Finding | Technical consequence | Records consequence | Value input changed? | Lender/insurer notice? | Closing condition |
|---|---|---|---|---|---|
An unsupported repair may be a records issue, configuration question, maintenance-planning problem, and value concern at the same time. The inspector should state technical facts; qualified specialists should own appraisal, financing, insurance, tax, and legal conclusions.
Section 7: final deliverables
Before issuing the final report, confirm it contains:
- Controlled PDF with revision history.
- Signed scope and limitation statement.
- Aircraft and component identity.
- Inspection and test results.
- Records inventory.
- Finding register with photographs and measurements.
- Specialist reports and laboratory results.
- Corrective-work packages and reinspection results.
- Open-item register.
- Buyer acceptance or commercial disposition record kept separately as appropriate.
Quality review before acceptance
- [ ] Aircraft and component serial identities match source records.
- [ ] Scope, exclusions, and unfinished work are explicit.
- [ ] Each conclusion points to evidence.
- [ ] Findings separate fact, technical follow-up, and transaction decision.
- [ ] No finding was closed without retrievable evidence.
- [ ] Current maintenance status was reconciled after corrective work.
- [ ] Material changes were routed to value, lender, and insurer reviewers as applicable.
- [ ] Report cutoff date and post-inspection aircraft use are disclosed.
- [ ] The report does not claim that a pre-buy replaces a regulatory inspection.
Sources and further reading
Common questions
Frequently asked questions
Is there a standard aircraft pre-purchase inspection report?
No universal regulatory pre-buy report applies to every transaction. The buyer and seller should define scope, access, standards, deliverables, deadlines, and remedies in the purchase agreement, with qualified maintenance and legal advisors.
Is a pre-purchase inspection the same as an annual inspection?
No. A pre-buy is a contractual diligence process. An annual inspection has regulatory scope and record requirements. A transaction can include an annual, but the agreement should state that explicitly.
What should every pre-buy finding include?
Record the affected aircraft area or document, objective condition, source evidence, applicable reference, technical follow-up, transaction significance, responsible person, due date, and final disposition.
Does a clean pre-purchase report guarantee the aircraft has no defects?
No. Access limits, sampling, concealed conditions, intermittent faults, incomplete records, and events after inspection create residual risk. The report should state limitations and open items clearly.
Keep researching
Related aircraft guides
Make the aircraft history decision-ready
Turn aircraft paperwork into evidence you can use.
Radar digitizes, connects, and verifies the maintenance history behind buying, financing, operating, and selling an aircraft.