Delivery and redelivery binder review for an aircraft changing registry

When this review is needed

• A redelivery binder built by the outgoing operator is about to become the incoming side's primary reference.
• The binder index was inherited from a previous transaction and nobody has reopened it since.
• An importing authority or receiving registry will sample the binder and the team wants the misses found first.
• Documents were swapped or updated late in the transition and the index may no longer describe what the binder holds.

The problem

A binder index is a promise about what the file contains, and transitions test that promise under time pressure. Binders assembled by different teams over years accumulate silent drift: a revision noted in the index that was never filed, a certificate replaced without the index changing, a tab that points at a document belonging to a different serial number. The reader who finds the drift is usually the counterparty, at the moment it costs the most.

What gets reviewed

• Every binder index entry opened and matched to the document actually filed behind it
• Document revisions and dates in the binder compared with the versions the source package holds
• Serial-number and registration checks so no document belongs to a different aircraft
• Index coverage tested against the transaction's agreed records standard
• Late-transition document swaps reconciled between the index and the physical or digital file
• Cross-references between binder sections verified in both directions

What gets validated

• No index line points at an empty tab, a placeholder, or a document awaiting retrieval
• The revision and date on each filed document match what the index declares
• Every document in the binder identifies this aircraft by serial number or registration where applicable
• Sections the agreed records standard requires are present and populated, without silent omissions
• Documents added or replaced during the transition appear in the index at the correct line

Evidence normally required

• The delivery or redelivery binder and its current index, physical or digital
• The agreed records standard or delivery-condition annex from the transaction
• The wider source package: status summaries, registry files, and correspondence
• A log of documents added, replaced, or removed during the transition

Common discrepancies

• Index lines pointing at documents that were removed for copying and never returned
• A certificate filed at the right tab but for the wrong engine serial number
• Revision letters in the index that lag the documents actually filed by one or two updates
• Whole sections the records standard calls for that the index quietly omits

What is at stake

Every empty or wrong tab a counterparty finds converts into a formal query, and enough of them convert into distrust of the whole package. Authorities that lose confidence in a binder widen their sampling, and closings have slipped over document sets that existed but could not be produced against their own index in time.

How the work runs

What the buyer receives

• A line-level exception report against the binder index
• A reconciliation of late-transition changes between index and file
• A gap summary mapped to the agreed records standard for the transaction

Who uses the output

• The transition lead who must present the binder to the counterparty and authority
• Records staff repairing the index and retrieving the documents the exceptions name
• Transaction managers deciding what to disclose before the counterparty samples the file

How the work fits into the transaction or program

The binder review usually runs late in package assembly, once the document set has stopped moving. Its exception report joins the authority-response evidence file alongside the package's other source reviews, and a clean binder shortens every downstream inspection because samplers stop early when the index keeps proving right.

Jurisdiction-specific considerations

FAA and EASA transactions tend to organize binders differently, and an aircraft crossing between the systems often needs its index re-mapped to the receiving side's expectations. Records retention rules under 14 CFR 91.417 and the transfer obligations of 91.419 shape what must travel with a US-registered aircraft, while EASA-side transfers lean on the continuing-airworthiness records structure the receiving CAMO expects to see.

Regulatory limits

The review reports on the binder's completeness and internal consistency. It does not certify the aircraft's condition, does not determine airworthiness, and does not decide whether the binder satisfies a specific authority; it equips the team that will make that case.

What this review does not cover

• Building or re-tabbing the binder itself
• Recovering missing documents from prior operators or shops
• Judging the technical adequacy of repairs or inspections the documents describe

Specific to this review

• Binder drift is cumulative: each transaction that touches the file without reopening the index adds a layer of unrecorded change.
• Counterparties sample binders rather than read them fully, so a small number of visible misses can trigger disproportionate scrutiny.
• The most damaging finding is a correct document for the wrong serial number, because it questions the assembly discipline of the entire file.
• An index reconciled against a late-transition change log catches the swaps that memory alone always misses.
• Digital binders inherit the same drift as paper ones; a scanned index page can be as stale as a typed one.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits