Airbus A320 family export-airworthiness records review

When this review is needed

• An A320-family tail is changing registers and the export certificate application is being built.
• The importing authority has issued special conditions and each one needs supporting evidence before acceptance.
• A prior register left status records in a format the receiving system will not accept without rework.
• The exporting authority requires an AD and modification position confirmed as of the export date.

The problem

An export package is only as strong as the records underneath it, and the importing authority sets conditions that the exporting file was never built to answer. On an A320-family aircraft that has served across several registers, the AD basis, modification standard, and status evidence were compiled under different rules, and translating them into what the receiving authority will accept is where the timeline slips. A condition raised late, with the aircraft ready to move, forces a scramble that the delivery schedule cannot absorb.

What gets reviewed

• The export certificate basis and the exporting authority's requirements for this aircraft
• Importing-authority special conditions listed with the evidence that answers each
• AD and mandatory-modification position confirmed as of the intended export date
• Modification and repair standard reconciled to data the receiving authority recognizes
• Status summaries and continued-airworthiness evidence formatted for the receiving system
• Outstanding items that would prevent the importing authority from accepting the aircraft

What gets validated

• Each importing-authority condition maps to a specific document that satisfies it
• The AD position is stated as of the export date and supported by accomplishment evidence
• Modifications carry an approval basis the receiving authority accepts, not only the exporting one
• Status figures in the export summary reconcile with the underlying logbooks and status lists
• Open items known to block acceptance are identified before the certificate is requested

Evidence normally required

• The draft or intended export certificate application
• The importing authority's special conditions or acceptance checklist
• Current AD, modification, and status reports for the aircraft
• Modification and repair approval data referenced in the package
• The continued-airworthiness records the receiving system will review

Common discrepancies

• An importing-authority condition with no evidence assembled to answer it yet
• A modification approved under the exporting basis but not recognized by the receiving authority
• An AD position stated without an export-date cutoff, so it cannot be relied on at acceptance
• Status figures in the export summary that do not match the source status lists

What is at stake

A package that does not answer the importing authority's conditions stalls at the receiving end, and a grounded aircraft waiting on a records point burns cost every day it cannot enter service. If a special condition is discovered only after the export certificate is requested, the fix competes with a departure date, and an evidence gap that would have been routine to close weeks earlier becomes a hold on the whole transfer.

How the work runs

What the buyer receives

• A package-readiness view stating what is ready and what still blocks the export
• A condition-by-condition evidence map for the importing authority's requirements
• A gap list of the items that would stall acceptance, each with the record that closes it

Who uses the output

• Asset managers holding the transfer to a departure date that depends on the package
• Records teams assembling the export application against the receiving authority's checklist
• Transaction stakeholders who need the export risk quantified before committing a date

How the work fits into the transaction or program

The export review sits between the decision to move the aircraft and the request for the export certificate. It takes the file the aircraft has accumulated on its current register and tests it against the receiving authority's conditions, so the gap list can be worked while there is still time, rather than discovered when the certificate is on the critical path.

Aircraft-specific considerations

A320-family aircraft frequently change registers over their service life, so an export package often has to reconcile a modification and AD history built under more than one authority. Cabin and connectivity modifications embodied for a prior operator are a common friction point, because the receiving authority may want the approval basis restated rather than carried across on trust.

Jurisdiction-specific considerations

The exporting and importing authorities apply different acceptance requirements, and an FAA-to-EASA move or the reverse can turn a routine status list into a reformatting and re-substantiation exercise. The review notes where the records built for the current register will need rework to satisfy the receiving system.

Regulatory limits

The review assesses the export documentation and the evidence behind it. It does not issue an export certificate of airworthiness, grant the importing authority's acceptance, or make an airworthiness determination on the aircraft.

What this review does not cover

• Issuing or applying for the export certificate on the authority's behalf
• Obtaining the importing authority's acceptance decision
• Physical survey or inspection of the aircraft for export

Specific to this review

• The export timeline breaks most often on a special condition surfaced late, because the fix then competes with a fixed departure date.
• A modification accepted by the exporting authority is not automatically recognized by the receiving one, so its approval basis often has to be restated.
• An AD position without an explicit export-date cutoff is not reliable at acceptance, since accomplishment can move between the statement and the crossing.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits