Release paperwork
Confirming authorized release certificates behind a maintenance-control export
Behind every installed serialized component in a maintenance-control export there should be an authorized release certificate, and this review confirms which ones actually have it. Records teams commission it ahead of operator transfers and system migrations, when the component release file must stand on its own. Each installation is matched to its FAA Form 8130-3 or EASA Form 1, and each certificate is checked for completeness, correct identity, and validity in the receiving context. Maintenance control gets an exception list separating clean installations from those needing document recovery.
When this review is needed
- The receiving operator's standard requires a release certificate for every serialized component on the transfer list.
- Components installed under time pressure, AOG events especially, may have been fitted before paperwork caught up.
- The release file mixes FAA and EASA certificates and the transfer crosses regimes.
- A sampling exercise found certificates filed against the wrong installations.
The problem
The export lists what is installed; the release file is supposed to prove each fit was legitimate. In practice the file accretes over years of component changes, AOG recoveries, and pool exchanges, and nobody reconciles it until a transfer forces the question. By then some certificates are missing, some are illegible copies of copies, and some belong to parts that came off the aircraft long ago.
What gets reviewed
- Every serialized installation on the export matched to a certificate in the release file
- Certificate identity blocks checked against the export: part number, serial number, description
- Release type and scope read against the work the certificate claims to release
- Dual-release status assessed where the receiving regime differs from the issuing one
- Certificate legibility and completeness confirmed, including signatures and approval references
- Orphaned certificates in the file mapped to removed components or flagged as unmatched
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 certificate's serial number matches the export line it is filed against, character for character
- The releasing organization held an appropriate approval at the certificate's issue date
- Work scope on the certificate covers the condition the export claims for the part
- Certificates supporting cross-regime installations carry the release statements the receiving side needs
- No installation relies on a purchase invoice or packing slip standing in for a release document
Evidence normally required
- The installed-component listing from the maintenance-control export
- The component release file, however it is currently organized
- Removal and installation records tying certificates to fitment events
- The receiving operator's or lessor's documentation standard, if defined
Common discrepancies
- AOG-era installations where the certificate was promised and never filed
- A legible certificate whose serial number differs from the installed part by one digit
- Single-regime releases supporting installations that the transfer will move across regimes
- Certificates filed against positions rather than serial numbers, scrambled by later swaps
What is at stake
An installation without an acceptable release document reads as an unapproved part until proven otherwise. Receiving operators reject such lines outright, and the cure, chasing the issuing shop or replacing the component, is slow and expensive when compressed into a transfer window.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Extract the population
Pull the serialized installations from the export and fix the certificate population to match against.
Match and read
Pair each installation with its certificate and check identity blocks, scope, and legibility.
Judge the context
Assess each certificate's validity for the receiving regime and the claimed part condition.
Deliver the split
Report clean lines, defective lines, and the recovery route for each gap.
What the buyer receives
- An installation-by-installation match report with certificate status for each line
- A recovery list naming the issuing organization for every missing or defective certificate
- A reorganized certificate cross-reference keyed to serial numbers
Who uses the output
- Maintenance control closing the component release file before transfer
- Receiving-side reviewers confirming what arrived is supportable
- Quality leadership tightening the certificate-filing loop that produced the gaps
How the work fits into the transaction or program
Release-document review anchors the component side of an export review. Its serial-level matching feeds the LLP trace work, its recovery list merges into the wider evidence-chase effort, and the reconciled certificate file becomes a standing asset the operator carries into every later transaction.
Jurisdiction-specific considerations
FAA Order 8130.21 governs FAA Form 8130-3 issuance and 14 CFR Part 43 governs the maintenance releases behind it, while EASA Form 1 operates under Regulation (EU) 1321/2014. The regimes accept each other's certificates only under specific bilateral conditions, so a transfer that changes regime changes what the same certificate is worth.
Regulatory limits
The review assesses documentation. It does not authenticate certificates with issuing authorities beyond documentary checks, does not approve parts for installation, and makes no airworthiness determination about any component.
What this review does not cover
- Physical part inspection or data-plate verification
- Procurement of replacement components for failed lines
- Suspected-unapproved-part investigation beyond flagging the documentary trigger
Specific to this review
- Certificate defects cluster around AOG events, when getting the aircraft moving outranked getting the paperwork filed.
- Filing certificates by aircraft position instead of serial number guarantees scrambling after the first component swap.
- A one-digit serial mismatch fails review as completely as a missing certificate, and takes nearly as long to cure.
- Dual-release wording is the cheapest insurance in the file; its absence is discovered only when a transfer crosses regimes.
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
Is a shop's work order enough when the certificate is missing?
Work orders and teardown reports help reconstruct events but they are not release documents. Some counterparties will accept them as interim support while a duplicate certificate is requested from the issuing organization; others will not. The review records exactly what exists for each line so that judgment is made with open eyes.
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.