Export airworthiness documentation reviewed within the redelivery binder source set

When this review is needed

• The next lessee registers the aircraft in a different state and the export application is being drafted from the binder.
• The importing authority has issued its requirements letter and each line needs an identified document behind it.
• An earlier export attempt stalled on documentation questions and the file must be rebuilt before resubmission.
• The lease return and the registry change share a deadline, so export gaps must surface while the operator can still fix them.

The problem

Export files make affirmative statements: directives complied with for the importing state, configuration as declared, noise and emissions status as claimed. Someone has to be able to substantiate each one, yet the file is typically compiled from summaries under time pressure. Authorities respond with pointed follow-up questions, and any deviation from import requirements needs the importer's documented acceptance, which is slow to obtain and impossible to backdate.

What gets reviewed

• The export application and its declared basis checked against the binder's status summaries
• The importing authority's special requirements mapped line by line to documents in the source set
• AD status statements for the importing registry reconciled with the compliance evidence filed
• Configuration and modification declarations matched to the modification records and approvals present
• Exceptions or deviations checked for the importer's written acceptance
• Return-condition and acceptance notes reviewed for items that contradict the export declarations

What gets validated

• Every special requirement from the importing state resolves to a named document, page, or record in the binder
• AD statements reflect the importing registry's applicable directives rather than only the current registry's list
• Modifications declared on the export file carry their approval and embodiment evidence
• Deviations from import requirements are covered by the importing authority's documented concurrence
• Aircraft identity data, serial numbers, and hours and cycles on the export file agree with the binder's status records

Evidence normally required

• The draft or issued export application and any authority correspondence
• The importing authority's requirements letter or published import checklist
• AD, SB, and modification status summaries with their supporting records
• The redelivery binder index and acceptance notes
• Registry-change documents and deregistration planning dates

Common discrepancies

• A special requirement answered by a summary line with no underlying record filed in the binder
• AD compliance declared against the exporting registry's list while the importer's differing directives were never assessed
• A deviation everyone discussed by email that lacks the importer's formal acceptance
• Hours and cycles on the export application taken from an out-of-date status report

What is at stake

An export application that cannot be substantiated stalls at the authority while the aircraft sits registered to a departing operator and the delivery date slips. Deviations discovered late need acceptance letters that take weeks to obtain. In the worst cases the aircraft ferries under special flight authorization while the file catches up, at real cost to whichever party the delay lands on.

How the work runs

What the buyer receives

• A requirements matrix pairing each import condition with its evidence or its gap
• An exception list for the export file, ordered by how long each item takes to cure
• A note on statements in the application that should be revised before submission

Who uses the output

• The transition lead sequencing deregistration, export, and delivery dates
• The exporting operator's records team assembling the authority submission
• The incoming operator or its CAMO preparing the import side of the same move

How the work fits into the transaction or program

The export file sits at the junction of the redelivery and the registry change: it consumes the binder's status sections and produces what the authority acts on. Findings from this review feed the operator's document recovery on one side and the negotiation over who cures what before handback on the other.

Jurisdiction-specific considerations

An FAA export airworthiness approval and an EASA-context export run on different instruments and different expectations, with ICAO Annex 8 setting the baseline for transferring aircraft between states. Each importing authority then layers its own conditions on top. The same binder can satisfy one importer and fail another, so the review works from the actual requirements letter for this move, never from a generic checklist.

Regulatory limits

The review does not apply for, issue, or predict the issue of any export certificate, makes no airworthiness determination, and does not correspond with authorities unless separately agreed. It establishes what the file can prove, and leaves the application itself to the responsible parties.

What this review does not cover

• Preparation or submission of the export application itself
• Physical conformity inspection of the aircraft against its declared configuration
• Legal advice on deregistration, liens, or the registry change

Specific to this review

• Export findings have asymmetric cure times: a missing status report can be regenerated in a day, while an importer's deviation acceptance can outlast the remaining lease term.
• The importing state's AD list is a separate population from the current registry's, and directives unique to the importer are the most common late surprise in export files.
• An export certificate speaks as of its issue date, so status data assembled early in binder compilation usually needs a refresh pass just before submission.
• Requirements letters sometimes cite documents under the importer's local naming while the matching binder record exists under a different title; a mapping table prevents false gaps.
• Registry-change dates interlock: deregistration, export certification, and delivery must land in sequence, and one unsupported export statement can shift all three.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits