Export readiness
Export airworthiness documentation review before an operator's transaction
This review confirms that an operator's export airworthiness documentation is complete before a sale or transfer commits to dates. It examines the export certificate application, the importing authority's special requirements, and the status summaries and records that must stand behind them, then reconciles all of it against the export evidence package as assembled. Records specialists run it for the operator once the destination registry is known and before commercial sign-off. The result is a requirement-by-requirement gap list and the assembly actions that must complete before the export application is filed.
When this review is needed
- A sale to a foreign buyer is agreed and the export certificate of airworthiness process is about to start.
- The importing authority has published special requirements and nobody has mapped them to the aircraft's records yet.
- The transaction timeline puts deregistration and export on the critical path to funding.
- A previous export attempt on a fleet sister stalled on documentation and this one must not.
The problem
Export documentation sits at the junction of two authorities' expectations. The exporting side's application requirements are known territory; the importing authority's special requirements arrive as a list written for its own system, referencing status formats and evidence the operator's records were never organized to produce. Assembly starts late because the destination is confirmed late, and every unmapped requirement discovered during the application window pushes deregistration, delivery, and payment.
What gets reviewed
- The export certificate application and its required attachments under the exporting regulation
- The importing authority's special requirements mapped one by one to responsive evidence
- AD, SB, and modification status summaries in the format the destination expects
- Supporting records behind each summary: accomplishment evidence, releases, approvals
- Deregistration prerequisites that interact with the export file
- The export evidence package structure against how the two authorities will actually read it
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 special requirement has a mapped, present, and responsive document
- Status summaries in the package reconcile to the underlying compliance records, never merely to the maintenance system
- Application data such as hours, cycles, and configuration matches the records the package contains
- Third-party documents needed for the export are identified with realistic lead times
- Nothing required for deregistration conflicts with what the export application asserts
Evidence normally required
- The purchase or transfer agreement's delivery condition and export obligations
- The importing authority's special requirements list for the aircraft type
- Current AD, SB, modification, and LLP status reports with supporting records
- Prior export files for similar aircraft where the operator has them
- Registry correspondence covering deregistration mechanics
Common discrepancies
- Special requirements answered with a status list where the authority asks for accomplishment evidence
- Configuration or noise documentation formats accepted domestically but rejected by the destination registry
- Hours and cycles on the draft application that disagree with the status reports enclosed behind it
- Third-party certificates, such as fresh releases or authority letters, identified only after the filing window opened
What is at stake
An export file that fails at the authority reopens at the transaction: delivery dates slip, deregistration windows are missed, and penalty or interest clauses in the purchase agreement start to run. Some importing-authority requirements need documents from third parties with their own lead times, so a gap found late may be impossible to close on schedule.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map the requirements
Combine exporting-regulation attachments and importing-authority special requirements into one checklist.
Match evidence
Assign each requirement a responsive document and verify it exists, reads correctly, and reconciles to source.
Chase the long poles
Start third-party documents and authority correspondence items first, against the filing date.
Assemble and verify
Build the package in submission order and re-check internal consistency before filing.
What the buyer receives
- A requirement-by-requirement readiness matrix for the export file
- A gap list with responsible party and lead time against the filing date
- An assembled-package review note stating what the file supports as submitted
Who uses the output
- Directors of maintenance sequencing the export against the delivery schedule
- Records leads assembling and defending the evidence package
- Transaction counsel and closing teams timing funds flow against deregistration
How the work fits into the transaction or program
Export readiness closes the records phase of a cross-border sale. It draws on the AD, configuration, and LLP work done earlier in transaction preparation and converts it into the specific shapes two authorities require, so the export application becomes a formality instead of a discovery process.
Jurisdiction-specific considerations
Exports from the United States run under 14 CFR 21 subpart L, with FAA practice shaping what the application must show; EU exports operate through Regulation 748/2012 and the airworthiness review structure of Regulation 1321/2014. ICAO Annex 8 gives importing states the hook for special requirements, and those vary widely: some registries want little beyond the export certificate, others require notarized status attestations or type-acceptance evidence the operator has never produced before.
Regulatory limits
The review prepares and verifies documentation. It does not issue export certificates, conduct airworthiness reviews, or determine airworthiness, and it does not act as the applicant before either authority. Certificate issuance remains between the operator, its designees, and the regulators.
What this review does not cover
- Filing the export application or acting as applicant
- Physical inspections associated with export or import acceptance
- Import-side type acceptance or validation engineering
Specific to this review
- Special requirements are keyed to the importing state, so an export package that succeeded for one buyer can fail unchanged for the next destination.
- The slowest documents in most export files are third-party attestations, and their lead time is invisible until someone maps requirements to sources.
- Application-versus-package mismatches, like differing cycle counts, are minor clerical errors that authorities treat as file-stopping.
- Deregistration and export sequencing traps are contractual as much as regulatory: funds flow provisions often assume an order of events the registries do not guarantee.
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
When should export readiness work start?
As soon as the destination registry is known, even provisionally. Requirement mapping and third-party lead times dominate the schedule, and both can run in parallel with price and contract negotiation. Waiting for a signed agreement routinely puts the export file on the critical path.
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.