Skip to content

Authorized release

Boeing 737NG authorized release documentation records review

This review checks the authorized release documents in a Boeing 737NG's component file for validity and for a clean match to the installation each supports. It is run by or for the party taking on the aircraft, where a component's acceptability rests on the paperwork that released it. It examines FAA Form 8130-3 and EASA Form 1 completeness, the basis for any dual release, and whether each certificate matches the part and installation record it is filed against. You receive a release-validity view, a list of components with defective or mismatched certificates, and the installation records that do not reconcile to a release.

When this review is needed

  • A 737NG is transferring and installed components have to carry release paperwork the receiving side will accept.
  • A component was installed against a certificate whose form fields are incomplete or unsigned.
  • Parts moved between FAA and EASA systems and the dual-release basis needs to be confirmed.
  • An installation record cannot be matched to any release document in the component file.

The problem

A release certificate looks like a formality until a downstream buyer or authority rejects one. On a 737NG, components installed across a long service life carry a stack of FAA Form 8130-3 and EASA Form 1 certificates, and some have blank required fields, cite an approval basis that does not fit the work, or belong to a part number the installation record does not match. A certificate that fails on inspection can strand the component that depends on it, and the problem surfaces exactly when the aircraft is under scrutiny.

What gets reviewed

  • FAA Form 8130-3 and EASA Form 1 certificates checked for completeness and required signatures
  • The dual-release basis where a certificate carries both FAA and EASA acceptance
  • Each certificate matched to the part number and serial number of the installed component
  • Installation records reconciled to a supporting release document
  • Certificates citing an approval basis appropriate to the work released
  • Components in the file whose release cannot be located or reconciled

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 has its required fields completed and signed
  • A dual-release certificate states a basis valid under both systems it claims
  • The part number and serial number on the certificate match the installation record
  • The approval basis cited on the certificate fits the maintenance actually released
  • Every installed component reconciles to a retrievable release document

Evidence normally required

  • The component release file with its FAA Form 8130-3 and EASA Form 1 certificates
  • Installation records for the components in the file
  • Part number and serial number references for the installed units
  • Any dual-release approvals relied on for the components
  • The maintenance records that each release is meant to support

Common discrepancies

  • A release certificate with a required field blank or a missing authorizing signature
  • A dual-release claim not supported by a basis valid under both systems
  • A certificate whose part or serial number does not match the installation record
  • An installed component with no release document in the file at all

What is at stake

A component whose release certificate is defective or mismatched may be treated as unacceptable by a buyer or an authority, which can force removal and replacement of a serviceable part purely on paperwork. An installation with no traceable release behind it is worse, because reconstructing the certificate long after the work leaves the owner chasing a shop that may no longer exist.

Move from findings to resolution

Move from findings to a documented resolution path.

How the work runs

01

Check each certificate

Confirm the release documents are complete, signed, and cite a basis that fits the work released.

02

Test the dual-release basis

Where both systems are claimed, verify the certificate states a basis valid under each.

03

Match to installation

Reconcile every certificate's part and serial number to the installation record it supports.

04

Report the exceptions

List defective, mismatched, and missing releases, and the installations that cannot be reconciled.

What the buyer receives

  • A release-validity view separating clean certificates from defective ones
  • A list of components with mismatched or missing release documents
  • The installation records that do not reconcile to a release, each identified

Who uses the output

  • Asset managers assessing the paperwork exposure on installed components
  • Continuing-airworthiness teams confirming release acceptability before program entry
  • Records teams recovering missing certificates while the source shop is still reachable

How the work fits into the transaction or program

The release review supports the broader component and traceability read on an incoming 737NG, since a life-limited or rotable part's standing depends on the certificate that released it. Its list of defective or missing releases drives recovery from the shops and prior operators that issued them, before the acceptability of a component becomes a hold at the next transfer.

Aircraft-specific considerations

A 737NG accumulates release documents across engine, APU, and rotable component changes over a long life, and the mix of FAA and EASA acceptance across successive operators makes dual-release validity a frequent question. Components changed during airline-program maintenance are where a certificate most often cites a basis that no longer fits the installation it is filed against.

Jurisdiction-specific considerations

A component released under one authority may need acceptance under the other when the aircraft changes register or operator, and a dual-release certificate is only as good as the basis it states under each system. The review notes where a release accepted on the current register will be questioned by a receiving authority.

Regulatory limits

The review assesses the validity and match of the release documents on file. It does not issue a release certificate, approve a component for installation, or make an airworthiness determination on any installed part.

What this review does not cover

Specific to this review

  • A serviceable component can be stranded purely by a defective certificate, because acceptability rests on the paperwork rather than the part's condition.
  • A dual-release certificate is only valid if it states a basis good under both systems, and one that carries a single authority's basis fails when the second is tested.
  • An installation with no release behind it is the hardest gap to close, since the certificate has to be reconstructed from a shop that may no longer hold the record.

Sources

Frequently asked questions

Why does a certificate problem matter if the component is serviceable?

Acceptability rests on the release paperwork, not just the part's condition. A buyer or authority can treat a component with a defective or mismatched certificate as unacceptable, which can force removal of a sound part. Finding those certificates early lets them be corrected or reconstructed while the source is reachable.

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.