Component paperwork at return
Authorized release certificate review within the lease-transition records file
Every component that joined the aircraft during the lease should have a release certificate the delivered records can produce, and this review confirms whether the component release file meets that test. It is performed on the lease-transition records file, before acceptance, by a specialist reading each installation against its FAA Form 8130-3, EASA Form 1, or equivalent. Certificates that are absent, incomplete, altered, or issued for a different context than the installation are written up as exceptions. The transition lead gets a component-level account of what the file supports and what still needs to be recovered.
When this review is needed
- Redelivery terms call for release documentation on rotable installations and the file has never been checked component by component.
- A mid-lease operator change left component paperwork split between two record systems and the transition file merged them untested.
- Acceptance sampling has already turned up a certificate with a mismatched serial number and the full population needs the same scrutiny.
- Components were robbed between aircraft during the lease and the release chain for the reinstallations was never confirmed.
The problem
Release certificates are created at the moment of release and then have to survive years of filing, scanning, and custody changes before anyone reads them again. Installation records live in the operator's system; the certificates live in binders and folders; the two are joined only by discipline. A transition file merges whatever both custodians kept, and the joins are exactly where certificates go missing.
What gets reviewed
- The component release file compared against installation records for the components fitted during the lease term
- Certificate completeness checked: identification blocks, work performed, approval basis, and the certifying signature
- Release context matched to the installation, distinguishing new, overhauled, repaired, and inspected releases
- Dual-release status confirmed where the receiving regime requires both FAA and EASA acceptance
- Serial and part numbers reconciled across the certificate, the installation record, and the status system
- Exceptions already logged in acceptance correspondence reconciled to avoid duplicate queries
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 installation resolves to a certificate physically or digitally present in the delivered file
- Certificate part and serial numbers match the fitted component, including dash-number changes after rework
- The work scope stated on the release supports the condition claimed in the status system
- Remarks blocks carry the references the release depends on, such as the repair or overhaul data used
- Certificates show issue dates and approval references consistent with the issuing shop's authority at the time
Evidence normally required
- The component release file or tag binder as delivered for the transition
- Installation and removal records covering the lease term
- The rotable status listing from the operator's system
- Acceptance notes and prior sampling results from either side
Common discrepancies
- An installation whose certificate is on file for the previous serial number, from before a swap the records barely captured
- Releases issued as inspected-tested where the status system claims overhauled condition
- Single-regime certificates on components the receiving jurisdiction requires dual release for
- Legibility failures: scanned tags missing the blocks that carry the approval basis
What is at stake
A fitted component without an acceptable release is a removal candidate in the eyes of an acceptance team, and removal arguments arrive at the worst moment, with the aircraft scheduled and the deadline fixed. Even where the component is plainly serviceable, replacing or re-certifying paperwork under time pressure costs more than early recovery would have. Certificate defects also cluster in the reviewer's mind: after the first bad tag, every following one gets read harder.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Define the population
Establish which installations during the lease term require release documentation under the lease standard.
Match certificates
Pair each installation with its certificate and check identity, completeness, and release context.
Screen the misfits
Separate missing, incomplete, and context-mismatched certificates and confirm none duplicate known queries.
Hand over the index
Deliver the evidence index and the recovery worksheet keyed to issuing shops and prior operators.
What the buyer receives
- A component-level exception report separating missing, incomplete, and context-mismatched certificates
- An evidence index tying each supportable installation to its certificate location in the file
- A recovery worksheet naming the issuing shop or prior operator for each missing document
Who uses the output
- Transition leads separating negotiable certificate exceptions from must-fix ones
- Records staff sending document-specific requests to issuing shops
- Acceptance teams on both sides working one agreed component exception baseline
How the work fits into the transaction or program
Release-document review runs against the same delivered package as the repair and shop-visit strands and shares their recovery channels, since the issuing shops overlap. Cleared certificates flow into the acceptance evidence set; exceptions flow to the tracker with named recovery targets, so the transition lead negotiates from a fixed list rather than a moving one.
Jurisdiction-specific considerations
Whether a certificate satisfies the receiving side depends on regime as much as content. Components entering EASA-managed service from FAA sources, and the reverse, rely on bilateral acceptance arrangements and dual-release conventions, so the review flags single-regime releases wherever the transition changes the applicable system. FAA Form 8130-3 usage is governed by FAA Order 8130.21, while EASA Form 1 requirements sit in Regulation (EU) 1321/2014.
Regulatory limits
Findings describe the state of the documentation, nothing more. The review does not issue, correct, or validate release certificates, does not judge component serviceability, and does not make airworthiness determinations for the components or the aircraft.
What this review does not cover
- Confirming fitted components against their data plates on the aircraft
- Arranging re-certification of components at a shop
- Serviceability or remaining-life assessment of any component
Specific to this review
- The failure mode acceptance teams reject fastest is a context mismatch: a valid certificate for the wrong event, such as a repair release supporting an overhauled claim.
- Scanned tag binders lose evidentiary value page by page; a certificate missing its reverse side often fails review even when the original was complete.
- Components robbed between aircraft generate the thinnest paper trails because the move happens under line-maintenance time pressure.
- Dual-release expectations depend on the receiving operator's regime, so the same file can pass one transition and fail the next.
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 dual release always required?
No. The requirement depends on the regime the aircraft is entering and on the lease's return conditions. The review applies the standard the transition actually faces and marks each certificate that would fail it, rather than holding every tag to the strictest possible test.
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.