Structural repairs
Boeing 737 MAX structural repair records review
A Boeing 737 MAX structural-repair review confirms each repair on the airframe rests on approved or acceptable data and is located and tracked on the repair map. It is run by or for a party evaluating, transferring, or maintaining a specific tail. Damage reports, repair maps, structural repair manual references, and the approval data behind each repair are reconciled so a repair is neither undocumented nor recorded without the basis that authorized it. You receive a supported exception list of repairs that lack a traceable basis, a source map to the approval data, and a plan to close each open item.
When this review is needed
- A buyer wants the repair history confirmed to approved data before pricing structural exposure.
- A repair appears on the airframe or in a shop report but is not located on the repair map.
- A repair references an SRM chapter or an engineering approval the file does not contain.
- A repair may impose a recurring inspection that has to be carried on the maintenance program.
The problem
Structural repairs accumulate over an airframe's life, and each one has to trace to the data that authorized it, whether an SRM reference, a manufacturer approval, or an engineering repair design. A repair can be recorded in a shop report without reaching the repair map, an SRM reference can be cited without the applicable revision on file, and a repair beyond SRM limits can be embodied without the approval data that should back it. On the MAX the airframe is young, so a repair history is usually short, which makes an undocumented or unmapped repair conspicuous and worth resolving.
What gets reviewed
- Each repair on the airframe located and identified on the structural repair map
- Damage reports reconciled to the repairs that closed them
- SRM references confirmed present at the applicable revision
- Repairs beyond SRM limits matched to manufacturer or engineering approval data
- Recurring inspections arising from a repair confirmed carried onto the program
- Repairs recorded in shop reports checked for presence on the map
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 repair traces to an SRM reference or an approval appropriate to its scope
- Repairs beyond SRM limits carry engineering or manufacturer approval data
- The repair map accounts for every repair the shop reports and logbooks record
- Any recurring inspection a repair imposes is reflected on the maintenance program
- Each damage report reconciles to the repair recorded as closing it
Evidence normally required
- The structural repair map for the airframe
- Structural shop-visit packages and the damage reports behind them
- SRM references and revisions cited by the repairs
- Approval data for repairs beyond SRM limits
- The maintenance program for recurring inspections tied to repairs
Common discrepancies
- A repair in a shop report that is not located on the repair map
- An SRM reference cited without the applicable revision on file
- A repair beyond SRM limits with no engineering approval data behind it
- A recurring inspection imposed by a repair but never added to the program
What is at stake
A repair without a traceable basis undermines the structural integrity story a buyer and a receiving operator rely on, and it can force re-substantiation or, in the worst case, rework. A repair that imposes a recurring inspection but was never carried onto the program leaves an interval unmanaged, which surfaces as an open finding at the next check under the new operator.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the repair history
Pull the repair map, damage reports, and structural shop-visit packages for the airframe.
Trace each repair to its basis
Confirm every repair references an SRM chapter or carries approval data appropriate to its scope.
Reconcile to map and program
Check that each repair is on the map and that any recurring inspection reached the program.
Flag the exceptions
List repairs lacking a basis, a map entry, or a carried inspection, with the evidence each needs.
What the buyer receives
- A supported exception list of repairs lacking a traceable basis or a map entry
- A source map tying each repair to its approval data and SRM reference
- A plan to close each open item, including recurring inspections to be carried
Who uses the output
- Records teams confirming the repair history rests on approved data before a milestone
- Engineering deciding how to treat a repair with no traceable basis
- Asset and acquisition teams pricing structural exposure the records actually support
How the work fits into the transaction or program
The structural-repair review reads the airframe's damage and repair history against the data that authorized it, and it feeds the maintenance program where a repair imposes a recurring inspection. It runs before a transfer or after a heavy structural check, and its exception list drives either the recovery of approval data or an engineering decision on a repair that cannot be substantiated.
Aircraft-specific considerations
The 737 MAX airframe is recent, so a full repair history should be short and traceable, and a repair that cannot be located or substantiated stands out against that clean baseline rather than blending into decades of accumulated work. Because the family relies on configuration control, a repair that altered structure is checked against the configuration record so its effect is not lost when later work touches the same zone.
Jurisdiction-specific considerations
A repair approved under FAA data may need EASA acceptance before a receiving European operator can rely on it, so the review flags repairs whose approval basis is register-specific rather than assuming the repair data transfers with the airframe.
Regulatory limits
The review confirms each repair traces to approved or acceptable data and is properly recorded. It does not approve a repair, design repair data, or make an airworthiness determination on the structural condition of the airframe.
What this review does not cover
- Physical inspection or assessment of the repairs or structure
- Designing or approving repair data
- Any airworthiness determination on the structural condition
Specific to this review
- A repair beyond SRM limits needs approval data the SRM alone does not provide, so those repairs are the first ones checked for a substantiation gap.
- A repair can impose a recurring inspection that lives on the program, not the repair record, so the review confirms the interval was actually carried forward.
- Because the MAX airframe is young, an unmapped or undocumented repair is anomalous, which makes it worth resolving rather than accepting as historical.
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
How is a repair beyond SRM limits handled in the review?
The SRM covers repairs within defined limits. A repair beyond those limits needs separate approval data, whether a manufacturer disposition or an engineering repair design. The review confirms that data is on file at the applicable revision and flags the repair as an exception where it is missing.
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.