Skip to content

777 family release evidence

Boeing 777 family authorized release documentation review

This review checks that installed components on a Boeing 777 family aircraft carry the release paperwork a buyer or auditor will demand, and that each certificate ties to the part actually fitted. It is run for a lessor, airline, or manager evaluating, transferring, or holding a specific tail. The work reads the component release file against FAA Form 8130-3, EASA Form 1, dual-release certificates, and the installation entries behind them. You receive a supported exception list, a source map linking each component to its release evidence, and a closure plan for the serial number under review.

When this review is needed

  • A 777 is heading to redelivery and each installed rotable must show a release certificate that matches the part.
  • A component was changed at line or base and the installation entry has no release form filed behind it.
  • The aircraft will move between an FAA and an EASA register and the release basis has to satisfy the receiving system.
  • A diligence team flagged missing release paperwork and the file has to be reconciled before the deal moves.

The problem

A release certificate proves a part was returned to service by an authorized source, and on a widebody the installed rotables run into the hundreds. A form that names a different serial number than the part fitted, or an installation entry with no certificate behind it at all, breaks the chain that a buyer relies on. These mismatches accumulate quietly across shop visits and line changes and only surface when someone reconciles the file against the aircraft.

What gets reviewed

  • The component release file reconciled to the parts actually installed on this serial number
  • FAA Form 8130-3 and EASA Form 1 certificates matched to part and serial numbers
  • Dual-release certificates confirmed for components crossing FAA and EASA acceptance
  • Installation entries checked against a corresponding release for each changed rotable
  • Release evidence for engine and landing-gear components that carry their own paperwork
  • Certificates issued by the correct approved source for the class of work

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 release certificate names the same part and serial number as the component installed
  • Every installation entry in the records has a corresponding release form on file
  • Dual-release forms show both the FAA and EASA acceptance the register change will need
  • The issuing source on each certificate is authorized for the work the form covers
  • Superseded or duplicate release forms are removed so no two describe the same installation differently

Evidence normally required

  • The component release file and installation records for the tail
  • FAA Form 8130-3 and EASA Form 1 certificates for installed rotables
  • Shop-visit reports showing components returned to service
  • The list of components installed at the last several line and base events
  • Any records standard the release evidence must satisfy for the receiving register

Common discrepancies

  • A release certificate whose serial number does not match the part recorded as installed
  • An installation entry with no release form filed behind it
  • A component released under one authority when the deal requires dual release
  • A certificate issued by a source not authorized for the class of work it describes

What is at stake

A component without acceptable release evidence may have to be removed and re-released, or its value discounted until the paperwork is found. On a register change, a part released only under one authority can stall acceptance until the basis is reconstructed, and reconstructing a certificate from a shop that has moved on is slow and sometimes impossible.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Assemble the release file

Collect the certificates and installation entries the records hold for the serial number.

02

Match forms to parts

Confirm each certificate names the same part and serial as the component installed.

03

Check the acceptance basis

Verify the issuing source and confirm dual-release where the register change requires it.

04

List the exceptions

Flag missing, mismatched, or single-authority forms and sequence the recovery.

What the buyer receives

  • A supported exception list of components whose release evidence is missing or mismatched
  • A source map linking each installed component to its release certificate
  • A closure plan sequencing which certificates to recover before the next milestone

Who uses the output

  • Records teams clearing release gaps before a redelivery binder is assembled
  • Asset managers pricing components whose paperwork is incomplete
  • Buyers confirming each installed part traces to an acceptable release before closing

How the work fits into the transaction or program

Release evidence is the layer diligence checks first and redelivery depends on, so this review runs before the binder is built or the register changes. The exception list drives certificate recovery while the shops that issued the paperwork can still be reached, and the source map becomes the reconciliation a counterparty accepts.

Aircraft-specific considerations

A 777 that has operated across FAA and EASA fleets often carries a mix of Form 8130-3 and Form 1 release evidence, and dual-release becomes the pinch point when the tail moves register. High-value rotables and engine build components dominate the release file, so those are reconciled first, and the volume of installed parts on a widebody means the review is scoped to the serial number's actual change history rather than a generic checklist.

Jurisdiction-specific considerations

FAA and EASA accept each other's release forms under specific conditions, and a component released only under one system may need dual-release evidence before the other register will accept it, which is exactly where a 777 changing register tends to stall.

Regulatory limits

The review reconciles the release evidence the records hold against the parts installed. 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 re-issuing any release certificate
  • Physical inspection of installed components
  • Any airworthiness determination on a part or the aircraft

Specific to this review

  • A serial-number mismatch between a certificate and the installed part is more common than an outright missing form, and it is easy to miss on a quick scan.
  • On a register change, dual-release is the recurring blocker because a part accepted under one authority is not automatically accepted by the other.
  • The volume of installed rotables on a widebody means release gaps concentrate at the busiest line stations rather than the base checks.

Sources

Frequently asked questions

What if a part is installed but the release certificate is missing?

The component is flagged and the certificate is requested from the shop or operator that returned the part to service. Where the form cannot be recovered, the item is carried as a documented exception so the buyer sees it rather than discovering it later.

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.