A320 family release paper
Airbus A320 family authorized release documentation records review
An A320 family release document review confirms that the authorized release paper behind a specific narrowbody aircraft's installed components is present, valid, and matched to the installation records. It is run for teams evaluating, transferring, or maintaining an A320 family asset, against the component release file. Each component is checked for an FAA Form 8130-3, EASA Form 1, or dual-release certificate that ties to its part and serial number and its installation entry. You receive a supported exception list, a source map per component, and a closure plan for the specific serial number under review.
When this review is needed
- An A320 family tail will transfer between FAA and EASA acceptance and dual-release adequacy has to be confirmed.
- Components were fitted across several operators and their release certificates have never been reconciled to installation.
- A buyer requires release paper on the rotables before pricing the aircraft.
- The component release file has release certificates that do not match the installed part and serial numbers.
The problem
A component is only as installable as its release paper, and on an A320 family aircraft that has changed hands the release certificates and the installation entries drift apart. A part fitted under a release that does not match its part and serial number, an FAA Form 8130-3 where a dual-release was needed for the acceptance in view, or an installation entry with no supporting certificate all read as gaps against the configuration. The release file looks complete until each certificate is matched to the part it releases and the entry that installed it.
What gets reviewed
- Release certificates matched to the part number and serial number of each installed component
- FAA Form 8130-3 and EASA Form 1 checked for the release basis the acceptance in view requires
- Dual-release adequacy confirmed where the tail moves between FAA and EASA acceptance
- Installation entries tied to the release certificate that supports each fitment
- Components installed without a supporting certificate identified against the release file
- Release paper that does not match the installed part mapped to the component and the discrepancy
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 certificate matching its part number and serial number
- The release basis on each certificate suits the FAA or EASA acceptance the tail is moving toward
- Dual-release is present where the component's acceptance path requires it
- Each installation entry ties to the release certificate that supports the fitment
- No installed component is carried on an installation entry with no certificate behind it
Evidence normally required
Common discrepancies
- A component fitted under a release certificate that does not match its serial number
- A single-release certificate where the acceptance in view requires a dual-release
- An installation entry with no supporting release certificate in the file
- A release certificate present in the file but never tied to an installation entry
What is at stake
A component whose release paper does not tie to its installation can be treated as unsupported until the certificate surfaces, which at a deal becomes a price reduction and at a handover a held acceptance. A single-release certificate where a dual-release was required can block the acceptance the transaction depends on, and reconstructing a missing certificate after the shop that issued it has moved on is often impossible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Set the acceptance path
Confirm whether the tail is moving toward FAA or EASA acceptance and the release basis that path requires.
Match certificate to part
Tie each release certificate to the part number and serial number of the component it releases.
Tie release to installation
Confirm each installation entry is supported by a release certificate and each certificate supports a fitment.
Build the closure plan
List components with missing or mismatched release paper and the certificates that close each exception.
What the buyer receives
- A supported exception list of components whose release paper is missing or mismatched
- A source map tying each component to its release certificate and installation entry
- A closure plan for the exceptions on this specific serial number
Who uses the output
- Asset managers pricing the components whose release paper is thin or mismatched
- Continuing-airworthiness teams confirming the release basis suits the acceptance path
- Records teams recovering the release certificates that close each exception
How the work fits into the transaction or program
The review reconciles the component release file on an A320 family asset before a transaction or a handover relies on it. The exception list and source map it produces feed the recovery of the release certificates that must close each gap while the shops that issued them can still be reached.
Aircraft-specific considerations
A320 family assets frequently move between FAA and EASA acceptance, which makes dual-release adequacy a recurring question on this family, and the repeated cabin and connectivity component changes typical of the type multiply the number of release certificates that have to tie to installation entries. High turnover across operators means the release file and the installation records drift apart more than on a single-operator aircraft, so each certificate is matched to the part and the fitment rather than accepted from the file.
Regulatory limits
The review confirms release paper is present, valid on its face, and matched to installation. It does not issue a release certificate, approve an installation, or make an airworthiness determination on any component.
What this review does not cover
- Issuing or re-issuing any release certificate
- Physical inspection of the installed components
- Any airworthiness determination on a component or the aircraft
Specific to this review
- Because A320 family tails move between FAA and EASA acceptance, dual-release adequacy is a live question on this family rather than an edge case, and a single-release certificate can block the acceptance in view.
- The frequent cabin and connectivity component changes on this type multiply the release certificates that must tie to installation entries, so drift between the two is common on high-turnover aircraft.
- A release certificate present in the file but never tied to an installation entry is as much a gap as a missing one, because it does not support any fitment on the aircraft.
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 does the acceptance path matter for release documents?
Because the release basis the components need depends on whether the tail is heading toward FAA or EASA acceptance. A single-release certificate that suits one path can be inadequate for the other, so the review checks the release paper against the acceptance the aircraft is actually moving toward rather than against its own face alone.
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.