Export documentation
Export airworthiness documentation and the modification-baseline source file
When a modified aircraft changes registry, the export evidence package has to satisfy an authority that never saw the modifications happen. This review reads that package against the modification-baseline source file, checking that each embodied design change is documented in a form the importing authority recognizes, that stated special requirements are addressed or formally excepted, and that the export paperwork's configuration description matches the verified baseline. Records specialists run it ahead of an export or registry transfer. It concludes with a gap list per importing-authority requirement, structured for the configuration support package.
When this review is needed
- A sale or lease moves the aircraft to a new registry and the export package must be assembled from a heavily modified history.
- The importing authority has published special requirements and no one has mapped them to documents on hand.
- Modifications were embodied under STCs of one authority and the receiving authority's acceptance position is undetermined.
- A prior export left exceptions on the certificate and the current file cannot explain what they covered.
The problem
Export is where a records file meets a reader with no shared history and no obligation to be charitable. The exporting side knows its modifications are fine; the importing authority knows only what the package shows, in the forms it accepts. Special requirements arrive late, differ by state, and often demand documents that were never generated because the exporting regime did not require them. The team assembling the package discovers these gaps one query at a time, against a delivery date that does not move.
What gets reviewed
- The draft or existing export evidence package, document by document
- Importing-authority special requirements mapped to specific evidence on hand or noted as unmet
- Design-change documentation for each embodied modification, checked for a form the receiving authority accepts
- Exceptions proposed for the export certificate, verified as accurate and fully described
- Consistency between the package's configuration description and the verified modification baseline
- Supporting statements of conformity and airworthiness evidence required by the transfer
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 special requirement of the importing authority pairs with a document, a waiver, or an explicit open item
- STC-based modifications show an acceptance path with the receiving authority: validation, bilateral acceptance, or pending application
- The export package's modification listing agrees with the verified status report, with no unlisted embodiments
- Proposed certificate exceptions describe their subject precisely enough to be closed later
- Airworthiness and conformity statements in the package carry dates and signatories consistent with the underlying records
Evidence normally required
- The export evidence package in its current state of assembly
- The importing authority's published requirements and any correspondence received
- The verified modification status report and STC files from the source package
- Prior export certificates and their exception lists, if the aircraft exported before
- Bilateral agreement guidance applicable to the two authorities involved
Common discrepancies
- A special requirement answered by a document type the importing authority has already said it will not accept
- Modifications embodied under a domestic approval with no acceptance evidence for the receiving state
- An exception carried from a previous export, still unresolved and no longer understood
- Configuration descriptions in the package written from the unverified status report rather than the baseline
What is at stake
A package gap at export stalls the registry transfer, and every week of delay has a carrying cost someone contractually owns. Worse, an export certificate issued with unexplained exceptions follows the aircraft: the next transaction inherits the exceptions along with the burden of reconstructing what they meant.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Collect the requirements
Compile the importing authority's published and corresponded requirements into a single checklist.
Map the evidence
Assign each requirement a document from the package or the source file, marking unmet items honestly.
Build the acceptance matrix
Determine the receiving-system path for every embodied design change, flagging those without one.
Test the package
Read the assembled package as the importing reviewer will, and issue the gap list and exception-quality findings.
What the buyer receives
- A requirement-by-requirement gap list against the importing authority's stated needs
- A modification-acceptance matrix showing each design change's path into the receiving system
- An exception-quality review of anything proposed for the export certificate
Who uses the output
- Configuration managers finalizing the export evidence package
- Transaction teams sequencing the registry transfer around real document lead times
- Continuing-airworthiness staff of the receiving operator preparing induction
How the work fits into the transaction or program
Export documentation is a consumer of every other strand in the modification-baseline review: it can only be as good as the verified status report, equipment list, and repair map it summarizes. Running this review last in the sequence lets the gap list reflect the corrected baseline instead of amplifying errors the other strands have since fixed.
Jurisdiction-specific considerations
On the FAA side, export airworthiness approvals under 14 CFR 21.321 and part 21 subpart L define the certificate and its exception mechanics; on the EASA side, Regulation 748/2012 governs the equivalent instruments, with ICAO Annex 8 framing the state-to-state transfer beneath both. The operative question per modification is which instrument the receiving authority will honor, and the answer differs across bilateral arrangements, which is why the acceptance matrix is built per design change rather than per aircraft.
Regulatory limits
This review prepares and tests documentation. It does not issue export certificates, does not represent the applicant before any authority, and makes no determination that the aircraft is eligible for export or import; eligibility remains a matter between the applicant and the authorities.
What this review does not cover
- Filing applications with exporting or importing authorities
- Obtaining STC validations or acceptance decisions
- Physical export survey or conformity inspection of the aircraft
Specific to this review
- Special requirements are the only part of the export process the importing state can rewrite per transaction, which is why a package that worked for a sister aircraft can fail for this one.
- An exception on an export certificate is permanent documentation; a vague exception costs more over the aircraft's life than the gap it papered over.
- Modification acceptance is the long pole: document gaps close in days, but an STC with no acceptance path can add months to a registry transfer.
- Packages assembled from unverified status reports fail in a characteristic way, listing modifications the records cannot support while omitting embodiments the records clearly show.
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 aircraft exported cleanly once before. Why review the package again?
Three things change between exports: the aircraft's modification history grows, the importing state differs or updates its special requirements, and bilateral acceptance practice moves. A package that satisfied one authority in one year establishes very little about the next transfer, so the review treats each export as a fresh mapping exercise seeded, but never settled, by the previous one.
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.