Deferred defects reviewed for carryover or closure at import

The problem

whether to clear or carry each deferred defect and MEL item across the transition, because import authorities differ on issuing a C of A over open items.

What gets reviewed

• Confirm the decision path for open deferred items at aircraft import review before the aircraft file is submitted.
• Reconcile deferral log with rectification intervals to logbook entries, certificates, approvals, or status reports.
• Challenge assumptions about carryover items, accepted approvals, and stale summaries.
• Package the open list so commercial, records, and technical owners can close items in sequence.

What gets validated

• Verify that the file answers the specific import, redelivery, or registration question raised by the brief.
• Mark stale data as failed when AD, LLP, mod, or deferral status stopped before the review date.
• Review copies for certification, legibility, and link to the source package before treating them as evidence.
• Keep commercial acceptance separate from technical closure in the discrepancy register.

Evidence normally required

• deferral log with rectification intervals
• MEL basis change at the new registry or operator
• carryover policies for acceptable deferred defects
• Current AD status report
• Life-limited component status
• Modification and repair approval list

Common discrepancies

• C of A withheld over items the team assumed transferable.
• deferral intervals lapsing mid-transition so the aircraft is neither airworthy nor importable. The page is anchored on the clear-versus-carry decision per item.
• what the importing authority will accept over open items - not on re-verifying the deferral log against export declarations.
• The file treats deferral log with rectification intervals as closed without enough support.

What is at stake

a C of A withheld over items the team assumed transferable, and deferral intervals lapsing mid-transition so the aircraft is neither airworthy nor importable. The page is anchored on the clear-versus-carry decision per item and what the importing authority will accept over open items - not on re-verifying the deferral log against export declarations, which is the source-review page's job.

How the work runs

What the buyer receives

• Open deferred items at aircraft import review review memo
• Gap list with affected status items
• Submission-ready records index
• Commercial exposure notes

How the work fits into the transaction or program

The decision is whether to clear or carry each deferred defect and MEL item across the transition, because import authorities differ on issuing a C of A over open items; the deferral log with rectification intervals and approvals, the MEL basis change at the new registry or operator, and carryover policies for acceptable deferred defects. The evidence set centers on the deferral log with rectification intervals and approvals, the MEL basis change at the new registry or operator, and carryover policies for acceptable deferred defects. The likely weak points are a C of A withheld over items the team assumed transferable, and deferral intervals lapsing mid-transition so the aircraft is neither airworthy nor importable. Handoff: continuing airworthiness manager, import with open deferred items, Deferred defects reviewed for carryover or closure at import.

Regulatory limits

EE identifies gaps and prepares the records case. It does not perform regulatory certification, sign a release to service, approve design data, or make the final technical acceptance decision for any authority or buyer.

Specific to this review

• Open deferred items at aircraft import review depends on the aircraft status at the transfer date, not on an older audit snapshot.
• FAA and EASA context changes what evidence is persuasive even when the status heading looks familiar.
• A summary gains value only when the release, approval, inspection, or utilization record behind it can be found.
• add-carryover-at-import is the page-specific risk that drives the request list and closure plan.
• The scope uses the Open Deferred Items Import question as the control point, so the review stays tied to Import with open deferred items and the buyer decision behind it.
• The evidence starts with AD status and follows Records Review Aircraft Defects references until every exception has a source location and a reason code.
• The finding logic separates missing paperwork, conflicting status, stale revision data, and unsupported disposition because each class closes through a different owner.
• The timing matters for continuing airworthiness manager: the output is useful only if the unresolved items are visible before acceptance, submittal, handback, or negotiation pressure fixes the sequence.
• The boundary control keeps Reviewed Carryover Closure Registry questions in the records or certification lane and sends technical acceptance issues to the authorized people who own them.
• The handoff value comes from Open deferred items at aircraft import review review memo; it gives the next reviewer a precise map instead of another broad request for a better file.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits