Export airworthiness documentation review for lease transitions

When this review is needed

• The transition crosses registries and the importing authority has published special requirements nobody has yet mapped to the file.
• The export package was assembled from a template used on a previous aircraft and the team suspects state-specific items are missing.
• Deregistration is scheduled and any documentation gap discovered afterward will be much harder to close.
• Statements in the draft package rest on status lists the transition team knows have since been revised.

The problem

Export documentation gets assembled late in a transition, under time pressure, by people who are simultaneously fighting the return conditions. Importing authorities publish special requirements that differ state by state, so a package built from the last transaction's template quietly misses items this delivery needs. Because the package summarizes statuses maintained elsewhere in the file, it can also drift out of step with them, asserting an AD position or configuration the file's own current records contradict.

What gets reviewed

• The export evidence package measured against the importing authority's published requirements
• Special requirements and exceptions declared with the export certificate application
• Supporting records for each declared statement, from AD status through configuration
• Consistency between the export package and the rest of the transition file
• Deregistration and registration sequencing documents referenced in correspondence
• Open-item tracker entries tied to export or import conditions

What gets validated

• Each importing-authority special requirement is met with evidence or explicitly excepted with the counterparty's knowledge
• Statements in the package trace to current source records rather than superseded status lists
• The configuration described for export matches the equipment and modification records in the file
• AD compliance claims in the package align with the AD evidence elsewhere in the transition folders
• Certificate application data is internally consistent on serial number, registration, and dates

Evidence normally required

• The draft or issued export evidence package and certificate application data
• The importing authority's requirements or special-conditions correspondence
• Current AD, modification, and configuration status records from the transition file
• Deregistration correspondence and the transaction timeline
• The open-item tracker filtered to export-related entries

Common discrepancies

• A special requirement of the importing state answered by a bare statement with no evidence behind it
• An export package citing an AD status list two revisions older than the one in the transition folders
• Import correspondence promising documents that no folder in the file contains
• Configuration statements contradicted by the equipment records assembled for the same transition

What is at stake

A stalled export certificate delays deregistration and delivery, with rent, financing, and crew positioning costs accruing daily while the parties wait. A special requirement discovered after the aircraft is positioned abroad is far harder and costlier to close than one caught at the desk. Export files that shipped incomplete also resurface at the next trade, where an unexplained gap in the last delivery's paperwork becomes this transaction's diligence finding.

How the work runs

What the buyer receives

• An exception list mapped to each importing-authority requirement
• A cross-reference showing which transition-file records support each export statement
• A prioritized close-out sequence aligned with the deregistration timeline

Who uses the output

• Transition leads sequencing deregistration, export, and physical delivery
• Records staff assembling the final export package
• Counterparty technical representatives verifying the import side

How the work fits into the transaction or program

Because the export package summarizes the rest of the file, this review runs best after the AD, configuration, and repair checks have settled their own exceptions. Its distinctive job is catching contradictions between the summary and the file beneath it, the failure mode internal package checks miss. Findings feed the tracker and, through the close-out sequence, the delivery timeline itself.

Jurisdiction-specific considerations

FAA exports proceed under 14 CFR 21.321 and related provisions, with FAA Form 8130-4 as the export certificate of airworthiness, while EASA export certificates issue under Regulation (EU) No 748/2012. ICAO Annex 8 frames the transfer between states of registry. The decisive documents are usually the importing state's own special requirements, and the package is judged against those rather than against the exporting authority's baseline.

Regulatory limits

The review does not apply for or issue export certificates, does not represent either party before an authority, and makes no airworthiness determination. It verifies that documentary support exists for what the package claims, and reports where it does not.

What this review does not cover

• Filing certificate applications or corresponding with authorities on either side
• Physical export survey or conformity inspection
• Customs, tax, or trade-control aspects of the export

Specific to this review

• Export findings are timeline findings: the same missing document costs a day when found early and a week of delivery delay when found after the aircraft is positioned.
• Special requirements vary enough between importing states that reusing a package from the last transition of the same aircraft type is itself a recognized source of gaps.
• An export package is a summary of summaries, which is why it can pass its own internal consistency check while contradicting the transition file underneath it.
• Deregistration is hard to walk back, so the practical rule is to close evidence gaps while the aircraft is still on the exporting registry.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits