Export airworthiness documentation checked against the continuing-airworthiness source file

When this review is needed

• A sale or lease places the aircraft on a new register and the export CofA sits on the critical path to delivery.
• The importing authority has published special requirements the team has read but not yet mapped to actual documents.
• The export package was assembled by a transition team working from summaries while the CAMO holds the source records.
• A previous export attempt on a sister aircraft drew authority queries and nobody wants a repeat.

The problem

Export packages are compiled under deal pressure from whatever documents come to hand, and they read convincingly right up until an inspector compares them with the source records. The failure is rarely a missing headline document; it is a status list that predates a recent AD, a special requirement answered with a document type the importing state does not accept, or a compliance statement the CAMO file supports only partially. Each gap surfaces as an authority query, and each query is measured in days against a delivery deadline measured in hours.

What gets reviewed

• Every document in the export evidence package cross-checked against the CAMO source records for currency and consistency
• The importing state's special requirements mapped item by item to responsive evidence
• AD and modification status statements verified against the file as of the application date, including recently effective directives
• Configuration, weight and balance, and equipment list references confirmed to describe the aircraft being exported
• Deviations and exceptions intended for the application identified, worded, and supported
• The package's internal consistency checked so no two documents state conflicting figures

What gets validated

• Status statements in the package carry dates consistent with the latest CAMO reports rather than an earlier compilation snapshot
• Each importing-state special requirement has a named responsive document, an accepted equivalent, or a declared exception
• Compliance claims about ADs effective within the last cycle of revisions are backed by accomplishment or applicability evidence
• Serial numbers, registration marks, and model designations agree across every document in the package
• Nothing in the CAMO open-item log contradicts a clean statement made in the package

Evidence normally required

• The draft export evidence package as currently assembled
• The importing authority's special requirements and any bilateral agreement provisions in play
• The CAMO source file: status reports, review notes, program references, open-item log
• Current AD, modification, and LLP status reports
• Correspondence with either authority about this export, if any exists yet

Common discrepancies

• A special requirement answered with a domestic document form the importing state has explicitly declined to accept
• An AD that became effective after the status list was cut, leaving the package silent on it
• Open items in the CAMO log that contradict an unqualified compliance statement in the draft package
• Registration or serial-number inconsistencies introduced when documents were reused from a sister aircraft's export

What is at stake

A stalled export application holds the entire transaction hostage: delivery dates slip, lease rent commencement moves, ferry crews and slots are rebooked, and the commercial parties start assigning blame for costs. Worse, a package that clears with an unsupported statement inside it leaves the exporter exposed after the fact, since export certification attests to a condition the records must be able to demonstrate if the importing authority ever looks back.

How the work runs

What the buyer receives

• An exception list mapping every unsupported statement and unanswered requirement to its fix
• A requirement-to-evidence matrix for the importing state's conditions, ready to accompany the application
• A marked-up package index showing which documents to refresh, replace, or add before submission

Who uses the output

• The continuing-airworthiness manager signing off the technical content of the application
• Transition and delivery teams sequencing the remaining work against the delivery date
• The counterparty's technical representatives, who receive a cleaner package and fewer reasons to escalate

How the work fits into the transaction or program

Export documentation is where the whole source-file series converges under a deadline: logbook continuity, modification status, weight and balance, and deferral history all get restated in the package, and any weakness in those reviews resurfaces here as an authority query. Running this check last, after the underlying record types are settled, turns the export application from a gamble into an assembly task.

Jurisdiction-specific considerations

Exports from the US operate under 14 CFR 21.321 and subpart L, where the export CofA reflects conformity plus the importing state's filed special requirements. EASA-side exports work through Regulation 748/2012 and the airworthiness review framework of 1321/2014, with ICAO Annex 8 supplying the state-of-registry transfer backbone both systems build on. The practical variable is the importing authority: requirements differ sharply between states, change without much notice, and are enforced as written, so the review always works from the current published text rather than precedent from a previous export.

Regulatory limits

The review prepares evidence; it does not certify. No export certificate of airworthiness, conformity finding, or airworthiness determination is issued or implied, and the review does not represent the applicant before any authority. The application, its statements, and their consequences remain the exporter's own.

What this review does not cover

• Acting as applicant or agent in the export certification process
• Physical conformity inspection of the aircraft against its records
• Negotiation of special-requirement relief with the importing authority

Specific to this review

• Importing-state special requirements are the least cached knowledge in the process: teams reliably reuse last year's list, and authorities reliably revise it.
• The most damaging package errors are internal contradictions, two documents stating different figures, because they undermine the credibility of everything else submitted.
• An export package assembled from the CAMO file directly, rather than from transaction summaries, generates measurably fewer authority queries because dates and figures arrive already consistent.
• Authority queries during export review are sequential, one answered before the next arrives, which is why three small gaps can cost three weeks.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits