Skip to content

737 MAX assets

Boeing 737 MAX records review

A Boeing 737 MAX records review is for lessors, airlines, and acquisition teams moving a single-aisle 737 MAX aircraft through a transition, return, or sale. The trigger is usually an aircraft carrying mandated modifications and, on many airframes, an extended-storage period that has to reconcile cleanly. We check mandated-modification embodiment against the applicable Airworthiness Directives, preservation and de-preservation records, and the return-to-service package against the resumed maintenance program and source documents. You receive a discrepancy register, a modification-embodiment and storage-return reconciliation view tied to source records, and the evidence each open item needs to close.

When this review is needed

  • A 737 MAX is changing hands and the mandated modification embodiment needs confirming against the applicable ADs.
  • An aircraft returned from extended storage and the preservation and return records need reconciling.
  • A buyer needs the AD status read against the modifications required for return to service.
  • A transition is planned and the records must support the next operator's program.

The problem

737 MAX records are shaped by mandated modifications and, on many airframes, an extended storage period. The modification embodiment has to be clearly established and tied to the Airworthiness Directives that required it, and the storage period adds preservation, inspection, and return-to-service records that have to fit cleanly into a short service history. Storage and return records that do not reconcile with the resumed program are a distinctive risk on these aircraft.

What gets reviewed

  • AD compliance status, including the directives tied to mandated modifications
  • Embodiment of mandated modifications and its reconciliation with the applicable ADs
  • Records of preservation and de-preservation across any storage period
  • Return-to-service records and their fit with the resumed maintenance program
  • Authorized release certificates for components changed during storage or return
  • Status lists reconciled against the source documents behind them

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

  • Embodiment of the mandated modifications is clearly established and tied to the applicable ADs
  • Preservation and de-preservation records are complete for any storage period
  • The return-to-service package reconciles with the resumed maintenance program
  • Each component release uses a release document appropriate to the installation and the registry
  • The interrupted service history reconciles into a continuous record across the storage period
  • Status lists reconcile against the underlying source documents

Evidence normally required

  • Current AD and SB status reports with modification embodiment
  • Configuration records for the mandated modifications
  • The preservation and de-preservation records from the storage period
  • Return-to-service work packages and findings
  • Component release certificates for the storage and return period

Common discrepancies

  • Embodiment of a mandated modification that the records do not clearly establish
  • Preservation or de-preservation records missing for part of the storage period
  • A return-to-service package that does not reconcile with the resumed program
  • AD status that does not tie to the modifications required for return
  • Status lists that disagree with the source documents they summarize

What is at stake

Accepting a 737 MAX with unclear modification embodiment or storage-return records that do not reconcile can leave the next operator unable to show its baseline at induction. Re-establishing the storage and modification trail after acceptance is slow and can delay the next placement.

How the work runs

01

Tie embodiment to the ADs

Establish the mandated modifications and reconcile their embodiment against the Airworthiness Directives that required them.

02

Reconcile the storage period

Confirm preservation, de-preservation, and return-to-service records bridge the storage period into a continuous history.

03

Register discrepancies

Record each finding with its source document, evidence trace, and effect on continuity or embodiment.

04

Map closure

Recommend a closure path and responsible party so the baseline can be relied on at induction.

What the buyer receives

  • A discrepancy register pairing each finding with its source document and evidence trace
  • A modification-embodiment and storage-return reconciliation view tied to source records
  • A closure recommendation for each item with the responsible party named
  • A continuous record view that bridges the storage period

Who uses the output

  • Asset managers and buyers pricing an aircraft with an interrupted history
  • Continuing-airworthiness teams confirming the modification and storage baseline
  • Operators inducting the aircraft against the resumed program

How the work fits into the transaction or program

The review runs ahead of acceptance so embodiment and storage-return findings can be resolved while the storage and return records are still reachable. It feeds a continuous baseline the receiving operator inducts against.

Start with a single asset

Start with a single tail and expand once the workflow is proven.

Aircraft-specific considerations

Mandated modifications on the 737 MAX are tied to specific Airworthiness Directives, so embodiment status is reconciled directly against the applicable ADs. Many airframes carry extended-storage records, so preservation, de-preservation, and return-to-service evidence is checked for fit with the resumed maintenance program.

Jurisdiction-specific considerations

Where a 737 MAX moves between authorities, the mandated-modification embodiment and the return-to-service evidence have to satisfy the receiving authority, and a component released on one authority's form is not automatically acceptable under another.

Regulatory limits

This review confirms records completeness, consistency, and continuity across the modification and storage history. It does not determine compliance on the authority's behalf, issue an approval, or determine airworthiness.

What this review does not cover

  • Physical inspection or functional test of the aircraft
  • Performance of preservation or return-to-service tasks
  • Any airworthiness or acceptance determination

Specific to this review

  • Mandated modifications on the 737 MAX are tied to specific Airworthiness Directives, so embodiment status is reconciled directly against the applicable ADs.
  • Many 737 MAX airframes carry extended-storage records, so preservation, de-preservation, and return-to-service evidence is checked for fit with the resumed maintenance program.
  • An interrupted service history has to reconcile into a continuous record across the storage period, since a gap there breaks the baseline the next operator inducts against.

Sources

Frequently asked questions

What makes the 737 MAX records distinctive?

Two things. Mandated modifications tie directly to specific Airworthiness Directives, so embodiment is reconciled against those ADs, and many airframes carry an extended-storage period whose preservation and return-to-service records have to reconcile into a continuous history with the resumed program.

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.

Walk through your situation with an engineer who has done this work.