Cross-border engine transfer
Export-airworthiness review for a cross-border engine transfer
This review confirms that the export evidence for an engine answers the importing authority's requirements before the engine transfers across a border. It is run by or for the transferring party ahead of shipment. It covers the export application, the importing authority's special requirements, the status summaries the export rests on, and the supporting records behind each line. You receive an evidence map from each requirement to its document, a list of requirements the package does not yet answer, and a request set for the records that must be recovered before the export tag is issued.
When this review is needed
- An engine requires an export tag and the evidence set has to answer the importing authority.
- The importing authority has issued special requirements the export package must satisfy line by line.
- Status summaries in the export application need to tie back to the engine's records.
- A prior engine export stalled on a documentation query and the party wants a clean file.
The problem
An engine export tag rests on status summaries that read as settled to the operator that ran the engine. The importing authority does not accept the summary; it accepts the record beneath it. When the special requirements ask for the evidence behind a compliance line, the exporter finds out whether that evidence was filed with the engine or only ever summarized. A summary with no record behind it is exactly the kind of line an export query lands on.
What gets reviewed
- The export application checked against the importing authority's requirements
- Special requirements mapped to the specific document that answers each
- Status summaries in the application tied back to the engine's source records
- Supporting records for compliance claims present and legible in the package
- The evidence set read as a whole for internal contradiction before the tag is sought
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
- Each special requirement maps to a document that answers it on its face
- Every status summary in the application traces to the engine record it was built from
- Compliance claims carry the accomplishment evidence behind them
- No two documents in the package assert contradictory status for the same item
- Superseded summaries are removed so the application cites only the current position
Evidence normally required
- The draft export application for the engine
- The importing authority's special requirements
- Status summaries cited in the application
- The engine records supporting each summarized position
Common discrepancies
- A special requirement with no document in the package that answers it
- A status summary that no longer matches the engine record behind it
- A compliance claim asserted without the accomplishment evidence attached
- Two documents in the package stating a different position for the same item
What is at stake
A special requirement the exporter cannot answer holds the export tag, and without the tag the engine cannot legally enter the receiving register. An engine sitting for a missing record accrues storage and positioning cost, and a late-discovered gap can force a status to be reworked under the receiving authority's rules rather than closed on the exporter's terms.
How the work runs
Read the receiving requirements
Extract the importing authority's special requirements and treat them as the checklist to answer.
Map requirements to records
Tie each requirement to the specific engine record that satisfies it, not a summary.
Trace the summaries
Confirm every cited status summary still matches its source record.
Close the answer set
List unanswered requirements and the records needed before the export tag is sought.
What the buyer receives
- An evidence map from each importing-authority requirement to its supporting document
- A list of requirements the package does not yet answer
- A document request set for the records to recover before the export tag is sought
Who uses the output
- Records teams confirming each special requirement is answered before the tag is sought
- Continuing-airworthiness leads responding to importing-authority documentation queries
- Asset managers tracking the engine toward a firm entry date on the new register
How the work fits into the transaction or program
This review runs before the export tag is sought, so a gap surfaces while the exporter can still recover records on its own timeline. The evidence map becomes the response file if the importing authority queries a line, and the gap list drives the recovery that has to finish before the tag is issued.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
The importing authority sets its own special requirements for an engine, and what satisfies an FAA export tag is not automatically what an EASA or TCCA receiving side accepts. The review reads the export evidence against the receiving requirements specifically, not the exporting authority's baseline alone.
Regulatory limits
This review assembles and checks the export evidence for the engine. It does not issue the export tag, grant the importing authority's acceptance, or make an airworthiness determination. The tag and the acceptance rest with the exporting and importing authorities.
What this review does not cover
- Issuing or applying for the export tag on the exporter's behalf
- Securing the importing authority's acceptance decision
- Any airworthiness determination on the engine
Specific to this review
- The importing authority accepts the engine record, not the summary, so a compliance line with no document beneath it is the most common export hold.
- Special requirements are set by the receiving authority, so an evidence set built for one importing side rarely carries to another.
- An engine held for a missing export record accrues storage and positioning cost, which makes a late documentation gap costly out of proportion to its size.
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.
Frequently asked questions
The engine's status summaries are current. Why check the records beneath them?
A summary can be current while the record it was built from is missing from the engine file. The importing authority reads the record, so the review confirms the evidence is in the package before the export tag is sought, rather than only in the system the summary came from.
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.