Release paper before signing
Authorized release certificate review for operators preparing a sale or lease return
This review confirms that the components installed on an operator's aircraft carry authorized release certificates a transaction counterparty will accept. FAA Form 8130-3, EASA Form 1, and dual-release documents are matched against installation records and the component release file, part by part and serial by serial. An aircraft-records reviewer performs it before a sale, lease return, or financing review, on the operator's side and ahead of the counterparty's sampling. The operator receives a component exception list, the verified certificate set, and a recovery plan for paper that is missing or deficient.
When this review is needed
- A sale or lease return is scheduled and the records standard in the agreement covers release documentation for installed components.
- The aircraft may change registry at delivery and dual-release acceptability has never been checked component by component.
- Years of component changes were filed by different staff and the release file has never been audited against what is actually installed.
- A financier's technical advisor has requested certificate evidence for a sampled set of rotables.
The problem
Every component change in the aircraft's life produced a certificate somewhere, and the transaction requires each of those somewheres to be the release file. Paper gets filed against the removed unit instead of the installed one, single-authority releases sit on components that a registry change will require dual release for, and a certificate can be present yet useless because its serial number belongs to a different unit. None of this shows up until someone matches paper to installations methodically.
What gets reviewed
- Installed rotable components matched to release certificates by part number, serial number, and installation date
- Certificate completeness reviewed: block entries, work scope described, authority release ticked, signatures and approval references present
- Dual-release status assessed against the registry the aircraft will land on after the transaction
- The component release file reconciled against removal and installation history so paper follows the installed unit
- The release basis on each certificate compared with what the transaction's records standard requires
- Certificates screened for legibility, correct revision of the form, and internal date consistency
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 serial number on each certificate matches the unit shown installed at that position in the aircraft records
- Work described on the certificate is consistent with the component's history at that point, such as overhaul following a heavy removal
- Components requiring dual release for the receiving registry hold certificates with both authority blocks completed
- Installation entries without a locatable certificate are isolated and dated so recovery requests target the right shop
- No certificate in the file is doing double duty for two different installations of the same part number
Evidence normally required
- The component release file as currently maintained
- Removal and installation history from the maintenance system
- The current installed-component listing by position
- The transaction's records standard or lease return conditions
- Shop and supplier contacts for certificate recovery
Common discrepancies
- A certificate on file for the right part number but the wrong serial, usually the previously installed unit
- Single-authority releases on components bound for a registry that will expect dual release
- An inspected-and-tested release where the deal standard requires evidence of overhaul
- Scanned certificates too degraded to read the approval reference or release blocks
What is at stake
Counterparty reviewers sample rotables, and a failed sample expands until the reviewer trusts the file or the deal team runs out of schedule. Components lacking acceptable releases get priced for replacement or held back in escrow, and at a lease return they become the slowest class of open item because sourcing substitute paper depends on shops with no stake in the deadline.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the installed baseline
Establish which unit sits at each position from the maintenance system and current installed-component listing.
Match paper to positions
Pair each installed unit with its release certificate and verify serials, work scope, and release basis.
Judge against the standard
Evaluate each certificate against the transaction's records standard and the destination registry's expectations.
Package and pursue
Index the verified set for the data room and launch recovery requests for the exceptions.
What the buyer receives
- A component-by-component exception list separating missing, mismatched, and deficient certificates
- The verified certificate set indexed to installed positions for the data room or redelivery binder
- A recovery plan naming the issuing shop for each missing document and flagging items with no recovery path
Who uses the output
- Records leadership managing certificate recovery against the transaction schedule
- The deal or redelivery team deciding which exceptions to cure, disclose, or negotiate
- The counterparty's reviewers, who work faster against an indexed and pre-checked file
How the work fits into the transaction or program
Release paper is usually the largest document population in a transaction records review, so proving it early removes the bulk risk from the timeline. This review runs alongside LLP trace and AD verification in a readiness program, and its indexed certificate set flows straight into the data room or the redelivery documentation package.
Jurisdiction-specific considerations
Acceptability of a release depends on where the component will fly next. An FAA-registered future accepts 8130-3 releases; an EASA-registered one expects Form 1 or a dual release executed under the applicable bilateral agreement. The review evaluates each certificate against the destination registry, since paper that was fine for the current operation can fail the transfer.
Regulatory limits
Findings here concern documents, never hardware. The review does not approve any component for return to service, does not issue or amend release certificates, and does not decide airworthiness; those functions belong to appropriately rated organizations and the responsible authority.
What this review does not cover
- Issuing replacement certificates or obtaining them on the operator's behalf as an authorized signatory
- Physical inspection of components or verification of data-plate details on wing
- Legal interpretation of the purchase agreement or lease return conditions
Specific to this review
- Lease return conditions frequently demand a stronger release basis than 14 CFR 43 requires for operation, so a component can be legitimately in service and still fail redelivery on paper.
- Certificates misfiled against the removed unit are the single most common release-file defect, because removal and installation paperwork travel together at the time of the change.
- Dual-release wording changes with bilateral-agreement revisions, and older certificates written to superseded language draw questions even when the work was sound.
- A shop's retained copy is often recoverable years later, but shops answer such requests at their own pace, which is why recovery starts before the counterparty finds the gap.
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 aircraft has flown for years without anyone questioning these certificates. Why would a buyer?
Operation and transfer apply different tests. In service, the operator's own system accepted each component when it was fitted, and nobody revisits that paper. At a transaction, a reviewer re-examines the file against a contractual standard and a destination registry, with an incentive to find gaps. Documents that were never challenged in service fail that examination regularly.
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.