Boeing 767 export
Boeing 767 family export-airworthiness records review
This review checks that the export-airworthiness package for a specific Boeing 767 supports the certificate the exporting authority will issue and satisfies the importing authority's special conditions. It is run for a seller, lessor, or records team moving the aircraft across a border, before the export application goes in. It covers the export evidence package, status summaries, importing-authority special requirements, and the underlying records those documents rest on. You receive an exception list where the package falls short of the export basis, a source map behind each summary, and a plan to close the gaps before filing.
When this review is needed
- A 767 is being sold across a border and the export certificate application depends on a complete records package.
- The importing authority has issued special conditions that the aircraft's records must demonstrably meet.
- A prior export attempt stalled because the status summaries did not reconcile to the underlying records.
- The aircraft is transferring registries and the export basis has to be fixed before deregistration.
The problem
An export certificate rests on a stack of status summaries that must each trace back to real records, and the importing authority almost always adds special conditions on top. On a 767 with a long operating history, the AD summary, LLP status, and repair record that feed the export package were assembled at different times by different teams, and they rarely agree on first inspection. The exporting party discovers the mismatch when the authority queries the application, by which point the transfer clock is already running.
What gets reviewed
- The export evidence package assembled against the exporting authority's requirements
- Status summaries for time, cycles, AD, and LLP reconciled to source records
- Importing-authority special conditions mapped to the records that satisfy them
- Open items and deferrals reviewed for their effect on the export basis
- Configuration and modification records confirmed for the exporting statement
- Deregistration and registry-transfer prerequisites identified for sequencing
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 status summary in the export package traces to the logbooks and status records behind it
- Every importing-authority special condition maps to a record that demonstrably meets it
- AD position stated for export agrees with the accomplishment evidence for the serial
- LLP status in the package traces to release documents rather than a tracking summary alone
- Open deferrals and findings are disclosed and consistent with the exporting statement
Evidence normally required
- The exporting authority's export-airworthiness requirements for the aircraft class
- The importing authority's special conditions or acceptance criteria
- Current AD, LLP, and status summaries with their supporting records
- Airframe, engine, and APU logbooks or their digital equivalents
- The registry-transfer and deregistration prerequisites for the move
Common discrepancies
- Status summaries in the export package that do not reconcile to the underlying logbooks
- Importing-authority special conditions with no record identified that satisfies them
- AD positions stated for export that lack the accomplishment evidence for this serial
- Open deferrals omitted from the export statement that a query later surfaces
What is at stake
A weak export package stalls the certificate, and a stalled export holds title, payment, and delivery. Importing-authority special conditions that the records cannot satisfy can force late remediation, a re-inspection, or a renegotiated delivery condition. Every day the aircraft sits between registries carries cost, and the seller absorbs it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the export basis
Establish the exporting requirements and the importing authority's special conditions for this aircraft.
Reconcile the summaries
Trace every status summary in the package back to the logbooks and records behind it.
Map the special conditions
Match each importing-authority condition to the record that demonstrably satisfies it.
Sequence the closure
Deliver the exception list, source map, and a plan timed against deregistration and filing.
What the buyer receives
- An export-readiness exception list against both the exporting requirements and the importing conditions
- A source map tying each status summary and condition to its supporting record
- A closure plan sequencing the gaps against the deregistration and filing timeline
Who uses the output
- Sellers assembling an export application that will withstand authority query
- Records teams reconciling the status summaries the export package rests on
- Asset managers sequencing the export against the delivery and payment schedule
How the work fits into the transaction or program
The export package is the records deliverable that closes a cross-border trade. It draws on the AD, LLP, configuration, and deferral records already reviewed and repackages them against the exporting and importing requirements. Running this review before filing keeps the authority query from becoming the first place the mismatches are found, when the transfer clock leaves no room to fix them.
Aircraft-specific considerations
A 767 crossing borders often carries a mixed regulatory history, with periods under different registries and modifications approved in more than one jurisdiction. Freighter conversion complicates the export statement, because the conversion approval and its ICA have to travel with the aircraft and be recognized by the importing authority. The review scopes to this serial's registry history and conversion state rather than a family export checklist.
Jurisdiction-specific considerations
Export airworthiness sits at the boundary between the exporting and importing authorities, and each imposes its own basis. An FAA export certificate and an EASA acceptance turn on different documentation, and the importing authority's special conditions govern what the package must additionally show. The review states which record satisfies each authority so neither side has to reconstruct the basis.
Regulatory limits
This review prepares and checks the records that support an export application. It does not issue an export certificate of airworthiness, does not grant any importing-authority approval, and does not make an airworthiness determination on the aircraft.
What this review does not cover
- Issuance of the export certificate of airworthiness itself
- Any physical inspection or survey required for export
- Negotiation of importing-authority special conditions
Specific to this review
- The importing authority's special conditions, not the exporting requirements, are usually where an export package fails, because they are aircraft-specific and added late.
- A status summary that reconciles internally can still fail export if it does not trace to the primary logbooks the authority will ask for.
- Freighter-conversion approvals have to be recognized by the importing authority, and a conversion accepted at home is not automatically accepted abroad.
- Deregistration timing constrains the whole sequence, because the aircraft cannot sit between registries while a records gap is closed.
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
Why check the package before filing rather than responding to authority queries?
Once the application is filed the transfer clock is running, and a query that surfaces a records gap has to be answered under pressure. Reconciling the summaries and mapping the special conditions first means the gaps are found and closed while there is still time to close them cleanly.
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.