Lease return
Release-document source review for the redelivery binder
This review tests whether the authorized release certificates presented in a redelivery binder actually stand up at source. A records specialist works the component release file line by line, matching each FAA Form 8130-3 or EASA Form 1 to the installation it is supposed to cover and confirming the certificate is complete, legible, and consistent with the fitment context. It runs while the binder is being assembled or contested, before acceptance conditions are formally tested. The asset manager receives an itemized exception report tied to specific certificates and positions, ready to hand to the returning operator.
When this review is needed
- Redelivery conditions call for a release certificate behind every rotable installed during the lease term, and the binder index has never been proven against the certificates themselves.
- The returning operator swapped components at multiple line stations and the release paperwork arrived from several repositories with different naming conventions.
- An acceptance inspector has already rejected a handful of certificates and the lessor wants the rest screened before the next review session.
- Redelivery is weeks away and nobody has confirmed that scanned certificates are readable at the block level.
The problem
During a lease, release certificates accumulate through line maintenance, shop events, and pool exchanges, and each channel files them differently. At return, the binder presents an index of certificates that no one has opened one by one. A certificate can be present yet useless: the serial in block on the form disagrees with the fitted part, the work-order reference points somewhere else, or the scan cuts off the certifying signature. The records team discovers this only when the counterparty does, in the acceptance room.
What gets reviewed
- Line-by-line comparison of the component release file against the binder's certificate index
- Match of each certificate's part number, serial number, and status block to the installation record it supports
- Check of work-order and purchase-order references linking the certificate to the actual removal and installation event
- Legibility and completeness screening of scanned certificates, including signature and approval-number fields
- Identification of positions that carry a part with no certificate anywhere in the source set
- Flagging of single-authority releases where the return conditions require dual FAA and EASA release
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 FAA Form 8130-3 or EASA Form 1 agrees with the serial recorded as installed at that position
- The status entry on the certificate matches the claim made for the part, such as overhauled versus inspected or tested
- Remarks-block references trace to a work order or shop report that exists in the source set
- Certificates carry the certifying authority approval reference and a signature or electronic equivalent that survives the scan
- Every rotable installation event in the discrepancy and movement records has a corresponding release document
Evidence normally required
- The component release file and the binder's certificate index
- Installed-configuration or component movement records covering the lease term
- The lease's redelivery conditions relating to release documentation
- Removal and installation records or line-maintenance work orders for component changes
- Any acceptance notes or rejection lists already raised against the release file
Common discrepancies
- A certificate whose serial number belongs to the removed unit rather than the one fitted at return
- Positions filled through pool exchanges where the exchange paperwork exists but the release document was never collected
- Scans in which the certifying signature, date, or approval number is truncated or illegible
- Single-release certificates for parts that the redelivery conditions require under dual FAA and EASA release
What is at stake
Each certificate that fails inspection at acceptance becomes a negotiated item, and a pattern of failures invites the counterparty to audit the entire release file rather than sample it. That widens the review, stretches the return timeline, and can convert paperwork defects into holdback claims or component replacement demands priced at the operator's expense.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Fix the certificate population
Establish from movement and installation records which positions and parts actually require a release document for this return.
Open every claimed certificate
Read each 8130-3 or Form 1 against its installation event, checking serials, status, references, and legibility.
Classify the exceptions
Separate absent documents, mismatched documents, and defective scans, since each needs a different cure path.
Issue the exception report
Deliver the position-level report and reconciled index to the asset manager and the operator's records team.
What the buyer receives
- An exception report listing each defective or absent certificate by position, part number, and serial number
- A reconciled certificate index the acceptance team can rely on for the remainder of the return
- A retrieval list naming the likely source, such as a shop, supplier, or line station, for each missing document
Who uses the output
- Asset managers preparing the lessor's position ahead of acceptance sessions
- Operator records teams tasked with curing release-document gaps before the return date
- Technical representatives sampling the binder on site who need to know where the weak certificates sit
How the work fits into the transaction or program
Release documents are usually the first record class an acceptance inspector samples, so this review typically runs early in the binder work. Its exception report feeds the operator's cure effort and sets the sampling expectations for the repair, shop-visit, and configuration reviews that follow on the same source set.
Jurisdiction-specific considerations
FAA Order 8130.21 governs how an 8130-3 is completed, while EASA Form 1 usage follows Regulation (EU) 1321/2014, and the two forms differ in block conventions and dual-release wording. A return that moves the aircraft between regulatory regimes tends to expose certificates that were acceptable where issued but do not satisfy the receiving side's expectations.
Regulatory limits
The review evaluates documentation only. It does not certify any part as airworthy, does not issue or amend release certificates, and does not decide whether the aircraft meets its redelivery conditions; those determinations remain with the certificate-issuing organizations and the parties to the lease.
What this review does not cover
- Physical inspection of installed components or verification of data plates on wing
- Procurement of replacement certificates from repair stations or suppliers
- Legal interpretation of the lease's redelivery clauses
Specific to this review
- A certificate can be genuine and still fail the binder: if its work-order reference does not connect to the installation event, the trace is broken even though the form is valid.
- Dual-release language on an 8130-3 or Form 1 is easy to overlook in bulk scanning, and its absence surfaces late when the next operator sits under the other authority.
- Certificate indexes are frequently built from a component-tracking system export, so the index can list documents that were never scanned into the binder at all.
- Consumables and standard hardware rarely need item-level certificates, so a reviewer who applies rotable rules to the whole parts list generates noise that buries the real exceptions.
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 binder index shows a certificate for every position. Why review further?
An index proves that someone logged a document reference, and no more than that. Acceptance inspectors open the certificates, and defects such as a wrong serial, a missing signature, or an unreadable approval number live inside the form. Sampling regularly shows indexed certificates that were never scanned or that belong to a part no longer installed.
Can the review run before the operator finishes assembling the binder?
Yes, and it is usually more useful that way. Working from the partial source set identifies missing certificates while the operator still has time to chase shops and suppliers, instead of discovering the gaps during acceptance when cure options are limited.
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.