767 release documents
Boeing 767 family authorized release documentation records review
This review checks that the components installed on a Boeing 767 carry the authorized release paperwork a buyer or auditor will demand. It is run for a lessor, airline, or asset manager working a specific 767 tail through a transaction or a records clean-up. The work matches each release certificate, FAA Form 8130-3 or EASA Form 1, to the part it accompanies and confirms the installation entry that puts it on the aircraft. You receive a component-by-component status of the release file, an exception list for units missing or mismatched paperwork, and a closure plan for the gaps.
When this review is needed
- A 767 is heading into diligence and each rotable needs a release certificate the buyer will accept on its face.
- A component was installed without the 8130-3 traveling with it and the installation entry now has to be reconciled.
- The tail will move to an EASA register and single-release FAA paperwork has to be checked for dual coverage.
- A records archive holds release certificates that were never matched to the parts on the current configuration.
The problem
A component is only as saleable as the paperwork that releases it. On a 767 with decades of component changes, the release file is a stack of forms that has to line up part number, serial, and installation date against what is actually fitted. A form that names a superseded serial, or a unit installed with no form at all, reads fine in a folder count but fails the moment a buyer cross-checks it against the configuration.
What gets reviewed
- Release certificates on file matched to the installed component by part and serial
- FAA Form 8130-3 and EASA Form 1 coverage for each rotable and time-controlled unit
- Dual-release status where the tail sits across FAA and EASA acceptance
- The installation entry linking each release to its return to service
- Components fitted with no release document identified as open items
- Superseded or duplicate certificates reconciled so the file is not self-contradictory
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's release certificate names the part number and serial actually fitted
- The release form's authorizing statement is appropriate to the work and the jurisdiction
- Every release ties to an installation entry that returns the component to service on the aircraft
- Dual-release coverage exists where the receiving register will require it
- No two certificates in the file contradict each other on the same component
Evidence normally required
Common discrepancies
- A rotable installed with no release certificate in the file
- A release form naming a serial superseded by a later component change
- Single-release FAA paperwork on a unit the receiving register wants dual-released
- An installation entry with no release document behind the return to service
What is at stake
A rotable without acceptable release paperwork is discounted or rejected at diligence, and on a register change a form that lacks dual release can block acceptance until it is reissued or supported. Chasing the original release long after installation is slow and sometimes dead-ends at a shop that has closed, so the exposure hardens into the asset.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
List the configuration
Pull the installed-component list with part numbers and serials for the tail.
Match release to part
Tie each 8130-3 or Form 1 to the component it accompanies and the installation entry behind it.
Check jurisdiction coverage
Confirm dual release where the current or receiving register requires it.
Flag the gaps
List units with missing, mismatched, or single-release paperwork and the source that can close each.
What the buyer receives
- A component-by-component status of the release file against the configuration
- An exception list for units missing, mismatched, or single-released paperwork
- A closure plan identifying the shop or source that can reissue each missing release
Who uses the output
- Asset managers confirming the components will survive a buyer's cross-check
- Records teams matching a release archive to the installed configuration
- Continuing-airworthiness staff preparing the file for a register change
How the work fits into the transaction or program
Release paperwork underpins every installed component's standing, so this review feeds the configuration and traceability work that a transaction or register change depends on. The exceptions it produces route into remediation while the issuing shops can still be reached, before the file goes to a buyer.
Aircraft-specific considerations
A 767 that has served two or three decades has cycled through many component changes, so its release file is large and layered with superseded paperwork. Freighter-converted tails add a batch of release documents from the conversion, and long service life means some releases predate the current record system and sit only on paper.
Jurisdiction-specific considerations
The release form that satisfies an FAA operator is not automatically accepted by an EASA CAMO, and a 767 moving between the two systems has to show dual release or supporting evidence on affected components. The review flags where single-release paperwork will need reissue or a supplementary form for the receiving authority.
Regulatory limits
The review confirms that release paperwork is present, matched, and internally consistent. It does not issue or reissue a release certificate, approve the underlying maintenance, or determine that a component is airworthy.
What this review does not cover
Specific to this review
- A component's resale standing rests on its release paperwork, so a strong unit with a missing 8130-3 is treated as unsupported until the form is found.
- Register changes are where single-release FAA paperwork most often stalls, because an EASA CAMO expects dual release on affected units.
- On a long-served 767 the oldest releases predate the current digital file and exist only on paper in an archive.
- A serial that changed at a later component swap can leave an earlier valid release pointing at a part no longer fitted.
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 counts as acceptable release paperwork on a 767 component?
A release certificate that names the part number and serial actually installed, carries an authorizing statement appropriate to the work and jurisdiction, and ties to an installation entry returning the component to service. Where the tail sits across FAA and EASA acceptance, dual release may be needed on affected units.
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.