Skip to content

737NG configuration state

Boeing 737NG modification and STC status records review

A 737NG modification status review reconciles the Service Bulletins and STCs shown as embodied against the approval data and configuration records that prove them. It is for teams that need the modification state of a Boeing 737NG to be accurate and defensible before a transaction or an operator change. The review checks each SB and STC for its approval basis, its effectivity for the serial number, and the record that shows it was actually embodied. You receive an exception list of unsupported or mis-stated modifications, a source map from each entry to its approval data, and a plan to close the configuration gaps.

When this review is needed

  • A 737NG modification status report has to be proven against approval data before a sale.
  • A cabin or avionics STC was installed and the buyer wants the approval and effectivity confirmed.
  • The aircraft is changing registries and the modification state must be acceptable to the new authority.
  • An SB shown as embodied lacks the record that proves it was actually accomplished.

The problem

A modification status report is a summary, and summaries drift from the approval data underneath them. An SB can show as embodied with no accomplishment record, an STC can be listed without the approval that authorized the specific installation on this serial, and configuration entries can lag a modification that was actually done or claim one that was not. Cabin and avionics changes accumulate across operators, and the paper trail for each runs to a different source that has to be pulled and matched by hand.

What gets reviewed

  • Each Service Bulletin shown as embodied matched to its accomplishment record
  • STCs listed for the aircraft matched to the approval covering this serial number
  • Effectivity of each modification confirmed for the specific serial and configuration
  • Configuration list entries reconciled against the modifications actually embodied
  • Approval data present for every claimed modification, including foreign validations
  • Superseded or partially embodied modifications identified and their status resolved

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

  • Every SB marked embodied carries an accomplishment record dated to the work
  • Each STC traces to an approval whose effectivity includes this serial number
  • The configuration list matches the set of modifications the records show as embodied
  • Foreign validations are present where a modification approved under one authority is used under another
  • Partially embodied or superseded modifications are stated as such rather than shown fully complete

Evidence normally required

  • The current modification and STC status report for the aircraft
  • SB accomplishment records and the referenced service bulletins
  • STC certificates, approved data, and installation records
  • The aircraft configuration list or configuration deviation record
  • Foreign validation approvals for modifications used across authorities

Common discrepancies

  • An SB shown embodied with no accomplishment record behind the entry
  • An STC listed without the approval effective for this serial number
  • A configuration list that omits a modification the work records show was done
  • A partial embodiment reported as complete, hiding the remaining work

What is at stake

A modification claimed without its approval data is a configuration the new owner cannot defend, and a receiving authority may refuse to accept it until the basis is produced. An STC that does not trace to an approval effective for the serial number can force removal or re-approval, both expensive late in a deal. Configuration entries that disagree with the physical state of the aircraft surface at the worst time, usually when a shop opens a panel and finds something the records did not predict.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Take the status apart

Break the modification report into individual SB and STC entries so each can be checked against its own evidence.

02

Match to approval data

Confirm each entry's approval, effectivity for the serial, and accomplishment or installation record.

03

Reconcile the configuration

Compare the configuration list against the modifications the records prove were embodied.

04

List and plan closure

Deliver the exception list and name who can supply each missing approval or validation.

What the buyer receives

  • An exception list of unsupported and mis-stated modifications with the missing evidence noted
  • A source map from each SB and STC to its approval and accomplishment record
  • A closure plan naming who can supply the missing approval or accomplishment data

Who uses the output

  • Records teams proving the modification state before a sale or registry change
  • Receiving authorities' technical reviewers checking the acceptability of the configuration
  • Asset managers pricing the cost of any modification that cannot be defended

How the work fits into the transaction or program

Modification status defines the configuration the rest of the records describe, so this review sits alongside the equipment-list and weight-and-balance reviews that depend on the same embodied state. A modification confirmed here becomes a fixed point the structural-repair and STC-driven records can reference rather than re-derive.

Aircraft-specific considerations

737NG airframes accumulate cabin reconfigurations and avionics upgrades across successive operators, and each leaves an STC or modification trail that a later operator's status report often summarizes without carrying the underlying approval. Aircraft moved between regions frequently need foreign validations for modifications approved under the outgoing authority, and those validations are a common gap. Structural SBs on high-cycle 737NG airframes tie directly to the repair map, so an embodiment claimed without evidence can leave a structural inspection basis unproven.

Jurisdiction-specific considerations

A modification approved under the FAA and used on a 737NG operated under EASA, or the reverse, needs a validation the receiving authority accepts, and the review checks that each cross-authority modification carries one. It records the approving authority for every modification so the receiving side can see the basis rather than assume mutual acceptance.

Regulatory limits

The review reports whether modifications are supported and correctly stated as records. It does not approve or validate a modification, issue an STC, make an airworthiness determination, or substitute for the receiving authority's acceptance of the configuration.

What this review does not cover

  • Obtaining a foreign validation for a modification that lacks one
  • Physical inspection to confirm a modification is installed as recorded
  • Weight and balance recalculation, which the weight-and-balance review covers

Specific to this review

  • On a 737NG moved between regions, missing foreign validations are among the most common modification gaps, because the summary report rarely tracks them.
  • A partial embodiment reported as complete is treated as a finding, since the remaining work is a hidden liability the buyer would otherwise miss.
  • Structural SBs are cross-checked against the repair map, because an unproven structural embodiment can leave a repeat-inspection basis without support.

Sources

Frequently asked questions

Why do foreign validations matter for a used 737NG?

A modification approved under one authority is not automatically accepted by another. When a 737NG moves between FAA and EASA operation, each cross-authority modification needs a validation the receiving authority accepts, and a missing validation can force removal or re-approval. The review flags these before they become a transaction problem.

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.