Skip to content

737NG repair map

Boeing 737NG structural repair records review

A 737NG structural repair review builds a map of every recorded repair on the airframe and ties each one to its approved data and any recurring inspection it carries. It is for teams that need the structural repair history of a Boeing 737NG to be complete and its continuing obligations understood before a transaction. The review locates each repair, confirms the SRM reference or repair approval behind it, and tracks any repeat inspection the repair introduced. You receive a structural repair map, an exception list of repairs lacking approval or inspection trace, and a plan to close the gaps.

When this review is needed

  • A 737NG structural repair map has to be assembled and proven before a sale or re-lease.
  • A repair was done to an SRM figure and the buyer wants the reference and its limits confirmed.
  • A repair introduced a recurring inspection that has to be shown as tracked and current.
  • Damage was found and repaired under an operator scheme whose approval needs tracing.

The problem

Structural repairs are the records most likely to carry an ongoing obligation, and on a high-cycle 737NG they accumulate across the fuselage, wings, and empennage over years of service. A repair can be recorded with a bare SRM callout and no confirmation the damage stayed within the manual's limits, an operator-designed repair can lack the approval that authorized departing from the SRM, and a repair that introduced a repeat inspection can lose that inspection when the aircraft changes programs. Assembling a complete map from scattered repair records is slow, and a missing repair is invisible until a shop finds the doubler.

What gets reviewed

  • Every recorded structural repair located and placed on a repair map by area
  • SRM references confirmed and each repair checked against the manual's damage limits
  • Repairs beyond the SRM matched to the approval that authorized the departure
  • Recurring inspections introduced by repairs tracked to their current status
  • Damage reports tied to the repairs that dispositioned them
  • Overlapping and adjacent repairs identified where interaction matters

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 on the map ties to a recorded damage report and a disposition
  • SRM-based repairs fall within the manual's stated limits or carry an approval where they do not
  • Repairs departing from the SRM carry approved data authorizing the departure
  • Every recurring inspection a repair introduced is present and current in the status records
  • Adjacent or overlapping repairs are flagged where their interaction affects the inspection basis

Evidence normally required

  • The structural repair records and any existing repair map
  • Damage reports and the dispositions that resolved them
  • SRM references and repair approvals for each repair
  • Recurring inspection status records for repair-driven inspections
  • Non-routine records where structural findings originated the repairs

Common discrepancies

  • A repair recorded with an SRM callout but no confirmation it stayed within limits
  • An operator-designed repair beyond the SRM with no approval authorizing it
  • A recurring inspection introduced by a repair that dropped off at a program change
  • A repair on the aircraft with no damage report or disposition behind it

What is at stake

A repair without approved data is a structural change the new owner cannot defend, and one that exceeded SRM limits without an approval may need re-engineering or removal. A recurring inspection that dropped off at a program change is a live airworthiness obligation nobody is tracking, and it surfaces when the next heavy check reopens the area. An incomplete repair map means the buyer prices in unknown structural liability, and the receiving operator inherits repairs it cannot account for.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Locate and map

Place every recorded structural repair on a map by airframe area so nothing sits outside the picture.

02

Confirm the basis

Match each repair to its SRM reference or approval and check it against the applicable damage limits.

03

Trace the inspections

Follow each recurring inspection a repair introduced to its current status in the records.

04

Report the liabilities

Deliver the repair map and exception list, and name who can supply each missing approval or inspection.

What the buyer receives

  • A structural repair map placing every recorded repair by airframe area
  • An exception list of repairs lacking approval, limits confirmation, or inspection trace
  • A closure plan naming who can supply the missing approval or reinstate the inspection

Who uses the output

  • Structures engineers assessing the repair liability on a specific serial number
  • Records teams assembling the repair map before it anchors a transaction
  • CAMO leads confirming repair-driven recurring inspections are tracked and current

How the work fits into the transaction or program

Structural repairs often originate as non-routine findings, so this review draws on the same records the non-routine review closed, and it feeds the recurring inspections that the maintenance program has to carry. The repair map it produces becomes the reference the next check works from rather than rediscovering each repair on opening the airframe.

Aircraft-specific considerations

High-cycle 737NG airframes accumulate repairs in the fatigue-sensitive areas that this type is known for, and those repairs frequently introduce recurring inspections tied to the structural program. Repairs done under one operator's engineering can depart from the SRM and rest on an approval that has to travel with the aircraft, which is where a program change most often drops the continuing inspection. Overlapping repairs in high-traffic areas can interact in ways a single repair record does not show, so adjacency is mapped rather than assumed independent.

Jurisdiction-specific considerations

A repair approved under the FAA and carried on a 737NG operated under EASA, or the reverse, needs its approval basis to be acceptable to the receiving authority, and the review records the approving authority for each departure from the SRM. It does not re-approve any repair; it establishes which authority's data supports each one so the receiving side can judge acceptability.

Regulatory limits

The review reports whether structural repairs are supported and their inspections tracked as records. It does not approve a repair, engineer a repair scheme, make an airworthiness determination, or substitute for the receiving operator's structural acceptance of the aircraft.

What this review does not cover

  • Engineering or approving a repair that lacks a scheme
  • Physical inspection of the repaired structure
  • Non-routine finding closure, which the non-routine review covers

Specific to this review

  • On a 737NG, a recurring inspection introduced by a repair is the item most likely to drop off at a program change, so each repair-driven inspection is traced to its current status.
  • An SRM callout alone does not close a repair record, because the damage still has to be shown within the manual's limits or carry an approval where it is not.
  • Overlapping repairs in fatigue-sensitive areas are mapped for adjacency, since interacting repairs can change the inspection basis in a way individual records hide.

Sources

Frequently asked questions

Why track recurring inspections as part of a repair review?

Many structural repairs introduce a repeat inspection that becomes a continuing obligation. When an aircraft changes operators or programs, those inspections can drop off silently. The review ties each repair-driven inspection to its current status so a live obligation is not carried into service unnoticed.

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.