Release documentation
Authorized release document review across a shop-visit source file
Each component fitted during a shop visit should be covered by an authorized release certificate that matches the part, the serial number, and the work performed. This review pulls the component release file apart and checks every installation in the work package against its FAA Form 8130-3, EASA Form 1, or equivalent. It is carried out for the accepting quality organization or lessor as the package closes. The result is a certificate-level exception list naming each install that lacks a valid, matching release.
When this review is needed
- A work package is at acceptance and the component release file has not been reconciled against the installs.
- Parts arrived through brokers or exchanges and the certification trail behind them is thin.
- A dual-release requirement applies because the asset will operate under both FAA and EASA oversight.
- Receiving inspection flagged certificates during the visit and the follow-up was never confirmed closed.
The problem
Certificates and parts separate easily inside a busy shop. A component gets drawn from stores against one work order and consumed on another, a subcontracted overhaul returns with a scanned release that never reaches the job file, and an exchange unit arrives with paperwork for a different dash number. The package still closes, because the fitment is physically done, and the certificate gap only exists on paper where nobody is looking at closeout.
What gets reviewed
- The install list from the work package reconciled part by part against the component release file
- Certificate content checked: part number, serial number, quantity, work scope, and certifying authority
- Dual-release status confirmed where the receiving context requires FAA and EASA coverage
- Sub-tier and subcontractor releases traced into the primary package
- Exchange, loan, and robbed parts checked for the paperwork their sourcing route requires
- Certificate dates ordered against removal, receiving, and installation dates
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
- The release document identifies the same part and serial number that the fitment record shows installed
- The certifying statement covers the work actually performed: new manufacture, overhaul, or repair
- Signatures, approval numbers, and certificate references are present and legible on each document
- No certificate is being reused across multiple installations of the same part number
- Dates form a coherent sequence from release through receiving to installation
Evidence normally required
- The closed work package with its installation and removal records
- The component release file as compiled by the shop
- Receiving inspection records and stores traceability data
- Subcontract purchase orders and the releases returned against them
- Any dual-release or contractual certification requirements that apply
Common discrepancies
- An exchange unit installed against a certificate issued for the core that was sent out
- A single-authority release where the operating context requires dual certification
- A subcontracted repair present in the invoice trail but absent from the release file
- A certificate whose work-scope statement does not cover the modification status of the part fitted
What is at stake
An installed part without a valid release is a finding that no later audit will wave through. At redelivery it becomes a rejected component and a demand to replace or re-certify; in an authority audit it raises questions about receiving controls that spread beyond the single part. Retrieving a certificate from a supplier long after invoicing closes is slow, and reconstructing one is sometimes impossible.
How the work runs
Extract the install list
Pull every installation and removal from the work package into a single reconciliation set.
Match documents to fitments
Pair each install with its certificate and record the pairs that fail.
Read the failed pairs
Determine whether each gap is a filing miss, a wrong document, or a true absence.
Issue the reconciliation
Deliver the matrix, the exceptions, and the retrieval requests before acceptance closes.
What the buyer receives
- A reconciliation matrix linking every installation to its release document or to a gap
- An exception list stating, per gap, what document is missing and who should hold it
- A corrected component release file index ready for the permanent record
- Draft retrieval requests for certificates still recoverable from suppliers or subcontractors
Who uses the output
- Quality leadership signing the acceptance of the work package
- Lessors and asset managers whose return conditions specify release coverage per install
- Records staff building the component file that travels with the asset
How the work fits into the transaction or program
Release verification anchors the other source-file reviews: the LLP trace leans on these same certificates for its installation events, and repair findings often begin as a work-scope mismatch spotted here. Running it while supplier accounts are still open keeps certificate retrieval a routine request instead of an escalation.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
FAA Form 8130-3 and EASA Form 1 serve parallel roles but are not interchangeable in every receiving context, and bilateral arrangements set where one authority's release is accepted by the other. Components cycling between US and EU maintenance systems accumulate mixed paperwork, so the review reads each certificate against the regime the next installation will actually sit under.
Regulatory limits
This is a documentary reconciliation, and its findings stop at the paper. It does not certify parts, issue or amend any release document, judge a component unairworthy, or approve installation of anything; certification decisions rest with appropriately rated organizations and authorized signatories.
What this review does not cover
- Authenticating documents suspected of forgery, beyond flagging them for the operator's process
- Sourcing replacement parts for rejected installations
- Evaluating supplier quality systems or approving vendors
Specific to this review
- The highest-risk certificates are usually attached to the lowest-value parts, because expendables and hardware get the least receiving scrutiny.
- A release can be genuine, current, and still wrong for the install if its work-scope statement covers a different repair standard than the fitment required.
- Shops index release files by purchase order more often than by installation, which is why a part-by-part reconciliation finds gaps a file-completeness check misses.
- Dual-release shortfalls are cheap to fix at the certifying shop and expensive everywhere else.
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 shop says the release file is complete. What does this add?
Completeness counts documents; reconciliation checks that each document actually covers the part fitted, in the position fitted, with the right work scope and authority. Most exceptions this review finds sit inside files that pass a count.
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.