Cross-border records
Export airworthiness documentation review
An export airworthiness documentation review is for sellers, lessors, and acquisition teams moving an aircraft across a bilateral boundary. The trigger is an export airworthiness certificate that has been issued or requested. It examines the certificate, any exceptions written on it, the AD and modification status declared at export, and the release evidence for installed components, all tested against the source records held with the airframe. You receive a finding list tied to each supporting document and a ranked view of the items the receiving authority is likely to question.
When this review is needed
- An aircraft is leaving one authority and an export airworthiness certificate has been issued or is being prepared.
- The receiving side has attached special conditions or exceptions that have to be reconciled with the records.
- A sale or lease carries the asset across a bilateral boundary and the configuration must travel intact.
- An import has stalled because the receiving authority is questioning items the export package asserts.
The problem
The export certificate is a summary signed at one point in time, while the evidence sits across logbooks, modification dossiers, and component paperwork that the receiving side reads on its own terms. Exceptions noted at export are easy to overlook until an importing authority asks what record stands behind each one. By then the asset has often already moved, the exporting party has been released, and the cost of sourcing a missing dossier lands on the importer.
What gets reviewed
- The export airworthiness certificate with each exception, limitation, and condition stated on it
- Airworthiness Directive status declared at export against the accomplishment evidence behind it
- Service Bulletin and modification status as it appears in the exported configuration
- Authorized release certificates for components named in the package and their acceptability to the receiving side
- The maintenance status reported at export reconciled to the source documents held with the aircraft
- Bilateral and importing-authority special requirements the package is meant to satisfy
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 exception listed on the export certificate resolves to an underlying record that explains and bounds it
- AD status declared at export matches the accomplishment evidence and the method of compliance shown
- The exported configuration agrees with the modification and major-repair records carried with the airframe
- Component releases referenced in the package are present and appropriate for acceptance by the receiving authority
- Time-in-service and last-event figures stated at export are consistent with the logbooks and status lists
- Special requirements named by the importing side are addressed by a document in the set rather than assumed
Evidence normally required
- The export airworthiness certificate and its attachments and exception schedule
- Current AD and Service Bulletin status reports as declared at export
- Airframe modification and major-repair records
- Authorized release certificates for components installed before export
- Any importing-authority special requirements or bilateral acceptance conditions on record
Common discrepancies
- An exception on the certificate with no record behind it that explains its basis or scope
- Modification status in the package that disagrees with the airframe configuration records
- AD closure stated at export without the accomplishment evidence attached to the set
- Component releases referenced in the package but absent from the documentation delivered
- A repair approved under the exporting basis that the receiving side will want re-substantiated
What is at stake
An export package whose exceptions or modification status cannot be traced can delay the receiving certificate, force re-substantiation of a change, or strand the aircraft between registries. Recovery is slower once custody has transferred, because the data and the people who produced it stay behind the boundary the asset just crossed.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the certificate and its exceptions
Capture every exception, limitation, and condition on the export certificate and the importing requirements the package is meant to meet.
Trace each entry to source
Tie the declared AD, modification, and component status back to the accomplishment and release evidence held with the airframe.
Test against the receiving basis
Check exceptions and component forms for acceptability under the bilateral agreement and the importing authority's known requirements.
Register and recommend
List each finding with its document trace and a closure path for the items the receiving side is most likely to raise.
What the buyer receives
- A finding list mapped to each supporting document and each certificate entry
- An exception register showing the evidence that supports or contradicts each item
- A closure recommendation for the items the receiving authority is most likely to raise
Who uses the output
- Seller and lessor technical teams preparing the export package
- Acquisition and import teams accepting the asset under a new authority
- Continuing-airworthiness staff who will own the configuration after transfer
How the work fits into the transaction or program
The review runs while the exporting party is still engaged, so exceptions can be explained and missing dossiers recovered before custody changes. Its output seeds the import file and the configuration baseline the receiving authority will work from.
Aircraft-specific considerations
Modification and repair history drive which exceptions matter at export. A type carrying field approvals, supplemental type certificates, or major repairs presents more places where the exported configuration and the receiving basis can diverge, so the package is read against the specific change history rather than a generic export checklist.
Jurisdiction-specific considerations
A bilateral agreement governs what the receiving authority will accept, and a release valid on the exporting side is not automatically valid on the importing side. The package is read against where the asset is going, so the exceptions and component forms are tested for acceptability under the receiving basis.
Regulatory limits
This review confirms that the export documentation is complete, consistent, and traceable to its records. It does not issue or replace an export or import certificate, does not bind any authority, and does not by itself make the aircraft acceptable to the receiving state.
What this review does not cover
- Issuing or amending the export airworthiness certificate
- Negotiating bilateral acceptance terms with an authority
- Physical survey or borescope of the aircraft
Specific to this review
- An export airworthiness certificate can carry exceptions, and an exception is only meaningful when the record that justifies it can be produced.
- A component released on the exporting authority's form is read for acceptability to the receiving authority rather than assumed to transfer with the asset.
- Once custody crosses the boundary, the data and the people who created it usually stay behind, which is why the trace is built before the asset moves.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
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 review the export package if a certificate has already been issued?
The certificate states a position; the records have to support it when the importing authority reads them. The review confirms the exceptions and declared status are backed by evidence the receiving side can use, before custody transfers and recovery gets harder.
Does this guarantee the receiving authority will accept the aircraft?
No. The review establishes that the documentation is supported and traceable. Acceptance is the receiving authority's decision, and the output is built to anticipate and answer what that authority is likely to ask.
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.