Redelivery binder gap
Gaps in the aircraft redelivery records binder
Redelivery binder gaps mean the assembled return package is missing documents the lease return conditions require, so the binder does not yet support acceptance. It is a problem for lessors, airlines, and MROs assembling or reviewing a return near end of lease. The check reads the binder contents against the return conditions and the index they are built on. You receive a list of missing or non-conforming items mapped to the clause each one satisfies and the path to complete the binder.
When this review is needed
- A return is being assembled and the binder must satisfy every document the return conditions name.
- A binder has been offered and the accepting party needs to confirm what is actually present before signing.
- A return was assembled under time pressure and the index does not match the documents behind it.
The problem
A redelivery binder is built against a specific list of required documents, but the binder is assembled late, from many sources, and against an index that is easier to complete than the evidence it points to. A line on the index can read as satisfied while the document behind it is missing, superseded, or non-conforming. The accepting party then inherits whatever the binder failed to carry.
What gets reviewed
- The return-condition document list and the binder index built from it
- Each required status report, certificate, and evidence item
- Whether each indexed item is present, current, and conforming
- Component, modification, and repair evidence the conditions call for
- Cross-references between the index and the documents behind it
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
- Every document the return conditions require is present in the binder
- Each indexed item points to the actual conforming document, not a placeholder
- Status reports in the binder are current as of the return date
- Certificates and evidence items are the correct type for what they support
- The index and the underlying documents agree item by item
Evidence normally required
- The lease return conditions and the required document list
- The redelivery binder and its index
- Status reports, certificates, and evidence assembled for the return
- Component, modification, and repair records the conditions reference
Common discrepancies
- An indexed item with no conforming document behind it
- A status report in the binder that is out of date as of the return
- A certificate of the wrong type for the evidence it is meant to provide
- An index that lists documents the binder does not actually contain
What is at stake
A binder with gaps can stall acceptance until the missing documents are produced, and once the return is accepted the cost of the gap moves to the accepting party. On a tight return window, items left open in the binder become a list the asset cannot move against until they are closed.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Build the requirement list
Translate the return conditions into the specific documents the binder must carry, clause by clause.
Test the index
Check that each indexed line points to an actual conforming document, not a placeholder or a missing item.
Confirm currency and type
Verify status reports are current as of the return date and each certificate is the right type for what it supports.
Map completion
List each gap against its clause with the responsible party and document needed to close it.
What the buyer receives
- A register of missing or non-conforming binder items mapped to return-condition clauses
- The current state of each indexed item against what the conditions require
- A completion path per item, with the responsible party and document identified
Who uses the output
- Asset managers deciding whether the binder supports acceptance
- Records teams completing the binder before the return window closes
- Transaction stakeholders confirming the package against the lease clauses
How the work fits into the transaction or program
The review checks the binder as the assembled deliverable for the return, so packaging and completeness gaps are caught separately from the underlying records findings that feed it. It feeds the return-condition gap list and the acceptance decision.
Jurisdiction-specific considerations
A binder built for one authority is read against the registry the aircraft is moving to. A document conforming under the prior authority may need a bridging item or an equivalent before the receiving party accepts the return package.
Regulatory limits
The review confirms whether the binder is complete and conforming against the return conditions. It does not accept the return, issue any certificate, or make an airworthiness determination.
What this review does not cover
- Accepting the return or signing technical acceptance
- Negotiating the lease return conditions the binder is built against
- Issuing any certificate or airworthiness determination
Specific to this review
- A binder index is easier to complete than the evidence it points to, so an item can read as satisfied while the document behind it is missing or superseded.
- Once a return is accepted, the cost of a binder gap moves to the accepting party, which makes pre-acceptance the point of maximum leverage to close it.
- Binder completeness and records correctness are checked as distinct problems, since a well-built binder can still carry forward a defective underlying record.
Sources
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.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is a binder gap different from a records discrepancy?
A records discrepancy is a defect in the underlying document. A binder gap is a packaging failure where a required document is missing, superseded, or non-conforming in the assembled return. A binder can be complete and still carry a defective record, so the two are checked separately.
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.
Walk through your situation with an engineer who has done this work.