Redelivery binder assembly
Aircraft redelivery binder records checklist
A redelivery binder checklist confirms that the records package travelling with an aircraft at lease return is complete, indexed, and internally consistent before handover. It is used by the party assembling the binder and by the party receiving it. It covers the status reports, life-limited part trace, release certificates, and modification evidence the return conditions call for, organized so each item can be found and tied to its source. You receive a completeness matrix, a list of missing or mis-filed sections, and a cross-reference check confirming the index resolves to real documents.
When this review is needed
- An outgoing operator is compiling the data package for an aircraft that is about to be returned.
- A receiving party needs a defined index to check the binder against before it accepts the handover.
- A return condition lists a records standard and the binder has to be built to satisfy each clause.
- A binder was assembled in parts by different teams and needs a single completeness pass before it ships.
The problem
The binder is built clause by clause from a return-conditions list, then populated from status reports, shop packages, and release certificates gathered over the whole lease term. An index is written early and the documents arrive late, so a section can read as present while the document behind it is still outstanding. When the receiving party opens the binder against its own copy of the conditions, the line that fails is usually one the index promised and the package never actually filled.
What gets reviewed
- The binder index and whether every required section is present and populated
- Current AD, SB, and modification status reports and the evidence each summary points to
- Life-limited part trace and the release certificates that support the stated life remaining
- Authorized release certificates for components installed during the lease term
- The certificate of airworthiness, review documentation, and any export paperwork called for
- Cross-references between the index and the documents they are meant to resolve to
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 section named in the return conditions exists in the binder and is not an empty placeholder
- Status reports reference accomplishment or release evidence that is actually filed in the binder
- Life-limited part entries carry the release certificates the stated life depends on
- Components added during the lease have release paperwork matching their part and serial numbers
- The index points to a real document for every line, with no broken cross-reference
- Modification and STC entries carry the approval and instructions-for-continued-airworthiness data they rely on
Evidence normally required
- The lease return conditions and the records standard they name
- Status reports for AD, SB, modification, and life-limited part position
- Release certificates for installed and replaced components
- Airworthiness, review, and export documentation where the conditions require it
- The draft binder index the package is being built against
Common discrepancies
- A binder index that lists a section the underlying documents do not actually fill
- A status report that cites accomplishment evidence missing from the package
- A life-limited part entry with no supporting release certificate behind the stated life
- A component installed during the lease with no release paperwork in the binder
- Cross-references in the index that point to documents filed under a different tab or not at all
- A modification recorded without the approval basis or continued-airworthiness data behind it
What is at stake
A binder that fails acceptance stalls the handover and pushes the outgoing operator back into archives after the aircraft has moved, when the people who can produce a missing certificate are harder to reach. Until the package is whole, the asset cannot carry a clean records baseline into its next lease, and the gap becomes the next set of return conditions to argue over.
How the work runs
Map the clauses
Build a completeness matrix from the return conditions so every required section has a row before the binder is opened.
Populate and mark
Place each document against its clause and flag any section that is indexed but not yet filled by a real document.
Resolve the cross-references
Follow each index entry to the document it names and correct entries that point to the wrong tab or to nothing.
Test the binder
Read the populated package as the receiving party would and deliver the gap list and cross-reference check before handover.
What the buyer receives
- A binder completeness matrix mapping each return-condition clause to its section
- A list of missing, empty, or mis-filed sections to close before handover
- A cross-reference check confirming the index resolves to real documents
Who uses the output
- Asset and records teams assembling the binder before it ships
- Receiving-party reviewers checking the package on handover
- Transaction stakeholders confirming the records baseline for the next lease
How the work fits into the transaction or program
The checklist sits between the records audit that defines what the return owes and the technical acceptance that closes the handover. It turns a clause list into a checked package, so the binder that travels with the asset matches what the conditions called for instead of what the index claimed.
Aircraft-specific considerations
A heavily modified airframe carries more STC and modification evidence than a baseline configuration, so the cross-reference work grows with the modification history rather than the aircraft size. The binder is checked against the specific configuration the conditions reference, not a generic table of contents.
Jurisdiction-specific considerations
A binder that crosses authorities has to satisfy the receiving authority as well as the one the aircraft was operated under. A release certificate accepted on one authority's form is not automatically accepted on another, so the binder check confirms the package supports the configuration and approval basis the receiving side will read it against.
Regulatory limits
The checklist confirms the binder is complete, indexed, and consistent with its source documents. It does not certify the aircraft, perform technical acceptance, or make any airworthiness determination, and a complete binder does not by itself guarantee the return will be accepted.
What this review does not cover
- Physical survey of the aircraft or its components
- Technical acceptance or sign-off of the redelivery
- Negotiation of the lease return conditions the binder is built against
Specific to this review
- A redelivery binder fails acceptance most often on an index that promises a section the documents behind it do not fill.
- Components added during the lease term are the installations whose release paperwork is most likely to be absent at handover.
- The binder is checked against the specific return-condition clauses rather than a generic table of contents, because the required sections vary by lease.
- Modification and STC sections fail more often on missing continued-airworthiness data than on a missing approval, since the approval is filed and the supporting data is not.
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.
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Frequently asked questions
How does the binder checklist relate to a lease-return records audit?
The audit reconciles the records to find what the return actually owes. The binder checklist confirms the package being handed over contains and indexes that evidence, so the two run in sequence rather than in place of each other.
Does a complete binder mean the return will be accepted?
No. A complete, indexed binder removes the records gaps that commonly block acceptance, but acceptance is the receiving party's decision and depends on factors beyond the records package.
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.
Adapt the checklist to your asset, event, and jurisdiction.