Global 7500 releases
Bombardier Global 7500 authorized release documentation review
This review checks the authorized release documentation behind the components installed on a Bombardier Global 7500, confirming each release certificate is valid and matches its installation. It is run for an owner, lessor, or management provider who needs the component release file settled before a transaction or a registry change. The work examines FAA Form 8130-3 and EASA Form 1 certificates, confirms dual-release coverage where the destination requires it, and ties each release to the installation record it supports. You receive a release-file status per component, an exception list for invalid or missing certificates, and a closure plan.
When this review is needed
- A transaction is opening and the buyer will check release certificates against the installations.
- A registry change requires dual-release coverage the current certificates may not provide.
- Components were installed across several shops and the release paperwork was never reconciled.
- A release certificate is relied on but its validity and installation match have never been confirmed.
The problem
A component is only as installable as its release paperwork. On a Global 7500, serialized components arrive from shops on FAA Form 8130-3 or EASA Form 1, and each certificate has to be valid on its face, cover the right part and serial number, and match the installation it supports. In practice certificates go missing, name a superseded part number, lack a signature block, or provide single release where the aircraft's registry needs dual release. Those defects sit quietly in the file until a buyer or a receiving authority reads the certificates line by line.
What gets reviewed
- Each installed serialized component matched to a release certificate
- FAA Form 8130-3 and EASA Form 1 certificates checked for validity on their face
- Dual-release coverage confirmed where the registry or destination requires it
- Part and serial numbers on the certificate reconciled to the installation record
- Release status confirmed against removal and installation history
- Certificates for superseded or reworked parts checked for currency
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 valid on its face
- Part and serial numbers on the certificate match the installation record
- Dual release is present where the receiving registry requires it
- Signature, authorization, and reference blocks on the certificate are complete
- The release ties to the removal and installation history for the component
Evidence normally required
- The component release file with FAA Form 8130-3 and EASA Form 1 certificates
- Installation and removal records for serialized components
- The configuration and equipment list for installed components
- Shop-visit packages behind the released components
- The registry and any destination requirements for release coverage
Common discrepancies
- An installed component with no release certificate in the file
- A certificate naming a part or serial number that does not match the installation
- A single-release certificate where the receiving registry requires dual release
- A release certificate with an incomplete signature or authorization block
What is at stake
An installed component without valid release documentation is a component a buyer cannot rely on and a receiving authority may not accept. It can force removal and reinstallation with correct paperwork, a fresh release, or a hold on the transaction. Where dual release was needed but not obtained, the component may be acceptable on one registry and not the one the aircraft is moving to, which surfaces exactly at the transfer.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Pull the release file
Assemble the FAA Form 8130-3 and EASA Form 1 certificates for installed serialized components.
Check each certificate
Confirm validity, completeness, and the release coverage the registry requires.
Match to installation
Reconcile part and serial numbers on the certificate against the installation record.
List the exceptions
Flag missing, invalid, or mismatched releases and plan how each is corrected.
What the buyer receives
- A release-file status per installed component
- An exception list for invalid, missing, or mismatched certificates
- A closure plan to obtain or correct the release evidence
Who uses the output
- Asset managers confirming the component file supports the transaction
- Records teams reconciling release paperwork before a registry change
- Buyers and receiving authorities checking release coverage for installed parts
How the work fits into the transaction or program
The release-document review sits at the component level beneath the configuration and LLP work, confirming that each installed part rests on valid paperwork. Its status feeds the export package and the redelivery binder, and its exception list drives the effort to obtain or correct release certificates before a buyer or an authority reads the file.
Aircraft-specific considerations
The Global 7500 carries integrated avionics and cabin management components whose releases come from a mix of shops during production and in service, so the release file blends original and replacement paperwork of varying form. That mix is where dual-release gaps most often appear, and the review is scoped to the components most likely to move between FAA and EASA acceptance rather than every routine consumable.
Jurisdiction-specific considerations
Whether a single or dual release is acceptable depends on the registry the aircraft is on and the one it is moving to. The review confirms each certificate provides the release coverage the receiving system requires, so a component is not left acceptable under the current registry but unsupported for the destination.
Regulatory limits
The review confirms the release documentation is valid and matches the installations. It does not issue a release certificate, grant any approval, or determine that a component or the aircraft is airworthy.
What this review does not cover
- Issuing or reissuing any release certificate
- Physical inspection or functional check of the components
- Any airworthiness determination on the components or the aircraft
Specific to this review
- A release certificate can be valid yet still fail to support an installation if its part or serial number does not match what is fitted.
- Dual-release gaps surface at a registry change, because a single release acceptable on one system may not satisfy the one the aircraft is moving to.
- On a Global 7500, the mix of original and replacement release paperwork across integrated systems is where certificate defects concentrate.
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
What is the difference between a single and a dual release, and why does it matter here?
A dual release certifies the component under both FAA and EASA acceptance, while a single release covers one. It matters because a component released under one system may not be acceptable on the registry the aircraft is moving to, and the review confirms the release coverage matches the destination before that gap surfaces at transfer.
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.