Delivery and redelivery
Bombardier Global 7500 delivery and redelivery binder records review
This review checks that a Bombardier Global 7500's delivery or redelivery binder is complete, indexed, and backed by the source records it claims. It is run by or for the party accepting or handing over the aircraft, at the point where the binder becomes the agreed account of what changed hands. It examines the binder index, the acceptance evidence, the discrepancy register carried at handover, and the source-record references each tab points to. You receive an exception list of index entries with no backing document, a source map for the binder, and a plan to close the discrepancies before acceptance.
When this review is needed
- The aircraft is being accepted and the binder is about to become the agreed record of the handover.
- A lease is ending and the redelivery binder has to reconcile to the source records before sign-off.
- An index tab points to a document that the receiving party cannot locate in the binder.
- A discrepancy register was carried at delivery and its items have to be resolved before acceptance.
The problem
A redelivery binder is the interface where two parties agree on what the aircraft is, so any tab that points to a document not actually present becomes a dispute at the worst moment. On a Global 7500 the binder can be assembled quickly under a redelivery deadline, and an index that reads complete while the underlying scans are missing, illegible, or filed against the wrong tab shifts the burden onto whoever accepts it. Once acceptance is signed, that burden does not go back.
What gets reviewed
- The binder index checked tab by tab against the documents actually filed
- Acceptance evidence confirming each handover milestone was met
- The discrepancy register reconciled to the open items still outstanding
- Source-record references verified to point to the real underlying document
- Legibility and completeness of the scans behind each index line
- Cross-reference between the binder and the status summaries it should agree with
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 document that is present, legible, and correctly filed
- Acceptance evidence covers each milestone the handover agreement requires
- The discrepancy register reflects the same open items a fresh review would find
- Source-record references point to the actual document, not a placeholder or duplicate
- The binder reconciles with the current status summaries for AD, LLP, and configuration
Evidence normally required
- The delivery or redelivery binder with its index
- The handover or lease agreement's records requirements
- The discrepancy register carried at delivery
- Current AD, LLP, and configuration status summaries
- The source records the binder index references
Common discrepancies
- An index tab pointing to a document the binder does not actually contain
- An image-only scan behind an index line that cannot be read or cited
- A discrepancy left open in the register with no closure recorded
- A binder status summary that disagrees with the current AD or LLP position
What is at stake
An index that overstates the binder leads the accepting party to sign for records they do not hold, and the missing documents then have to be chased after leverage has passed. Discrepancies left in the register at acceptance become the new owner's open items, and reconstructing a source document after handover is harder than confirming it while the counterparty is still on the hook.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Check each tab against the document actually filed behind it for presence, legibility, and correct placement.
Confirm acceptance evidence
Verify each handover milestone is supported by the evidence the agreement requires.
Reconcile the register
Match the discrepancy register to the open items a fresh review finds.
Close before sign-off
Sequence the missing documents and open discrepancies to resolve while leverage holds.
What the buyer receives
- An exception list of index entries with missing, illegible, or mis-filed backing documents
- A source map tying each binder tab to the record that supports it
- A closure plan for the discrepancies to resolve before acceptance is signed
Who uses the output
- Asset managers deciding whether the binder is safe to accept as delivered
- Records teams reconciling the binder to source before sign-off
- Transaction stakeholders holding the counterparty to the open discrepancies
How the work fits into the transaction or program
The binder review is the last records gate before acceptance, sitting after the individual status reviews and pulling their results into the document the two parties will sign against. Its closure plan drives the corrections that have to land while the handing-over party still has an obligation to supply them.
Aircraft-specific considerations
A Global 7500 binder carries engine and APU release evidence, cabin-system acceptance, and configuration records that a generic template does not anticipate, so the index is checked against what this type actually needs rather than a standard tab list. Because these aircraft often transition between management providers, a redelivery binder can inherit gaps from an earlier handover that were never closed, and those surface again here.
Jurisdiction-specific considerations
A binder assembled for an FAA handover and one built for an EASA redelivery emphasize different acceptance evidence, so a binder crossing systems needs its index checked against the receiving side's expectations. The review flags where the binder would need supplementing for the destination register.
Regulatory limits
The review confirms the binder reconciles to its source records and the handover requirements. It does not accept the aircraft on a party's behalf, sign the redelivery, or make any airworthiness determination.
What this review does not cover
- Signing acceptance or redelivery on behalf of either party
- Negotiating which discrepancies the counterparty will close
- Physical inspection tied to a binder acceptance item
Specific to this review
- The binder index is a promise, and a tab that points to a document not present converts directly into a post-acceptance liability.
- Leverage to close a discrepancy lives with the handover, so an open register item is far cheaper to resolve before sign-off than after.
- Image-only scans behind an index line slow acceptance even when the underlying record exists, because they cannot be cited or searched.
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
The binder index looks complete, so why review it further?
A complete-looking index is exactly the risk. Index entries can point to documents that are missing, illegible, or filed against the wrong tab, and once acceptance is signed the accepting party owns those gaps. Checking the index against the source records before sign-off keeps the burden with the party still obligated to supply them.
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.