Redelivery binder
Airbus A330 family delivery and redelivery binder records review
This review tests whether an A330 delivery and redelivery binder is complete, correctly indexed, and backed by the source records it claims. It is run for the delivering or receiving party around a lease return or a sale handover. The work checks the binder index against its contents, the acceptance evidence against the aircraft's actual status, and the discrepancy register against what was really open at handover. You receive an exception list of missing or misindexed items, a map from each binder tab to its source record, and a plan to complete the binder before signing.
When this review is needed
- A lease return is imminent and the binder has to satisfy the lease's records conditions.
- The binder index lists items that are not actually behind the tab, or the reverse.
- Acceptance evidence in the binder does not match the aircraft's current status.
- The discrepancy register understates what was really open at handover.
The problem
A redelivery binder is where the whole records history is supposed to converge, and it is assembled under deadline pressure at exactly the moment attention is thinnest. On an A330 return, the index promises documents the tabs do not hold, acceptance certificates get filed against a status that has since moved, and the discrepancy register reflects negotiation rather than the true open position. The receiving side then rejects the binder tab by tab, and the return stalls.
What gets reviewed
- Binder index reconciled against the documents actually behind each tab
- Acceptance evidence checked against the aircraft's current status at handover
- Discrepancy register compared with the true open-item position
- Source-record references confirmed to resolve to a real, retrievable document
- Binder completeness tested against the lease or sale records conditions
- Cross-references between binder sections checked for internal 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
- Every item the index lists is present and correctly placed behind its tab
- Acceptance certificates match the aircraft's status as of the handover date
- The discrepancy register reflects the genuine open position, not a negotiated subset
- Each source reference in the binder resolves to a retrievable underlying record
- The binder meets the records conditions set out in the lease or sale agreement
Evidence normally required
- The draft delivery and redelivery binder and its index
- The lease or sale records conditions the binder must satisfy
- Acceptance and discrepancy documents prepared for handover
- The underlying status and source records the binder cites
- The open-item and deferral position at the handover date
Common discrepancies
- Index entries with no matching document behind the tab
- Acceptance evidence filed against a status that has since changed
- A discrepancy register that understates the real open position
- Source references that do not resolve to a retrievable record
What is at stake
A binder that fails on acceptance drags out the redelivery, and every day the aircraft sits unaccepted carries cost for one side or the other. Missing or misindexed items reopen the underlying records questions the binder was meant to settle, and a discrepancy register that understated the open position invites dispute after the aircraft has changed hands.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Reconcile index to contents
Check that every item the index lists is present and correctly placed behind its tab.
Test acceptance evidence
Confirm acceptance certificates match the aircraft's status as of the handover date.
Verify the discrepancy register
Compare the register against the true open position and flag any understatement.
Complete for signing
List the gaps, map each tab to its source, and plan the binder to a signable state.
What the buyer receives
- An exception list of missing, misindexed, or unsupported binder items
- A source map from each binder tab to its underlying record
- A completion plan to close the binder before the handover is signed
Who uses the output
- Records teams completing the binder ahead of a lease return
- Asset managers confirming the handover package before acceptance
- Receiving parties checking the binder against the records conditions
How the work fits into the transaction or program
The redelivery binder is the convergence point for the AD, LLP, deferral, and airworthiness-review positions, and it inherits any gap those reviews left open. This review confirms the binder actually holds what it claims and ties each tab to a real record, so acceptance proceeds without the tab-by-tab rejection that stalls returns.
Aircraft-specific considerations
An A330 lease return binder tends to run long because widebody cabins, long-haul equipment, and layered modification histories generate more tabs than a narrowbody return. A serial number that has been through prior returns often carries a binder built from earlier binders, so the review checks that the index reflects the current aircraft rather than an inherited structure.
Jurisdiction-specific considerations
The records the binder must contain depend on the registry the aircraft is returning to or moving onto, and the acceptance criteria follow that registry's expectations. The review confirms the binder meets those expectations in content but does not accept the aircraft or sign the redelivery.
Regulatory limits
The review reports on the completeness and support of the binder as of the review date. It does not accept the aircraft, sign the redelivery, or make an airworthiness determination about the asset.
What this review does not cover
- Accepting the aircraft or signing the redelivery on either party's behalf
- Negotiating the discrepancy register or the return conditions
- Physical inspection of the aircraft at handover
Specific to this review
- A binder fails most often on the index, where listed items are not behind the tab they promise.
- Acceptance certificates go stale quickly because status moves between the filing date and the handover.
- A widebody return binder runs long, so index-to-content mismatches are easy to miss under deadline.
- A binder rebuilt from a prior return often carries an index describing a different configuration than the current aircraft.
- A source reference that points to a document nobody can retrieve is worse than a missing one, because it reads as complete until tested.
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.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is this different from a general records audit?
A records audit examines the underlying records across the aircraft. This review examines the binder that presents them at handover: whether it is complete, correctly indexed, and backed by retrievable source records against the lease or sale conditions. It assumes the underlying records exist and tests whether the binder proves it.
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.