Cross-border records
How to prepare aircraft records for an import or export
Preparing records for an import or export means lining up the aircraft's configuration, compliance evidence, and component releases with what the receiving authority will accept before the asset crosses authorities. It is read by sellers, buyers, and operators moving an aircraft across registries. The work covers the configuration the receiving side accepts, the releases that hold under its basis, the AD position read against its applicability, the export package, and the bridging evidence for items it will question. You hand over a cross-border readiness view, a list of likely receiving-side questions, and the evidence prepared to answer each.
When this review is needed
- An aircraft is moving between authorities and the records have to satisfy the receiving side, not only the exporting one.
- An export airworthiness package has been requested and its contents must match the records behind it.
- A receiving authority is expected to question component releases or compliance evidence issued under a different basis.
- A registry change is planned and the configuration has to be reconciled to what the new authority accepts.
The problem
A release that is unquestioned where the aircraft sits is not automatically valid where it is going, so records assembled to the exporting side's logic can fail the receiving side's reading. The export package can carry exceptions, and the receiving authority reads those exceptions against the records rather than waving them through. The questions tend to land on component releases and AD applicability, exactly the areas where a difference in basis between two authorities is widest.
What gets reviewed
- The configuration and modification status the receiving authority will accept
- Component releases and whether they hold under the receiving basis
- AD and Service Bulletin compliance read against the receiving authority's applicability
- The export airworthiness package and the records it rests on
- Any exceptions on the export certificate and the evidence behind each
- Bridging evidence for items the receiving side is likely to question
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 exported configuration agrees with the airframe modification and repair records
- Component releases are appropriate to, or bridged for, the receiving authority
- AD status reflects the receiving authority's applicability, not only the exporting one
- Each exception on the export certificate has its supporting evidence prepared
- Each likely receiving-side question has prepared evidence behind it
Evidence normally required
- The export airworthiness certificate and its attachments if issued
- Configuration, modification, and major-repair records for the airframe
- Component release certificates for installed parts
- The receiving authority's acceptance basis and any bilateral arrangement
Common discrepancies
- A component release the receiving authority will not accept as issued
- Configuration in the export package that disagrees with the airframe records
- AD status framed only against the exporting authority's applicability
- An export certificate exception with no supporting evidence assembled
- Likely receiving-side questions with no bridging evidence prepared
What is at stake
An aircraft can sit while a receiving authority's questions are answered one at a time, with each answer requiring a document nobody assembled in advance. A component release the receiving side will not accept as issued can force a re-release or a bridging exercise after the asset has already moved, when the exporting organization has less reason to help.
How the work runs
Read against the receiving basis
Identify the receiving authority's acceptance basis and any bilateral arrangement, and re-read the records against it rather than the exporting side.
Test the releases and AD position
Check whether component releases hold and whether the AD status reflects the receiving authority's applicability.
Map the likely questions
List the documents the receiving side is most likely to question, especially releases and exceptions.
Assemble the bridging pack
Prepare the supporting and bridging evidence for each likely question before the asset moves.
What the buyer receives
- A cross-border readiness view of the records against the receiving basis
- A list of likely receiving-authority questions with evidence behind each
- A bridging-evidence pack for the items most at risk on import
Who uses the output
- Records and airworthiness teams answering the receiving authority
- Asset teams scheduling the move against records readiness
- Buyers and sellers pricing the cross-border risk
How the work fits into the transaction or program
Cross-border preparation runs alongside the transaction and ahead of the receiving authority's review. Its readiness view and bridging pack feed the import filing and the records baseline the aircraft will carry on the new registry.
Jurisdiction-specific considerations
Bilateral arrangements set what one authority will accept from another, and they govern which releases and approvals carry across. The preparation is built around the specific pair of authorities in play, because what bridges between two of them does not generalize to a third.
Regulatory limits
Preparation aligns the records with the receiving authority's basis. It does not issue an export or import approval, does not make an airworthiness determination, and the receiving authority remains the party that accepts or questions the records.
What this review does not cover
- Issuing the export airworthiness certificate or the import approval
- Performing any re-release or re-certification of components
- Any airworthiness determination on the receiving authority's behalf
Specific to this review
- A component released on the exporting authority's form is not automatically acceptable to the receiving authority, so the records are prepared against where the asset is going.
- An export airworthiness certificate can carry exceptions, and the receiving side reads those exceptions against the records, so each one needs its supporting evidence ready.
- Bridging depends on the specific pair of authorities and the bilateral arrangement between them, so a route that works for one pair does not transfer to another.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
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.
Frequently asked questions
Why prepare against the receiving authority instead of the exporting one?
Because the receiving authority is the side that has to accept the records, and a release or an AD position valid on the exporting side is not automatically valid on the receiving side. Preparing against where the asset is going is what keeps the move from stalling on questions.
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.
Adapt the checklist to your asset, event, and jurisdiction.