Defect history at handover
Non-routine closure review for the lease-transition records file
Non-routine cards record what was actually found on the aircraft, which makes them the part of a records file acceptance teams trust least when the closure paperwork is thin. This review works through the non-routine register in a lease-transition records file and confirms that every raised item shows its disposition, its corrective action, and the data that authorized both. Items signed closed without that chain, and deferrals that never resurface, are reported as exceptions. The transition lead receives the exception list with each item's origin, so recovery requests go to the right check and the right shop.
When this review is needed
- A redelivery check is about to raise fresh non-routines and the historical register needs to be clean before the populations merge.
- The register shows closures the incoming operator has begun challenging for missing corrective-action detail.
- Deferred defects from a prior check cannot be matched to the later work that supposedly cleared them.
- The lease's return conditions require defect records with dispositions and the file was never audited to that standard.
The problem
Routine cards prove that planned work happened; non-routine cards prove what the aircraft was actually hiding, which is why acceptance teams read them differently. Closure quality tracks the pressure under which items were raised: findings from the last days of a check close thin, and deferrals rely on someone remembering them at the next input. A transition file inherits every one of those shortcuts at once.
What gets reviewed
- The non-routine register reconciled against the cards it summarizes, in both directions
- Each closed item traced through evaluation, disposition, corrective action, and certification
- Deferrals followed to the record of later accomplishment or to the open item that should still exist
- Dispositions that left findings in service checked for the data that supported the call
- Non-routines that generated repairs cross-referenced into the repair records
- Register items already in acceptance dispute consolidated into the exception set
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
- Every register line resolves to a card, and every card in the set appears on the register
- Closed items name the corrective action taken, with the sign-off that certified it
- In-service dispositions cite the evaluation and the data under which the finding remained acceptable
- Deferred items connect to a subsequent closure record or a still-open tracking entry
- Findings that created repairs or repetitive inspections appear in the corresponding record sets
Evidence normally required
- The non-routine register or registers covering the lease term
- Non-routine cards and their attachments from each check package
- Deferred-defect logs and carried-forward item lists
- Repair records and program records for cross-referenced items
- Acceptance correspondence raising defect-history questions
Common discrepancies
- An item marked closed whose card shows an evaluation and no corrective action at all
- A deferral carried across a check boundary and absent from every later package
- In-service dispositions resting on a verbal engineering call no document memorializes
- A register renumbered mid-lease, leaving two item sequences that partially overlap
What is at stake
A closure without its corrective action reads as an unresolved defect, whatever actually happened in the hangar, and unresolved defects on a delivered aircraft are acceptance stoppers. Orphaned deferrals are worse: an item that left the register without a closure record anywhere puts the current physical status of that finding in doubt. Both push the counterparty toward physical verification, which converts a records question into check time.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Square the register
Reconcile register lines and cards in both directions and resolve numbering seams.
Walk each closure
Trace sampled items through evaluation, disposition, corrective action, and certification.
Chase the deferrals
Follow every deferral to its later closure record or confirm it as an orphan.
Deliver by origin
Report exceptions keyed to originating check and shop so recovery requests batch correctly.
What the buyer receives
- An exception list of unsupported closures and orphaned deferrals, keyed to originating check
- A register reconciliation showing card-to-register agreement in both directions
- A recovery sheet naming the shop or operator holding each missing closure document
Who uses the output
- Transition leads settling defect-history queries with evidence keyed to its origin
- Records staff recovering closure documents from the checks that produced them
- Receiving-side engineers deciding which historical findings warrant physical follow-up
How the work fits into the transaction or program
The non-routine strand connects the task-card review to the repair review: findings begin as cards and end as repairs or dispositions, and this review walks that path for each register line. Its exceptions merge into the same tracker, keyed by originating check so recovery requests batch sensibly.
Jurisdiction-specific considerations
Both systems require defect records: FAA practice grounds them in 14 CFR 43.9 entries and the guidance of AC 43-9C, EASA practice in the operator and Part-145 records kept under Regulation (EU) 1321/2014. Deferral mechanics differ more than closure mechanics, since MEL and carried-forward item handling follow the operator's own approved procedures, and the review reads each deferral against the regime that governed it at the time.
Regulatory limits
Reporting a closure as unsupported is a statement about the records, never about the aircraft's condition. The review makes no airworthiness determination, approves no deferral or disposition, and does not direct physical verification; those calls belong to the operator and the authority.
What this review does not cover
- Physical verification that closed findings remain rectified
- Engineering disposition of any open or reopened defect
- MEL management or deferral decision-making
Specific to this review
- The two directions of register reconciliation find different defects: register-to-card finds paperwork gaps, card-to-register finds items that never reached the summary at all.
- Registers renumber when operators or systems change, and the seam between numbering schemes is where items vanish.
- An in-service disposition is the highest-value recovery target because the engineering evaluation usually still exists at whoever made it.
- Acceptance teams weight non-routine history as a proxy for how the aircraft was maintained overall, so exceptions here color the review of every other record set.
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
An item was fixed on the aircraft but the paperwork is thin. Does it still fail the review?
Yes, as a records exception, because the review reports what the file proves rather than what happened in the hangar. The useful part of the finding is its origin key, which points recovery at the specific check and shop where the closure evidence most likely still exists.
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.