Engine shop-visit records
Pilatus PC-12 PT6A engine shop-visit records review
This review confirms that a Pilatus PC-12 engine shop-visit package holds together from workscope to release, with the module build and test-cell records that support what the visit claims. A records specialist runs it for a buyer, owner, or engine trader who needs the shop-visit history to carry the engine's status. It reads the shop report against the build records, checks the test-cell data and any LLP movement, and confirms the release certificate closes the visit. You receive an exception list for the shop-visit package, a source map from the release back through the visit, and a plan to recover the records the package is missing.
When this review is needed
- A PC-12 or its PT6A is being sold and the buyer will read the last shop visit for the status it sets.
- An engine is coming off for separate sale and its shop-visit history carries the value.
- A recent hot-section or overhaul visit produced a package no one has reconciled end to end.
- The workscope claimed at the visit has to be confirmed against the build and test records behind it.
The problem
A PT6A shop visit generates a package that looks thick but can be internally inconsistent: a workscope that names more than the build records show, test-cell data missing for the acceptance run, or a release certificate that closes the visit without the module records that support it. On a single-engine PC-12 the last shop visit sets the engine's whole status, so a gap in that package is not diluted by a second engine. The release reads as final while the evidence chain behind it has a hole.
What gets reviewed
- The shop workscope read against the module build records that support it
- Test-cell and acceptance-run data checked for the parameters the visit claims
- Life-limited part movement at the visit reconciled with the build records
- The release certificate confirmed to close the visit and cover the work performed
- Disassembly and inspection findings matched to the corrective work recorded
- Post-visit engine status reconciled with the shop report and the logbook entry
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
- The workscope performed matches the module build records, tested against more than the shop's cover sheet
- Test-cell data is present for the acceptance run the release relies on
- LLP movement at the visit reconciles with the build records and the status sheet
- The release certificate covers the work the shop report describes
- Post-visit status in the logbook agrees with the shop report figures
Evidence normally required
- The engine shop-visit package including the shop report
- Module build records for the work performed
- Test-cell and acceptance-run data
- The release certificate and the engine logbook entry for the visit
Common discrepancies
- A workscope that names work the module build records do not show
- Test-cell data missing for the acceptance run behind the release
- An LLP moved at the visit with no build record to support the change
- A logbook status entry that disagrees with the shop report figures
What is at stake
When a shop-visit package does not reconcile, the engine's post-visit status is left unproven, and a buyer discounts an engine whose last major event cannot be fully documented. A missing build record can break the LLP trace that runs through the same visit, and recovering shop records after the visit closes depends on a shop that may not retain them, so the gap can become permanent.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the workscope
Establish what the visit claims to have done from the shop report and cover documents.
Reconcile the build
Match the workscope and any LLP movement to the module build records behind it.
Check test and release
Confirm the acceptance-run data is present and the release covers the work performed.
Flag the gaps
List where the package fails to reconcile and map the release back through the visit.
What the buyer receives
- An exception list for the shop-visit package where the chain does not reconcile
- A source map from the release certificate back through the visit records
- A closure plan to recover the missing build, test, or release records
Who uses the output
- Engine traders pricing the engine by the shop-visit history it can prove
- Asset managers deciding whether the last visit's package needs recovery before sale
- Records teams assembling the reconciled shop-visit package a buyer will require
How the work fits into the transaction or program
The shop-visit review sits upstream of the LLP and status work, since the build records inside the package are where part movement and remaining life are set. It runs before an engine or aircraft sale so a gap in the last visit is found while the shop can still supply the record, and its exception list feeds the recovery ahead of diligence.
Aircraft-specific considerations
The PC-12 runs a single PT6A, so the most recent shop visit sets the entire engine status with no second engine to fall back on, and the package for that visit carries proportionally more weight than it would on a twin. Module build records inside the visit are also where life-limited parts move, so a shop-visit gap and an LLP-trace gap on this aircraft often share the same missing document.
Regulatory limits
The review reconciles the shop-visit records and flags where the package does not hold together. It does not certify the engine, validate the shop's workmanship, or make any airworthiness determination on the engine or aircraft.
What this review does not cover
- Physical inspection or test of the engine
- Re-performing or approving any shop work
- Any airworthiness determination on the engine or aircraft
Specific to this review
- On a single-engine PC-12 the last PT6A shop visit sets the whole engine status, so a gap in that one package is not diluted by a second engine.
- The module build records inside a shop visit are shared ground with LLP trace, so one missing build record can break both the visit and the life-limited stack.
- A release certificate can close a visit on its face while the test-cell or build records that support it are absent from the package.
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The engine has a release certificate. Why reconcile the whole package?
The release closes the visit, but its value rests on the build and test records behind it. If those are missing, the post-visit status cannot be fully proven, which is exactly what a buyer of a single-engine aircraft 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.