Export support
Export airworthiness documentation in a component-history source file
Before a component or its host aircraft crosses registries, the export evidence package must satisfy the importing authority, and this review tests whether it will. Each element of the package, export certificates, release documents, statements of special-requirement compliance, is checked against the importing state's published expectations and against the component-history source file that must substantiate it. The work is scheduled during a serialized-component trace review, ahead of the export event itself. It ends with a package gap list stating which required elements are missing, unsupported, or inconsistent with the underlying records.
When this review is needed
- A sale moves the component or aircraft to a new registry and the export package is being assembled for the first time.
- The importing authority has published special requirements and nobody has mapped them against the assembled documents.
- An earlier export attempt stalled on a document request the package could not answer.
- Certificates in the package make statements the component-history file has not been checked to support.
The problem
Export packages are assembled from templates built for the last export, while requirements differ by importing state and change between transactions. A statement of conformity gets signed on the strength of a status report nobody re-verified, a special requirement is answered with a document that addresses a different revision of the rule, and the gap only surfaces when the importing authority's reviewer sends questions with the aircraft already committed to a delivery date.
What gets reviewed
- The importing state's requirements, including published special requirements, mapped item by item against the package
- Export certificates and their supporting statements checked for documentary basis in the source file
- Release documentation for the component verified as acceptable to the receiving system
- AD and modification statements in the package reconciled with the underlying status evidence
- Exceptions and deviations declared on certificates checked for required importing-authority acknowledgment
- Package internal consistency verified across certificates, statements, and attachments
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 importing-authority requirement has a designated responsive document in the package
- Statements signed on export certificates are each traceable to evidence in the component-history file
- The release documents carried by the component are of a form the importing system accepts
- No package document contradicts another on status, configuration, or utilization figures
- Declared exceptions carry the acceptance or acknowledgment the importing authority requires
Evidence normally required
- The draft export evidence package as assembled
- The importing authority's requirements and any published special requirements for the asset type
- The component-history source file, including status reports, releases, and movement records
- Prior correspondence with the importing authority, where any exists
- Details of declared exceptions or deviations and their supporting rationale
Common discrepancies
- A special requirement of the importing state with no responsive document anywhere in the package
- Export-certificate statements resting on status reports the file cannot substantiate
- Release paperwork in a form the exporting system accepts but the importing system does not
- Utilization figures that differ between the export application and the records package behind it
What is at stake
Deficiencies discovered by the importing authority are the most expensive kind, because the transaction is by then public, dated, and financed. Registration can stall with the asset in limbo between registries, and each round of authority questions adds weeks. A certificate later shown to have overstated what the records support creates liability that outlives the deal.
How the work runs
Map the requirements
Compile the importing state's current requirements and specials for the asset and transaction type.
Test the package
Match each requirement to its responsive document and each certificate statement to source evidence.
Check coherence
Reconcile figures and statements across the package and against the component-history file.
Sequence remediation
Deliver the gap list ordered by document lead time relative to delivery.
What the buyer receives
- A requirement-by-requirement gap list for the export package
- A substantiation index tying each certificate statement to its evidence in the source file
- A remediation sequence ordered by document lead time against the delivery date
Who uses the output
- Records leads finalizing the package before submission to the exporting authority
- Transaction managers holding the delivery timeline against document lead times
- The receiving operator's or buyer's technical team preparing for import acceptance
How the work fits into the transaction or program
The export check is the outward-facing end of the source review: everything the other record checks substantiate, status, configuration, repairs, deferrals, is what the export certificates ultimately assert to a foreign authority. Running it after those checks lets the package cite verified positions instead of inherited ones.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Exports from the United States operate under 14 CFR 21.321 and related subpart L provisions, with importing-state special requirements documented and answered as part of the application. Movements into or out of the EASA system engage Regulation 748/2012, and ICAO Annex 8 supplies the airworthiness framework both sides reference; bilateral agreements between the states involved determine which certificates transfer on their face and which need supplementary evidence.
Regulatory limits
The review prepares and tests documentation only. It does not issue export certificates of airworthiness or authorized-release documents, does not represent the applicant before any authority, and cannot guarantee acceptance by the importing state; those decisions rest with the authorities and their designees.
What this review does not cover
- Issuance of export certificates or FAA Form 8130-4 documentation
- Physical export condition surveys of the aircraft or component
- Customs, tax, or trade-control aspects of the export
Specific to this review
- Special requirements are published per importing state and revised without ceremony; a package built from the previous export to the same country can still be answering last year's list.
- The longest-lead documents in export remediation are almost always releases from third-party shops, so sequencing the gap list by lead time matters more than by severity.
- Certificates are read as a set by importing reviewers: a single utilization figure that differs between two package documents triggers questions about both.
- Declared exceptions are often the safer path; an exception acknowledged by the importing authority in advance causes less delay than a marginal statement discovered after submission.
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 exporting authority already reviewed our application. Why test the package again?
The exporting authority checks its own issuance requirements; the importing authority applies a different list, including its special requirements, and it is the party that can hold up registration. Packages routinely clear export review and then stall on import questions, which is why this check is built around the receiving state's expectations.
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.