Structural repairs
Structural repair records review before a lessor sale or redelivery
This review establishes whether an aircraft's structural repair records will hold at technical acceptance. Working from the structural repair map, records specialists verify that each mapped repair carries its damage report, the approved data it was accomplished under, and any repeat inspection requirement it created. Lessors commission it ahead of a sale, redelivery, or financing review, before the counterparty's team opens the file. It closes with a repair-by-repair exception schedule and the substantiation actions that must finish before commercial terms are signed.
When this review is needed
- A sale or redelivery is scheduled and the structural file has grown across several lessees without a consolidated check.
- The repair map was redrawn or redigitized and its links to repair dossiers have not been proven since.
- A pre-purchase inspection is expected to survey the airframe and the records must be ready to answer what the survey finds.
- Financing terms require representations about repair status that the current file has not been tested against.
The problem
Structural repair files accumulate under operational pressure. A blend here, a doubler there, each accomplished correctly at the time, but documented to the standard of whoever held the aircraft that year. The lessor inherits the union of every lessee's documentation habits, and the repair map, if one exists at all, reflects the last operator's system rather than the full history. When an acceptance team compares fuselage reality to the file, the mismatches all land on the lessor.
What gets reviewed
- The structural repair map or dent and buckle chart against the repair dossiers behind it
- Damage reports establishing what was found, where, and when
- Approved data for each repair: SRM references, FAA Form 8110-3 approvals, DOA-approved data, or equivalent
- Repeat inspection and threshold requirements generated by repairs and their transfer into the maintenance program
- Repairs referenced in logbooks or work orders that never reached the map
- Interior and hidden-zone repairs recorded outside the structural file
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
- Each mapped repair links to a dossier containing the damage report, accomplishment record, and its approval basis
- Approved data cited by each dossier actually covers the repair as installed, including size and location limits
- Repairs classified as permanent meet the criteria of the data they cite; time-limited repairs show a tracked limit
- Repeat inspections required by repair approvals appear in the operator's maintenance program
- Logbook and heavy-check references to structural work reconcile to the map with no unmapped repairs remaining
Evidence normally required
- The current structural repair map and any predecessor charts
- Repair dossiers, including damage reports, work orders, and approval documents
- Heavy-check packages where structural findings and rectifications are recorded
- The operator's maintenance program sections carrying repair-driven inspections
- Prior redelivery or diligence reports touching the structural file
Common discrepancies
- Mapped repairs with an accomplishment record but no retrievable approval basis
- Time-limited repairs carried for years without the limit appearing in any tracking system
- Structural work described in heavy-check non-routines that never generated a map entry
- Approval documents citing SRM revisions that did not cover the repair's actual dimensions
What is at stake
Every repair the survey finds that the records cannot substantiate becomes a delay and a cost at the transaction. Unsubstantiated repairs can require new engineering evaluation, fresh approved data, or in the worst case rework, all on the lessor's account and the transaction's critical path. Repeat inspection requirements missed in the file carry forward as airworthiness exposure for the next operator.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Consolidate the history
Merge the current map, predecessor charts, and logbook references into one repair population.
Verify each dossier
Check every repair for damage report, accomplishment evidence, and covering approved data.
Check the carried obligations
Confirm repair-driven inspections and limits live in the maintenance program.
Deliver the schedule
Issue exceptions ranked by acceptance risk with a closure plan fitted to the transaction date.
What the buyer receives
- A repair-by-repair exception schedule ranked by acceptance risk
- A substantiation index tying each clean repair to its full dossier
- A pre-transaction action plan naming who supplies each missing document
Who uses the output
- Asset managers setting redelivery positions and sale representations
- Records leads assembling the structural chapter of the delivery bible
- Transaction managers timing commercial sign-off against file readiness
How the work fits into the transaction or program
The structural review runs alongside AD and LLP verification in transaction preparation, but it is the chapter most likely to interact with a physical survey. Closing the records side first means survey findings can be answered from a proven file instead of triggering parallel document hunts during acceptance.
Jurisdiction-specific considerations
Approval bases read differently across registries. A repair substantiated by an FAA Form 8110-3 or a repair station's data may need re-evaluation for an EASA-bound aircraft, and DOA-approved repairs travel the other way with similar friction. Under both 14 CFR 91.417 and Regulation 1321/2014 the repair record must persist with the aircraft, so gaps do not expire with time.
Regulatory limits
The review reports what the records substantiate. It does not inspect structure, classify damage, generate or approve repair data, or decide continued airworthiness. Engineering dispositions for unsubstantiated repairs belong to the design approval holders and authorities involved.
What this review does not cover
- Physical survey of the airframe or non-destructive testing
- Engineering evaluation or creation of new repair approvals
- Negotiation of redelivery condition disputes with the lessee
Specific to this review
- The structural file is the transaction chapter where records gaps most often convert into physical work, because an unsubstantiated repair can demand re-evaluation of the metal itself.
- Repair maps rarely survive operator changes intact; each lessee tends to restart the chart from its own survey rather than reconcile the inherited one.
- Time-limited repairs are the highest-severity finding class: a lapsed limit is an airworthiness issue, no longer merely a records one.
- Hidden-zone repairs found only in heavy-check paperwork are the usual source of the surprise mismatch between survey and map.
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 last redelivery accepted this file. Does it still need review?
Acceptance standards are set by each counterparty, and the file has usually grown since. A repair waved through under one lease's terms can stop a sale governed by stricter representations, so the file is tested against the standard of the coming transaction, never the last one.
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.