Incomplete export documentation for aircraft transfer

When this review is needed

• An aircraft is being sold or leased across a border and the package has to satisfy the importing authority before the move can complete.
• A registry change is planned and the special conditions the receiving authority has stated are not all addressed in the records.
• An export airworthiness approval is being prepared and the statement of conformity references records that cannot all be produced.
• A previous export was returned for additional items and the package has to be rebuilt against a clear list of what the receiving side requires.

The problem

Moving an aircraft across borders rests on a package that satisfies two authorities at once: the exporting side that approves the aircraft for export and the importing side that states its own special conditions. The package is assembled under deal pressure from records that were never organized around an export, and the items the importing authority requires are easy to assume present and hard to confirm until the receiving side asks for them. A package that looks complete on the exporting side can still fall short of what the importing authority will accept.

What gets reviewed

• The export airworthiness approval and the statement of conformity it carries
• Exceptions and exclusions noted on the export statement and whether each is acceptable to the importing side
• The special conditions the importing authority has stated for the type and configuration
• The records the export statement relies on, present and consistent with the statement
• The configuration and modification status as it has to be presented to the receiving authority
• Outstanding items the importing authority will require before the aircraft is placed on its register

What gets validated

• The export statement is supported by records that are present and consistent with it
• Each exception on the export statement is one the importing authority will accept
• Every stated special condition of the importing authority is addressed in the package
• Configuration and modification status is presented in the form the receiving authority requires
• No item the importing authority requires is assumed present without being confirmed

Evidence normally required

• Export airworthiness approval and statement of conformity
• The importing authority's stated special conditions for the type
• Configuration and modification status records
• The maintenance and compliance records the export statement relies on
• Any prior correspondence returning the package for additional items

Common discrepancies

• A special condition stated by the importing authority that the package does not address
• An exception on the export statement the receiving side will not accept as written
• A record the export statement relies on that cannot be produced from the file
• A configuration status presented in a form the receiving authority does not work from
• An item assumed present in the package that turns out to be missing when the receiving side asks

What is at stake

A package missing an item the importing authority requires stalls the transfer, and the delay lands on whichever party owns the timeline, often with the aircraft already positioned and idle. Each round trip to the receiving authority costs time and standing charges, and an export returned for missing items is far more expensive to fix late than a gap found before the package is submitted.

How the work runs

What the buyer receives

• A completeness register mapping the package against the importing authority's requirements
• A list of special conditions and exceptions not yet satisfied, with what each needs
• An assembly path closing each gap so the package can be submitted with confidence

Who uses the output

• Records teams assembling the export package before submission
• Asset and transaction teams holding the cross-border timeline
• Continuing-airworthiness staff bridging the aircraft onto the new register

How the work fits into the transaction or program

The review reads the package against the receiving side's requirements rather than the exporting side's alone, so gaps surface before submission instead of on return. It sits at the end of a transfer, taking the output of earlier records work and confirming the assembled package will be worked from by the importing authority.

Jurisdiction-specific considerations

An export airworthiness approval issued on the exporting side does not bind the importing authority, which sets its own special conditions and decides what it will accept. A component or configuration acceptable on one register may need a bridging assessment before the receiving authority will place the aircraft on its own, so the package is built around what the importing side requires.

Regulatory limits

The review confirms whether the export package is complete and consistent against the importing authority's stated requirements. It does not issue an export airworthiness approval, accept the aircraft onto a register, or make an airworthiness determination on behalf of either authority.

What this review does not cover

• Issuance of an export airworthiness approval or any regulatory document
• Acceptance of the aircraft onto the receiving register
• Any airworthiness determination or regulatory acceptance

Specific to this review

• An export package has to satisfy two authorities at once, and an approval acceptable to the exporting side does not bind the importing authority, which sets its own conditions.
• Items the importing authority requires are the ones most often assumed present, because the package is assembled from records that were never organized around an export.
• An exception noted on the export statement is only useful if the receiving side will accept it; an exception acceptable on one register can stall the transfer on another.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits