Export airworthiness documentation checked against maintenance-control sources

When this review is needed

• An export certificate of airworthiness application is in preparation and the supporting file has to hold together.
• The importing authority has published special requirements nobody has yet mapped to specific records.
• Status lists in the draft package were generated weeks ago and the aircraft has flown since.
• A previous export file for a different destination country is being reused as a template.

The problem

An export certificate attests conformity at a point in time, but the evidence package behind it is assembled over weeks while the aircraft keeps flying. Status lists age, deviations get disclosed on the application without their substantiation making it into the file, and the importing authority's special requirements sit in a notice nobody has translated into a document checklist. Each of these gaps is invisible until the authority, or the buyer's representative, asks for the page.

What gets reviewed

• The importing authority's special requirements mapped one by one to documents in the package
• AD, LLP, and modification status lists checked for consistency with the system data at the certificate date
• Disclosed deviations and exceptions matched to their substantiation in the file
• Application data cross-checked against aircraft records for serial numbers, marks, and configuration
• The package index verified so every cited record is actually present and current

What gets validated

• Every special requirement has a named document in the package or a recorded, justified exception
• Each status list can be re-derived from the system data as of the certificate date, without unexplained movement
• Deviations shown on the application appear identically in the package with support attached
• Aircraft identity data agrees across the application, the records, and the registry
• No package document is superseded by later system activity the file fails to mention

Evidence normally required

• The draft export evidence package and its index
• The importing authority's requirements or notice applicable to the destination
• Current AD, LLP, and modification status outputs from the maintenance-control system
• The export certificate application as drafted
• Utilization data covering the period between list generation and the certificate date

Common discrepancies

• A status list generated weeks before the certificate date, with flights and maintenance in between
• A special requirement acknowledged in correspondence but supported by nothing in the file
• A deviation disclosed on the application that the package copy omits entirely
• Package citations pointing to records the accompanying data set does not contain

What is at stake

Deficiencies discovered at application review delay the certificate, and a delayed export certificate strands the aircraft in the outgoing registry at exactly the point when insurance, crewing, and delivery obligations converge. Worse, a package rejected for a stale status list invites deeper scrutiny of everything else in the file.

How the work runs

What the buyer receives

• A requirement-by-requirement gap register against the importing authority's list
• A refresh plan for status lists so they can be re-dated to the certificate date
• An exception summary for deviations and their substantiation status

Who uses the output

• Fleet management sequencing the application so the certificate lands on the delivery date
• Maintenance control regenerating status outputs while the system remains authoritative
• The counterparty's delivery team, which receives a package that has already been tested

How the work fits into the transaction or program

This review is usually the last of the maintenance-control export checks before a cross-border transfer, because it consumes the status outputs the earlier reviews have already cleaned. Gap-register items route back to the AD, modification, and LLP work streams, and the refreshed package feeds directly into the certificate application.

Jurisdiction-specific considerations

FAA export airworthiness approvals are issued under 14 CFR 21.321 and the sections that follow, while EASA handles export within the Regulation (EU) 748/2012 framework, and ICAO Annex 8 supplies the shared conformity backdrop. Importing authorities attach destination-specific special requirements to their acceptance, and those requirements, rather than the exporting rule, are where most packages fall short.

Regulatory limits

The review prepares evidence; it does not apply for or issue any certificate, does not represent the operator before an exporting or importing authority, and does not attest that the aircraft conforms or is airworthy. Certification decisions remain entirely with the authorities involved.

What this review does not cover

• Filing the export certificate application or acting as applicant
• Representation before the importing authority or negotiation of its requirements
• Customs, export-control, and freight matters attached to the physical movement

Specific to this review

• An export certificate speaks as of a single date, so every supporting status must be re-datable to that date; a list that was accurate last month supports nothing.
• Special requirements differ by destination, and reusing a prior export file as a template imports the previous country's checklist along with its blind spots.
• The export certificate does not itself transfer airworthiness to the new registry, a distinction both sides of a delivery tend to rediscover late in the process.
• Authorities sample the freshest-looking documents first, because recency is where assembled packages most often fail.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits