Boeing 737 MAX export airworthiness records review

When this review is needed

• A tail is moving between registers and the export evidence has to satisfy the importing authority before filing.
• The importing authority has published special conditions the package does not yet address.
• A status summary in the package does not reconcile to the underlying records it claims to represent.
• A modification or repair valid on the exporting register needs validation before the import will accept it.

The problem

An export application stands or falls on whether the evidence answers the importing authority's basis, and that basis is rarely identical to the exporting register's. The importing authority can impose special conditions on AD status, modification acceptance, or life-limited part evidence that the exporting file was never built to satisfy. A status summary can read clean while the records underneath it carry a gap the import will find, and a modification approved on the departing register can need validation the package does not include. Assembling all of this against a filing deadline is where exports stall.

What gets reviewed

• The export application checked against the importing authority's stated basis
• Importing-authority special conditions matched to evidence in the package
• Status summaries reconciled to the underlying AD, modification, and life-limited part records
• Modifications and repairs assessed for validation the importing register requires
• Supporting records confirmed present for each claim the summary makes
• Gaps against the export basis identified before the application is filed

What gets validated

• Each importing-authority special condition is answered by evidence in the package
• Status summaries reconcile to the underlying records rather than standing alone
• AD status in the package reflects the accomplishment evidence on file
• Modifications needing validation on the importing register are identified before filing
• The package answers the importing authority's basis, not only the exporting register's

Evidence normally required

• The draft export application and any prior export correspondence
• The importing authority's special conditions or acceptance requirements
• Current AD, modification, and life-limited part status summaries
• The supporting records behind each status claim
• Modification and repair approval data that may need validation

Common discrepancies

• A special condition the importing authority published that the package does not address
• A status summary that does not reconcile to the underlying records
• A modification approved on the exporting register that needs validation before import
• An AD position stated in the summary without the accomplishment evidence behind it

What is at stake

An export application filed against an incomplete package is rejected or held, and the aircraft cannot enter the importing register until the gap is closed, which delays the transaction and the revenue behind it. A special condition discovered after filing forces a scramble to produce evidence, and a modification that needs validation can hold the whole application while the receiving authority reviews it.

How the work runs

What the buyer receives

• A supported exception list of gaps against the importing authority's basis
• A source map tying each package claim to its supporting record
• A plan to close each gap before the export application is filed

Who uses the output

• Records teams assembling the export package to the importing authority's basis
• Asset managers sequencing an export against the transaction timeline
• Transaction teams confirming the package will not stall on a special condition

How the work fits into the transaction or program

The export review sits at the register boundary, reading the assembled evidence against the importing authority's basis before the application is filed. It inherits the AD, modification, and life-limited part status the earlier reviews established, and its exception list drives the work that has to close before the aircraft can move onto the new register.

Aircraft-specific considerations

The 737 MAX carries configuration, software, and modification content that an importing authority may scrutinize closely, so the export package for this family is checked against the receiving authority's acceptance of the specific configuration rather than assuming a clean type acceptance. Because the fleet is young, the export history for a given tail is usually its first, which means the package is built from scratch against the importing basis rather than carried from a prior export.

Jurisdiction-specific considerations

An export from an FAA register to an EASA one, or the reverse, turns on bilateral acceptance and any special conditions the importing authority publishes, so the review works from the importing authority's stated basis and flags where a modification or repair valid on the departing register needs separate validation before the import will accept it.

Regulatory limits

The review assembles and checks the export evidence against the importing authority's basis. It does not issue an export certificate of airworthiness, grant import acceptance, or make an airworthiness determination on the aircraft.

What this review does not cover

• Issuing an export or import certificate of airworthiness
• Physical inspection or survey of the aircraft
• Negotiating special conditions with the importing authority

Specific to this review

• The importing authority's basis, not the exporting register's, sets what the package must prove, which is why special conditions are checked before filing rather than after.
• A modification valid on the departing register can need separate validation on the receiving one, and that validation can hold the whole application.
• A clean status summary can sit over an underlying gap the import will find, so summaries are reconciled to source rather than trusted at face value.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits