Delivery binders
Boeing 777 family delivery and redelivery binder records review
This review tests whether a Boeing 777 delivery or redelivery binder actually delivers what its index promises, by checking each indexed item against the source record it stands for. It is run for a lessor, operator, or buyer at the point of a handover, where the binder is the contractual record of condition. The work confirms the index is complete, acceptance evidence is present, and the discrepancy register captures every open item, so the binder holds up when the counterparty reads it. You receive a verified binder index, a supported exception list of missing or mismatched items, and a closure plan for this tail.
When this review is needed
- A 777 is being redelivered and the binder must be shown to match the lease's records conditions before acceptance.
- A buyer is receiving the aircraft and needs the delivery binder verified against source before closing.
- A discrepancy register is being negotiated and both sides need the open items evidenced rather than asserted.
- The binder was assembled quickly at the end of a lease and its index needs checking before the counterparty reviews it.
The problem
A redelivery binder is judged by its index, and the index is where a rushed handover breaks. A tab points to a document that is a version behind, an acceptance certificate is listed but the signed copy is missing, or the discrepancy register omits an item everyone knew about but no one wrote down. On a 777 the binder runs to thousands of pages, and the receiving party will pull the exact items that are weakest, turning a handover into a standoff over documents that should have been settled.
What gets reviewed
- The binder index checked item by item against the documents it references
- Acceptance and redelivery certificates confirmed present and signed
- The discrepancy register reconciled to the known open items on the aircraft
- Status summaries in the binder dated to the handover point and traced to source
- Cross-references between binder sections checked for consistency
- Completeness of each section against the lease's records delivery requirements
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 indexed item resolves to the correct document at the correct revision
- Acceptance and redelivery certificates are present, signed, and dated
- The discrepancy register captures every open item known at handover
- Status summaries in the binder agree with the source records they represent
- Every section required by the lease is present and complete
Evidence normally required
- The delivery or redelivery binder and its index for the serial number
- The lease's records delivery requirements or agreed binder standard
- The discrepancy register and the list of known open items
- Source status reports for AD, SB, LLP, and configuration
- Acceptance and redelivery certificates for the handover
Common discrepancies
- Index tabs pointing to documents a revision behind the current source
- An acceptance certificate listed in the index with no signed copy behind it
- A discrepancy register missing an open item that was known at handover
- Status summaries in the binder that do not match the source records they cite
What is at stake
A binder that does not match its source records stalls acceptance and hands the counterparty leverage to reopen the condition negotiation. Every mismatch found on their read is a delay to the aircraft's next placement and a cost to the delivering party, and an omitted discrepancy discovered after acceptance can become a claim the binder was supposed to foreclose.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the index as a promise
Treat every indexed item as a claim that must resolve to the correct document at the correct revision.
Resolve items to source
Check each tab against its source record and confirm certificates are present and signed.
Reconcile the discrepancy register
Match the register to the known open items so nothing is omitted at handover.
Sequence the fixes
Deliver a verified index and a plan to close the mismatches before the counterparty reads the binder.
What the buyer receives
- A verified binder index confirming each item resolves to its source
- A supported exception list of missing, misfiled, or mismatched items
- A closure plan ordering the fixes before the counterparty's review
Who uses the output
- Asset managers presenting or accepting the aircraft at handover
- Records teams assembling the binder to the lease's delivery standard
- Transaction stakeholders negotiating the discrepancy register
How the work fits into the transaction or program
The binder review is the last records check before a handover, and it draws on every earlier review. It confirms that the AD, LLP, repair, and configuration positions established upstream are actually represented in the binder the counterparty will read, so a mismatch here usually points back to a document that moved after an earlier review closed.
Aircraft-specific considerations
A 777 records review rests on careful engine-module trace, structural-repair history, ETOPS-related evidence, and heavy-check work-package closure. Those items are the ones a receiving party checks first in a widebody binder, so the review confirms the engine, structural, and heavy-check sections resolve cleanly to source before the counterparty reaches them.
Regulatory limits
This review checks whether the binder matches its source records and the lease's requirements. It does not accept the aircraft, sign a redelivery certificate, resolve the underlying discrepancies, or make an airworthiness determination.
What this review does not cover
- Signing acceptance or redelivery certificates on behalf of either party
- Physical resolution of items on the discrepancy register
- Renegotiation of the lease's records delivery conditions
Specific to this review
- Binders fail on revision control more than on missing documents: the item is present but a version behind.
- The discrepancy register is the highest-stakes section, because an omission there can defeat the protection the binder was meant to give.
- On a 777, receiving parties open the engine, structural, and heavy-check tabs first, so the review checks those sections before the rest.
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 the individual status reviews?
The status reviews verify the AD, LLP, repair, and configuration records themselves. This review checks that those settled positions are correctly represented in the handover binder, with the right documents at the right revisions and a complete discrepancy register, so the binder holds up when the counterparty reads 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.