Export package prep
Maintenance-program records review for an export package
This review checks that an aircraft's maintenance-program records are ready to go into an export package before the assembler locks it. It is run by or for the exporting party once export is decided, ahead of submission to the importing authority. It looks at approved program revisions, task escalations, bridging analyses, and the source references each interval rests on, then compares them against what the receiving system will ask for. You get an evidence map tying each program element to its supporting document, a gap list, and a document request set aimed at the elements most likely to draw a question.
When this review is needed
- An export certificate application is being prepared and the program records go into the package.
- The importing authority has published special conditions on maintenance-program acceptance for this type.
- Program intervals were escalated under the current operator and the escalation basis has to travel with the aircraft.
- A bridging analysis exists but no one has confirmed the source data behind it is in the file.
The problem
A maintenance program reads as settled to the operator that built it, because every escalation and bridge was approved in its own context. Pull that program into an export package and the receiving side sees a chain of revisions whose reasoning lives outside the records. An escalated task with no analysis attached, or a bridge that points to a document the operator never included, becomes a query the assembler cannot answer without going back to a source that has moved on.
What gets reviewed
- Approved program revisions with the revision that governs at export identified
- Task escalations paired with the analysis and approval that authorized each one
- Bridging analysis between the outgoing program and the receiving framework
- Source-document references behind sampling, reliability, and interval decisions
- Program status as of the export date reconciled to the current tracking output
- Elements the importing authority is known to question flagged for pre-work
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 escalated interval traces to the specific analysis and approval that granted it
- The governing program revision at export is the one the status figures were run against
- Bridging analysis references documents that are actually present in the package
- Reliability or sampling decisions carry the source data they were derived from
- Program status at the export date agrees with the tracking system it was exported from
Evidence normally required
- The approved maintenance program and its revision history
- Escalation analyses and the approvals authorizing each escalation
- Any bridging study prepared for the receiving framework
- Current program status output from the tracking system
- The importing authority's stated maintenance-program conditions, where issued
Common discrepancies
- An escalated task whose supporting analysis was never filed with the program
- A bridging study that cites source documents missing from the package
- Program status run against a superseded revision of the program
- A sampling program with no retained basis for the sample rate in use
What is at stake
A program element the importing authority cannot trace holds the whole export application while the exporter reconstructs it. If the source analysis is genuinely gone, the receiving side may reset the interval to a conservative default, which changes the aircraft's near-term maintenance cost and can reprice the deal after it was struck.
How the work runs
Fix the governing revision
Identify which program revision applies at export and confirm status was run against it.
Trace escalations and bridges
Pair each escalated interval and bridging claim with the analysis and approval behind it.
Confirm the sources are present
Check that referenced documents are physically in the package rather than merely cited.
Map gaps to requests
List the elements a receiving authority will question and the documents needed to answer.
What the buyer receives
- A program evidence map linking each interval and revision to its supporting document
- A gap list of program elements the receiving side will likely challenge
- A document request set targeting the escalation and bridging sources to recover
Who uses the output
- Export package assemblers deciding which program elements need pre-work
- Continuing-airworthiness leads answering importing-authority program queries
- Asset managers weighing whether a reset interval affects the deal economics
How the work fits into the transaction or program
This review runs before the export package is closed, so program weaknesses are found while the exporter still holds the source. Its gap list feeds the document recovery that has to finish before submission, and the evidence map becomes the answer file when the importing authority raises a program question.
Start with a single asset
Confirm the status list matches the underlying evidence.
Jurisdiction-specific considerations
FAA, EASA, and TCCA each frame maintenance-program acceptance differently, and an importing authority may ask a program approved under one to be rejustified in its own terms. The review notes where an escalation or sampling basis accepted by the exporting authority will not carry across without additional support.
Regulatory limits
This review reads program records against what a receiving authority is likely to ask. It does not approve the maintenance program, grant or transfer any acceptance, or make an airworthiness determination. Approval of the program on the receiving side rests with the importing authority and the accepting operator.
What this review does not cover
- Authoring or revising the maintenance program itself
- Securing the importing authority's acceptance of the program
- Any airworthiness determination tied to the program status
Specific to this review
- Escalated intervals are the first thing a receiving authority tests, because the analysis behind them is where operator-specific reasoning hides.
- A bridging study is only as portable as the source documents it cites, and those are the items most often left out of the package.
- If the escalation basis is unrecoverable, the receiving side resets to a conservative interval, which is a cost the importer inherits.
Sources
U.S. Government (eCFR). Air carrier maintenance recordkeeping and retention requirements under Part 121.
U.S. Government (eCFR). Maintenance recordkeeping and retention requirements for Part 135 operators.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
International Civil Aviation Organization. International standards for aircraft operation, including maintenance program and recordkeeping expectations.
U.S. Government (eCFR). Export airworthiness approval requirements and special requirements of an importing authority.
Frequently asked questions
Why check the program before the package is assembled rather than after?
Once the package is submitted, a missing escalation analysis becomes an open query against the export application. Finding it beforehand lets the exporter recover the source while the deadline is theirs, not the importing authority's.
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.