Crossing registries
Export airworthiness documentation verified from scanned records
When an aircraft crossed registries, an export evidence package was assembled to satisfy the importing authority: export certificate of airworthiness, declarations of conformity to special requirements, and the technical records those declarations leaned on. Years later, that package survives only as scans, and this review verifies the digitized set is complete, legible, and internally consistent for each historical export event. It matters because the current file inherits whatever the exports established, and gaps there resurface at the next registry change. A findings memo per export event tells records control what the archive proves and what it merely mentions.
When this review is needed
- A new registry transfer is planned and the incoming authority will ask what previous exports established.
- The aircraft's history includes deregistration and import events whose paperwork exists only in the scanned archive.
- Diligence questions reference special requirements from a past import and nobody can produce the compliance declarations.
- Archive migration separated export certificates from the supporting records they were issued against.
The problem
Export packages are assembled once, under deadline, from documents borrowed out of the main records set, and then filed as a unit that nobody opens again until the next transfer. Scanning tends to dismember them: the certificate lands in a certificates folder, the special-requirements correspondence in general correspondence, and the supporting status lists back into their home categories. What was a coherent demonstration to an authority becomes scattered fragments whose relationships survive only in cover letters, if the cover letters were scanned at all.
What gets reviewed
- Each historical export event identified and its evidence package located across the archive
- Export certificates of airworthiness confirmed present, complete, and legible for each event
- Importing-authority special requirements identified from correspondence and matched to compliance declarations
- Supporting records cited in declarations, such as AD status and configuration statements, found as scanned at the event date
- Exceptions or deviations negotiated during the export documented with their authority acceptance
- Deregistration and registration continuity checked across each transfer
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 known registry change in the aircraft's history has a locatable export evidence package
- The export certificate for each event is a full scan including any continuation or exception sheets
- Each special requirement raised by the importing authority has a matching response in the package
- Status documents cited in export declarations exist in the archive as of the dates cited
- No export exception was left open without documented acceptance or later discharge
Evidence normally required
- The aircraft's registration history and known transfer dates
- The scanned archive with its index, including correspondence folders
- Export certificates and conformity statements as digitized
- Authority correspondence covering special requirements for each import
- Delivery or closing binders from the transfers, where these were scanned
Common discrepancies
- An export certificate present while the special-requirements correspondence that defined its exceptions is missing
- Compliance declarations citing status lists that were scanned in later revisions, leaving the as-declared version unrecoverable
- A transfer visible in the registration history with no export package anywhere in the archive
- Exception items accepted by the importing authority with the acceptance letter never digitized
What is at stake
The next export leans on the last one. If the archive cannot show what the previous importing authority required and received, the new transfer team rebuilds the demonstration from scratch, under transaction deadline, for requirements that may have been satisfied years ago. Undischarged special conditions from a historical import are uglier still, since they can surface as open compliance questions on an aircraft everyone assumed was settled.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map the transfers
Establish every registry change from the registration history and set the event dates to review against.
Reassemble each package
Gather certificate, requirements, declarations, and cited records for each event from across the archive.
Test the internal logic
Match requirements to responses, declarations to cited documents, and exceptions to acceptances.
Memo and re-link
Grade each event, restore package linkage in the index, and name recovery targets for gaps.
What the buyer receives
- A findings memo per export event grading the package complete, fragmentary, or absent
- A cross-reference restoring the linkage between certificates, requirements, and supporting records in the index
- A recovery target list naming the authority or party likely to hold each missing element
Who uses the output
- Records control leads restoring export packages as coherent units in the digital index
- Transition teams planning the next registry change on known rather than assumed history
- Diligence responders answering import-compliance questions with sourced documents
How the work fits into the transaction or program
Export evidence is a composite record: it draws on AD status, modification status, weight and balance, and configuration records as they stood at each transfer date. This review runs well after those individual source reviews because their findings explain why an export package cites documents the archive holds differently today, and its cross-reference work permanently improves how the archive answers transfer-history questions.
Jurisdiction-specific considerations
FAA exports operate under 14 CFR 21.321 and related subpart L provisions, while EASA-side exports draw on Regulation 748/2012, with ICAO Annex 8 supplying the airworthiness framework both sides recognize. Importing authorities attach their own special requirements per event, so each historical package is judged against the specific bilateral context of its transfer rather than a generic checklist.
Regulatory limits
The review reports on the state of historical export documentation in the archive. It does not obtain or reissue export certificates, does not determine whether any special requirement was in fact satisfied, does not interact with authorities on the operator's behalf, and issues no airworthiness finding for any past or future transfer.
What this review does not cover
- Preparation of export documentation for an upcoming transfer
- Legal interpretation of bilateral agreements or import conditions
- Verification of the underlying technical records beyond their role in the export packages
Specific to this review
- Cover letters are the connective tissue of export packages, and they are the document category scanning projects most often discard as administrative, which is how packages lose their internal map.
- Special requirements vary sharply by importing authority and era, so two exports of the same aircraft five years apart can have almost no structural overlap in their evidence.
- As-declared document versions matter: an AD status list revised after the export date cannot substantiate what was declared at the event, even though it looks more current.
- Undischarged export exceptions behave like dormant findings, invisible during stable operation and reactivated the moment the aircraft approaches another registry boundary.
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 aircraft is heading to a registry it has never been on. Does historical export review still help?
Yes, because the new authority's questions will reach back through the aircraft's compliance history regardless of destination. Knowing exactly what earlier exports established, and where their evidence sits, shortens the new demonstration and prevents the transfer team from rediscovering old exceptions under deadline.
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.