Airbus A220 family delivery and redelivery binder records review

When this review is needed

• An A220 is approaching redelivery and the binder must be shown to resolve to real records, not just index them.
• An acceptance team needs the binder's discrepancy register confirmed complete before signing.
• A binder assembled under a delivery deadline needs its index entries followed to source.
• A prior handover left the binder with entries that do not lead to a document and they must be closed.

The problem

A delivery binder is judged on its index, but the index is a promise, and the promise is only kept if every entry actually resolves to a source record in the pack. Under a redelivery deadline the index gets built ahead of the documents, so entries point to a status list that was never attached, to a certificate filed under a different reference, or to a record that exists elsewhere but not in the binder. The binder reads as complete because the index is complete, while the documents behind a subset of entries are missing.

What gets reviewed

• Each binder index entry followed to the source record it names
• Acceptance evidence confirmed present and attributable to this airframe
• The discrepancy register checked for completeness against the records reviewed
• Index entries that resolve to a wrong or missing document flagged for correction
• Cross-references between the index and the underlying record set reconciled
• Discrepancies found during the review captured that the register omitted

What gets validated

• Every binder index entry resolves to an actual source record in the pack
• Acceptance evidence is present, dated, and tied to this airframe
• The discrepancy register accounts for every discrepancy surfaced in the records
• Index cross-references match the documents they point to
• No index entry points to a record filed under a different reference or absent entirely

Evidence normally required

• The delivery or redelivery binder and its index
• Acceptance evidence such as certificates and status summaries
• The discrepancy register accompanying the binder
• The source records the index entries point to
• The redelivery conditions or records standard the binder is assembled against

Common discrepancies

• An index entry pointing to a status list that is not actually in the binder
• A certificate filed under a reference that does not match its index entry
• A discrepancy surfaced in the records but absent from the register
• Acceptance evidence present but not attributable to this specific airframe

What is at stake

A binder whose index does not resolve is a binder the receiving side cannot accept on its face, and it turns the acceptance window into a document hunt at the moment there is least time for one. Discrepancies that were found but never registered come back as post-handover disputes, and by then the leverage to have them corrected as a condition of redelivery is gone.

How the work runs

What the buyer receives

• An exception list of index entries that fail to resolve and discrepancies not registered
• A source map reconciling the binder index to the underlying record set
• A closure plan for correcting entries and completing the discrepancy register

Who uses the output

• Asset managers and lessors who need the binder to stand up at redelivery
• Acceptance teams confirming the binder resolves before signing
• Records teams reconciling the index to the source documents

How the work fits into the transaction or program

The binder review is the last check before the pack is handed over, and it converts an index into a set of entries that actually resolve. It gives the acceptance team a binder they can accept on its face and a discrepancy register that is complete, so the handover does not become a document hunt or a source of later dispute.

Aircraft-specific considerations

An A220 redelivery binder is usually assembled from largely digital source records, so an unresolved index entry is more often a broken cross-reference or a document filed under the wrong name than a truly lost paper. Because the type's operating history is short, the binder is smaller than an older aircraft's, which makes it realistic to follow every index entry to source rather than sampling.

Jurisdiction-specific considerations

A binder assembled for a redelivery between FAA and EASA operators must carry acceptance evidence in the forms the receiving authority expects, and an index entry that resolves under one framework may name a document the other side does not recognize. The review notes where the binder's evidence needs re-expressing for the receiving authority.

Regulatory limits

The review confirms the binder resolves to its records. It does not accept or reject the aircraft, issue an airworthiness determination, or replace the acceptance team's judgment at handover.

What this review does not cover

• Signing or accepting the aircraft at redelivery
• Physical inspection of the aircraft against the binder
• Negotiating the redelivery conditions or records standard

Specific to this review

• A complete index is not a complete binder, because the test is whether each entry resolves to a document actually in the pack.
• On an A220 an unresolved entry is usually a broken digital cross-reference rather than lost paper.
• A discrepancy found but never registered turns into a post-handover dispute once the redelivery leverage is gone.
• The short operating history of the type makes it realistic to follow every index entry to source rather than sample.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits