Structural history
Structural repair records review for the owner-managed aircraft file
This review tests whether every repair on a managed aircraft's structural repair map is backed by evidence the file actually contains. Each mapped repair is traced to the logbook entry, the work order, and the drawing or approval basis that supports continued operation, and each logbook damage entry is traced back to the map. Owner representatives commission it ahead of a sale or a management-provider change, before a pre-buy team opens the folders. The output is a per-repair exception list naming what is missing and which provider or folder most likely holds it.
When this review is needed
- The aircraft is going to market and the pre-buy will include a walk of the repair map against the logbooks.
- A management-provider change is imminent and the incoming provider will accept the file as delivered.
- A repair was found on the airframe during routine work and nobody can locate its paperwork.
- The owner wants a defensible handover baseline before signing exclusivity with a buyer.
The problem
On a managed aircraft, structural repairs accumulate at whichever service center was convenient when the damage happened. The management company logs the event, the invoice lands in an accounting folder, and the repair drawing stays with the shop. Years later the repair map, if one is maintained at all, lists entries no document in the owner's possession can support, and the person who arranged the work has moved on.
What gets reviewed
- Every entry on the structural repair map traced to the logbook entry and work order that created it
- The approval basis for each repair: an SRM chapter within limits, FAA Form 337 with approved data, or a repair design approval
- Logbook damage write-ups checked for a matching map entry and a recorded disposition
- Repairs performed under earlier management arrangements reconciled against the packages those providers left behind
- Repeat-inspection obligations created by repair schemes, and whether the tracking statement carries them
- Map revision history compared against the newest structural entries in the logbooks
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
- The map entry, logbook entry, and work order agree on repair location, dimensions, and date
- Any repair exceeding SRM limits carries approved data rather than a signoff alone
- Repairs that impose recurring inspections appear in the maintenance tracking statement with the correct interval
- No damage write-up in the logbooks remains open without a repair or a documented disposition
- Form 337s on file cite the approved data actually used, and the cited data is present or obtainable
Evidence normally required
- The structural repair map or dent-and-buckle chart as currently held, in any state
- Airframe logbooks and work orders covering the ownership period
- FAA Form 337s, repair drawings, and approval packages in the owner's folders
- Invoices and work packages from previous management and maintenance providers
- The current maintenance tracking statement showing inspection obligations
Common discrepancies
- A mapped repair with a clean logbook entry but no drawing and no stated approval basis
- A logbook damage write-up that never reached the map and shows no disposition
- A repair signed off against SRM limits that its recorded dimensions exceed
- A repeat-inspection requirement from a repair scheme absent from the tracking system
What is at stake
An unsupported repair reads as an unapproved repair to a pre-buy inspector. That single reading can convert a paperwork question into a structural inspection demand, a price adjustment, or a walked deal, and the owner absorbs the delay because the burden of proof sits with the seller.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the source set
Collect the map, logbooks, work orders, 337s, and prior-provider packages, and record what could not be obtained.
Walk the map
Trace each mapped repair to its logbook entry, work order, and approval basis, grading the evidence for each.
Walk the logbooks
Sweep damage write-ups the other direction to catch repairs and dispositions the map never captured.
Issue the exception list
Deliver per-repair findings with the missing element named and a recovery path suggested for each.
What the buyer receives
- A per-repair exception list naming the missing element and the likeliest source for it
- The repair map annotated with the evidence status of each entry
- A short summary the owner representative can hand to counsel or the broker before pre-buy
Who uses the output
- Owner representatives setting expectations before a purchase agreement is signed
- Incoming management providers deciding what they are accepting responsibility for
- Pre-buy teams scoping which repairs justify physical inspection time
How the work fits into the transaction or program
The structural repair check is one lens of the wider owner-managed file source review, and usually the one with the longest recovery lead times. Findings feed the owner handover baseline, and chasing a repair drawing from a shop takes weeks, so this piece runs first when a sale timeline is already set.
Jurisdiction-specific considerations
On the FAA register, 14 CFR 43 governs how repairs are performed and recorded, with major repairs riding on Form 337 and the approved data behind field approvals or designated-engineer packages. Under EASA, repairs rely on approved repair design data, with different paperwork and different holders. A managed aircraft that has crossed registries usually carries both regimes in one file, and each repair must be read against the rules in force where and when it was done.
Regulatory limits
This review reports documentation status. It does not approve repairs, does not judge the airworthiness of the structure, and does not replace the physical inspection or the certifying mechanic's determination that a return to service requires.
What this review does not cover
- Physical inspection or non-destructive testing of any repair
- Development or procurement of new repair approval data
- Negotiation of purchase-agreement conditions arising from the findings
Specific to this review
- Many business aircraft trade without a maintained dent-and-buckle chart, so the map is often reconstructed during the sale itself, which is exactly when missing approvals surface with no time to chase them.
- A repair inside SRM limits is fine on substance yet still fails review if the SRM chapter is not cited, because the reviewer has no basis to distinguish it from an unapproved scheme.
- Provider changes are where repair paperwork orphans: the logbook entry travels with the aircraft while the drawing and invoice stay in the departing provider's archive.
- A repair scheme that imposes repeat inspections creates two exposures at once, the missing document and the untracked inspection, and buyers price the second more harshly.
- Walking the logbooks toward the map matters as much as walking the map toward the logbooks; unmapped damage entries prove the map is incomplete rather than proving the structure is clean.
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
The aircraft has been with one management company for a decade. Would the file still have gaps?
Often, yes. A long single tenure helps, but repairs done at outside service centers during trips still scatter paperwork, and anything from before the current arrangement depends on how well the previous handover was done. The review is what confirms the assumption rather than the assumption standing in for the review.
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.
Talk through the aircraft, records, evidence, deadline, and next useful step.