Boeing 767 redelivery
Boeing 767 family delivery and redelivery binder records review
This review checks that the delivery or redelivery binder for a specific Boeing 767 is complete, correctly indexed, and points to real source records. It is run for a lessor, operator, or buyer assembling or accepting a binder at handover, before either side signs against it. It covers the binder index, acceptance evidence, the discrepancy register, and the source-record references each binder entry relies on. You receive an exception list where an index entry has no record behind it, a source map for the binder, and a plan to close the gaps before acceptance.
When this review is needed
- A 767 lease is ending and the redelivery binder has to satisfy the return conditions before acceptance.
- An operator is receiving the aircraft and needs the delivery binder index to point to real records.
- A binder was assembled under deadline and the index entries have not been checked against their sources.
- A discrepancy register carries items whose closure the binder does not actually evidence.
The problem
A redelivery binder is assembled fast, against a return checklist, and it is easy for the index to promise records that are not behind the tabs. On a 767 the binder pulls from years of maintenance history across multiple systems, and an index entry can point to a status summary rather than the primary record, or to a document that closes a different discrepancy than the one it claims. The accepting party discovers the mismatch during acceptance, when both sides are already at the table.
What gets reviewed
- The binder index reconciled against the documents actually present behind each tab
- Acceptance evidence checked against the return or delivery conditions
- The discrepancy register matched to the closure evidence for each item
- Source-record references verified to point at primary records, not summaries
- Status summaries in the binder traced to the logbooks and status lists behind them
- Open items at handover identified and reconciled with the acceptance conditions
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 index entry has the document it names present and legible behind the tab
- Acceptance evidence satisfies the specific return or delivery condition it is offered against
- Each discrepancy in the register has closure evidence that resolves that item
- Source references point at primary records rather than a status summary standing in for them
- Open items in the binder are consistent with the deferral and finding logs
Evidence normally required
- The delivery or redelivery binder and its index
- The lease return conditions or the delivery acceptance criteria
- The discrepancy register and the closure evidence for each item
- Status summaries and the logbooks or status lists they draw from
- The deferral and open-finding logs current at handover
Common discrepancies
- Index entries pointing to a status summary where the primary record is what the condition requires
- Discrepancy-register items marked closed with evidence that resolves a different item
- Acceptance evidence that does not actually satisfy the return condition it is filed against
- Open items present in the deferral log but absent from the binder's open-item statement
What is at stake
A binder that does not hold up at acceptance stalls the handover and can trigger a return-condition dispute. Missing source records behind index entries push work back onto the returning party under the least favorable timing, and a discrepancy register with unevidenced closures reopens after the aircraft has changed hands. The binder is the handover contract in records form, and a weak one costs both sides.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Reconcile the index
Check every index entry against the document actually present behind its tab.
Test the closures
Match each discrepancy-register item to evidence that resolves that specific item.
Trace to primary records
Confirm source references point at primary records rather than summaries.
Deliver the exceptions
Provide the exception list, source map, and a plan to close gaps before acceptance.
What the buyer receives
- An exception list for index entries lacking a record and for closures that do not resolve their item
- A source map linking each binder entry to the primary record behind it
- A closure plan sequencing the binder gaps against the acceptance date
Who uses the output
- Lessors assembling a redelivery binder that will hold up at acceptance
- Operators accepting an aircraft who need the index to point to real records
- Records teams closing the binder gaps before both parties reach the table
How the work fits into the transaction or program
The binder is where every other records stream converges for handover: configuration, AD, LLP, repairs, deferrals, and release evidence all resolve into an index the two parties sign against. Checking that the index points to primary records, not summaries, means the acceptance meeting confirms a package that is already sound. This review usually follows the individual record checks and pulls their results into the binder that carries the handover.
Aircraft-specific considerations
A 767 redelivery binder can span decades of history and, for a converted airframe, has to carry the freighter-conversion package alongside the passenger-era records. Multiple operators mean the binder pulls from status summaries built under different programs, and older records may exist only as scans of paper originals, so the review scopes to this serial's history and the specific return conditions rather than a generic binder checklist.
Jurisdiction-specific considerations
Return conditions and acceptance criteria are written against the regulatory framework the aircraft is moving between, so an FAA-to-EASA handover requires the binder to satisfy both sides' expectations for the same records. The review notes which framework each acceptance condition serves so the binder maps cleanly for the receiving party.
Regulatory limits
This review checks the binder against its index and the source records. It does not accept or reject the aircraft on any party's behalf, does not sign a delivery or redelivery certificate, and does not make an airworthiness determination.
What this review does not cover
- Physical acceptance inspection of the aircraft
- Signing or countersigning any acceptance certificate
- Negotiation of the return or delivery conditions
Specific to this review
- An index entry that points to a status summary instead of the primary record is the most common way a binder passes assembly but fails acceptance.
- A discrepancy closed with evidence for a different item is a silent defect, because the register reads as clean while a real item stays open.
- The binder is the last place the individual records streams have to agree, so any disagreement between them surfaces here if it was not caught earlier.
- Scanned paper originals in an older 767 binder can be present but illegible, which fails the condition just as surely as a missing document.
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
Why check the binder before the acceptance meeting?
The acceptance meeting is where both parties commit against the binder, and a gap found there is negotiated under pressure. Reconciling the index and testing the closures beforehand means the meeting confirms a package that already holds up, instead of becoming the place the problems are discovered.
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.