Export airworthiness
Airbus A350 family export airworthiness records review
This review assembles and tests the export airworthiness evidence for an Airbus A350 family aircraft against what the importing authority will require before it accepts the aircraft onto its register. It is run by or for a lessor, operator, or manager moving a specific serial number across borders, ahead of the export certificate application. It checks the evidence package, identifies the importing authority's special conditions, and confirms the status summaries and supporting records line up with what the receiving system expects. You receive an exception list of items the importing authority will question, a source map to the record behind each, and a plan to close the package before export.
When this review is needed
- A serial number is moving to a new register and the export airworthiness package has to be assembled.
- The importing authority has published special conditions the current records may not satisfy.
- An export certificate application is being prepared and the supporting status summaries need checking first.
- A prior export attempt stalled on records the receiving authority would not accept.
The problem
Export airworthiness is where a records file meets a second authority's expectations, and the two rarely match line for line. The importing authority may impose special conditions, require records in a form the exporting system never produced, or expect status summaries built to its own recordkeeping. On an A350 the STC and modification content approved under one authority may need validation to stand under another, and a package that looked complete for the current register can fall short of the receiving one. The gaps only appear when the package is tested against the actual import requirements.
What gets reviewed
- The export evidence package assembled and tested against the importing authority's requirements
- Importing-authority special conditions identified and matched to the records that answer them
- Status summaries for AD, life-limited parts, and modifications built to the receiving system's expectations
- Cross-authority validity of STCs and modifications confirmed for the receiving register
- Supporting records confirmed present, legible, and in the form the importing authority accepts
- Items the importing authority will question carried onto an exception list with the record owed
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 importing-authority special condition is matched to a record that satisfies it
- AD and life-limited status summaries are built to the receiving authority's recordkeeping, not only the exporting one
- STCs and modifications relied on carry the validation the receiving register requires
- Supporting records are legible and in a form the importing authority will accept
- The evidence package reconciles internally so no summary contradicts its own supporting record
Evidence normally required
- The draft export evidence package and status summaries
- The importing authority's export and acceptance requirements and any special conditions
- Current AD, life-limited part, and modification status reports
- Approval and validation records for the aircraft's STCs and modifications
- The supporting records the summaries draw on
Common discrepancies
- A special condition from the importing authority with no record assembled to answer it
- A status summary built to the exporting system that the receiving authority will not accept as is
- An STC valid on the current register with no validation for the receiving one
- A supporting record present but in a form the importing authority does not accept
What is at stake
An export package that does not meet the importing authority's requirements stalls the aircraft at the border, and the delay lands squarely in the transaction timeline. A special condition discovered late can require records work, a validation, or a status rebuild that takes weeks the deal cannot absorb. Every day the aircraft sits unaccepted carries cost, so the gaps are far cheaper to find before the application than after it is rejected.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the import requirements
Establish the importing authority's acceptance requirements and any special conditions for the aircraft.
Assemble and map the package
Build the evidence package and match each requirement to the record that answers it.
Test cross-authority validity
Confirm STCs, modifications, and summaries will stand under the receiving register.
List and plan the gaps
Flag items the importing authority will question and set the work to close each before application.
What the buyer receives
- An exception list of items the importing authority will question before acceptance
- A source map from each requirement and special condition to the record that answers it
- A plan to close the package, including any validation or status rebuild needed
Who uses the output
- Records teams assembling the export package before the certificate application
- Asset and transaction teams protecting the timeline against a border stall
- Continuing-airworthiness staff aligning the status summaries to the receiving system
How the work fits into the transaction or program
Export airworthiness sits at the boundary between the outgoing register and the receiving one, after the aircraft's status is otherwise settled and before the export certificate is applied for. This review tests the assembled package against the actual import requirements and feeds any gap into remediation while there is still time to validate an STC or rebuild a summary before the application goes in.
Aircraft-specific considerations
The A350's modification and STC content, much of it cabin, connectivity, and avionics, is where cross-authority acceptance most often turns, because a change approved under one authority may need a validating approval to stand under the receiving one. The type's software-defined configuration means the export summaries have to account for data and software standards as well as hardware, and the composite repair history has to be presented in a form the importing authority will accept alongside the rest of the package.
Jurisdiction-specific considerations
Because the aircraft moves between authorities, the review reads the current register's records against the receiving authority's requirements and flags where a summary, an approval, or a supporting record built for the exporting system will not carry to the importing one. It notes the special conditions and validation steps the receiving authority imposes so they can be addressed before the export certificate is sought.
Regulatory limits
The review assembles and tests the export evidence against the importing authority's stated requirements. It does not issue an export certificate of airworthiness, grant acceptance onto the receiving register, or make an airworthiness determination; those rest with the exporting and importing authorities.
What this review does not cover
- Issuing or applying for the export certificate of airworthiness
- Obtaining a validation or approval from the receiving authority
- Any airworthiness determination for the receiving register
Specific to this review
- The importing authority sets the bar, so a package complete for the current register can still fall short of the receiving one.
- Special conditions from the importing authority are the items most likely to require records work discovered late.
- An STC valid on the outgoing register often needs a separate validation to be relied on after export, and that lead time drives the timeline.
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 records satisfied the current authority. Why might they not satisfy the importing one?
Export acceptance is set by the importing authority, which can impose special conditions, require status summaries built to its own recordkeeping, and expect STCs and modifications to be validated for its register. A package that was complete for the outgoing authority can still fall short. The review tests the package against the receiving authority's actual requirements before the export certificate is sought.
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.