G650 handover binder
Gulfstream G650 delivery and redelivery binder records review
This review checks that the delivery or redelivery binder for a Gulfstream G650 is complete and that every entry ties back to a source record. It is run for a lessor, owner, or management provider assembling or accepting a binder at handover. The work tests the binder index against what it claims to contain, confirms the acceptance evidence and discrepancy register are consistent, and traces each referenced document to where it actually lives. You receive an index-to-source reconciliation, an exception list for entries that do not resolve to a document, and a closure plan before the binder is signed.
When this review is needed
- A redelivery is being assembled and the binder has to hold up when the receiving party checks it.
- An aircraft is being accepted and the recipient wants the binder reconciled before signing.
- A prior handover left a binder whose index and contents were never fully matched.
- A discrepancy register was carried into the binder and its items need confirming before closeout.
The problem
A handover binder is where the whole records file gets compressed into an index, and the index is where it quietly fails. On a G650 the binder pulls acceptance certificates, status summaries, the discrepancy register, and pointers to source records, often under time pressure at the end of a transaction. An index line that points to a document the binder does not contain, or a discrepancy shown resolved without the closing evidence, passes unnoticed until the receiving party works the binder line by line.
What gets reviewed
- The binder index tested against the documents the binder actually contains
- Acceptance and delivery certificates confirmed present and consistent
- The discrepancy register reconciled to its closing evidence
- Status summaries in the binder tied to the source status records
- Cross-references from the binder to logbooks and release documents
- Duplicate, superseded, or missing entries flagged against the index
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 the binder actually contains
- Discrepancy register items shown closed have the evidence that closes them
- Acceptance certificates are present and consistent with the delivery condition recorded
- Status summaries in the binder reconcile to the underlying status records
- Referenced source documents are retrievable rather than named but absent
Evidence normally required
- The delivery or redelivery binder and its index
- Acceptance and delivery certificates for the handover
- The discrepancy register and its closing evidence
- Status summaries and the source status records behind them
- Logbooks and release documents the binder references
Common discrepancies
- An index line pointing to a document the binder does not actually contain
- A discrepancy shown resolved in the register with no closing evidence attached
- A status summary in the binder that does not match the source record
- A referenced source document named in the binder but not retrievable
What is at stake
A binder whose index does not resolve to source records slows acceptance and erodes trust in the whole file. The receiving party stops taking entries on faith and re-checks everything, which is exactly the delay the binder was meant to prevent. A discrepancy carried as resolved but not actually closed becomes the recipient's problem the moment they sign.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Test the index
Confirm every index line resolves to a document the binder actually holds.
Reconcile the register
Match each discrepancy shown closed to the evidence that closes it.
Tie summaries to source
Trace status summaries in the binder back to the underlying records.
Close before signing
List the entries that do not resolve and clear them before handover.
What the buyer receives
- An index-to-source reconciliation for the binder
- An exception list for entries that do not resolve to a document
- A closure plan for the gaps before the binder is signed
Who uses the output
- Asset managers assembling a binder that will survive the recipient's review
- Records teams reconciling the index before a handover closes
- Receiving parties confirming the binder before they accept the aircraft
How the work fits into the transaction or program
The binder review is the last records step before a handover closes. It draws on the status, discrepancy, and configuration work done earlier and confirms the binder faithfully represents them, so the receiving party accepts on a reconciled document rather than reopening the file entry by entry.
Aircraft-specific considerations
On a managed G650, the redelivery binder frequently has to reflect owner-specific cabin and connectivity configuration alongside the standard status evidence, so the index carries more configuration references than a commercial handover would. Those references are the entries most likely to point to installation records held outside the core maintenance file, which is where the index-to-source check earns its keep on this asset.
Regulatory limits
The review reconciles the binder against its source records. It does not accept the aircraft on any party's behalf, resolve a discrepancy, or make an airworthiness determination on the asset being handed over.
What this review does not cover
- Accepting or delivering the aircraft on any party's behalf
- Resolving the discrepancies the register carries
- Any airworthiness determination on the aircraft
Specific to this review
- The index is where a handover binder fails: a line that points to a document the binder does not contain reads as complete until someone opens the tab.
- A discrepancy marked resolved without closing evidence transfers to the recipient the moment the binder is signed.
- On a G650, configuration references in the binder often point to installation records kept outside the core file, so they are checked first.
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 was assembled by the other side. Can you still reconcile it?
Yes. The review works from the binder and its index as delivered, tests each line against the documents present, and flags the entries that do not resolve. That gives the accepting party a clear list to raise before signing rather than discovering the gaps afterward.
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.