Cross-border transition
Export airworthiness evidence map for cross-border transfers
An export airworthiness evidence map lays out, authority by authority, which records the exporting and importing states expect before an export certificate of airworthiness can be issued and accepted. It is built for lessors, airlines, and acquisition teams ahead of a cross-border transfer. It covers the configuration baseline, AD and modification status, life-limited part trace, and the release and conformity evidence each side relies on. You receive a side-by-side evidence map, a gap list per authority, and the records needed to close each item before the aircraft moves.
When this review is needed
- An aircraft is being moved to a new state of registry and an export certificate of airworthiness will be requested from the exporting authority.
- A transaction term hinges on a clean export certificate and the parties want the evidence demand understood before signing.
- A prior export was issued with exceptions noted and the receiving side wants to know what those exceptions cover.
- The same airframe may route through more than one authority and the records demand of each has to be reconciled in advance.
The problem
An export certificate of airworthiness is issued against a body of evidence the exporting authority expects to see, and the importing authority can add its own conditions on top. Those expectations live in advisory material, bilateral arrangements, and local practice rather than in one list, so a team assembling the file late discovers the demand item by item as the deadline closes. A configuration the records do not fully support, or a release form the receiving side will not take, can hold the certificate after the aircraft is already committed to move.
What gets reviewed
- The export certificate of airworthiness file and the exporting authority's stated expectations for it
- The configuration and modification baseline the certificate will be issued against
- AD compliance status that the exporting and importing authorities each enforce
- Life-limited part traceability to the origin the receiving side will accept
- Authorized release certificates and the form types each authority recognizes
- Any exceptions, deviations, or conditions the exporting authority is likely to note on the certificate
- The importing authority's additional acceptance conditions layered on the export file
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
- The configuration the export certificate will name is supported by the modification and conformity records
- AD status is reconciled against the directives the receiving authority enforces rather than the exporting state alone
- Life-limited part trace reaches the origin the importing side accepts without an unexplained gap
- Release certificates use form types both authorities recognize, or a dual release where required
- Items the exporting authority is likely to except are identified before the certificate is requested
- The importing authority's additional conditions are mapped against evidence already in the file
- Where the aircraft routes through more than one authority, each authority's demand is reconciled against the others
Evidence normally required
- Current AD and modification status reports for the airframe and engines
- Life-limited part status list with supporting release certificates
- Configuration and conformity records establishing the export baseline
- Prior export or airworthiness review documentation where it exists
- The exporting authority's published expectations and any bilateral arrangement in play
- The importing authority's stated acceptance conditions for the type
Common discrepancies
- A configuration item the export baseline names that the modification records do not fully support
- An AD the importing authority enforces that the exporting status report does not track
- A release form acceptable to the exporting state that the receiving authority will not take as is
- A life-limited part trace that satisfies one authority's origin but falls short of the other's
- An exception likely to land on the certificate that the parties had not priced
- A bilateral acceptance path assumed to apply that does not cover the specific evidence in question
What is at stake
An export certificate issued with open exceptions transfers the cost of closing them to the importing party, and an aircraft that cannot get its certificate stalls on the ground while the records are chased. Evidence the receiving authority rejects after import is far harder and slower to source than the same evidence assembled before the aircraft leaves, when the exporting operator and shops are still reachable.
How the work runs
Define the export path
Establish the exporting and importing authorities, the type, and the configuration the certificate will be issued against.
Build the demand
Assemble each authority's evidence expectations from its published material and any bilateral arrangement that applies.
Map evidence to demand
Place the records already held against each authority's expectations and mark where the file falls short.
Flag gaps and exceptions
List the open items per authority and the exceptions the certificate is likely to carry, with the records each needs.
What the buyer receives
- A side-by-side evidence map showing what each authority expects for the export and import
- A gap list per authority with the records each open item needs to close
- A flag of the exceptions the export certificate is likely to carry and who must address them
Who uses the output
- Asset and acquisition teams confirming the export path before committing the aircraft
- Records teams assembling the export certificate file against a defined demand
- Transaction stakeholders pricing the cost of any exception the certificate may carry
How the work fits into the transaction or program
The map runs ahead of the export request so the evidence demand of both authorities is known while the exporting operator and shops can still produce records. It feeds the export file itself and the discrepancy register for the wider transfer, and it tells the team which items must close before the certificate is requested rather than after.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
An export certificate of airworthiness reflects the exporting authority's view at the moment of issue, and the importing authority decides separately what it will accept. A bilateral arrangement may smooth that acceptance for some evidence and leave other items to be addressed directly, so the map reads each authority's demand on its own terms rather than assuming one certificate satisfies both.
Regulatory limits
The map confirms which records each authority expects and whether they are present and consistent. It does not issue an export certificate, bind either authority to accept the aircraft, make an airworthiness determination, or guarantee the importing state will issue a certificate of airworthiness on the strength of the file.
What this review does not cover
- Application for or issuance of the export certificate of airworthiness itself
- Physical inspection or conformity survey of the aircraft
- Any airworthiness determination or regulatory approval
Specific to this review
- Export-certificate expectations are spread across advisory material, bilateral arrangements, and local practice, so the demand is assembled rather than read from a single list.
- An exporting authority can note exceptions on the certificate, and an exception the parties had not priced shifts cost to whoever accepts the aircraft on the other side.
- The importing authority sets its own acceptance conditions on top of the export file, so a clean export certificate is the start of acceptance, not the end of it.
- Where an airframe routes through more than one authority, the same record can satisfy one demand and fail another, so the map is built per authority rather than once.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
Transport Canada. Canadian airworthiness, maintenance records (CAR 605/571), and Airworthiness Directive requirements (CAR 593).
U.S. Government (eCFR). Type certificates, STCs (Subpart E), TSO authorizations (Subpart O), PMA (Subpart K), and export airworthiness approvals (Subpart L).
Frequently asked questions
Does a clean export certificate guarantee the importing authority will accept the aircraft?
No. The export certificate reflects the exporting authority's view at issue. The importing authority decides separately what it accepts and can add conditions, so the map covers both sides rather than treating the export certificate as the whole story.
Is this the same as applying for the export certificate?
No. The map sets out what each authority expects and where the records fall short. The application itself is made by the operator or its agent, and the map gives them a file that meets the demand before the certificate is requested.
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.
Walk through your situation with an engineer who has done this work.