Repair and alteration records
Pilatus PC-12 repair and alteration approval records review
This review confirms that every repair and alteration recorded on a Pilatus PC-12 rests on approved data and returned the aircraft to service with the right entry. A records specialist runs it for an owner or buyer who needs the repair history to hold rather than assume approval behind each disposition. It maps each repair, reads the damage report and disposition against the approved data cited, and checks that STC-based alterations carry their approval basis. You receive a repair map with an exception list, a source map from each repair to its approved data, and a plan to substantiate the dispositions that lack it.
When this review is needed
- A PC-12 is being sold and the buyer will test each repair against the approved data cited for it.
- Mission equipment was fitted under an STC and the alteration's approval basis has never been confirmed.
- A damage repair appears in the logbook with a disposition but no reference to the data that approved it.
- The aircraft is changing registers and its alterations have to be acceptable to the receiving authority.
The problem
A PC-12 in owner-directed service tends to accumulate repairs and mission-equipment alterations whose approval basis lives in a shop file rather than the aircraft record. A damage disposition can read as complete while the approved data it relied on is named nowhere, and an STC alteration can be embodied with the installation recorded but the approval reference missing. The return-to-service entry closes the event on paper before anyone confirms the data behind it.
What gets reviewed
- Each recorded repair mapped to its location and the damage report behind it
- Damage dispositions read against the approved data they cite
- STC-based alterations checked for the approval basis and effectivity for this serial number
- Return-to-service entries confirmed to follow from the repair records on file
- Mission-equipment changes checked for treatment as an alteration where the type requires it
- Repairs affecting configuration reconciled with the configuration record
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 repair cites approved or acceptable data appropriate to the damage and the aircraft
- An STC alteration carries its approval reference and applies to this serial number
- The return-to-service entry follows from the disposition and the data behind it
- A repair that altered configuration is reflected in the configuration record
- Mission-equipment changes are recorded as alterations where the type design requires it
Evidence normally required
- The repair and alteration records with their dispositions
- Damage reports and the approved data referenced for each repair
- STC paperwork for embodied alterations
- Return-to-service entries and the configuration reference for the aircraft
Common discrepancies
- A damage disposition recorded without a reference to the approved data behind it
- An STC alteration installed with no approval reference in the aircraft file
- A repair that changed configuration without the configuration record catching up
- Mission equipment fitted as a routine change where the type required an alteration
What is at stake
A repair without traceable approved data may have to be re-substantiated or, in the worst case, reworked, and an alteration whose STC basis cannot be produced can stall a register change until it is reconstructed. On a privately operated aircraft the shop that held the approval file may be gone, which turns a missing reference into an expensive reconstruction the owner funds under deadline.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map the repairs
List each repair and alteration by location and event, drawing from the logbooks and work orders.
Test the basis
Read each disposition against the approved data it cites and confirm STC alterations carry their reference.
Reconcile configuration
Check that repairs and alterations affecting configuration are reflected in the configuration record.
Flag and map
List the unsupported dispositions and tie each confirmed repair to its approved data.
What the buyer receives
- A repair map with an exception list where approval data is missing or mismatched
- A source map from each repair to the approved data behind it
- A closure plan to substantiate or reconstruct the unsupported dispositions
Who uses the output
- Asset managers pricing the repair history the records can defend
- Engineering deciding how to treat a repair with no traceable approval basis
- Records teams reconstructing the approval references that came up short
How the work fits into the transaction or program
The repair review sits alongside configuration and release work, confirming the alterations the configuration record asserts are actually approved. It runs before a sale or register change so an unsubstantiated disposition is found while the approval file can still be recovered, and its exception list drives the substantiation ahead of diligence.
Aircraft-specific considerations
PC-12 owners often fit mission equipment to suit a specific role, and each of those changes is an alteration whose approval basis has to be traceable, over and above its installation. Because the work is frequently done under owner direction at a shop that keeps its own file, the approved-data reference is the item most likely to be absent from the aircraft record.
Regulatory limits
The review confirms repairs and alterations cite traceable approved data and flags where they do not. It does not develop or approve repair data, grant an STC, or determine that a repair or the aircraft is airworthy.
What this review does not cover
- Developing or approving repair or alteration data
- Performing or re-performing any repair
- Any airworthiness determination on a repair or the aircraft
Specific to this review
- On a PC-12 the approved-data reference is the field most often missing, because owner-directed repairs are done at shops that keep the substantiation in their own files.
- A return-to-service entry closes a repair on paper regardless of whether the approval basis was ever recorded, so a clean logbook can still hide an unsupported disposition.
- Mission-equipment alterations are the alteration type most likely to be recorded as a routine change, which understates what has to be traceable for a register move.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The repair has a return-to-service entry. Isn't that enough?
The entry records that the aircraft was returned to service, not that the data behind the repair was approved. The review confirms each disposition cites traceable approved data, which is what a buyer or the receiving authority will test.
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.