Export airworthiness
LEAP engine export-airworthiness records review
This review checks that a LEAP engine's export-airworthiness package will hold up to the importing authority before the engine crosses a border. It works through the export application, the special conditions the receiving authority attaches, and the status summaries and supporting records the package rests on, confirming each claim traces to evidence rather than a cover sheet. It is run for the party exporting, importing, or financing the move. You receive a supported exception list, a source map behind the package, and a closure plan for the items an importing authority would question.
When this review is needed
- A LEAP engine is being exported to a new register and the importing authority's special conditions have to be met on paper first.
- An export certificate is being prepared and the status summaries behind it have not been checked against source.
- A financed engine is moving between jurisdictions and the lender needs the export basis confirmed before funding.
- A prior export stalled at the border and the package has to be rebuilt to satisfy the receiving authority.
The problem
An export package presents status summaries the importing authority takes on faith only until it does not. The special conditions a receiving authority attaches often reach into AD position, LLP standing, and configuration in ways the exporting operator did not track for that destination. A summary line that looks complete can sit on records that were never assembled to the importing state's expectations, and that gap surfaces at submission when the schedule is already committed.
What gets reviewed
- The export application and its claimed status against the records that support each line
- Special conditions imposed by the importing authority mapped to the evidence that satisfies them
- AD and configuration status summaries reconciled to accomplishment and modification records
- LLP standing presented for export traced to release documents rather than the tracking summary
- Supporting records assembled to the importing state's expected structure
- Exceptions the receiving authority is likely to raise identified before submission
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 importing-authority special condition maps to a specific record that satisfies it
- Status summaries in the application agree with the accomplishment and configuration records behind them
- LLP figures presented for export trace to release certificates and cycle records, not a summary alone
- AD position stated for the receiving state reflects that state's applicability rather than the exporting one alone
- The package structure matches what the importing authority expects to receive
Evidence normally required
- The draft export application and the evidence package assembled for it
- The importing authority's special requirements or conditions for the transfer
- Current AD, configuration, and LLP status summaries for the engine
- Release certificates and shop-visit records supporting the status claims
- Any correspondence from a prior export attempt on this asset
Common discrepancies
- A special condition from the importing authority with no evidence assembled to answer it
- An AD summary built on the exporting state's applicability that the receiving state reads differently
- An LLP figure in the package that cannot be traced past the tracking summary
- Supporting records present but structured for the exporting operator rather than the importing authority
What is at stake
An export package that fails the importing authority's check stalls the engine at the point of transfer, holds up the financing tied to it, and forces a scramble to reconstruct evidence under a live deadline. Special conditions discovered late can require accomplishment records or configuration proof that take weeks to gather, and the cost of the delay lands on whoever agreed the delivery date.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the destination
Assemble the importing authority's special conditions and the structure it expects the package to take.
Reconcile the summaries
Confirm each status claim in the application traces to accomplishment, configuration, and release records.
Map conditions to evidence
Tie every special condition to the specific record that answers it and flag those with none.
Close before submission
List the exceptions the receiving authority would raise and plan their closure before the package goes out.
What the buyer receives
- A supported exception list of items an importing authority would question
- A source map linking each package claim to the evidence behind it
- A closure plan for the special conditions not yet satisfied on paper
Who uses the output
- Asset managers confirming an engine can clear its destination authority before transfer
- Records teams assembling the export package to the importing state's structure
- Financing and transaction stakeholders whose funding depends on a clean export
How the work fits into the transaction or program
The export review runs after the engine's status and traceability are settled and before the application goes to the importing authority. It converts a status summary into a package the receiving state can accept, and its exception list feeds the remediation that has to close before the export certificate can issue.
Aircraft-specific considerations
Because LEAP fleets are young, most export packages lean on digital maintenance records and shop-visit releases rather than decades of paper. That works in the exporter's favor for AD and configuration currency, but it puts weight on the LLP release evidence and current configuration statement, which the review confirms are export-grade rather than operational summaries repurposed for the border.
Jurisdiction-specific considerations
An export from an FAA environment to an EASA state, or the reverse, changes which authority's AD applicability and configuration basis governs the package. The review reconciles the status summaries to the receiving state's expectations and flags where a claim that reads as complete under the exporting authority needs restatement for the importing one.
Regulatory limits
The review assesses whether the export package is supported and internally consistent. It does not issue an export certificate of airworthiness, bind any importing authority to accept the records, or make an airworthiness determination on the engine.
What this review does not cover
- Issuing or applying for the export certificate itself
- Negotiating special conditions with the importing authority
- Any airworthiness determination on the engine or its parts
Specific to this review
- Importing-authority special conditions are the most common cause of a stalled export, because they reach into status the exporter never tracked for that specific destination.
- An AD summary that is correct for the exporting state can be incomplete for the importing one, since applicability and effectivity are read against the receiving authority's fleet.
- Export packages fail on structure as often as substance: the right records assembled in the wrong shape still force the importing authority to send them back.
Sources
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The engine is currently airworthy on our register. Why is a separate export review needed?
Currency on your own register does not mean the package satisfies the importing authority. That authority attaches its own special conditions and reads AD applicability against its own fleet, so the review checks the package against the destination's expectations, not just your operating status.
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.