Skip to content

Export documentation

Repairing export airworthiness evidence gaps at the MRO

Export evidence gap remediation helps an MRO close the space between the export documentation it shipped and what the receiving authority actually requires. It is engaged by MRO quality or records teams after a receiving state, an importer, or an internal audit questions whether the export package answers a special import requirement or supports the certificate issued. The review reconstructs the package against the destination authority's published requirements, isolates which statements lack backing evidence, and drives recovery of the missing substantiation. The MRO receives a requirement-by-requirement gap analysis, the recovered evidence file, and a closure record for the customer and authority conversation.

When this review is needed

  • A receiving authority or importing customer has asked for substantiation the export package does not contain.
  • An export certificate was issued against special import requirements nobody verified line by line.
  • An internal or customer audit sampled export files and found statements without supporting records.
  • A repeat export program to the same destination keeps generating the same document requests.

The problem

Export documentation is signed under schedule pressure at shipment, while the requirements it certifies against belong to another authority and change without ceremony. A statement that the article meets the importing state's special requirements is easy to make and hard to reconstruct six months later when the question arrives, especially when the supporting evidence is spread across work orders, subcontractor releases, and a customer contract file.

What gets reviewed

  • Reconstruction of the export package against the destination authority's import requirements in force at issue
  • Verification that each certifying statement is backed by records in the work-order file
  • Subcontracted work checked for releases that carry through to the export certificate
  • New-parts and used-parts documentation streams separated and tested against their different requirements
  • Cross-check of the export file against 14 CFR 21 subpart L or the EU export basis, as applicable
  • A recovery path for each unsupported statement, with owners and deadlines

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

  • Every special import requirement cited by the destination state is answered by a specific document in the package
  • Certifying statements on the export document match the scope of work actually released
  • Subcontractor and supplier releases exist for the portions of work the MRO did not perform itself
  • Serial numbers, part numbers, and modification status agree across the certificate, release, and work order
  • The export file shows which requirement revision was used, so later questions land on the right baseline

Evidence normally required

  • The export certificates or release documents under question, with their work-order files
  • The destination authority's special import requirements or bilateral agreement provisions relied on
  • Subcontractor releases and purchase records for supplied parts
  • Customer contract or purchase-order clauses that set documentation requirements
  • Prior correspondence with the receiving authority or importer

Common discrepancies

  • Special import requirements certified as met on the strength of a prior shipment rather than the current file
  • Subcontracted plating or NDT work released internally without the subcontractor certificate reaching the export file
  • Used articles exported with new-article documentation logic, leaving the service history unsupported
  • Statement wording copied between export documents until it no longer matches the work performed

What is at stake

An unanswered export question rarely stays administrative. The importing operator may be unable to fit the article, the customer relationship absorbs the delay, and the exporting MRO's certificates start receiving heightened scrutiny on later shipments. In the worst case a certificate has to be qualified or reissued, which turns a records gap into a formal quality escape.

Move from findings to resolution

Sequence the fixes and the documentation that closes each finding.

How the work runs

01

Fix the requirement baseline

Identify the importing state, the agreement in force, and the exact special-requirements version the certificate was issued against.

02

Map statements to evidence

Tie every certifying statement on the export document to a record in the work-order file, and log the ones that have none.

03

Recover and substantiate

Chase subcontractor releases, supplier documents, and internal records that close each unsupported statement.

04

Close and harden

Assemble the closure file for the customer and authority, and correct the export checklist that let the gap through.

What the buyer receives

  • A requirement-by-requirement gap analysis for each questioned export file
  • The recovered evidence set, indexed to the certifying statements it supports
  • A closure record suitable for the customer and, where needed, the authority conversation
  • Recommendations for the export checklist so the same gap does not recur

Who uses the output

  • Quality leadership answering the receiving authority or customer challenge
  • Records control rebuilding export files that must survive future sampling
  • Program managers protecting delivery schedules on active export contracts

How the work fits into the transaction or program

The remediation runs alongside the MRO's own quality investigation and feeds it evidence rather than opinions. Its output plugs into the customer's acceptance process at the importing end and into the MRO's corrective-action system at home, and the requirement mapping it produces is reusable for every later shipment to the same destination.

Jurisdiction-specific considerations

Exports from the United States rest on 14 CFR 21 subpart L and FAA guidance on authorized release documents, while exports from EU-based approvals follow Regulation (EU) 748/2012 and the associated release rules. ICAO Annex 8 frames what importing states may ask for, but each destination publishes its own special requirements, and bilateral agreements change what evidence transfers automatically, so the review always fixes the exact importing state and agreement version first.

Regulatory limits

The work assesses documentation against published requirements and recovers evidence. It does not issue, amend, or validate export certificates, does not speak for any authority on acceptance, and does not make findings about the physical condition of exported articles.

What this review does not cover

  • Re-inspection or re-certification of shipped articles
  • Negotiating bilateral acceptance positions with either authority
  • Acting as the MRO's formal quality organization in enforcement matters

Specific to this review

  • Special import requirements are versioned documents; certifying against last year's list is a common and invisible failure until a shipment is challenged.
  • The export certificate is only as strong as the weakest subcontractor release beneath it, and those releases are the items most often missing from the file.
  • Used-article exports fail differently from new-article exports: the gap is usually service history and prior release continuity rather than build documentation.
  • Recurring exports to one destination justify a standing requirement map, because the marginal cost of verifying each shipment drops once the first file is reconstructed properly.

Sources

Frequently asked questions

The receiving authority accepted our previous shipments, so does that settle the question?

Prior acceptance shows the earlier packages were not challenged, and nothing more. Each export certificate stands on its own file, and authorities sample rather than review everything, so an unsupported statement can pass many times before it is questioned. The remediation treats the challenged file as the test case and then checks whether the same gap exists across the export program.

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.