Skip to content

Registry change

Export airworthiness documentation review for a registry change

A registry-change export airworthiness review confirms that the export documentation and its supporting status summaries will satisfy both the exporting and importing authorities when the aircraft changes register across borders. It is run for the team preparing the transition, before the export certificate is sought, on the export application, the importing authority's special requirements, and the records that back them. The work checks that the status summaries match the underlying records and that each importing-authority special condition has an evidence trail. You receive an export evidence view keyed to the package, a gap list flagging unmet special conditions, and a request set for the supporting records still needed.

When this review is needed

  • An aircraft is being exported to a new register and an export certificate of airworthiness has to be supported.
  • The importing authority has issued special conditions the exported aircraft must meet.
  • Status summaries assembled for the export need to be reconciled to the records behind them.
  • A handover date is fixed and the team needs to know which special conditions still lack an evidence trail.

The problem

Export documentation is where every other records strand has to converge, and it fails on the special conditions the importing authority attaches rather than on the export certificate itself. Those conditions can call for a specific modification, a particular AD standard, or a records format the aircraft was never maintained to, and each one needs an evidence trail assembled from parts of the file that were prepared separately. The team pulling the export package together is the one that finds out, late, which conditions have no proof behind them.

What gets reviewed

  • The export application and the status summaries it presents
  • Each importing-authority special condition matched to the evidence that satisfies it
  • Status summaries reconciled to the AD, LLP, modification, and program records behind them
  • Records format checked against the importing authority's stated expectations
  • Outstanding special conditions isolated with the evidence each one still requires
  • Consistency confirmed between the export package and the underlying transition record set

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 importing-authority special condition maps to a specific record that satisfies it
  • Status summaries in the export package reconcile to the AD, LLP, and modification records
  • The records format meets the importing authority's stated expectations for the export
  • No status summary asserts a position the underlying records do not support
  • Every unmet special condition is identified with the evidence needed to close it

Evidence normally required

  • The export application and draft export certificate documentation
  • The importing authority's special conditions and acceptance requirements
  • AD, LLP, modification, and maintenance program status summaries
  • The supporting records behind each status summary
  • Any correspondence with the importing authority on the export

Common discrepancies

  • An importing-authority special condition with no evidence trail assembled behind it
  • A status summary that asserts a position the underlying records do not support
  • A records format that does not meet the importing authority's stated expectation
  • A special condition calling for a modification the aircraft was never confirmed to carry

What is at stake

An unmet importing-authority special condition holds the export certificate, and without it the aircraft cannot enter the new register regardless of how sound the rest of the file is. A status summary that does not reconcile to its records undermines the whole export application and can force the exporting authority to withhold the certificate until the discrepancy is resolved.

How the work runs

01

List the special conditions

Capture every importing-authority condition and requirement attached to the export.

02

Reconcile the summaries

Confirm each status summary in the export package agrees with the records behind it.

03

Trace each condition to evidence

Map every special condition to the record that satisfies it and flag those with no trail.

04

Close the export gaps

Request the supporting records needed and isolate any condition requiring engineering work.

What the buyer receives

  • An export evidence view mapping each status summary and special condition to its records
  • A gap list flagging the unmet special conditions and reconciliation shortfalls
  • A document request set for the supporting records the export package still needs

Who uses the output

  • Continuing-airworthiness leads assembling the export application and its supporting evidence
  • Asset managers tracking which special conditions could hold the export certificate
  • Records teams gathering the evidence trail behind each importing-authority condition

How the work fits into the transaction or program

The export review is where the registry-change package converges, drawing on the AD, LLP, modification, and program strands to answer the importing authority's conditions. Its gap list often points back into those strands, so it is run once they have matured enough to feed the export application without reopening.

Start with a single asset

Confirm the status list matches the underlying evidence.

Jurisdiction-specific considerations

Export airworthiness sits between the exporting authority that issues the certificate and the importing authority that sets the special conditions, and ICAO Annex 8 frames the recognition between them. FAA, EASA, and TCCA attach different conditions on import, so the review works to the specific importing authority rather than a generic export standard.

Regulatory limits

The review assembles and reconciles the export evidence against the importing authority's conditions. It does not issue an export certificate of airworthiness, grant import acceptance, meet a special condition on the operator's behalf, or determine that the aircraft is airworthy.

What this review does not cover

  • Issuing the export or import certificate of airworthiness
  • Performing the maintenance or modification a special condition requires
  • Any airworthiness determination for the exporting or importing authority

Specific to this review

  • Export packages fail on importing-authority special conditions far more often than on the export certificate itself, so those conditions are worked first.
  • The export summary is only as strong as the records under it; a summary that does not reconcile can force the exporting authority to withhold the certificate.
  • A special condition can require a modification or AD standard the aircraft never carried, turning a documentation task into an engineering one late in the transition.

Sources

Frequently asked questions

What most often holds up an export certificate?

The importing authority's special conditions, not the export certificate itself. A condition can require a specific modification, AD standard, or records format the aircraft was never maintained to, and each needs its own evidence trail. The review works those conditions first because they are where the transition usually stalls.

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.