Airframe damage history
Damage-history records review
A damage-history records review traces each reported damage event on an aircraft from the report through its assessment, disposition, and closure. It is used before a purchase, a lease return, or after a known event such as a ground strike or lightning hit. It checks that every event has an engineering disposition, that the chosen action was carried out and recorded, and that any deferred or limited disposition is tracked. You receive an event-by-event register, the open or unsupported items, and the evidence needed to close each one.
When this review is needed
- An aircraft has known events such as ground handling damage, a bird or lightning strike, or a hard landing.
- A buyer wants to confirm that each reported damage event was assessed and closed before committing.
- A return is approaching and the lessor needs the damage history reconciled to its dispositions.
- A maintenance-program change makes it necessary to confirm which damage-related inspections remain live.
The problem
Damage events are reported quickly but resolved slowly, and the trail from report to closure crosses crew logs, engineering orders, and repair packages. An event can have a report but no disposition, a disposition that allows continued operation under a limit that was never tracked, or a repair that closed a different event. A history that reads as clean in a summary can hide an open event whose limit has quietly expired.
What gets reviewed
- Each reported damage event with its date, location on the aircraft, and source report
- The engineering disposition for each event and the action it required
- Repairs or operational limits applied as a result of each disposition
- Deferred or interim dispositions and the tracking that keeps them live
- Events that closed against a repair and the link between the two records
- Recurrence of damage in the same area that may compound an earlier event
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
- Every reported damage event carries an engineering disposition appropriate to the damage
- The action the disposition required is recorded as carried out
- Any operational limit or repeat inspection from a disposition is tracked and current
- A repair that closed an event traces to the specific event it resolved
- Interim dispositions have not lapsed without conversion to a permanent action
Evidence normally required
- Damage reports, crew logs, and event notifications
- Engineering dispositions and the analysis supporting each
- Repair packages and approval data for repairs tied to events
- The maintenance program entries for any damage-related repeat inspections
- Prior survey findings that identified or assessed the damage
Common discrepancies
- A reported event with no engineering disposition in the records
- A disposition that imposed a limit that was never carried into tracking
- A repair recorded against an event it does not actually resolve
- An interim disposition that lapsed before a permanent action was applied
- Repeat damage in one area that was each time treated as a new, isolated event
What is at stake
An unresolved damage event can leave an aircraft operating against an expired inspection limit or an undocumented repair. In a transaction, a damage history that cannot be tied to dispositions forces the buyer to assume the worst, and the cost of reconstructing the trail after the deal is higher than confirming it before.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the event list
Collect every reported damage event from crew logs, event notifications, and survey findings, dated and located on the aircraft.
Trace to disposition
For each event, find the engineering disposition and the action it called for, flagging events that stop at a report.
Confirm action and limits
Check that the disposition's action was carried out and that any operational limit or repeat inspection reached tracking and is current.
Register open and recurring
List open events, lapsed interim dispositions, and repeat damage in one area, then set a closure path for each.
What the buyer receives
- An event-by-event register tracing report to disposition to closure
- A list of open or unsupported events with the missing element named
- A recommended closure path for each item, including limits that need tracking
Who uses the output
- Structures engineering confirming the cumulative effect of events
- Continuing-airworthiness teams confirming damage-related limits are live
- Acquisition and asset teams pricing damage history into the aircraft
How the work fits into the transaction or program
The review supports a pre-purchase, a redelivery, or post-event closure by turning scattered reports into a traced damage history. It feeds the discrepancy register and confirms which damage-driven inspections belong in the program.
Jurisdiction-specific considerations
An engineering disposition issued under one authority's approval basis is not automatically accepted by another. Where the aircraft will change registries, the review flags dispositions that the receiving authority will need to confirm.
Regulatory limits
The review confirms that the damage history is complete, consistent, and traceable to dispositions. It does not assess damage, issue a disposition, or make an airworthiness determination.
What this review does not cover
- Physical inspection or assessment of the damaged structure
- Issuance of an engineering disposition or repair approval
- Any airworthiness determination on the aircraft
Specific to this review
- Damage events are reported fast and closed slowly, so the open risk usually sits in the gap between a report and a confirmed disposition.
- An interim disposition often carries an inspection limit; the failure mode is the limit expiring before a permanent action replaces it.
- Repeat damage in one area can compound, yet records frequently treat each occurrence as an isolated event with its own disposition.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Do you assess whether a damage event was handled correctly?
The review confirms that each event has a disposition and that the action was recorded and tracked. It does not re-assess the damage or replace the engineering judgment behind the original disposition.
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.