Deferred maintenance records before import or export

When this review is needed

• Open deferrals exist and the export airworthiness process expects them cleared or explicitly addressed.
• Deferral closures in the log have never been sampled against their corrective-action records.
• The transfer date is close enough that some open items will breach their intervals before or during the ferry.
• Watch items and carried defects are known to be managed outside the formal deferral system.

The problem

A deferral log under operational pressure optimizes for keeping the aircraft flying, and its habits show at transfer: closures recorded with a reference nobody can find, items re-deferred in chains that stretch the original intent, and a shadow population of watch items living in shift notes. The log that satisfied daily operations now has to satisfy an authority reading it as a statement of the aircraft's condition on a specific date.

What gets reviewed

• Every open deferral, checked for category, limit, and expiry against the planned transfer timeline
• Sampled closed deferrals, traced to corrective-action and certification evidence
• MEL category discipline: each deferral raised under a category the approved MEL revision permits
• Repetitive deferrals of the same item or system, identified and characterized
• Reconciliation of the log with the current status summary and the draft export declaration
• Known watch-item or carried-defect populations outside the formal log

What gets validated

• No open item's interval expires before the transfer completes, on the current schedule
• Each sampled closure names the corrective action and traces to the work record that performed it
• Deferral categories match what the approved MEL revision in force at the time actually allowed
• Chains of re-deferral for a single defect are visible in the log rather than reset as new items
• The open-item picture in the log matches what the export application and status summary declare

Evidence normally required

• The complete deferral log covering the review window, with open and closed items
• The approved MEL and its revision history for the same period
• Work records and certifications behind sampled deferral closures
• The current status summary and the draft export or import application
• Any known watch lists or carried-defect records held outside the log

Common discrepancies

• A closure entry whose referenced work record cannot be produced
• An open item whose limit expires inside the transfer window on the current plan
• A deferral raised under a category the approved MEL revision of the day did not permit for that item
• Recurring deferrals of one system, closed and reopened in a pattern the log presents as unrelated items

What is at stake

An open deferral that breaches its limit mid-transfer grounds the process at the moment of least flexibility, away from the operator's own maintenance network. Unsupported closures do slower damage: each one the importing side finds erodes trust in the log as a whole, and a reviewer who stops trusting the deferral record starts asking for corrective-action evidence item by item, which is the most time-expensive form of authority scrutiny a package can attract.

How the work runs

What the buyer receives

• An open-items risk table against the transfer timeline, expiry by expiry
• A closure-evidence exception list from the sampled history
• A reconciliation statement between the log, the status summary, and the export declaration

Who uses the output

• Transition leads planning which items to clear before the ferry and which to present to the authority
• Line maintenance and CAMO staff scheduling the clearing work while the aircraft is still in the network
• The importing operator's team deciding what open history it is prepared to inherit

How the work fits into the transaction or program

Deferral findings connect to nearly every other review in the package: unsupported closures point back into task-card and non-routine evidence, repetitive deferrals hint at maintenance program weaknesses, and the open-item picture feeds directly into the export application. It is typically one of the last reviews refreshed before filing, because its subject keeps changing until the aircraft stops flying.

Jurisdiction-specific considerations

Export airworthiness processes on both the FAA and EASA sides expect the applicant to account for open discrepancies, and ICAO Annex 6 frames the deferral disciplines third-country authorities look for. What differs is tolerance: some importing authorities accept a short, well-documented open list at transfer while others expect a clean sheet, so the review's open-item table is built to support either conversation.

Regulatory limits

The review reads records against records. It does not determine whether any deferral was operationally justified, does not clear or extend deferred items, and makes no airworthiness determination about the aircraft's fitness for the ferry or for export certification. Those decisions rest with the operator, its approved organizations, and the authorities.

What this review does not cover

• Performing or certifying the rectification of deferred items
• MEL revision or operational-approval work
• Judgments on the operational legitimacy of historical deferral decisions

Specific to this review

• The weeks before a transfer reliably produce a spike in deferrals as the operator protects the schedule, so the log needs a final review pass close to the ferry date, not just at package assembly.
• A log with tidy open items and careless closures is a recognized pattern; reviewers who see it widen their closure sampling immediately.
• Items managed on informal watch lists are invisible to the export declaration until someone asks for them, and importing operators increasingly do.
• Clearing a deferral costs least while the aircraft is inside the operator's own network; the same item cleared at a transition facility can cost multiples in access, parts, and delay.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits