Engine export files
Export airworthiness documentation review for engine-module records files
This review tests an engine or module export evidence package against the records that have to stand behind it: module build sheets, LLP status pages, disk sheets, shop findings, test-cell data, and installation history. It is run when an engine or module is being sold or shipped across registers, before the export paperwork is finalized. A records specialist traces each statement in the export file back to a source document and flags anything the importing authority could question. The engine records lead receives an exception list keyed to the source package so gaps are closed before the file ships.
When this review is needed
- An engine or module is being sold to a buyer under a different authority and the export file must satisfy that authority's special requirements.
- A shop visit has just closed and the exported unit's paperwork has to reflect the as-released build, including any module swaps.
- A lessor is repositioning a spare engine between jurisdictions and the receiving CAMO has asked what supports the export statements.
- An importing authority has queried a prior export package and the team wants the next one checked before submission.
The problem
Export paperwork for an engine is assembled at the end of the process, usually by whoever is closest to the shipping deadline, from a records file that grew over years of shop visits and installations. The statements in the export package assert compliance positions that live in build sheets, disk sheets, and test-cell reports scattered through that file. Nobody has time to read the whole file against the package, so the assertions ride on trust until an importing authority asks for the evidence behind one of them.
What gets reviewed
- Every compliance statement in the export evidence package traced to a named source document
- Special requirements of the importing authority checked against what the file actually contains
- Module build sheets read against the exported configuration, including swapped or replaced modules
- LLP status pages reconciled with disk sheets and back-to-birth evidence for exported life-limited parts
- Test-cell records and shop findings matched to the release condition the export file claims
- Installation and removal history checked for continuity up to the export date
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 export statement cites evidence that exists in the source file and says what the statement claims
- The exported serial numbers on the package match the build sheets and the latest installation record
- LLP cycles quoted in the export file agree with the status pages and the underlying disk sheets
- Importing-authority special requirements each map to a document, or appear on the exception list
- Shop findings that affected the exported configuration are dispositioned in the file, none left open
Evidence normally required
- The draft export evidence package and the importing authority's stated requirements
- Module build sheets and the engine or module records file as currently indexed
- LLP status pages with disk sheets and release documents behind them
- Test-cell run reports and the shop-visit findings summary
- Installation and removal history for the unit up to the planned export date
Common discrepancies
- An export statement that paraphrases a compliance position no document in the file actually states
- A special requirement of the importing authority with no corresponding evidence gathered at all
- LLP cycle figures in the export package taken from an older status page than the one in the file
- A module swapped at the last shop visit whose build sheet never made it into the export support set
What is at stake
A challenged export package stops the shipment while the team reconstructs support under scrutiny, with the buyer and the freight schedule waiting. If the missing evidence sits with a prior operator or a shop that has archived it, recovery takes weeks. A unit stuck in export limbo accrues storage and insurance cost, and repeated queries teach the importing authority to read the next submission harder.
How the work runs
Fix the export baseline
Confirm the exported configuration, serial numbers, and the importing authority whose requirements govern the package.
Trace every statement
Read each compliance statement in the export file back to build sheets, disk sheets, test-cell records, and installation history.
Log exceptions with sources
Record each unsupported or conflicting statement with the exact document that is missing or disagrees.
Report readiness
Hand the engine records lead a keyed exception list and a view on whether the package can be submitted.
What the buyer receives
- An exception list tying each unsupported export statement to the specific missing or conflicting source
- A cross-reference from the export package to the file locations that support each statement
- A short readiness note stating whether the package can go to the importing authority as drafted
Who uses the output
- Engine records leads who must close the exceptions before the unit ships
- Asset managers timing the sale or transfer around the export paperwork
- MRO records staff who supply the missing shop documents identified in the list
How the work fits into the transaction or program
The review sits between the close of the records file and the submission of the export package. Diligence on the transaction usually happens earlier and at aircraft level; this check is unit-specific and runs last, when the exported configuration is final and the package can be read against exactly what will ship.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Export requirements differ by importing authority, and the gap between FAA and EASA expectations is where most exceptions arise. A file organized to satisfy 14 CFR 91.417 retention habits may still lack items an EASA importer expects under Regulation 748/2012, such as specific release forms for modules overhauled outside the receiving system. The review reads the package against the named importing authority rather than a generic export standard.
Regulatory limits
The review verifies documentary support only. It does not issue or apply for an export certificate of airworthiness, does not determine that the engine or module is airworthy, and does not approve data or grant any release. Those acts remain with the certificating authority and the holders of the relevant approvals.
What this review does not cover
- Physical inspection of the engine or module being exported
- Preparation or submission of the export application itself
- Negotiation with the importing authority over its special requirements
Specific to this review
- Export packages fail most often on module-level evidence: the engine-level story holds, but one swapped module lacks the build sheet that supports its quoted status.
- Importing-authority special requirements are transaction-specific, so a package that cleared one export cleanly can still fail the next one on the same unit.
- Test-cell reports are frequently held in a shop system separate from the records file, and the export deadline is when that separation surfaces.
- An exception found before submission costs a document request; the same exception found by the importing authority costs the shipping slot.
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
Can the review start before the export package is final?
Yes, and it usually should. The source tracing on build sheets, LLP status, and test-cell records can run while the package is still in draft, so only the final statement-by-statement pass waits for the finished document. Starting early moves document recovery off the shipping deadline.
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.