Delivery and redelivery
Boeing 787 family delivery and redelivery binder records review
This review checks that a Boeing 787 delivery or redelivery binder actually contains what its index promises and that each entry points to a real source record. It is run by or for the party accepting or handing over the tail, at the point of transfer. It covers the binder index, the acceptance evidence, the discrepancy register carried at handover, and the references linking each tab back to source. You receive a reconciled binder, a list of index entries that do not resolve to a document, and a discrepancy view the receiving party can rely on.
When this review is needed
- A 787 is being redelivered and the binder has to match the lease's records conditions tab for tab.
- The receiving party wants the binder verified before it signs acceptance and inherits the file.
- A prior handover left a discrepancy register open and it now anchors the redelivery.
- The binder was assembled in a rush and its index has not been reconciled to the documents it lists.
The problem
A binder index is a promise, and at handover the promise gets tested. An index line points to a document that is not behind the tab, an acceptance certificate references a status that the discrepancy register contradicts, or the same finding appears in two places with different wording. The party signing acceptance is agreeing to whatever the binder actually holds, and a binder that does not reconcile turns the handover into an argument.
What gets reviewed
- The binder index reconciled tab by tab against the documents actually present
- Acceptance evidence checked against the status it certifies
- The discrepancy register carried at handover and its agreement with the file
- Cross-references from binder entries back to their source records
- Duplicate or contradictory entries identified across the binder
- Index lines that point to documents the binder does not contain
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 line resolves to a legible document behind the correct tab
- Acceptance certificates reference a status the discrepancy register supports
- The discrepancy register at handover agrees with the aircraft's open items
- Source references in the binder point to retrievable records, not dead links
- No two binder entries contradict each other on the same finding or status
Evidence normally required
- The delivery or redelivery binder and its index
- The lease or purchase records conditions the binder must satisfy
- The acceptance evidence and certificates included at handover
- The discrepancy register carried into the transfer
- The source records the binder entries reference
Common discrepancies
- An index line pointing to a document that is not behind its tab
- An acceptance certificate citing a status the discrepancy register contradicts
- The same finding recorded twice with different wording in different tabs
- A source reference that does not resolve to a retrievable record
What is at stake
An index that does not resolve to documents forces the receiving side to hunt during the handover, which slows acceptance and weakens the position of the party that assembled it. A discrepancy register that contradicts the acceptance evidence can reopen the technical conditions after signature, and a missing tab discovered later becomes the new owner's gap to close.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Reconcile every index line against the document actually present behind its tab.
Cross-check acceptance
Confirm acceptance evidence and the discrepancy register agree with each other.
Resolve the references
Verify each source reference points to a retrievable record.
Report the unresolved
Deliver the reconciled binder and the list of entries that do not resolve.
What the buyer receives
- A reconciled binder with every index line resolved to a document
- A list of index entries and references that do not resolve
- A discrepancy view the receiving party can sign against
Who uses the output
- Receiving-side teams verifying the binder before they sign acceptance
- Handover teams reconciling the binder to the lease conditions
- Records staff closing the entries that do not resolve before transfer
How the work fits into the transaction or program
The binder is the handover artifact that carries the file across the transfer, and this check confirms it holds before signature rather than after. What it surfaces feeds the discrepancy remediation and sets the baseline the receiving operator inducts on.
Aircraft-specific considerations
A 787 binder carries more configuration and systems documentation than an older widebody, so the index reaches into software part numbers, electrical change records, and composite repair substantiation. Those tabs are where an index line most often fails to resolve, because the underlying document lives in a configuration system rather than a conventional record set and can be listed without being attached.
Jurisdiction-specific considerations
An FAA-to-EASA redelivery brings the receiving side's records conventions to the binder, so a tab that satisfies one system's expectations may need re-presentation for the other. The review notes where the binder's structure or evidence will have to be adapted for the receiving register rather than assuming the outgoing format transfers.
Regulatory limits
The review confirms the binder is internally consistent and resolves to source. It does not accept the aircraft on any party's behalf, certify the discrepancy status, or make an airworthiness determination at handover.
What this review does not cover
- Signing acceptance or redelivery of the aircraft
- Closing the discrepancies the register carries
- Physical inspection of the aircraft at handover
Specific to this review
- The binder index is where handovers slow down: a line that does not resolve to a document is discovered exactly when both parties are at the table.
- Duplicate entries with different wording on the same finding create disputes because each side reads the version that suits it.
- 787 binder tabs often reference configuration-system documents, which can be listed in the index without being physically attached.
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
Is this the same as checking the aircraft meets its redelivery conditions?
No. This confirms the binder is complete and internally consistent so acceptance is not signed against a file that does not resolve. Whether the aircraft meets the technical redelivery conditions is a separate judgment the parties make against the reconciled record.
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.