King Air release docs
Beechcraft King Air authorized release documentation records review
This review checks the authorized release documents held for a Beechcraft King Air against the installations they are supposed to support. It is run for owners and buyers who need to know that each installed part carries a valid release, not a certificate for a different part or a form filled in wrong. It walks the component release file, matching FAA Form 8130-3, EASA Form 1, and dual-release certificates to the installation records that put each part on the aircraft. You receive a supported exception list of installs with missing or mismatched releases, a source map linking each certificate to its install, and a closure plan.
When this review is needed
- A King Air is under purchase and every installed part's release needs confirming before closing.
- A component was replaced and the review must confirm its release matches the install record.
- The aircraft crossed registers and dual-release status on key parts must be verified.
- A release file was inherited and no one has matched its certificates to actual installations.
The problem
A release file looks reassuring because it is thick with 8130-3 and Form 1 certificates, but a stack of forms is not the same as a valid release for each part actually on the aircraft. A certificate may be for a batch that includes the part but not name its serial, a Form 1 may lack the dual-release block the current register needs, or the install record and the release describe different part numbers. The file answers the question of whether releases exist, not whether the right release covers the right install.
What gets reviewed
- The component release file against the aircraft's installed configuration
- FAA Form 8130-3 certificates matched to the installs they support
- EASA Form 1 certificates and their dual-release status where the register requires it
- Serial and part-number agreement between each release and its install record
- Installation entries confirming each released part was actually fitted to this aircraft
- Release forms checked for completeness, block accuracy, and authorized signatures
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 part has a release certificate that names its part number and serial
- FAA Form 8130-3 blocks are complete and identify the correct approval basis for the install
- EASA Form 1 dual-release is present where the current register requires it
- The install record and the release describe the same part, not similar ones
- Release signatures and approval references are valid and from an authorized source
Evidence normally required
- The component release file with its 8130-3 and Form 1 certificates
- Installation records and work orders that fitted each part
- The aircraft's installed configuration and part-number list
- Register and dual-release requirements for the current registration
- Any prior notes on missing or disputed release documents
Common discrepancies
- A release certificate covering a batch but not naming the installed part's serial
- An EASA Form 1 without the dual-release block the current register requires
- An install record and its release certificate citing different part numbers
- A release form with an incomplete block or an unverifiable signature
What is at stake
An installed part without a valid release for its serial cannot be shown to have entered service properly, and a careful buyer treats it as suspect. The gap becomes the seller's problem in diligence or the operator's problem at an audit, when a part that has flown for years turns out to rest on a certificate that never covered it. Reconstructing a release long after the shop closed is often impossible, so the value simply drops.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Map installs to the release file
List the installed parts and locate the release certificate claimed for each in the component release file.
Match part and serial
Confirm each release names the installed part number and serial and describes the same item as the install record.
Check form and register validity
Verify block completeness, signatures, and dual-release status against the register the aircraft is on now.
Deliver exceptions and closure
Report the installs with missing or mismatched releases and a plan to source or resolve each one.
What the buyer receives
- A supported exception list of installs lacking a valid, matching release
- A source map linking each release certificate to its installation record
- A closure plan to source the missing releases or resolve the mismatches
Who uses the output
- Asset managers confirming installed parts carry defensible releases before a trade
- Continuing-airworthiness staff checking release validity for the current register
- Records teams reconciling an inherited release file against the install records
How the work fits into the transaction or program
The release review sits alongside the LLP and repair reviews, since a part's traceability and its release evidence answer different questions about the same install. It confirms every fitted part entered service on a valid certificate, so the configuration the operator maintains and the buyer prices rests on releases that actually cover what is on the aircraft.
Aircraft-specific considerations
King Airs accumulate avionics upgrades and special-mission installations over long service lives, and each of those brings components whose releases have to match a modification rather than the base type. Owner-operator continuity keeps the file together but also means older releases predate current form standards, so the review reads them for the standard in force when they were issued. Engine and propeller changes across the aircraft's life introduce dual-release questions whenever a part crossed between FAA and EASA maintenance.
Jurisdiction-specific considerations
A part installed on an FAA-registered King Air is released on FAA Form 8130-3, while an EASA-registered aircraft expects EASA Form 1, and a part that must serve either carries a dual release. The review checks each release against the register the aircraft is on now, since a certificate acceptable when the part was installed may not carry the dual-release the current registration requires.
Regulatory limits
This work verifies release documents against the installations they support and reports the exceptions. It does not issue a release certificate, approve a part for installation, or make an airworthiness determination. Issuing an authorized release stays with the approved organization and its authority.
What this review does not cover
- Issuing or re-issuing an authorized release certificate
- Approving a part for installation or return to service
- Physical inspection to confirm the installed part's identity
Specific to this review
- A thick release file proves certificates exist, not that each install has a release naming its serial, so the review matches parts to certificates rather than counting forms.
- Batch releases are a frequent King Air defect: the form covers a lot that includes the part but never identifies the specific serial fitted.
- A release that was valid at install can fail the current register's dual-release requirement after the aircraft changes authority, so each certificate is read against the register in force now.
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
Is a batch 8130-3 enough for a specific installed part?
Only if it identifies the installed serial. A batch certificate that names a lot but not the specific part fitted leaves the install without a serial-level release, so we flag it as an exception and plan closure by locating the certificate or record that names the actual part.
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.