Non-routine card records
Pilatus PC-12 non-routine defect closure records review
This review confirms that the non-routine cards raised during a Pilatus PC-12 check were dispositioned and closed with the corrective action and sign-off each one needed. A records specialist runs it for an owner, buyer, or continuing-airworthiness lead who needs the defect history to show clean closures rather than open findings hiding in a stack. It reads each non-routine from the raised defect through the engineering disposition to the corrective action and final sign-off, and checks that any approved data a disposition relied on is cited. You receive an exception list for the non-routine register, a source map from finding to closure, and a plan to close the cards that were left unresolved.
When this review is needed
- A PC-12 is being sold and the buyer will read the non-routine cards for defects closed without full resolution.
- A check raised a run of non-routine findings and the register has not been reviewed for clean closure.
- A defect disposition relied on approved data that the card may not actually cite.
- The aircraft is transferring and the receiving side needs each non-routine to show a documented closure.
The problem
Non-routine cards are where the messy work of a check lives, and they are the records most likely to close short. A defect can be raised, partly worked, and marked closed with the corrective action described but the final sign-off missing, or a disposition can lean on approved data the card never names. On a PC-12 where several shops have worked the aircraft, the non-routine register mixes closure conventions, and a card that ended in a deferral can read as resolved unless someone follows it to the end.
What gets reviewed
- Each non-routine traced from the raised defect to its final closure
- Engineering dispositions read for the corrective action they direct
- Approved data a disposition relied on checked for a reference on the card
- Final sign-offs confirmed present for every card marked closed
- Deferred non-routines distinguished from resolved ones in the register
- Corrective actions reconciled with the parts and work the aircraft records show
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 non-routine shows a disposition, a corrective action, and a final sign-off
- A disposition relying on approved data cites that data on the card
- A card marked closed is resolved, not deferred without a tracked open item
- The corrective action recorded matches the parts and work in the aircraft records
- No non-routine in the register is left in an unresolved state behind a closed mark
Evidence normally required
- The non-routine register for the check or period under review
- The individual non-routine cards with their dispositions
- Approved data referenced by any disposition
- The aircraft records showing the corrective parts and work
Common discrepancies
- A non-routine marked closed with the corrective action described but no final sign-off
- A disposition relying on approved data the card never references
- A deferred defect carried in the register as if it were resolved
- A corrective action that names a part the aircraft records do not show installed
What is at stake
A non-routine left open behind a closed mark carries a live defect into the next owner's operation, and a disposition without its approved-data reference cannot prove the repair met an acceptable standard. At a sale these are the findings a diligence team reads most closely, because an unresolved non-routine is a defect the buyer would inherit, and reconstructing the closure after the shop has moved on is often impossible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk each card
Trace every non-routine from the raised defect through disposition to corrective action and sign-off.
Check the basis
Confirm dispositions relying on approved data cite it and that closures carry a final sign-off.
Separate deferrals
Distinguish resolved cards from deferred ones and confirm deferrals are tracked as open items.
Flag and map
List the short closures and map each resolved card from finding to closure.
What the buyer receives
- An exception list for the non-routine register where closures fall short
- A source map from each defect finding through to its documented closure
- A closure plan to resolve, re-disposition, or reconstruct the open cards
Who uses the output
- Continuing-airworthiness leads confirming defect closures before a transfer
- Asset managers reading the defect exposure the register actually carries
- Records teams resolving the open non-routines before diligence
How the work fits into the transaction or program
The non-routine review sits alongside the task-card work, since non-routines are the findings the routine cards generate and hand off for disposition. It runs before a sale or transfer so a defect closed short is found while the shop that raised it can still explain the disposition, and its exception list drives the resolution ahead of diligence.
Aircraft-specific considerations
Because a PC-12 is often worked by more than one shop over its life, the non-routine register blends different closure conventions, and a card that ended in a deferral at one shop can read as resolved under another shop's format. The review reads each shop's non-routine cards against its own closure convention so a deferral is not mistaken for a clean resolution.
Regulatory limits
The review confirms non-routine defects were dispositioned and closed with traceable evidence and flags where they were not. It does not disposition a defect, approve a repair, or make an airworthiness determination on the aircraft.
What this review does not cover
- Dispositioning or re-dispositioning any defect
- Performing or approving corrective maintenance
- Any airworthiness determination on the aircraft
Specific to this review
- A non-routine that ended in a deferral can read as resolved when a later shop's closure convention is applied to it, so each card is read against the convention it was raised under.
- A disposition without its approved-data reference cannot prove the repair met an acceptable standard, even when the corrective action is fully described.
- The non-routine register is where a check's defect exposure concentrates, because these cards capture what the routine tasks turned up rather than the planned work.
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
How is a non-routine different from a routine task card for this review?
A routine card accomplishes planned work; a non-routine captures a defect the work turned up and has to be dispositioned and closed. The review follows each non-routine to a documented resolution, because an unresolved one is a live defect the next owner inherits.
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.