Heavy-check closure
Closing non-routine cards that lack disposition or sign-off
A non-routine card that records a defect but not its resolution leaves an open question in the middle of a closed check. This remediation works through an airline's flagged NRCs and completes the story of each one: what the disposition was, which corrective action was taken under what approved data, and where the final inspection acceptance lives. Fleet technical and records teams bring it in when an audit, redelivery review, or internal sweep has counted the incomplete cards, and the count is too high to absorb as individual exceptions. Every card ends the engagement either evidenced as properly closed or escalated as a genuinely unresolved defect for maintenance control.
When this review is needed
- An audit sampled heavy-check packages and found NRCs without corrective action or final acceptance blocks completed.
- A redelivery reviewer is working through non-routines card by card and the exceptions are accumulating.
- Scanned check packages show NRC first pages while the continuation sheets carrying the closure never made it into the file.
- A defect appears on an NRC with a deferral notation, and no trace of it exists in the deferral log it should have entered.
The problem
Non-routines are born in the least controlled moment of a heavy check: a finding on the hangar floor, a card raised fast, work split across shifts and sometimes across vendors. Closure discipline is what turns that churn into a record, and when it slips, the airline is left holding cards that prove a defect existed while staying silent on whether anyone fixed it. Reading those cards years later, no reviewer can tell a documentation failure from an unrectified defect, and neither can the airline.
What gets reviewed
- Census of flagged NRCs across the affected check packages, classified by what each card is missing
- Pairing of every NRC with the routine card, inspection, or finding that raised it
- Retrieval of closure evidence from the performing MRO, engineering support, and the airline's own systems
- Verification that corrective actions cite the approved data they were performed under
- Cross-check of deferral notations against the deferral log and MEL records of the period
- Escalation packaging for any card that appears to represent a genuinely open defect
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 disposition names a resolution path the finding supports: rectify, repair per approved data, or defer under the applicable program
- Corrective action blocks reference the data used, whether an SRM chapter, an engineering order, or a specific approval
- Final acceptance carries an authorized signature or stamp consistent with the check's certification records
- Continuation sheets are accounted for, so a card is not judged incomplete when its closure sits on a missing page
- Deferred items trace into the deferral system with the tracking and due dates the deferral category requires
Evidence normally required
- The flagged NRC population, or the check packages from which it will be drawn
- Routine cards and inspection findings that generated the non-routines
- The MRO's job files and any engineering dispositions issued during the checks
- Deferral logs and MEL records covering the check periods
- The airline's certification and stamp registers for signature verification
Common discrepancies
- Closure evidence that exists in the MRO's copy of the package but never transferred to the airline's file
- Corrective actions performed under engineering dispositions that were filed with engineering rather than with the card
- NRC continuation sheets lost at scanning, leaving complete paper closures invisible in the digital record
- A small residue of cards with no closure evidence anywhere, requiring physical verification of the defect area
What is at stake
Incomplete NRCs age badly. In an authority audit they read as findings against the quality system; in a redelivery they become per-card exceptions the counterparty prices; and in the worst case an actually deferred defect that never reached the deferral log has been flying unmonitored. The volume matters too, since a handful of incomplete cards is an exception list, but a pattern across checks is a systemic finding.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Census and classify
Count the incomplete cards across packages and sort them by which closure element is missing.
Reconnect the chain
Pair each NRC with its raising document and search airline, MRO, and engineering files for the closure evidence.
Separate paper from metal
Distinguish documentation failures from cards that may represent unrectified defects, and escalate the latter.
File and feed back
Complete the closure files, deliver the escalation package, and hand the pattern summary to quality.
What the buyer receives
- A completed closure file per NRC, assembling disposition, corrective action, and acceptance evidence
- A classification report separating documentation failures from candidate open defects
- An escalation package for maintenance control covering cards needing physical follow-up
- A pattern summary identifying which checks, shops, or periods produced the incomplete closures
Who uses the output
- Records leadership restoring check packages to a defensible state before the next review
- Continuing-airworthiness staff confirming no unmonitored deferral is hiding in the residue
- Quality teams using the pattern summary to fix the closure-discipline failure at its source
How the work fits into the transaction or program
NRC remediation usually follows a sampling event that revealed the problem and precedes the transaction or audit response that demands its solution. Its classification report is the hinge: documentation failures close on paper, while candidate open defects leave the records domain entirely and enter maintenance control as physical verification tasks with their own priority.
Jurisdiction-specific considerations
Both regimes require maintenance records to show work performed and its acceptance, with FAA practice shaped by 14 CFR 43 and AC 43-9C and EASA-regime packages governed by Regulation (EU) No 1321/2014. Checks performed at foreign shops introduce the extra wrinkle of dual-release paperwork, where a card can be properly closed under one regime's conventions and still look irregular to a reviewer trained in the other's.
Regulatory limits
Closure work assembles the disposition and acceptance evidence for each card. Where a defect turns out never to have been rectified, the finding transfers to maintenance control; this review does not rectify defects, accept work, or make the airworthiness call on what the residue means for the aircraft.
What this review does not cover
- Physical inspection or rectification of defect areas identified as unresolved
- Retroactive certification or sign-off of work lacking an authorized acceptance
- Redesign of the airline's non-routine control process, beyond the pattern summary
Specific to this review
- An NRC without a disposition is ambiguous in the most expensive way possible: it cannot prove the defect was fixed, and it cannot prove the defect was safely deferred either.
- Corrective actions referencing repair data must name it specifically, because a fix without its approved-data citation is unsubstantiated even when the workmanship was flawless.
- The raising document is half the record; an NRC that cannot be tied back to the routine card or finding that generated it will fail a thorough review even with a perfect closure block.
- Scanning projects hit NRCs hardest of all card types, since their handwritten continuation sheets and attached photos are exactly what batch digitization loses.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
Frequently asked questions
Most of our incomplete cards are probably just paperwork. Is a full remediation overkill?
The trouble is that the probably is doing all the work in that sentence. Until each card is either evidenced or escalated, the population reads as potential unrectified defects to every auditor and counterparty who samples it. Remediation is what converts a probably into a classification report, and in practice the small residue of genuinely unresolved cards it isolates is the part the airline most needed to know about.
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.