Non-routine closure
Non-routine closure review of a shop-visit source file
Every defect a shop visit raises should end in a documented disposition, and the non-routine register is where that accounting lives. This review walks the register line by line, confirming each raised item shows what was found, who dispositioned it, what corrective action closed it, and where deferrals carry an authorized basis. It runs for the accepting quality organization before the package is signed off. Unclosed logic, missing dispositions, and orphaned cards come back as a structured finding set.
When this review is needed
- Closeout is near and the register still shows items whose closure paths are unclear.
- Deferred defects are leaving the visit and their deferral authority needs verification.
- The ratio of non-routines raised to cards delivered looks wrong and the population needs reconciling.
- A counterparty's records team will audit this register at the next transition.
The problem
Non-routines are born fast and finish slowly. A finding raised at strip may be dispositioned by engineering, actioned by a subcontractor, inspected by a third party, and closed weeks later under a different reference, with the connecting thread held in someone's head. The register at closeout shows rows of closed statuses, and the question is whether the file behind each row reconstructs that thread or merely asserts the ending.
What gets reviewed
- The full register reconciled against non-routine cards actually present in the file
- Disposition records checked for authority, basis, and applicability on each item
- Corrective actions matched to the defect as described, including parts and repairs consumed
- Deferrals verified for the deferral authority, category, and downstream tracking entry
- Cross-links resolved between non-routines and the routine cards or inspections that raised them
- Closure sign-offs checked for the inspection level the disposition required
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 register line has a card, and each card in the file has a register line
- The disposition on file addresses the defect as written, at the recorded location and severity
- Corrective-action records account for the materials, repairs, or replacements the disposition called for
- Deferred items appear on the outgoing status with the tracking control the deferral requires
- Closure signatures meet the inspection requirement the item's classification imposes
Evidence normally required
- The non-routine register or log as delivered at closeout
- All non-routine cards, with dispositions and closure records
- Engineering dispositions and any subcontractor work records supporting closures
- The outgoing deferred-defect list and its tracking references
- Routine cards or findings reports that originated the non-routines
Common discrepancies
- Closed register lines whose cards show disposition pending at the last recorded step
- A corrective action that replaced a component without the fitment traceable in the release file
- Deferrals citing an authority that does not extend to the defect's classification
- Register numbering gaps where raised items were cancelled without a recorded rationale
What is at stake
A defect signed closed without its disposition record reads as a defect that may still be in the aircraft. Auditors treat such lines as open, forcing re-inspection or engineering assessment long after access panels are shut. Deferrals with weak authority are worse: they carry an unresolved condition into service on paperwork that fails scrutiny, and responsibility arguments start immediately when one is found.
How the work runs
Reconcile the population
Match register lines to cards both ways and account for cancellations.
Audit each closure
Verify disposition, corrective action, and sign-off level per item.
Test the deferrals
Check authority, category, and the tracking handoff for everything deferred.
Issue the grading
Deliver the graded register and carry-forward summary for acceptance.
What the buyer receives
- A reconciled register with per-line closure grading
- A finding set for unsupported closures, weak deferrals, and orphaned items
- A carry-forward summary of everything leaving the visit open, deferred, or tracked
Who uses the output
- Quality managers gating final acceptance of the visit
- CAMO staff loading deferred items into continuing-airworthiness tracking
- Lessor representatives assessing what the asset carries out of the shop
How the work fits into the transaction or program
Non-routine review is the connective pass of a source-file audit: its items spawn the repairs the repair review grades and consume the parts the release review reconciles. Reading the register first gives the other reviews their map of where the visit's real risk accumulated.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Deferral machinery differs between systems: US operators lean on MEL provisions and approved procedures under their operations specifications, while EASA operators route deferrals through Part-145 and Part-M interfaces with defined rectification intervals. A deferral valid under the shop's system can still fail the receiving operator's framework, so the review reads each one against the regime the aircraft flies under next.
Regulatory limits
Findings describe the documentation of defects and closures, never the condition of the aircraft or engine. The review does not disposition defects, authorize or extend deferrals, classify damage, or certify corrective work; those authorities remain with engineering, the certifying organization, and the operator's approved procedures.
What this review does not cover
- Inspecting or re-opening any area to verify physical closure
- Providing engineering dispositions for items found unsupported
- Adjudicating commercial responsibility for defects between owner and shop
Specific to this review
- Registers reconcile cleanly far less often than they read cleanly; cancelled and merged items are the usual source of silent numbering gaps.
- The closure signature is frequently correct while the disposition is missing, because sign-off systems enforce the former and only procedure enforces the latter.
- Non-routines closed by subcontractors are the most likely to lack their supporting records at closeout, since the documents chase the invoice rather than the card.
- A deferral that never lands in the operator's tracking system is functionally lost; the review treats the tracking entry, and never the deferral form alone, as the proof of control.
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 register shows everything closed. Why review it?
Register status reflects data entry, and the audit question is whether each closure can be reconstructed from the card, the disposition, and the corrective action behind it. Reviews of clean-looking registers routinely surface closures that cannot.
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.