Defect closure
Non-routine closure records review in the redelivery binder
Non-routine cards record what maintenance actually found, which makes their closure records the part of a redelivery binder most likely to be challenged. This review follows each entry in the non-routine register from the defect description through its disposition to the corrective action and final sign-off, verifying that the paperwork clearing the defect exists and fits it. It is carried out during binder preparation, on behalf of either party to the return. What it produces is a register-keyed schedule of closures that hold and closures that do not.
When this review is needed
- Heavy checks during the lease raised hundreds of non-routines and the register has never been reconciled against the cards themselves.
- Structural findings from the last check were dispositioned by engineering, and the dispositions live in an MRO system rather than the binder.
- Deferred defects are being carried toward the return date and the lessor wants each one's paper trail confirmed before acceptance.
- The return check is generating fresh findings and both parties need the historical closure record settled before arguing over the new ones.
The problem
Non-routines are written fast, on the hangar floor, in the middle of a check, and they close under the same pressure. A card gets signed off with the corrective action summarized in one line while the substantiating documents, the engineering disposition, the repair reference, the replacement part's release, scatter into other files. By redelivery, the register says closed, the card says closed, and the actual evidence chain has three links missing. Every challenged closure then requires a manual hunt through work packs that may sit with an MRO two operators ago.
What gets reviewed
- Reconciliation of the non-routine register against the physical or electronic cards enclosed in the binder
- Verification that each closure cites a corrective action specific enough to audit, with its substantiating record attached or referenced
- Trace of engineering dispositions for findings that exceeded published limits
- Follow-through of defect-driven part changes to the corresponding release documents
- Review of deferrals for authority, time limits, and disposition before or at the return
- Numbering-continuity check across the register to surface cards that were raised and never presented
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
- Register line counts, card counts, and work-pack cross-references agree, with voids explained
- Closures citing repair action name the approved data used, and that data covers the defect as written
- Dispositions for over-limit findings carry engineering authority appropriate to the finding
- Part replacements recorded on non-routines match removal and installation records and their release certificates
- Open or deferred items at binder cutoff appear on the acceptance-status documents rather than silently persisting
Evidence normally required
- The non-routine register and complete card set for lease-term checks
- Engineering dispositions, repair references, and approved data cited by closures
- Removal and installation records for defect-driven component changes
- The deferred-defect log and applicable deferral authority, such as the MEL or operator procedures
- Acceptance notes or open-items lists already exchanged between the parties
Common discrepancies
- Closures reading repaired per SRM with no chapter, figure, or dimension recorded, leaving the repair untraceable
- A defect signed closed by reference to a second card that is absent from the binder
- Register numbering gaps corresponding to cards raised during the check and later voided without record
- Deferrals that expired mid-lease with no evidence the underlying defect was ever rectified
What is at stake
A closure that cannot be evidenced reopens the defect. If the defect was structural, it drags the repair-substantiation question with it; if a part was changed, it pulls on the release-document file; if it was deferred, it raises whether the deferral was ever valid. Acceptance teams treat unproven closures as live findings, and live findings at redelivery translate directly into inspection demands, cure periods, and money.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Reconcile register to cards
Match every register line to a card, account for voids, and flag numbering discontinuities.
Trace each closure outward
Follow corrective actions to dispositions, approved data, part releases, and linked cards.
Resolve the deferrals
Check every carried defect for authority, time limits, and its status at binder cutoff.
Grade and report
Issue the closure-integrity schedule with a targeted retrieval list for the weak entries.
What the buyer receives
- A closure-integrity schedule keyed to the register, rating each entry as evidenced, partially evidenced, or unsupported
- A linked-record request list identifying the exact dispositions, releases, and repair documents to retrieve
- A deferral status summary reconciling carried items against the acceptance open-items list
Who uses the output
- Acceptance representatives for the lessor deciding which historical findings to press
- The returning operator's engineering and records staff closing evidence gaps against the clock
- Incoming-operator engineers assessing what defect history they are inheriting
How the work fits into the transaction or program
Non-routine closures knit the other binder reviews together: they hand structural findings to the repair-substantiation work, part changes to the release-document check, and carried defects to the acceptance open-items negotiation. Running this review after the task-card sample and before final acceptance sessions catches the linkage failures while retrieval from MRO archives is still feasible.
Jurisdiction-specific considerations
Recording and closure expectations for findings rest on 14 CFR 43.9 and AC 43-9C for FAA operators and on Part-145 release and Part-CAMO oversight under Regulation (EU) 1321/2014 for EASA operators. Deferral practice differs more than closure practice between the regimes, so carried defects on a cross-regime return attract particular scrutiny over whose deferral authority applied at each point in time.
Regulatory limits
The review establishes whether closure documentation exists and coheres. It makes no judgment that a defect was correctly rectified, confers no approval on dispositions or deferrals, and issues no airworthiness determination; those remain matters for the certifying mechanics, engineers, and authorities involved.
What this review does not cover
- Physical verification that rectified defects remain sound
- Engineering review of whether a chosen disposition was technically correct
- Adjudication of which party bears cost for unresolved findings
Specific to this review
- The one-line corrective action is the classic failure: it satisfied the check's closure process at the time, yet gives an acceptance auditor nothing to trace five years later.
- Non-routines closed in the last days of a check statistically carry the weakest evidence, because substantiating paperwork was still catching up when the aircraft left the hangar.
- A register with no voided cards at all is a red flag in itself; every real check voids some cards, and their absence suggests the register was rebuilt after the fact.
- Defect-driven part changes are where the non-routine file and the release-certificate file must agree, and disagreements between them are found on most first-pass reviews.
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
The check was years ago and the MRO archived everything. Is the review still worth running?
That situation is the argument for running it now rather than at acceptance. Archive retrieval takes weeks, and a review that names the precise dispositions and releases to pull lets the operator lodge one consolidated request early. Waiting until the counterparty challenges closures live means making the same request with no schedule left to absorb it.
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.