CFM56 engine export-airworthiness documentation records review

When this review is needed

• An engine is being sold or leased into a jurisdiction with its own import conditions.
• A prior export was rejected for missing status evidence and the package must be rebuilt.
• The receiving authority is known to impose special requirements the current file does not meet.
• A tight closing window leaves no room for the export documentation to bounce.

The problem

Export documentation is often assembled at the last minute from whatever status reports are on hand, and it meets an importing authority that applies its own special conditions. A records team preparing a CFM56 for export finds that the file that satisfied the departing jurisdiction leaves gaps the receiving reviewer will not overlook, and each gap surfaces one at a time as the reviewer works through it. The package looks ready until it is measured against the requirements that actually govern acceptance.

What gets reviewed

• The export application checked against the departing-jurisdiction requirements
• Special conditions the receiving authority is known to impose mapped to evidence
• AD and Service Bulletin status summarized to the standard the import review expects
• LLP and life-status evidence assembled in the form the receiving authority accepts
• Supporting release and shop records located for the summary figures
• A residual list of items the current file cannot yet satisfy

What gets validated

• The export application matches the departing authority's content requirements
• Each special condition the receiving authority imposes maps to a document in the package
• AD status in the package is supported by accomplishment evidence, not the summary alone
• LLP life figures reconcile to release certificates rather than the tracking list
• Status figures across the package agree with each other and with the source records

Evidence normally required

• The draft export application and any prior export correspondence
• The importing authority's known special requirements or acceptance conditions
• Current AD, Service Bulletin, and LLP status reports for the engine
• Release certificates and shop-visit records behind the status figures
• The engine's continued-airworthiness status summary

Common discrepancies

• A special condition the receiving authority imposes with no matching document in the file
• AD status carried on a summary with the accomplishment evidence not attached
• LLP figures in the package that do not reconcile to the release certificates
• Status figures that disagree between the application and the supporting reports

What is at stake

An export package that fails the importing authority's review stalls the engine at the border and can push a closing past its window, with holding costs and a counterparty growing impatient. Rework under that pressure is error-prone, and a second rejection is harder to recover from than getting the file right before it is submitted.

How the work runs

What the buyer receives

• An export evidence package indexed to the receiving authority's requirements
• A note on each special requirement showing the document that satisfies it
• A closure plan for items the current file cannot yet support

Who uses the output

• Lessors and asset managers moving the engine into a new jurisdiction
• Records teams assembling the file the importing authority will inspect
• Transaction leads who need the export not to stall a closing

How the work fits into the transaction or program

The export review draws on the same status and release evidence the airworthiness-review and LLP checks produce, and it repackages it to the receiving authority's standard. A clean AD status and a reconciled LLP position feed directly into an export file that can pass import review without the underlying work being redone at the border.

Aircraft-specific considerations

A CFM56 headed for export carries module build records, disk sheets, shop-visit releases, and installation history from a very large installed base, and its life across operators means status has been kept under several conventions. Importing authorities reviewing such an engine often want the life and AD position reconciled to source rather than to a summary, so the wide service history is exactly what the export package has to tie back cleanly.

Jurisdiction-specific considerations

Export acceptance depends on the receiving authority as much as the departing one, and FAA and EASA reviewers ask for evidence in different forms even where the underlying status is the same. The review maps the file to the specific importing authority's known requirements rather than assuming a package acceptable in one jurisdiction transfers to another.

Regulatory limits

The review prepares and tests the export documentation against known requirements. It does not issue an export certificate of airworthiness, bind the importing authority to any outcome, or make an airworthiness determination, and acceptance remains the receiving authority's decision.

What this review does not cover

• Issuing any export or import airworthiness certificate
• Representing the party before the importing authority
• Guaranteeing acceptance by the receiving authority

Specific to this review

• A CFM56 export file that satisfied the departing jurisdiction can still fail import review because the receiving authority applies its own special conditions.
• Importing reviewers frequently reject AD and LLP status carried on a summary and ask for the accomplishment and release evidence behind it.
• Rejections tend to surface one requirement at a time, so mapping every known special condition up front is what avoids a second bounce.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits