Export documentation
Export airworthiness documentation in the shop-visit source file
When a shop visit feeds an export, the closeout file has to satisfy two readers: the certificating authority and the importing one. This review examines the export evidence package assembled at the visit, checking each importing-state special requirement against a supporting document in the source file. It is performed before work-package acceptance, while the shop can still generate what is missing. The result is an exception list stating which export requirements the file meets, which it fails, and what document closes each gap.
When this review is needed
- The aircraft or engine leaves the visit for an operator under a different authority and export documentation is a delivery condition.
- An export certificate of airworthiness application is pending and its supporting file must be complete.
- The importing authority issued special requirements and nobody has confirmed the file answers each one.
- Exceptions on the export certificate need documented acceptance from the importer before shipment.
The problem
Export files fail on specifics. The importing authority's requirements arrive as a list of particulars: a noise statement, a defined modification status, an AD position at a stated date, a form the exporting system does not naturally produce. The shop builds its closeout file to its own regulator's logic, and the export items get bolted on late. Each unanswered particular stays invisible until the importing authority reads the application, at which point the asset is often already positioned and the shop records are far away.
What gets reviewed
- Importing-authority special requirements listed and matched item by item to file evidence
- The export certificate application data checked against the source records it summarizes
- AD status at the export effective date supported by accomplishment records in the file
- Release certificates verified for dual-release language where the import route needs it
- Exceptions to be carried on the export certificate documented with importer acknowledgment
- Configuration and modification status framed to the importing state's expectations
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
- Every special requirement has a named document in the package, or a recorded exception
- The AD position claimed for export reproduces from the compliance evidence, at the correct date
- 8130-3 or EASA Form 1 releases in the file carry the certifications the bilateral route requires
- Statements of conformity trace to inspection or test records rather than assertion
- Exception wording on the draft certificate matches what the importer agreed in writing
Evidence normally required
- The importing authority's requirements and any bilateral agreement guidance in play
- The draft export certificate application and its supporting package
- AD and modification status reports with accomplishment evidence
- Release certificates and test records generated during the visit
- Correspondence recording importer positions on proposed exceptions
Common discrepancies
- A special requirement answered by a document that exists but never entered the export package
- AD status cut at the closeout date when the importer required status at the export date
- Single-release certificates where the transfer route called for dual release
- Exceptions listed on the draft certificate that the importer never acknowledged in writing
What is at stake
An export rejected for documentation stalls delivery with the asset in the wrong country and payments sequenced against acceptance. Curing it remotely means extracting individual records from a closed shop file, re-certifying documents, and sometimes repeating inspections that were adequately done but inadequately evidenced. Exceptions accepted informally by the importer, with nothing in writing, tend to reappear at the next transfer as unresolved history.
How the work runs
Fix the requirement set
Compile the importing state's particulars, the bilateral route, and the effective dates that govern them.
Map evidence to requirements
Assign each requirement a document from the source file and mark the unmatched remainder.
Cure inside the shop
Route each gap to the party that can generate or re-certify the document before the aircraft moves.
Assemble the submission set
Index the verified package so the application and its evidence travel together.
What the buyer receives
- A requirement-by-requirement compliance matrix for the export package
- An exception list with the generating action and responsible party for each gap
- A verified document-set index the applicant can submit alongside the certificate application
Who uses the output
- Quality and certification staff preparing the export certificate application
- Asset managers sequencing delivery and payment against export milestones
- The receiving operator's technical team preparing the import side of the transfer
How the work fits into the transaction or program
Export document work is the last records task of a shop visit and the first task of the delivery. Running the review inside closeout, rather than after, lets the same shop that produced the records cure the gaps, and it converts the export application from a hopeful submission into one checked against its own evidence.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA exports run through 14 CFR 21.321 and the 8130-series practice, while EASA-side transfers rest on EU 748/2012 and the Part-145 release chain, with ICAO Annex 8 shaping what any importing state may ask beyond its bilateral. The review reads the specific route in play, since the same aircraft exported to two different states would need two different packages.
Regulatory limits
The review checks the documentary package against stated requirements. It does not issue or apply for export certificates, negotiate with authorities, or determine that the aircraft or article is airworthy or eligible for export; issuing authorities and their designees hold those functions.
What this review does not cover
- Filing the export application or liaison with the issuing authority
- Physical conformity inspection of the aircraft or article
- Customs, tax, or trade-control aspects of the export
Specific to this review
- Special requirements have effective dates; an AD status list cut at the wrong date is a common, entirely avoidable rejection.
- Dual-release language on 8130-3 and EASA Form 1 forms is fixed at signature time and cannot be retrofitted; missing it means re-certification by the original shop.
- Importer-accepted exceptions are only as durable as the written record; verbal acceptances evaporate when personnel change mid-transfer.
- The export package often needs records the closeout file holds but does not surface, so most gaps are extraction problems rather than missing work.
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 exceptions simply be listed on the export certificate?
Only exceptions the importing authority has accepted, and the acceptance should be in writing before the certificate is drafted. An exception the importer first sees on the issued certificate is a delivery risk, since acceptance at that stage becomes a negotiation with the aircraft already in motion.
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.