Delivery and redelivery binder records checked against the sources they cite

When this review is needed

• The binder was assembled by several teams over months and nobody owns the index end to end.
• An acceptance date is set and the lessor's checklist will be worked directly against the index as presented.
• Sections were converted from a prior operator's binder structure and the rows were carried across untested.
• Records that must transfer with the aircraft under 14 CFR 91.419 need the index as the instrument proving they did.

The problem

Indexes decay in predictable ways. Rows get added when documents are promised rather than filed, revisions supersede filed copies without the row updating, and whole sections inherit a prior structure whose contents nobody re-verified. The binder then projects a confidence its paper does not support, and every discovery made during acceptance week costs multiples of what the same discovery would have cost a month earlier.

What gets reviewed

• Every index row resolved to a filed document at the stated revision
• Section structures compared against the lease's return-condition and delivery-condition requirements
• Cross-references between sections tested, for example a repair row pointing to its approval-data row
• Documents found in the binder but absent from the index cataloged and placed
• What the index claims is closed reconciled against acceptance notes and discrepancy registers
• Revision control checked wherever multiple copies of the same record exist

What gets validated

• Row-level presence: the document exists, is legible, and matches the title, date, and revision the index states
• No placeholder rows, meaning nothing indexed as filed on the strength of a promise or a pending request
• Structural completeness: each annex-required section exists and is populated, or its emptiness is explained
• Duplicate and superseded copies are marked so the current record is unambiguous
• Unindexed documents are dispositioned into the structure rather than left loose

Evidence normally required

• The binder index at its current revision, with prior revisions where the structure changed
• The full binder contents, physical or digital
• The lease return-condition and delivery-condition annexes
• Acceptance notes and open discrepancy registers

Common discrepancies

• Rows created when a record was requested from a shop, still marked as filed months after the request went unanswered
• A section inherited from the previous operator whose rows cite that operator's document numbers, none matching the filed copies
• Two revisions of the same status list filed in different sections with the index citing the older one
• Dozens of legitimate records sitting unindexed in an overflow folder, invisible to acceptance

What is at stake

An index that fails sampling early in acceptance changes the inspector's posture toward the entire binder, and sampling escalates into full-population checking that extends the return by days. Rows promising missing records become disputed items, while records present but unindexed effectively do not exist at the negotiation table.

How the work runs

What the buyer receives

• A verified index with each row's status recorded and dated
• The gap list split by cure type: recover, refile, or re-index
• A reconciliation memo for acceptance explaining every variance between index and contents

Who uses the output

• Binder owners at the returning operator directing the remaining assembly effort
• Lessor acceptance teams deciding how deeply to sample each section
• The next transaction's data-room team, which inherits the verified structure

How the work fits into the transaction or program

This review runs before or alongside the record-type reviews covering structure, ADs, deferrals, and the review file, because those reviews consume the index and an unproven index sends them chasing documents that were never there. Once verified, the index anchors the acceptance meeting and later becomes the skeleton of the delivery binder handed to the next lessee.

Jurisdiction-specific considerations

Under the FAA framework the transfer obligation is explicit: 14 CFR 91.419 requires specified maintenance records to move with the aircraft, and 91.417 defines what must exist to transfer. EASA-context returns lean on Part-M record requirements and the incoming CAMO's need to take over a coherent set. Either way the index is how the transfer gets evidenced, so both regimes are considered whenever the return crosses registries.

Regulatory limits

The review establishes correspondence between index and contents. It does not judge the airworthiness significance of individual records, certify the binder as compliant with the lease, or make the completeness determination that belongs to the accepting party and, where applicable, the authority.

What this review does not cover

• Deep technical review of each record's content, which the record-type reviews perform
• Scanning, filing, or physical reorganization of the binder
• Drafting or amending the lease's return-condition annex

Specific to this review

• Index rows fail in both directions, and the unindexed-but-present population is routinely as large as the missing one; only the missing rows get attention because only they are visible.
• A reliable early indicator of binder quality is the ratio of rows citing a revision and date to rows citing only a title.
• Acceptance inspectors sample, and a binder that passes its first two sampled sections earns lighter treatment for the rest, which makes accuracy in the opening sections disproportionately valuable.
• When a binder is digitized after assembly, the scan structure often becomes a second index that drifts from the first, and acceptance can end up run against the wrong one.
• Sections assembled last, typically deferrals and open items, show the highest index error rates because they keep changing while the index is being finalized.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits