Structural repairs
Structural repair records checked against the modification-baseline sources
A structural repair map is a set of promises: every mark on it says a repair exists, was approved, and can stay on the aircraft under known limits. This review tests those promises against the modification-baseline source package, pulling the drawing, approval basis, and any repeat-inspection requirement behind each mapped repair. Repairs sitting on or near STC-modified structure get particular attention, since their approval basis must account for the modification. Configuration managers commission it during a baseline build and receive a repair-by-repair exception list ready for the configuration support package.
When this review is needed
- The repair map was consolidated from several operators' charts and the underlying repair files were never merged with it.
- Repairs are mapped inside areas later modified under an STC, and nobody has confirmed the approval basis still holds.
- Repeat-inspection requirements attached to older repairs cannot be found in the current maintenance program.
- A heavy check found undocumented repairs, and the map's credibility for the baseline is now in question.
The problem
Repair documentation scatters at the moment of repair and never reassembles on its own. The map entry gets made in one system, the repair drawing stays in the MRO's engineering files, the approval sits with a design office, and the repeat-inspection task may or may not have entered the maintenance program. Twenty years on, the map shows a riveted doubler at a station and nothing else, and proving that doubler can lawfully remain means reuniting documents that were separated the week the repair was made.
What gets reviewed
- Every entry on the structural repair map, matched to its repair file
- Approval basis per repair: SRM chapter and figure, or the specific approved data beyond SRM scope
- Repair limits, categories, and any life or inspection constraints attached
- Repeat-inspection requirements traced into the maintenance program
- Repairs coincident with STC-modified or SB-modified structure, checked for a compatible approval basis
- Unmapped repairs referenced in dent records or heavy-check findings, logged for map correction
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 resolves to a drawing or data reference specific enough to reconstruct what was installed
- Repairs beyond SRM limits show an approval from an appropriate design authority for the applicable system
- Category or interim repairs show either the terminating action performed or the tracking that controls them
- Repeat-inspection tasks arising from repairs appear as active requirements in the maintenance program
- Repairs within modified structure cite an approval basis that acknowledges the modification, whether STC or SB
Evidence normally required
- The structural repair map or dent-and-buckle chart, all revisions available
- Individual repair files: drawings, dispositions, and approvals
- STC files and SB records defining modified structural areas
- The maintenance program task list covering repair-driven inspections
- Heavy-check findings and non-routine records referencing structure
Common discrepancies
- A doubler mapped decades ago with no drawing, no data reference, and no approval anywhere in the file
- Interim repairs still installed long past the terminating-action deadline their approval imposed
- A repeat inspection required by a repair approval that never entered any operator's program
- Repairs inside an STC antenna or door-modification footprint approved against the unmodified SRM
What is at stake
A mapped repair without approval basis is treated as an unapproved repair until shown otherwise, and the conservative outcomes are expensive: engineering re-evaluation, possible rework, or acceptance as a permanent discrepancy that follows the airframe through every future transaction. Missed repeat inspections are worse, because they create a compliance gap in addition to a records gap.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Consolidate the map
Merge all map revisions and adjacent dent records into one working inventory of claimed repairs.
Attach the files
Pair each inventory entry with its drawing, approval, and limit documentation from the source package.
Test the interactions
Check repairs against modified-structure footprints and trace repeat inspections into the program.
Hand over the exceptions
Deliver the exception list, the inspection cross-reference, and map-correction inputs.
What the buyer receives
- A repair-by-repair exception list stating what each unsupported entry is missing
- A cross-reference of repair-driven inspection tasks against the active maintenance program
- A map-correction input covering unmapped repairs found in adjacent records
Who uses the output
- Configuration managers weighing structural findings in the baseline
- Structures engineers prioritizing re-evaluation of unsupported repairs
- Lessor technical staff assessing repair exposure before remarketing
How the work fits into the transaction or program
Structural repair findings interlock with the non-routine strand, where many repairs originate, and with the modification-status strand, which defines the modified areas whose approval bases interact with repairs. This review usually runs after those two so it can inherit their verified outputs instead of re-deriving them.
Jurisdiction-specific considerations
Approval pathways differ enough to matter: FAA-era repairs beyond SRM limits typically rest on designee-approved data under 14 CFR part 43 practice, while EASA-era repairs trace to design-organization outputs under the continuing-airworthiness framework of Regulation 1321/2014. A repair approved in one system is not automatically expressed in terms the other system's reviewers expect, and cross-registry aircraft need those translations identified rather than assumed.
Regulatory limits
The review establishes what the records support. It does not perform structural analysis, does not approve or re-approve any repair, and makes no finding on the airworthiness of the structure; repairs lacking support are handed to the responsible engineering organization as open items.
What this review does not cover
- Non-destructive testing or physical inspection of repaired areas
- Engineering re-substantiation of repairs
- Negotiation with design organizations over archived approval retrieval
Specific to this review
- Repair maps consolidated across operators inherit every predecessor's mapping conventions, so the same physical repair can appear twice under different station references.
- The approval basis question changes the day an STC modifies surrounding structure; a repair that was fine against the SRM may sit unevaluated against the modified configuration from that day on.
- Interim and time-limited repairs are the highest-yield review targets because their approvals expire by design, unlike permanent repairs that merely lack paperwork.
- Design organizations often retain repair approvals longer than operators retain repair files, which makes them the recovery source of first resort.
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
A repair is within SRM limits. Does it still need its own approval documents?
It needs enough documentation to show it was accomplished per the SRM: the chapter and figure applied, the sign-off, and evidence of any inspection the scheme requires. The SRM supplies the approved data, so no separate approval is expected, but a bare map entry with no reference to which scheme was used still fails review because the limits and repeat inspections cannot be identified.
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.