Transaction diligence
Export airworthiness documentation checked against the data room
This review tests whether the export airworthiness documentation offered in a seller's data room stands up when traced to its source files. A records specialist working for the buy side reads the export certificate, its listed exceptions, and the importing authority's special requirements against what the seller has uploaded and answered in Q&A. It runs during pre-purchase or pre-lease diligence, while the room is still open and the seller can still be asked for documents. The output is an exception list the transaction lead can drop into the diligence schedule, with each gap tied to the folder or Q&A response where the evidence should have been.
When this review is needed
- An aircraft is changing state of registry as part of the sale and the export file will face scrutiny at the importing authority.
- The seller's index shows an export certificate of airworthiness but its exceptions block references documents nowhere in the room.
- Q&A answers assert that special import requirements were met without pointing to the evidence behind the assertion.
- The diligence clock is short and the buy side must decide which export gaps to escalate before the room closes.
The problem
An export certificate looks decisive in a folder listing, yet the certificate is only the top sheet of a file. Behind it sit the importing state's special requirements, the compliance statements that answer them, and the supporting maintenance evidence. Data rooms often carry the certificate alone, and Q&A responses tend to restate its existence rather than produce what it rests on. The diligence team is left asserting cross-registry cleanliness on a single page.
What gets reviewed
- Export certificate of airworthiness, or the equivalent export statement, located and read in full
- Exceptions and deviations listed on the certificate matched to a disposition somewhere in the room
- Special requirements of the importing authority identified and traced to a compliance statement
- Supporting maintenance and status evidence cited by the export file confirmed as uploaded
- Seller Q&A responses about export condition checked against the documents they cite
- Data-room index entries for the export folder compared with the files actually present
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- The certificate identifies the correct serial number, importing state, and date consistent with the transaction
- Every exception noted on the export document has a stated disposition, waiver, or acceptance in the file
- Import-state special requirements called out in the export basis have matching compliance evidence
- Documents referenced by the export file open, are legible, and belong to this aircraft
- Nothing in the Q&A record contradicts the condition the export documentation asserts
Evidence normally required
- Access to the data room, including the export or transfer folder and its index export
- The export certificate of airworthiness or export statement as uploaded by the seller
- The Q&A log covering export condition and registry transfer questions
- The importing authority's published special requirements, where a target registry is known
- The draft diligence exception schedule, so findings land in the buyer's existing format
Common discrepancies
- A certificate exceptions block naming items whose disposition never made it into the room
- Special requirements answered by assertion in Q&A with no compliance statement uploaded
- An export file assembled for a previous transaction and never refreshed for this one
- Supporting status reports dated months before the certificate, leaving the interval unevidenced
What is at stake
If the gaps surface after signing, the buyer inherits an import that stalls at the new authority while documents are chased from a seller who has lost the incentive to answer. Registration timelines slip, delivery conditions in the purchase agreement become contested, and any exception the certificate listed becomes the buyer's problem to close at the buyer's cost.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Locate the export file
Find the certificate, its attachments, and every index row and Q&A answer that points at export condition.
Read the certificate against its basis
List the exceptions, the importing state's special requirements, and the evidence each one demands.
Trace to source
Open each cited document in the room and confirm it exists, is legible, and matches this serial number.
Write the exceptions
Hand the transaction lead a gap list with folder paths, so requests to the seller are specific.
What the buyer receives
- An exception list for the export file, each entry tied to a folder path or Q&A reference
- A short memo stating what the export documentation supports and where it is silent
- Suggested seller requests worded so the missing documents can be produced before the room closes
Who uses the output
- Transaction leads deciding which export gaps go into the purchase agreement as conditions
- Technical diligence managers consolidating records findings across the whole asset
- Asset managers planning the registry transfer once the deal closes
How the work fits into the transaction or program
Export documentation is one thread of a wider data-room source review. This check runs alongside the airworthiness review, binder, and status-list reviews on the same room, and its exceptions merge into the single schedule the transaction team negotiates from. Findings that survive negotiation carry forward into the post-closing records baseline.
Jurisdiction-specific considerations
Export paths differ by registry pair. An FAA export airworthiness approval under 14 CFR 21.321 works from the importing state's special requirements, while an EASA-regulated transfer leans on Regulation 748/2012 and the receiving authority's acceptance practice. The review reads the file against the pair actually in play, because evidence that satisfies one direction of transfer can be silent on the other.
Regulatory limits
The review reports what the uploaded evidence does and does not support. It does not issue or validate an export certificate, does not determine airworthiness, and does not commit any authority to accept the aircraft onto a register. Those remain matters for the certificate holder and the authorities involved.
What this review does not cover
- Physical inspection of the aircraft or verification of its current condition
- Filing or managing the registry transfer itself
- Legal interpretation of the purchase agreement's delivery conditions
Specific to this review
- An export certificate of airworthiness attests to condition on its issue date only; a long gap between that date and closing leaves an interval the data room must cover with other evidence.
- Exceptions typed on the certificate are easy to skim past in a folder viewer, yet each one is a formal statement that something did not meet the import standard.
- Import-state special requirements are published per registry and change over time, so a file built for one destination register can be incomplete for another.
- Sellers often upload the certificate under a legal folder rather than the technical records tree, which means index searches by document type miss it.
Sources
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. EASA design and production certification, STCs, ETSO authorizations, and EASA Form 1 release.
International Civil Aviation Organization. International standards for the airworthiness of aircraft and the framework states use for type and continuing airworthiness.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The data room contains an export certificate. Is that not enough on its own?
The certificate confirms an authority's finding on a specific date. Diligence still has to confirm the exceptions it lists were dispositioned, the importing state's requirements were answered, and the period since issue is covered by other records. A certificate with unresolved exceptions can cost more to close out than the review that would have caught them.
What if the target registry is not yet decided?
The review covers the elements every transfer needs, certificate integrity, exception dispositions, and interval coverage, and marks the import-specific checks to rerun once the registry pair is fixed. Doing the general pass early keeps the room open for follow-up questions.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.