The owner's release file
Authorized release document review for aircraft-management teams at export
Aircraft-management teams use this review to confirm that the release documentation behind an owner's aircraft is complete before the aircraft leaves the registry. It works through the component release file, checking FAA Form 8130-3s, EASA Form 1s, dual-release certificates, and the installation records that tie each certificate to a position on the aircraft. The check runs during export airworthiness preparation, before the certificate application is submitted. The owner's representative receives an indexed release-certificate file with verification marks, a deficiency list, and a tracker for documents still outstanding.
When this review is needed
- An owner's aircraft is being sold or re-registered abroad and the component file has never been read as one body of evidence.
- Parts were sourced over the years from exchange pools and brokers, with filing quality varying by who received them.
- The destination side is known to require dual releases that the file may not contain.
- A buyer's records team has requested the release file and management wants it verified before handover.
The problem
A managed aircraft accumulates release certificates from every parts source its operation has touched: exchange pools, brokers, repair shops, and the management company's own stock. Filing quality varies with whoever received the part that week, and certificates get separated from the installation entries that give them meaning. At export, an authority or buyer reads the file as a single body of evidence, and it was never assembled as one.
What gets reviewed
- The component release file mapped against the installed configuration
- FAA Form 8130-3 completeness, including block usage and certifying statements
- EASA Form 1 releases and their acceptability for the destination side
- Dual-release certificates where parts must satisfy both systems
- Installation records linking each certificate to a position, date, and work order
- New-part releases versus return-to-service releases, matched to the part's actual 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 tracked component has a release certificate whose part number, serial number, and modification level match the installation entry
- Certificate blocks are completed for the intended function, with return-to-service and new-part statuses used correctly
- Dual-release certificates carry both certifying statements where the destination requires them
- Certificate dates precede or match the installation dates they support
- The file contains no orphan certificates for parts not shown installed, and no installed tracked part without one
Evidence normally required
- The component release file or its digital equivalent
- The current installed-configuration or component listing
- Installation and removal entries from logbooks and work orders
- Purchase or exchange documents for recently fitted parts
- The export destination's documentation expectations, where known
Common discrepancies
- Certificates filed by purchase date rather than installation, hiding parts fitted with no release at all
- An 8130-3 completed as a new-part release for a component that had actually been through repair
- Single-system releases on parts that will need dual acceptance at the destination
- Installation entries citing a work order that never made it into the file
What is at stake
A component without an acceptable release is presumed unapproved for the purpose of the transfer, and pulling or re-certifying parts inside an export window is expensive and slow. Owners feel the gap financially too: a thin release file weakens the aircraft's presentation in exactly the transaction the export usually serves.
How the work runs
Map file to aircraft
Reconcile the release file against the installed component listing to find orphans and holes.
Examine each certificate
Check completion, function, dates, and identity data on every release.
Tie to installations
Link certificates to installation entries and flag broken pairs.
Report and chase
Issue the index, deficiency list, and tracker, and route requests to suppliers and shops.
What the buyer receives
- A release-certificate index keyed to installed positions with a verification mark per component
- A deficiency list stating what is wrong with each failing certificate
- An outstanding-document tracker for the suppliers and shops that owe paper
Who uses the output
- The owner's representative preparing the aircraft for export
- Maintenance control resolving deficiencies while the aircraft is still operating
- The receiving side's reviewers, who work from the verified index
How the work fits into the transaction or program
Release documentation is the layer under every other export record: AD accomplishments, LLP trace, and repair records all eventually rest on a certificate for a part. Running this review early lets the deficiency list drive supplier requests in parallel with the rest of the export package rather than after it.
Start with a single asset
Reconcile maintenance tracking against source records.
Jurisdiction-specific considerations
FAA Order 8130.21 governs completion of the 8130-3, and EASA Form 1 usage follows Regulation 1321/2014; bilateral agreements define when a single form serves both systems and when a dual release is required. The review is run against the destination's reading, since that is the standard the file must survive.
Regulatory limits
The review evaluates documents on their face. It does not authenticate certificates with issuing authorities, approve parts, issue or correct release documentation, or make the airworthiness finding behind the export certificate.
What this review does not cover
- Verification of physical part markings against certificates
- Procurement of replacement parts or re-certification services
- Suspected-unapproved-part investigations, which are referred rather than performed
Specific to this review
- The certificate itself is only half the evidence; without an installation entry naming the position and date, it proves a purchase, not a configuration.
- Blocks completed for the wrong release function are the most common defect and among the easiest to fix while the issuing shop still exists.
- Files organized by acquisition date reliably hide the small set of parts fitted without any release, which is what mapping against configuration exposes.
- Dual-release needs are destination-dependent, so a file that passed one export can fail the next without a single document changing.
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
The parts came from reputable suppliers. Is a certificate-by-certificate check necessary?
Supplier quality reduces the odds of bad paper but not of misfiled, mismatched, or wrong-function certificates, which are handling defects rather than sourcing defects. Export review is the point where those defects become visible to outsiders, so the file is checked as the destination authority will read 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.