Authorized release certificates
Pilatus PC-12 authorized release documentation records review
This review checks that every component installed on a Pilatus PC-12 carries the release paperwork a buyer or authority would ask for and that the paperwork matches the installation record. A records specialist runs it for an owner or buyer who needs the component release file to hold under a dual-jurisdiction sale. It reads each FAA Form 8130-3, EASA Form 1, and dual-release tag against the part it covers, confirms the release fits the installation, and finds components fitted without a certificate on file. You receive an exception list per component, a source map from each installed part to its release, and a plan to recover the missing tags.
When this review is needed
- A PC-12 is selling across the FAA and EASA systems and each installed part needs a release the receiving side accepts.
- A component was fitted during owner-managed maintenance and its release tag was never filed with the aircraft records.
- A buyer's diligence found a serialized part on the aircraft with no certificate behind it.
- A dual-release was expected for a part that will move between registers and only a single-authority tag is on file.
The problem
A PC-12 accumulates components through owner-directed maintenance where the release tag often stays with the shop rather than the aircraft file. A part can be correctly installed and airworthy yet arrive at a sale with no 8130-3 or Form 1 to prove its provenance, and a single-authority release on a part destined for the other register forces rework at exactly the wrong moment. The installation record and the release drift apart when they are filed in different places by different hands.
What gets reviewed
- Each installed serialized component checked for a release certificate on file
- FAA Form 8130-3 and EASA Form 1 read against the part and serial they cover
- Dual-release tags confirmed where the part will move between the two registers
- Release paperwork matched to the installation record for the same part and event
- Certificates checked for the fields an auditor relies on: part number, serial, and authorizing reference
- Components fitted during owner-managed work checked for a filed release rather than a shop-retained one
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 installed serialized part has a release certificate present in the aircraft file
- The part number and serial on the release match the installation record for that part
- A part destined to cross registers carries a dual-release rather than a single-authority tag
- The certificate fields an auditor cites are complete and legible, not cut off or blank
- The release covers the same maintenance event the installation record describes
Evidence normally required
- The component release file with the 8130-3 and Form 1 certificates on hand
- The installation records for the serialized components on the aircraft
- The component list or configuration reference identifying what is fitted
- Shop-visit and work-order records that would name the release for a fitted part
- Any records standard the sale requires the releases to satisfy
Common discrepancies
- A serialized component installed with no release certificate in the aircraft file
- A single-authority release on a part that will move to the other register
- A release whose serial number does not match the part actually installed
- A certificate with the authorizing reference field blank or cropped off the scan
What is at stake
A component without acceptable release paperwork loses provenance and can stall a cross-border sale until the tag is recovered or the part is replaced. Recovering a release from a shop that has since closed or changed hands is slow, and a buyer working under a records standard can reject the part outright, turning a paperwork gap into a physical removal the owner funds.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
List the components
Identify every serialized part fitted to the aircraft from the configuration reference.
Match to releases
Pull the 8130-3 or Form 1 for each and confirm the part and serial agree with the installation record.
Test the register fit
Check that parts crossing registers carry a dual-release rather than a single-authority tag.
Flag the gaps
List missing, mismatched, or single-authority releases and map the confirmed ones.
What the buyer receives
- An exception list per component where the release is missing or mismatched
- A source map from each installed part to its release certificate
- A closure plan to recover the missing tags or obtain the release the sale requires
Who uses the output
- Asset managers gauging the provenance the component file can defend
- Records teams recovering the missing release tags from the responsible shops
- Diligence teams confirming each part carries a release the receiving register accepts
How the work fits into the transaction or program
The release review confirms the provenance layer that LLP trace and configuration status both rely on. It runs before a cross-border sale so a missing or single-authority tag is found while the responsible shop can still supply it, and its exception list feeds the recovery effort ahead of diligence.
Aircraft-specific considerations
PC-12 components are frequently changed under owner-managed maintenance, where a shop hands the aircraft back with the part fitted but keeps its own copy of the release. That custody pattern is why the release file often lags the installed configuration, and it drives which parts the review checks first for a filed certificate.
Jurisdiction-specific considerations
A PC-12 moving between an FAA registration and an EASA member state needs releases the receiving authority will accept, which for a part crossing registers usually means a dual-release rather than a single-authority tag. The review flags where the release file was built to one system and will need dual-release recovery for the other.
Regulatory limits
The review confirms release paperwork is present, complete, and matched to installation, and flags where it is not. It does not issue a release certificate, approve any maintenance, or determine that a part or the aircraft is airworthy.
What this review does not cover
- Issuing or reissuing any release certificate
- Physical inspection of the installed components
- Any airworthiness determination on a part or the aircraft
Specific to this review
- On an owner-managed PC-12 the release tag often stays with the shop, so a correctly installed part can reach a sale with no certificate in the aircraft file.
- A single-authority release is not a defect until the part has to cross registers, at which point it forces either dual-release recovery or removal.
- A release with a blank authorizing-reference field cannot be relied on even when the part number and serial are correct.
Sources
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
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
The part is installed and flying. Why does the missing tag matter?
Installation confirms the part is on the aircraft, not where it came from. Provenance for a serialized part rests on its release, and without an 8130-3 or Form 1 on file a buyer or the receiving register may not accept it regardless of its physical condition.
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.