Review the event, documented repair and present condition separately. Define seller representations with counsel, obtain independent technical findings, and confirm the actual lender and insurer conditions before accepting the aircraft.
What aircraft damage history means to a purchaser
Aircraft damage history should be evaluated through the event, the documented repair and the aircraft's present condition. A label such as damage repaired compresses three different questions into two words. It does not tell a buyer what happened, which areas were affected, what technical basis supported the work, or what an independent reviewer can verify today. Begin by asking the seller for a factual narrative and the supporting records. Then appoint a qualified maintenance professional to evaluate their technical significance.
This article provides a transaction framework rather than a legal disclosure opinion, appraisal or airworthiness determination. Requirements and remedies depend on the transaction and applicable law. Counsel should draft the representations that matter to the actual purchase. The maintenance professional should interpret repair documentation and current findings. The buyer can then ask the lender and insurer about that specific aircraft, using the same factual package instead of different versions of an informal story.
Keep reporting definitions separate from purchase representations
The definitions in 49 CFR 830.2: accident-reporting definitions serve the federal accident-reporting framework. 49 CFR 830.5: immediate notification establishes notification obligations for accidents and specified incidents. Those provisions do not supply a complete list of everything a private buyer might want to know or everything a purchase agreement may require a seller to disclose. An event's regulatory label alone should not end diligence. Ask counsel to distinguish reporting requirements from the negotiated promises in the sale documents.
For example, a buyer may want written answers about a prior ground contact, repair, hard landing or component replacement even when the seller does not describe the event as an accident. That is a suggested information request, not a statement that every event has the same legal classification or market effect. Define the relevant questions clearly. Avoid a conversation in which the buyer means any structural repair while the seller hears only an accident that met a reporting definition.
Layer one: establish the event narrative
Request dates, the aircraft identity at the time, the location, the operator's description and the documents the seller actually possesses. Ask which components or areas were reportedly affected and whether the seller learned about the event firsthand or from a prior owner. Record the source of each statement. An owner honestly repeating an old explanation may have less knowledge than the confidence of the advertisement suggests. Attribution helps the technical reviewer decide what corroboration to seek.
Search available government records as one part of that process. The NTSB's NTSB: aviation database coverage and report status explains that its database includes accidents and selected incidents, and that preliminary information can change as an investigation develops. A reasonable diligence inference is that a search with no result does not establish a complete no-event history. Use identifying information carefully and save the search scope and date. If a record is found, distinguish a preliminary account from factual material and final findings.
Do not accuse a seller of concealment solely because a search result and a listing use different terminology. Ask for clarification, compare dates and identities, and have the appropriate advisers assess a material inconsistency. Conversely, do not dismiss a documented event simply because the airplane has since flown. The purchase decision requires evidence about the repair and current condition, not a contest over whether the marketing description sounds reassuring.
Layer two: connect the repair to its technical basis
Obtain the relevant maintenance entries and supporting documents. 14 CFR 43.9: maintenance entry content addresses entries for work within its scope, while the FAA's FAA: field approval process describes one approval pathway for certain major repairs and alterations. The reviewer should determine what was required for the actual work. Avoid assuming that every small repair needs a field approval, or that the mere presence of a form establishes the adequacy of all work performed.
Ask the reviewer to connect the affected area, referenced data, work description and approval documentation. Where a design change is involved, FAA: supplemental type certificates provides background on supplemental type certificates. The objective is to understand the actual configuration and its associated instructions and limitations. A buyer does not need to become a structural engineer to ask where the supporting evidence is kept and whether the reviewer could examine the relevant area.
Keep invoices, photographs and correspondence alongside the formal entries, while identifying what each item proves. An invoice may describe a paid task without documenting every approval element. A photograph can show a particular view without demonstrating the condition behind a closed panel. A seller's summary can point to useful evidence without replacing it. The decision packet becomes stronger when it states those limits directly rather than presenting a large file count as proof of completeness.
Layer three: evaluate present condition and inspection limits
Agree on a written inspection scope that directs attention to the affected area and any related systems the professional considers relevant. Ask what access is authorized, which specialist may be needed, and what could remain hidden without further work. Current technical findings should be reported independently of the event narrative. A known repair can be well documented yet still generate a present-condition question; an appealing exterior can coexist with an unresolved history.
Maintenance work must follow the applicable technical basis; 14 CFR 43.13: technical performance rules addresses current manufacturer instructions or other acceptable methods within its scope. For a purchaser, the useful request is a written explanation of the basis used, the observations and the limitations. This guide does not prescribe inspection procedures, dimensional limits or a universal engine teardown rule. The installed product and the actual event require a qualified professional's analysis using the relevant instructions.
A concrete document-control example is Lycoming SB 533D: strike and sudden-stoppage guidance, dated February 10, 2026. Its revision notice describes changes to the event discussion and separate checklists for geared and other engines. That is a reason to ask which revision and engine configuration informed the review. It is not a rule for another manufacturer's product, and this article does not determine the bulletin's legal applicability to a particular operation. Have the reviewer address the event, applicable directives and manufacturer information together.
An original evidence matrix can use five columns: statement, supporting document, present observation, unresolved question and decision owner. A statement such as repaired after ground contact might have an event report and work entry but no authorized access to one affected area. The matrix does not declare the airplane unacceptable. It identifies the exact evidence gap that the buyer must resolve, accept through an informed decision, or use as a reason to withdraw under the agreement.
Why a standard damage discount is unreliable
There is no single defensible percentage reduction for every gear-up landing, propeller contact or repaired structure. Event severity, workmanship, documentation, aircraft configuration, present findings and market comparisons differ. A percentage repeated online is not an appraisal of the aircraft under consideration. Ask an appropriately qualified valuation professional how the actual evidence affects the comparison set. Keep valuation analysis distinct from the cost of inspecting or correcting an identified condition.
Use a cash bridge instead of a slogan. Start with the negotiated price, add quoted diligence and known work, then identify reserve assumptions and unpriced uncertainty separately. If a seller offers a reduction, compare it with the buyer's revised acquisition plan and financing terms. The reduction may be sufficient for one buyer and unsuitable for another. Do not assume an allowance reimburses every future expense or removes the need for a technical acceptance decision.
For illustration only, imagine a buyer negotiating a $9,000 credit and receiving a $6,000 written estimate for defined work. The arithmetic leaves $3,000 before additional costs, but that difference is not proven profit or protection against unknown findings. It excludes anything outside the estimate and says nothing about marketability. The useful follow-up is to examine the estimate's exclusions, authorization process and timing. Keep hypothetical figures labeled so they do not turn into supposed national repair prices.
Coordinate the lender, insurer and purchase agreement
Provide a consistent history package to the proposed financing and insurance providers when requested. Ask for the actual acceptance conditions and outstanding information. Do not infer acceptance from a general prequalification, a quote for another aircraft or an informal statement about repaired airplanes as a category. A transaction can require separate technical, collateral and insurance decisions. Put their deadlines alongside the purchase agreement's inspection and cancellation dates.
Counsel can help specify seller representations, document delivery, inspection access, findings responses and remedies. Agree in advance whether the buyer can request further specialist review, how time extensions work and what happens if the parties disagree. A technical report identifies facts and limitations; it does not automatically rewrite the contract. A seller's agreement to repair an item also needs an understandable deliverable and acceptance process, rather than an open-ended promise to make the buyer comfortable.
Preserve records through closing and future ownership
Continuing maintenance records and their transfer are addressed in 14 CFR 91.417: maintenance records and retention. Request the repair package as an organized part of the aircraft handover, together with the relevant logs and supporting material. The FAA's FAA: requesting aircraft record copies service may provide useful additional airworthiness documents, but it is not a replacement for every owner-held maintenance record. Reconcile the file reviewed during diligence with the documents actually delivered at closing.
Save the independent findings and the answers that resolved them. A future owner, maintenance shop, lender or insurer may ask the same questions. A clear chronology makes those conversations more efficient without promising that every party will reach the same conclusion. Also record unresolved limitations. Concealing an inspection limitation inside an internal email creates confusion later when a buyer remembers a broader review than the professional actually performed.
Questions worth asking before committing funds
Ask what happened, how the seller knows, which records support the account, and which areas the independent reviewer examined. Ask what remains inaccessible or uncertain and which professional owns the next decision. Obtain actual lender and insurer responses when those are transaction conditions. These questions turn damage history from a vague negotiating label into a set of reviewable facts, costs and contractual choices.
Read the logbook review guide, pre-buy cost guide and corrosion guide for the adjoining workstreams. When requesting financing assistance, describe the aircraft and current diligence stage accurately. Supply sensitive records only through the channel agreed with the relevant professional, and keep final technical and legal judgments with the advisers appointed to make them.