Skip to content

Release certificates

Gulfstream G650 authorized release document records review

This review confirms that the components installed on a Gulfstream G650 carry the authorized release paperwork a buyer, lessee, or auditor will require. It is run by or for the party evaluating or transferring a specific G650, usually as part of pre-sale diligence or a lease return. A records specialist checks that each installed unit has a valid FAA Form 8130-3, EASA Form 1, or dual-release certificate, and that the certificate matches the part fitted and the installation entry. You receive an exception list of components without acceptable release, a source map tying each certificate to its installation, and a closure plan for the missing paperwork.

When this review is needed

  • A G650 is entering diligence and the buyer expects a release certificate behind every serialized component.
  • A lease return binder is being assembled and each installed rotable needs its 8130-3 or EASA Form 1 attached.
  • A component was fitted at a shop whose paperwork practice differs from the aircraft's home register.
  • An audit flagged installed parts whose release evidence is missing, illegible, or does not match the part.

The problem

A component on a G650 is only as transferable as the certificate that released it, and on a managed jet those certificates come from many shops over the aircraft's life, in FAA and EASA formats that do not always cross cleanly. A rotable with a strong overhaul history but a missing or mismatched release certificate stalls at diligence, because the buyer cannot rely on the installation without the paper that authorized it.

What gets reviewed

  • Each serialized component checked for a valid FAA Form 8130-3, EASA Form 1, or dual-release certificate
  • Release certificates matched to the part number and serial number of the installed unit
  • Certificates reconciled with the installation entry in the maintenance record
  • Dual-release evidence confirmed where a part crossed between FAA and EASA systems
  • Legibility and completeness of each certificate checked against the receiving authority's expectation
  • Components without acceptable release logged with the shop and event that should hold the paperwork

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 carries a release certificate valid for the receiving authority
  • The part and serial number on the certificate match the unit recorded as installed
  • The installation entry references the release document that authorized the fitment
  • Dual-release is present where the component moved between FAA and EASA oversight
  • Certificates are legible and complete rather than partial scans or unsigned copies

Evidence normally required

  • The component release file for the installed rotables and serialized parts
  • FAA Form 8130-3 and EASA Form 1 certificates on file
  • Installation records and work orders tying each part to its fitment
  • The component and configuration list for the serial number
  • Any records standard the transaction or lease return must satisfy

Common discrepancies

  • A rotable installed against a release certificate for a different serial number
  • An installation entry with no reference to the certificate that authorized the fitment
  • A part that crossed from EASA to FAA oversight without the dual-release the receiving side needs
  • A release document present only as an unsigned or image-only copy that diligence cannot cite

What is at stake

A component without acceptable release evidence is treated as unsupported, which can force its removal and replacement with a traceable unit before a sale closes. Reconstructing a certificate after the shop has moved on is slow and sometimes impossible, so the exposure sits on the asset and reappears at the next transfer with the same shop even harder to reach.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

List the installed components

Assemble the serialized rotables and parts from the configuration and component list.

02

Match certificate to unit

Confirm each part carries a release document whose serial number matches the installation.

03

Check cross-system acceptance

Verify dual-release where a component moved between FAA and EASA oversight.

04

Flag the gaps

Log each component without acceptable release and the shop that should hold the paper.

What the buyer receives

  • An exception list of installed components lacking acceptable release evidence
  • A source map tying each certificate to its part, serial number, and installation entry
  • A closure plan identifying the shop and event that should hold each missing certificate

Who uses the output

  • Records teams assembling the release binder a buyer or lessee will audit
  • Asset managers deciding which unsupported components must be swapped before closing
  • Diligence teams verifying installed configuration against release evidence rather than assertion

How the work fits into the transaction or program

The release review runs alongside the configuration and component checks in diligence, confirming that what the records say is installed is also authorized to be there. Its exception list feeds remediation so certificates can be recovered before closing, and the completed release file becomes part of the data room the transaction rests on.

Aircraft-specific considerations

Because a G650 is usually managed rather than airline-operated, its components pass through a mix of manufacturer, dealer, and independent shops, each releasing on its own authority. Cabin and avionics upgrades common on this type add serialized units whose release paperwork can lag the installation, so the review pays close attention to the release evidence behind owner-driven configuration changes.

Jurisdiction-specific considerations

A G650 moving between an FAA register and an EASA register needs release evidence the receiving authority will accept, and a component released only under one system may require dual-release before it is acceptable on the other. The review flags each installed unit whose certificate will not satisfy the destination register.

Regulatory limits

The review confirms that acceptable release evidence exists and matches the installed part. It does not issue or reissue a release certificate, approve an installation, or make an airworthiness determination on any component.

What this review does not cover

  • Physical inspection or functional test of any installed component
  • Issuing or reissuing a release certificate for an unsupported unit
  • Approving the installation of a component whose paperwork is incomplete

Specific to this review

  • A component's transferability is set by its release certificate, so a strong overhaul history behind a missing 8130-3 still stalls a sale.
  • Dual-release is where FAA and EASA files most often break, because a part released under one system is not automatically acceptable to the other.
  • Image-only or unsigned certificate copies slow diligence even when the release genuinely happened, because a buyer cannot cite them.

Sources

Frequently asked questions

Why does a valid overhaul not settle the release question on its own?

An overhaul restores the part, but the release certificate is what authorizes it back into service and lets a buyer rely on it. Without the certificate matching the installed serial number, the work is undocumented for transfer purposes even if it was performed correctly.

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.