Structural repairs
Pilatus PC-12 structural repair records review
This review confirms that the structural repairs recorded on a Pilatus PC-12 each trace to approved data and that any inspection a repair introduced is being tracked. It suits a buyer, lessor, or manager who needs the airframe damage history to hold before a sale or a heavy check. The work builds a repair map from damage reports, repair approvals, and structural repair manual references for the single-engine turboprop. You receive an exception list of repairs lacking an approved basis or a required recurring inspection, a source map to the data behind each repair, and a closure plan for the tail.
When this review is needed
- A PC-12 has known ramp, hangar, or bird-strike damage history and the repair paperwork was never consolidated.
- A buyer wants every structural repair mapped to approved data before pricing the airframe.
- A repair introduced a recurring inspection and the owner needs to confirm it is on the program.
- A heavy check is approaching and the repair map has to be settled before the airframe is opened up.
The problem
Structural repairs on an owner-managed PC-12 tend to be one-off events, handled by whichever shop was near when the damage happened, and the paperwork rarely gets pulled into a single map. A repair may have been done to a structural repair manual reference, a field approval, or a manufacturer disposition, and the distinction matters because some repairs carry a recurring inspection that has to live on the program forever. Years later the repair is visible on the skin but the basis and the follow-on inspection are scattered or lost.
What gets reviewed
- Each recorded structural repair matched to its approved-data basis
- Damage reports reconciled to the repairs that dispositioned them
- Structural repair manual references confirmed against the repair as performed
- Recurring inspections introduced by any repair traced onto the maintenance program
- Repairs affecting the fatigue-critical structure identified and flagged
- Overlapping or adjacent repairs checked for interaction and combined effect
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 structural repair cites an approved or acceptable data basis appropriate to the location and severity
- Each damage report ties to the repair that dispositioned it, with no orphaned damage left open
- Structural repair manual references match the repair actually performed rather than a generic citation
- Any recurring inspection a repair created is present and current on the maintenance program
- Repairs on fatigue-critical or principal structural elements are identified and their limits captured
Evidence normally required
- The structural repair map or repair log for the airframe
- Damage reports and their dispositions
- Approved and acceptable repair data, including SRM references and field approvals
- The maintenance program to confirm recurring inspections are tracked
- Heavy-check reports that record structural findings and their repairs
Common discrepancies
- A visible repair with no approved-data reference in the records
- A recurring inspection introduced by a repair but never added to the program
- A damage report with no corresponding repair disposition on file
- A repair citing an SRM reference that does not match the work performed
What is at stake
A repair with no approved-data reference can force re-substantiation or rework, and a repair that introduced a recurring inspection nobody carried onto the program leaves an open compliance obligation the new owner inherits blind. At a heavy check, a repair the records cannot explain can hold the aircraft while its basis is reconstructed under time pressure.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Build the repair map
Consolidate every recorded structural repair and the damage report behind it into one map.
Check the data basis
Confirm each repair cites approved or acceptable data matching the work performed.
Trace recurring inspections
Identify repairs that created a recurring inspection and confirm it is live on the program.
Flag the exceptions
List repairs missing a basis or an inspection and set the closure action for each.
What the buyer receives
- An exception list of repairs lacking an approved basis or a required recurring inspection
- A source map from the repair map back to each repair's data and damage report
- A closure plan naming the substantiation or program action needed per repair
Who uses the output
- Asset managers pricing the airframe with its repair history understood
- Continuing-airworthiness teams confirming recurring inspections are on the program
- Records teams assembling a defensible repair map before a heavy check or sale
How the work fits into the transaction or program
The structural-repair review feeds the airframe's continued-airworthiness picture and the heavy-check planning that depends on knowing what has already been repaired. Settling the repair map before the airframe is opened means findings during the check can be judged against a known baseline instead of a blank one.
Aircraft-specific considerations
PC-12s often operate from unimproved strips and into remote fields, so their damage histories skew toward ground handling, gravel, and strike events repaired locally rather than in a fleet MRO. That pattern scatters the approved-data basis across many shops and dispositions, so the review scopes to the individual airframe's operating history rather than a fleet repair profile.
Jurisdiction-specific considerations
A repair basis accepted under FAA field-approval practice may need re-evaluation before an EASA register accepts it, so a PC-12 changing register has its major repairs checked for whether their basis carries across or needs a fresh acceptance.
Regulatory limits
The review confirms each repair traces to an approved or acceptable data basis and that any inspection it created is tracked. It does not approve a repair, develop repair data, or determine that the repaired structure is airworthy.
What this review does not cover
- Physical inspection or non-destructive testing of the repaired structure
- Developing or approving structural repair data
- Any airworthiness determination on a repair
Specific to this review
- The costliest gap is a repair that introduced a recurring inspection nobody carried onto the program, because the obligation runs on invisibly.
- PC-12 damage tends to be strip-and-strike related and repaired locally, so the approved-data basis is unusually scattered across shops.
- Adjacent repairs can interact on fatigue-critical structure, so the map is read as a whole rather than one repair at a time.
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
What if a repair created a recurring inspection that was never tracked?
That is treated as an open compliance obligation and flagged first, because the inspection is required for the life of the repair. The closure plan restores it to the maintenance program and reconciles any inspections that were due while it was untracked.
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.