Boeing 747 release docs
Boeing 747 family authorized release documentation records review
This review verifies that installed components on a specific Boeing 747 carry valid release documents and that each release ties to an installation record on this aircraft. It is run for a buyer, lessor, or CAMO who needs to know that installed parts trace to an acceptable authorized release, not just to an inventory line. It covers FAA Form 8130-3, EASA Form 1, dual-release certificates, and the installation records that connect a release to the airframe. You receive an exception list where a release is missing, invalid, or unlinked, a source map behind each installed component, and a plan to close the gaps.
When this review is needed
- A 747 is in diligence and the buyer requires installed components to trace to valid release documents.
- A component's release certificate is present but does not link to an installation record on this airframe.
- The aircraft is moving between FAA and EASA oversight and dual-release status has to be confirmed.
- A release document appears to cover a different part number or serial than the one installed.
The problem
Every rotable and repairable on a 747 should carry a release document that follows it onto the aircraft, but across a long life those documents drift apart from the parts. A release certificate may sit in the file with no installation record linking it to this airframe, or an installation record may name a part whose release is missing. Dual-release status, which the aircraft needs to move between frameworks, is often assumed rather than confirmed. The component release file looks full until each certificate is matched to the part it actually authorizes.
What gets reviewed
- Installed rotable and repairable components checked for a valid release document
- FAA Form 8130-3 and EASA Form 1 certificates verified for completeness and validity
- Dual-release status confirmed where the aircraft moves between frameworks
- Installation records linking each release to this airframe and position
- Part-number and serial agreement between the release and the installed part
- Repaired and overhauled components traced to the release from their last shop event
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 document present and valid for the part and serial
- Every release certificate links to an installation record on this airframe and position
- Dual-release certificates carry both authority blocks completed where the move requires it
- Part number and serial on the release agree with the installed part
- Repaired components trace to the release issued at their most recent shop event
Evidence normally required
- The component release file for the airframe and its installed rotables
- FAA Form 8130-3, EASA Form 1, and dual-release certificates on file
- Installation records and work orders linking components to positions
- The installed-component list with part numbers and serials
- Shop-visit records for repaired and overhauled components
Common discrepancies
- Release certificates in the file with no installation record linking them to this airframe
- Installed components named in installation records whose release document is missing
- Dual-release status assumed where only a single authority block was completed
- A release covering a different part number or serial than the part actually installed
What is at stake
An installed component that cannot be traced to a valid release is a part the owner cannot prove is airworthy on paper, which surfaces at diligence, at a shop visit, or at a transfer. A missing dual release can block a cross-framework move until it is reconstructed. Buyers discount for release gaps because closing them means chasing the shop or vendor that issued the original certificate, and that path grows colder with time.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the components
List the installed rotables and repairables to be checked for release traceability on this serial.
Match release to part
Confirm each installed component has a valid release for its part number and serial.
Link to installation
Tie every release to an installation record on this airframe and position.
Report and close
Deliver the exception list, source map, and a plan to retrieve or reconstruct the missing releases.
What the buyer receives
- An exception list for components lacking a valid, linked release document
- A source map tying each installed component to its release and installation record
- A closure plan to retrieve, revalidate, or reconstruct the missing releases
Who uses the output
- CAMOs confirming installed components trace to an acceptable authorized release
- Buyers verifying release traceability before pricing the asset
- Records teams retrieving the release documents that close each component gap
How the work fits into the transaction or program
Release documents are the evidence that each installed part entered service through an acceptable authorized release, and they underpin the LLP trace, the configuration statement, and the repair map. Confirming that every installed component links to a valid release closes the loop between what is on the aircraft and what the records can prove. This review pairs with the LLP trace, since the release certificate is often the same document that carries a part's cycle history.
Aircraft-specific considerations
A 747 carries a large population of rotables across four engines and a complex airframe, and decades of service mean many components have been repaired or overhauled several times, each event generating a new release. Operator transitions leave release files assembled under different conventions, and freighter conversion adds cargo-system components with their own releases. The review scopes to this serial's installed-component population rather than a family parts list.
Jurisdiction-specific considerations
A component may carry an FAA Form 8130-3, an EASA Form 1, or a dual-release certificate, and a 747 moving between frameworks needs the right release form for the receiving authority. The review confirms which release each component holds and whether it is acceptable for the intended move, so the receiving CAMO does not have to re-qualify the release path.
Regulatory limits
This review verifies release documentation and its links to the aircraft. It does not issue or endorse any release certificate, does not accept a component onto the aircraft, and does not make an airworthiness determination.
What this review does not cover
- Issuance or endorsement of any release document
- Physical inspection of installed components
- Acceptance of a component onto the aircraft
Specific to this review
- A release certificate with no installation link is not traceability, because it cannot show the part it authorizes was ever installed on this airframe.
- Dual-release status is frequently assumed rather than confirmed, and a single completed authority block does not satisfy a cross-framework move.
- A repaired component's current release is the one from its last shop event, so an earlier release on file does not close the trace.
- The high rotable count on a four-engine 747 means release-file gaps are a volume problem, and closing them is bounded by the shops that issued the originals.
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
Why is an installation link required, not just a release certificate on file?
A release certificate on its own only shows a part was released by a shop. Without an installation record tying it to this airframe and position, it cannot demonstrate that the released part is the one actually installed, so an unlinked release is logged as an exception until the installation record closes it.
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.