Dassault Falcon 7X delivery and redelivery binder records review

When this review is needed

• A lease return is approaching and the binder has to satisfy the return conditions before the aircraft is accepted back.
• An incoming operator is receiving the aircraft and needs the delivery binder confirmed before it drives their entry status.
• The binder was assembled quickly and the index promises documents the receiving side has not yet seen.
• A prior redelivery left a discrepancy register open and the current holder cannot tell which items were ever closed.

The problem

A redelivery binder is judged on its index long before anyone opens every tab. An index that reads complete gets accepted, and the missing certificate or the unsigned acceptance sheet is discovered weeks later when it is far harder to obtain. On a returning Falcon 7X, the party who accepts the binder inherits whatever the tabs do not contain.

What gets reviewed

• The binder index tested tab by tab against the documents it lists
• Acceptance and conformity evidence supporting handover for this serial number
• The discrepancy register with proof of closure for each recorded item
• Cross-references from the binder into the airframe, engine, and APU record sets
• Continuity of the binder across any change of operator captured in the redelivery
• Coverage of the three PW307A engine positions and their status within the binder

What gets validated

• Every index line resolves to a legible, complete document rather than a placeholder or a reference
• Acceptance sheets carry the required signatures and match the configuration handed over
• Each discrepancy register entry shows how and when it was closed, or is flagged as still open
• Status figures quoted in the binder reconcile with the logbooks and standalone status lists
• Engine and APU documents in the binder cover all installed positions with no substituted serial numbers

Evidence normally required

• The complete delivery or redelivery binder with its index
• Acceptance certificates, conformity statements, and handover protocols
• The discrepancy register and any corrective-action records tied to it
• Airframe, PW307A engine, and APU record sets referenced by the binder
• The lease return conditions or purchase terms the binder is meant to satisfy

Common discrepancies

• Index entries that point to documents not actually filed in the binder
• Acceptance sheets missing a signature or referencing a configuration that later changed
• Discrepancy items recorded at redelivery with no evidence they were ever closed
• Engine status pages in the binder that predate the last shop visit on that position

What is at stake

If the binder is accepted and the source records behind it are thin, the return conditions were technically met on paper but not in fact. The receiving party is left chasing the previous holder for documents after the deal has closed, and any discrepancy that was recorded but never resolved becomes a live liability on an asset that has already changed hands.

How the work runs

What the buyer receives

• An exception list of every broken index reference and unsupported binder claim
• A source map linking each binder tab to the record that should sit behind it
• A closure plan identifying the documents needed to make the binder complete for this tail

Who uses the output

• Asset managers deciding whether a returning binder meets the lease conditions
• Records teams building the entry file for an incoming Falcon 7X
• Transaction leads who will rely on the binder as the handover record of what transferred

How the work fits into the transaction or program

The binder is the packaged output of a redelivery, and everything downstream trusts its index. This review checks that packaging before it is accepted, so the binder feeds a clean entry baseline instead of becoming the first source of disputes. It runs alongside the return-conditions check and ahead of the receiving operator setting its status.

Aircraft-specific considerations

A Falcon 7X binder has to carry status for three PW307A positions and a fly-by-wire flight-control configuration, so a two-engine binder template leaves gaps that are easy to miss on a fast index read. Because these aircraft are managed across multiple service providers over their life, the binder often stitches together records from several sources, and the seams are where index and source most often disagree.

Jurisdiction-specific considerations

Whether the Falcon 7X returns onto an EASA or an FAA register shapes which acceptance evidence the binder must hold. A binder built for one authority's return standard may omit forms the receiving side treats as mandatory, so the index has to be read against the destination rules, not the ones the last operator worked under.

Regulatory limits

This review reports on the completeness and traceability of the binder. It does not certify the aircraft as airworthy, confirm that lease return conditions are legally met, approve the handover, or replace the acceptance decision of the receiving party.

What this review does not cover

• Physical inspection of the aircraft or a boroscope of the binder's referenced work
• A ruling on whether the lease return conditions are contractually satisfied
• Assembling or reconstructing the binder from scratch

Specific to this review

• A binder is usually accepted on the strength of its index, so an index that overstates its contents is the highest-leverage defect to catch.
• The discrepancy register is where redelivery liabilities hide; an item recorded but never closed transfers with the aircraft.
• Falcon 7X status must span three engine positions, so a single stale engine tab can fail an otherwise complete binder.
• When a binder pulls records from several providers, the index and the underlying documents were often built by different hands and rarely reconcile on the first pass.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits