Delivery & redelivery binder
Cessna Citation Longitude delivery and redelivery binder records review
This review checks that the delivery or redelivery binder for a Cessna Citation Longitude is complete, that its index points to documents the binder actually holds, and that its acceptance evidence and discrepancy register reconcile against the source records. A records specialist runs it as a handover is assembled or received, before the binder becomes the contractual record of the transfer. It walks the binder index, the acceptance evidence, the discrepancy register, and the references back to the source records, confirming each index line resolves to a real document and each accepted discrepancy is captured. You receive a binder-completeness assessment, an exception list of index lines with no document and discrepancies not carried into the register, and a source map tying the binder to the file behind it.
When this review is needed
- A redelivery binder is being assembled and every index line has to resolve to a document before handover.
- A binder is being received and the accepting party wants it reconciled to the source records before signing.
- Discrepancies accepted during handover have to be confirmed as captured in the binder's register.
- A prior binder was assembled in a hurry and its index no longer matches the documents it contains.
The problem
The redelivery binder is the document that stands for the whole transaction after the aircraft has moved, so a gap in it is a gap that surfaces when leverage is gone. An index built while the binder is still being assembled ends up pointing to documents that were meant to go in but never did, acceptance evidence gets signed against a status that the source records do not quite match, and discrepancies agreed verbally at handover never make it into the register. On a business jet handover, where the binder is often compiled quickly against a delivery deadline, those gaps are easy to introduce and hard to see until the binder is the only record left.
What gets reviewed
- The binder index checked line by line against the documents the binder actually contains
- Acceptance evidence reconciled against the status the source records support
- The discrepancy register confirmed to capture every item accepted at handover
- References from binder entries back to their source records confirmed as resolvable
- Missing tabs, sections, or documents the binder structure calls for identified
- The binder cross-checked against the status summaries the transaction relied on
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
- Acceptance evidence reconciles to the status the underlying source records support
- Each discrepancy accepted at handover appears in the register with its basis
- References from the binder to source records resolve rather than pointing to nothing
- The binder structure is complete against the sections the handover requires
Evidence normally required
- The delivery or redelivery binder and its index
- The acceptance evidence and sign-off documents for the handover
- The discrepancy register or accepted-exceptions schedule
- The source records the binder entries reference
- The status summaries the transaction was agreed against
Common discrepancies
- An index line pointing to a document the binder does not actually contain
- A discrepancy accepted at handover that never made it into the register
- Acceptance evidence signed against a status the source records do not fully support
- A binder reference to a source record that cannot be resolved back to the file
What is at stake
A binder whose index does not resolve to real documents leaves the accepting party unable to prove what was actually delivered, and a discrepancy accepted at handover but never entered in the register can be disputed later with no record to settle it. Once the aircraft has moved and the deadline has passed, reconstructing a source reference or reopening an accepted discrepancy is far harder than catching the gap while the binder is still being assembled.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Test the index
Check every index line against the documents the binder actually contains.
Reconcile acceptance
Confirm the acceptance evidence matches the status the source records support.
Capture the discrepancies
Verify every item accepted at handover appears in the register with its basis.
Map and flag
Tie each entry to its source and list index lines and discrepancies that do not resolve.
What the buyer receives
- A binder-completeness assessment stating whether the binder reconciles to its source records
- An exception list of index lines with no document and discrepancies missing from the register
- A source map tying each binder entry to the record behind it
Who uses the output
- Records teams assembling a redelivery binder that will hold as the record of the transfer
- Accepting parties reconciling a received binder before they sign for it
- Asset managers relying on the binder as the contractual account of the handover
How the work fits into the transaction or program
The binder is the endpoint the other records reviews feed, consolidating the non-routine closures, the status figures, and the accepted discrepancies into the document that represents the transfer. This review confirms that consolidation is complete and reconciles to its sources before the binder is signed, so a gap gets closed while the parties are still at the table rather than after the aircraft has moved.
Aircraft-specific considerations
A Citation Longitude changing owners or managers moves faster than a commercial aircraft off lease, and its binder is often assembled by a management company against a delivery date rather than by a dedicated records team, so the pressure that introduces index-to-document gaps is high. The review weighs the avionics-configuration and cabin-equipment sections most closely, because those are the parts of a business jet binder where a document meant to be included is most often left out.
Jurisdiction-specific considerations
A binder assembled for an FAA handover and one an EASA operator will accept differ in the release and airworthiness-review documents they must contain, so a Longitude changing registers at handover needs its binder built to the receiving system's expectations, and the review notes where a binder complete for one authority lacks a document the other requires.
Regulatory limits
The review confirms the binder is complete and reconciles to its source records. It does not accept or deliver the aircraft, sign the handover, or make an airworthiness determination on the records the binder contains.
What this review does not cover
- Accepting or delivering the aircraft on any party's behalf
- Signing or witnessing the handover documentation
- Any airworthiness determination on the records in the binder
Specific to this review
- The binder's most common defect is an index line with no document behind it, introduced when the index is written before the binder is finished being assembled.
- A discrepancy accepted verbally at handover but never entered in the register is unenforceable later, so the register reconciliation is where post-handover disputes are prevented.
- On a business jet the avionics and cabin-equipment sections are where a document is most often left out, because those records move between shops during the upgrades that precede a sale.
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 looks complete. Why reconcile it to the source records?
A binder can look complete and still have index lines pointing to documents it does not contain, or acceptance evidence signed against a status the source records do not fully support. Reconciling the binder to its sources before it is signed is how you confirm it will hold as the record of the transfer once the aircraft has moved and the leverage to fix it is gone.
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.