Release documentation
Authorized release certificates reviewed against the CAMO source file
This review audits the component release file that a continuing-airworthiness record set depends on. It is run for CAMO managers and maintenance leadership when installed components must be shown to have entered service with valid release documentation, commonly ahead of an airworthiness review, an audit, or a lease event. Installed components drawn from the status data are matched to their FAA Form 8130-3, EASA Form 1, or equivalent, and each certificate is checked for completeness and for validity in the context where it was received. Components whose release cannot be located, or does not hold, come back as an exception list.
When this review is needed
- An audit or airworthiness review will sample installed components and expect a release document for each one.
- Components were fitted during AOG events under time pressure, and the paperwork trail was left to catch up.
- A change of CAMO or maintenance provider has left the component release file split across systems.
- A counterparty review at lease return or sale will read release documents against the receiving regulatory context.
The problem
Release certificates arrive with parts, get filed by whoever receives them, and are then presumed to exist forever. The component itself stays visible on the aircraft and in the status system, while its certificate lives one filing error away from being unproducible. Years later the CAMO owns an installed-parts population whose documentation quality reflects every goods-inwards desk the fleet has passed through.
What gets reviewed
- Installed components sampled or targeted from the status data against the component release file
- Certificate completeness: blocks, signatures, approvals, and the work scope stated on each form
- Dual-release status where components crossed between FAA and EASA environments
- Consistency of part number, serial number, and modification state between certificate and installation record
- Shelf-life and cure-date sensitive items where the release carries limits
- PMA, owner-produced, and standard parts documentation where full release forms do not apply
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 sampled installed component resolves to a release certificate in the file, on the correct form for its origin
- The certificate's part and serial numbers match the installation record and the configuration data
- Release blocks are completed and signed, and the stated work scope supports how the component was used
- Components moved between FAA and EASA contexts carry the dual release or acceptance basis the receiving side requires
- Certificate dates precede installation dates, and any limits stated on the release were respected at fitment
Evidence normally required
- Installed-component data from the CAMO status system or reports
- The component release file in whatever form it exists: paper, scanned, or mixed
- Installation records such as task cards, work orders, or logbook entries for the sampled fitments
- Goods-inwards or stores receiving records where available
- The aircraft's operating history across regulatory environments
Common discrepancies
- Components installed during AOG recoveries with a packing slip on file where the release certificate should be
- Certificates whose serial number differs from the installed unit by one transposed digit, unresolved for years
- Single-release documents for components that crossed into an environment expecting dual release
- Release forms present but with a work-scope block describing an inspection when an overhaul was the basis for fitment
What is at stake
An installed component without a valid release is a finding waiting to be written, and the response options are all expensive: locate the certificate, obtain a duplicate from the issuing organization, or remove and replace the part. Under a redelivery or audit deadline, the removal option starts looking cheap compared to the search.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Select the component sample
Draw installed components from status data, weighted toward rotables and known AOG fitments, plus any items already questioned.
Pull certificates and installations
Locate each component's release document and the task card or work order that fitted it.
Check each certificate in context
Verify form completeness, identity match, and validity for the regulatory environment in which the component was received.
Report and route recoveries
List failed items with their defect and prepare duplicate requests to issuing organizations where recovery is possible.
What the buyer receives
- A component-level exception list naming the document defect for each failed item
- A supported view of the sampled population, usable as audit or review evidence
- A duplicate-request package identifying the issuing organization for each recoverable certificate
Who uses the output
- CAMO managers closing release-document exposure before reviews and audits
- Maintenance leadership tightening receiving and filing practice at the stations that generate defects
- Records teams assembling component documentation for a lease return
How the work fits into the transaction or program
Release documentation underpins the other CAMO-file reviews: LLP traces terminate in release certificates, shop-visit packages cite them, and repair records depend on the parts they cover. Running the release-document review alongside those keeps one component file serving all of them, and its exceptions feed the same remediation track.
Jurisdiction-specific considerations
FAA Order 8130.21 sets out how Form 8130-3 is completed and used, while the EASA Form 1 serves the parallel role under Regulation (EU) 1321/2014; 14 CFR Part 43 and 91.417 govern the maintenance records the certificates support. Aircraft that have operated under both systems accumulate mixed files, and the review evaluates each certificate against the rules of the context in which the component was received, which is where most cross-system defects hide.
Regulatory limits
The review assesses documents against the requirements applicable when and where each component was received. It does not issue, correct, or validate release certificates, does not determine any component serviceable, and does not decide airworthiness for the aircraft.
What this review does not cover
- Physical verification that installed serial numbers match data plates on wing
- Procurement of replacement components or duplicate certificates, beyond identifying the issuer
- Vendor or supplier approval audits
Specific to this review
- The release file degrades fastest at outstations and during AOG events, so defect rates form a map of where the fleet has broken down.
- A certificate can be genuine, complete, and still invalid for the installation if the receiving context required a dual release it does not carry.
- Issuing organizations retain copies for a limited period, which makes duplicate requests time-critical in a way most remediation plans underestimate.
- Transposed serial digits are among the most common defects and among the cheapest to cure, if caught before an external reviewer treats them as missing trace.
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
Do you check every installed component?
No. The population is sampled, weighted toward rotables, LLP-adjacent hardware, and components fitted during known AOG events, because that is where defects concentrate. Targeted items, such as parts a counterparty has already questioned, are always included.
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.