Skip to content

Export airworthiness

Pilatus PC-12 export airworthiness records review

This review confirms that a Pilatus PC-12 records package supports an export airworthiness application and meets the importing authority's special conditions. It suits an owner, lessor, or manager moving the aircraft to a new register who needs the export documentation to hold before the certificate is issued. The work assembles the status summaries, AD position, and supporting records the export basis requires for the single-engine turboprop. You receive an exception list of gaps against the export requirements, a source map from each summary to its evidence, and a closure plan for the tail.

When this review is needed

  • A PC-12 is being exported to a new register and the records must support the export certificate.
  • The importing authority has issued special conditions that the current records may not yet meet.
  • A sale is contingent on the aircraft exporting cleanly and the buyer wants the package pre-checked.
  • Prior owners left status summaries that need reconciling before the export application goes in.

The problem

An export airworthiness certificate rests on a records package the exporting authority can stand behind and the importing authority will accept, and the two rarely want exactly the same thing. The importing authority often attaches special conditions: additional ADs, particular modification standards, or evidence formats the current file was never built to. A PC-12 assembled for owner-managed operation can hold everything the aircraft needs to fly yet still fall short of what the export application and the receiving register demand.

What gets reviewed

  • Records reconciled to the export airworthiness application requirements
  • AD position confirmed against the importing authority's applicable list and any special conditions
  • Status summaries for time, cycles, and life-limited parts checked to their source records
  • Modification and repair basis reviewed for acceptance on the receiving register
  • Open deferrals and findings dispositioned before the export application
  • Evidence formatted to what the importing authority will accept

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 package addresses every element the export airworthiness application calls for
  • AD status matches the importing authority's applicable list, including any special conditions imposed
  • Time, cycle, and life-limited status summaries trace to source records rather than a rollup alone
  • Modification and repair bases are checked for acceptance on the receiving register
  • No open deferral or finding remains that the export basis does not account for

Evidence normally required

  • The export application requirements and the importing authority's special conditions
  • Current AD and SB status reports with accomplishment evidence
  • Time, cycle, and life-limited part status summaries
  • Modification, STC, and repair records with their approval bases
  • The open-item and deferred-maintenance position at the time of export

Common discrepancies

  • A special condition AD the current status list does not yet address
  • A status summary that cannot be traced to its source records
  • A modification whose basis is accepted on the current register but not the receiving one
  • An open deferral left unresolved that the export basis does not cover

What is at stake

An export application that goes in against an incomplete package stalls, and a stalled export holds the aircraft, the sale, and the money behind it. Special conditions discovered late force AD accomplishment or modification work under deadline, and a status summary that cannot be substantiated can put the whole export basis in question just as the deal is meant to close.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Read the requirements

Assemble the export application requirements and the importing authority's special conditions for the target register.

02

Reconcile status to source

Trace AD, time, cycle, and life-limited summaries back to the records that support them.

03

Test the acceptance path

Check modifications, repairs, and open items for acceptance on the receiving register.

04

Close before applying

List gaps against the requirements and sequence the actions needed before the application goes in.

What the buyer receives

  • An exception list of gaps against the export and importing-authority requirements
  • A source map from each status summary to the evidence behind it
  • A closure plan sequencing the records and actions needed before the application

Who uses the output

  • Owners and managers driving the export to a clean certificate
  • Asset teams protecting a sale contingent on the aircraft exporting
  • Records teams assembling and formatting the package for the receiving register

How the work fits into the transaction or program

The export review draws on the AD, modification, and deferred-maintenance positions already settled elsewhere in the file and assembles them into the package the export application needs. It runs before the application goes in so special conditions are met on the exporter's schedule rather than surfacing as a rejection.

Aircraft-specific considerations

The PC-12 has a wide international installed base, so its exports run across many importing authorities, each with its own special conditions and preferred evidence. Because owner-managed files vary in how status was kept, the review scopes to the specific receiving register's requirements for this serial number rather than a generic export checklist.

Jurisdiction-specific considerations

Moving a PC-12 between FAA and EASA registers, or onward to a third authority, means the export basis has to satisfy both the exporting authority's certificate and the importing authority's acceptance, and the review notes where a modification or AD position accepted on one register needs a fresh basis on the other.

Regulatory limits

The review assembles and reconciles the records the export basis needs. It does not issue an export airworthiness certificate, grant the importing authority's acceptance, or make an airworthiness determination on the aircraft.

What this review does not cover

Specific to this review

  • Importing-authority special conditions, not the exporting authority's baseline, are the usual reason a PC-12 export stalls.
  • A status summary that cannot be sourced is a frequent late finding because export packages lean on rollups the file never fully supported.
  • The PC-12's broad international footprint means the acceptance path differs by receiving register, so no two export packages are built the same way.

Sources

Frequently asked questions

Why check the importing authority's conditions before the exporting authority signs off?

The exporting authority certifies against a baseline, but the importing authority's special conditions are what the aircraft ultimately has to satisfy to enter the new register. Meeting them before the application goes in avoids a rejection that would hold the aircraft and the sale.

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.