Release certificates
Boeing 787 family authorized release documentation records review
This review checks the authorized release documentation behind the installed components on a specific Boeing 787, confirming that each part carries a valid release certificate and that the certificate ties to its installation. It is run for a lessor, operator, or buyer who needs the component release file to hold up under an FAA and EASA transaction. The work verifies FAA Form 8130-3 and EASA Form 1 certificates, checks dual-release status where the register demands it, and ties each certificate to the installation record that put the part on the aircraft. You receive a reconciled release file, a supported exception list, and a closure plan for this tail.
When this review is needed
- A 787 is being transacted across the FAA and EASA systems and dual-release status must be confirmed.
- A component was installed with a release certificate that needs matching to its installation record.
- A lease return requires each installed part to show a valid release traceable to the aircraft.
- A records set shows release certificates that need checking for form validity and correct issuance.
The problem
Release certificates are easy to collect and hard to make consistent. A Form 8130-3 is in the file but for a part number one revision off what is installed. An EASA Form 1 covers the component but the aircraft is heading to an FAA register that wants dual release the certificate does not show. A certificate is present but the installation record that connects it to the aircraft is missing, so the paper proves the part was released, not that it was fitted here. The release file looks thick and still fails on the joins.
What gets reviewed
- Each installed component checked for a valid release certificate at the correct part number
- Form 8130-3 and EASA Form 1 certificates verified for form validity and correct issuance
- Dual-release status confirmed where the destination register requires it
- Each certificate tied to the installation record that fitted the part to the aircraft
- Certificate revisions matched to the installed configuration
- Modification and STC parts checked for release consistent with their approval basis
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 component has a release certificate matching the installed part number
- Form 8130-3 and EASA Form 1 certificates are valid in form and correctly issued
- Dual release is present where the destination register requires it
- Each certificate ties to an installation record placing the part on this aircraft
- STC and modification parts carry release consistent with their approval basis
Evidence normally required
Common discrepancies
- A release certificate for a part number one revision off what is installed
- A single-release certificate on a part heading to a register that requires dual release
- A valid certificate with no installation record tying the part to this aircraft
- An STC part released against data inconsistent with its approval basis
What is at stake
A component whose release cannot be matched to its installation is treated as unsubstantiated, and on a transaction that can mean removing and re-releasing the part or discounting the aircraft. A missing dual release surfaces at the register change, when the receiving authority will not accept a single-release certificate, and the fix arrives too late to avoid a delay. The release file is where a clean-looking data room quietly fails a detailed read.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the installed parts
List the components whose release must be shown and pull their certificates and installation records for the tail.
Validate each certificate
Check form validity, correct issuance, and part-number match for every Form 8130-3 and EASA Form 1.
Tie release to fitment
Match each certificate to the installation record and confirm dual release where the destination requires it.
Report and sequence
Deliver a reconciled release file and a plan to recover missing certificates and bridging releases.
What the buyer receives
- A reconciled release file matching each component to a valid, correctly issued certificate
- A supported exception list where release or installation cannot be traced
- A closure plan sequencing the missing certificates and dual releases for this tail
Who uses the output
- Asset managers confirming component provenance before a cross-register transaction
- Records teams aligning certificates with installation records and part numbers
- Continuing-airworthiness staff resolving dual-release gaps ahead of a register change
How the work fits into the transaction or program
The release-document review sits alongside the LLP and configuration checks and supplies the certificate evidence they depend on. Because the same certificates prove both component provenance and life-limited part history, this work is usually run with the LLP review, and its output feeds the export package where the receiving authority scrutinizes release status.
Aircraft-specific considerations
A 787 records set carries stronger configuration and systems-document emphasis, including software part numbers, electrical changes, and composite repair substantiation. Release documentation on this aircraft has to keep pace with part-number-driven configuration, so the review matches each certificate to the installed revision and checks that electrical and systems components released under a modification tie back to that modification's approval basis.
Jurisdiction-specific considerations
Because the audiences span FAA and EASA registers, dual-release status is a central check. A part released only under one system may not be accepted by the other on a register change, so the review confirms which release each destination requires and flags single-release parts that will need a bridging release before transfer.
Regulatory limits
This review reports whether installed components carry valid release documentation matched to their installation. It does not release any part to service, issue or reissue a certificate, or make an airworthiness determination on the aircraft.
What this review does not cover
- Issue or reissue of any release certificate
- Physical removal, inspection, or re-release of components
- Preparation of new approval data for a modification or STC part
Specific to this review
- The most frequent release defect is a part-number mismatch of one revision between the certificate and the installed part.
- A certificate without an installation record proves release but not fitment, which is the join a detailed read attacks first.
- Single-release parts are the ones that fail a register change, because the receiving authority will not accept a certificate issued only under the other system.
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
Why does a valid certificate still fail the review?
A certificate can be valid on its own and still not prove the part is correctly installed here. If it is for a different part-number revision, lacks the dual release a destination register requires, or has no installation record tying it to this aircraft, it fails the join between release and fitment, which is what this review checks.
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.