Registry export files
Export airworthiness documentation review inside an import and export records package
This review tests whether the export airworthiness documentation in an import and export records package holds up against the records behind it. It reads the export certificate application, the importing authority's special-requirements correspondence, and the deregistration items against status summaries and supporting source records. It is run for a lessor, airline, or acquisition team while the export file is being assembled, before the importing authority sees it. The output is an exception list, keyed to source documents, that the transition lead folds into the authority-response evidence file.
When this review is needed
- An export certificate of airworthiness application is being assembled and the supporting records were pulled from several archives.
- The importing authority has issued special requirements and each one needs evidence attached before submission.
- Deregistration is scheduled and the export file must be complete before the aircraft leaves the current registry.
- A prior export attempt stalled on authority questions and the resubmission has to close every open point.
The problem
Export files are usually assembled under a deregistration deadline from whatever status summaries the operator can produce quickly. The importing authority then reads the file cold and asks for the source document behind any line that looks thin. Answering those questions mid-transition means chasing records across archives while the aircraft sits deregistered and unable to fly on its old papers.
What gets reviewed
- The export certificate application and its declared basis, read against the aircraft status summaries
- Each importing-authority special requirement matched to the evidence intended to satisfy it
- Deregistration and non-registration confirmations checked for consistency with the transaction timeline
- Exceptions and deviations declared on the export application traced to written authority acceptance
- Status lists cited in the export file compared with the underlying compliance records
- Registry-change correspondence reviewed for commitments the records must still support
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 special requirement on the importing authority's list has a named source document, and that document is in the package
- Declared exceptions on the export application carry written acceptance from the importing authority, dated before submission
- The aircraft configuration described in the export file matches the modification status the source records support
- Times and cycles quoted in the export documentation agree with the status summaries and the records behind them
- Nothing in the registry-change correspondence promises evidence the source package does not actually contain
Evidence normally required
- The draft export file, including the export certificate application and any declared exceptions
- The importing authority's special-requirements list and all correspondence to date
- Aircraft status summaries for AD, SB, LLP, and modification standing
- The registry-change file with deregistration and non-registration requests
- The supporting source records the export file is meant to rest on
Common discrepancies
- A special requirement answered with a status summary when the authority asked for accomplishment evidence
- An exception declared on the export application that was discussed with the authority but never accepted in writing
- Configuration statements in the export file that predate a modification embodied during the same transition
- Deregistration paperwork whose dates conflict with the delivery sequence the parties have agreed
What is at stake
An export file that cannot answer authority questions stalls the registry change itself. The aircraft can end up between registries with the delivery date slipping day by day, and each query that goes unanswered invites a wider look at the rest of the file. Special requirements accepted late, or missed entirely, can force rework of the whole submission.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map the file to its claims
List every statement the export documentation makes: status, configuration, exceptions, special-requirement responses.
Trace each claim to source
Match each statement to the record in the source package that supports it, noting substitutes and summaries.
Isolate the exceptions
Record every claim the package cannot support, with what is missing and where it likely lives.
Hand off the response index
Deliver the exception list and cross-reference the transition lead will work from during authority review.
What the buyer receives
- An exception list identifying each export-file statement the source package cannot yet support
- A cross-reference from every special requirement to the evidence that answers it
- A short readiness note on whether the file can face authority review as it stands
Who uses the output
- The transition lead assembling the authority-response evidence file
- Technical-records staff retrieving the documents the exception list calls for
- Deal counsel and asset managers tracking whether the registry change can hold its date
How the work fits into the transaction or program
The review sits between file assembly and authority submission. Findings route back to the records team for retrieval or correction, and the cross-reference it produces becomes the working index the transition lead uses when the importing authority starts asking questions.
Jurisdiction-specific considerations
An FAA export under 14 CFR 21.321 and an EASA import each define their own documentation baseline, and the importing state's special requirements sit on top of both. The same aircraft can need different evidence depending on direction of travel, so the review is scoped to the specific exporting and importing pair rather than a generic checklist.
Regulatory limits
The review reports what the source package supports and where it falls short. It does not issue or apply for an export certificate of airworthiness, does not make airworthiness determinations, and does not speak for the importing authority on whether an exception will be accepted.
What this review does not cover
- Filing the export application or corresponding with authorities on the client's behalf
- Physical survey of the aircraft prior to export
- Negotiating the transaction terms that drive the registry-change timeline
Specific to this review
- An export certificate of airworthiness attests to the exporting authority's findings; it does not by itself make the aircraft airworthy on the new registry.
- Importing authorities may add special requirements beyond the exporting state's baseline, and each one needs its own evidence trail.
- Exceptions on an export application are only safe when the importing authority has accepted them in writing before the certificate is issued.
- The window between deregistration and re-registration is when records gaps cost the most, because the aircraft cannot operate while questions stay open.
- Status summaries carry no weight with an importing authority on their own; the accomplishment records behind them decide the outcome.
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
Does this review replace the importing authority's own inspection of the aircraft and records?
No. The authority makes its own findings. The review prepares the file the authority will read, so the questions that come back are ones the package can already answer.
How long does the review take relative to the export timeline?
It scales with the size of the special-requirements list and the state of the source package. Run early in file assembly it works in parallel with retrieval; run after submission it becomes reactive, which is why teams schedule it before the authority sees the file.
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.