Delivery and redelivery binder review for the lease transition

When this review is needed

• The binder was assembled over several months and the statuses inside its earliest sections have moved on since.
• The index was copied from a previous transition's template and promises documents this aircraft's file may never have held.
• Counterparty sampling is scheduled and the first misses will determine how deep their page-turn goes.
• Placeholder entries marked to-follow have sat unresolved long enough that nobody remembers what they were waiting for.

The problem

Binders are built over weeks while the underlying records keep moving. A section completed in month one is stale by month three, an index inherited from the last transaction promises a standard file regardless of what this aircraft actually has, and to-follow placeholders quietly become permanent. At acceptance the counterparty does not read everything; it samples. Each sampled line that fails costs credibility for the entire package, and the sample widens with every miss.

What gets reviewed

• Every index line checked for presence, revision currency, and legibility of the document behind it
• Status documents in the binder compared with the latest versions in the working folders
• Binder sections mapped to the return-condition document requirements they exist to satisfy
• Cross-references between binder sections verified in both directions
• Tracker and correspondence items that should have produced binder updates but did not
• Placeholder and to-follow entries, aged and assigned

What gets validated

• The index count matches the binder contents section by section
• No status document in the binder is older than its counterpart in the transition folders
• Documents the return conditions require appear where the index says they do
• Superseded revisions have been retired rather than left filed beside current ones
• Every to-follow placeholder has an owner and a matching entry on the open-item tracker

Evidence normally required

• The binder index at its current revision, together with the binder contents
• The working transition folders the binder was assembled from
• Return-condition document requirements from the lease
• The open-item tracker and recent transition correspondence

Common discrepancies

• Index lines inherited from a prior transition template that this aircraft's file cannot support
• A status list in the binder superseded weeks earlier by the version sitting in the working folders
• Documents present but filed under a different section than the index claims
• Placeholders that became permanent because no tracker entry was ever raised for them

What is at stake

An index that fails sampling invites a full-file page-turn, which stretches the acceptance timeline by days or weeks. Documents found missing or superseded at the table get logged as findings with settlement value attached. A binder rebuilt in a rush during acceptance week duplicates work already done once and introduces fresh errors under the worst possible time pressure.

How the work runs

What the buyer receives

• An index-referenced exception list for the binder as presented
• A currency table flagging binder documents older than their folder counterparts
• A shortlist of updates to complete before counterparty sampling begins

Who uses the output

• Records staff finalizing the binder ahead of acceptance
• Transition leads deciding when the binder is ready to hand over
• Counterparty representatives who receive a package that has already been tested

How the work fits into the transaction or program

The binder check is a late-stage integration test of the whole transition records effort. Upstream reviews of AD status, repairs, and configuration settle what the content should say; this review settles whether the assembled package presents that content completely and at current revision. Most findings route back to the assembling team rather than across the table, which is the point of running it first.

Jurisdiction-specific considerations

Binder structure is contractual, but the records inside carry regulatory weight: 14 CFR 91.417 defines what an owner must keep and 14 CFR 91.419 requires records to transfer with the aircraft at sale, while EASA-side continuing-airworthiness records pass to the receiving operator or CAMO under Regulation (EU) No 1321/2014. A binder that satisfies the lease but omits records the receiving framework expects still leaves the incoming side with a compliance problem.

Regulatory limits

The review compares documents against an index and a requirement list. It does not certify the completeness of the aircraft's records in any regulatory sense, does not create or approve records, and takes no position on return-condition compliance, which remains a matter between the parties.

What this review does not cover

• Assembling, re-filing, or physically reorganizing the binder
• Drafting or negotiating return-condition positions
• Verifying the quality of maintenance work behind the documents

Specific to this review

• Binder sampling failures compound, because counterparties widen their sample after the first miss, which makes early exceptions disproportionately expensive.
• Elapsed time since a section was assembled is the most reliable predictor of its staleness, so the sections finished first deserve the final check.
• Index templates carried between transitions are efficient and dangerous for the same reason: they assert a standard file shape regardless of what this aircraft's history produced.
• A digital binder does not remove the currency problem; it makes superseded versions easier to leave in place unnoticed.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits