Bombardier CRJ delivery and redelivery binder records review

When this review is needed

• A CRJ redelivery is scheduled and the binder must be checked before the acceptance walk begins.
• A binder was inherited at delivery and its index has never been reconciled against what it actually contains.
• A discrepancy register lists open items and the party wants each one tied to a document before closing.
• Two counterparties disagree on whether the binder as delivered met the lease return conditions.

The problem

A redelivery binder is built under deadline pressure by people racing an aircraft off lease, and the index is written before the last tabs are filled. Sections get promised and never populated, discrepancy entries reference a report that was pulled at the last minute, and acceptance evidence points to a certificate that lives in a different folder. The receiving team opens the binder expecting a settled package and instead finds an index that describes a binder that was never quite finished.

What gets reviewed

• The binder index checked line by line against the actual contents
• Acceptance evidence for each returned or delivered condition
• The discrepancy register and the disposition claimed for each entry
• Cross-references from the binder to source records held outside it
• Missing tabs, empty sections, and index lines with no backing document
• The binder structure against the records standard named in the transfer agreement

What gets validated

• Every index line resolves to a document actually present in the binder or a cited external source
• Each discrepancy-register entry shows a disposition backed by a record, not just a status word
• Acceptance evidence for returned conditions traces to the certificate or report it names
• The binder covers each records category the transfer agreement requires
• Source references point to documents that exist and match the described item

Evidence normally required

• The delivery or redelivery binder and its index
• The discrepancy register and any acceptance certificates
• The transfer agreement's records standard or return conditions
• Source records held outside the binder that its entries reference
• Prior correspondence on binder scope or disputed items

Common discrepancies

• Index lines that name a section the binder never actually contained
• Discrepancy entries closed on a status word with no disposition record attached
• Acceptance evidence pointing to a certificate that was never included
• Duplicate or superseded documents left in the binder without the current version

What is at stake

A binder accepted with dangling references transfers the missing evidence problem to whoever signs. The lessor thinks the item was delivered, the operator cannot find it, and the dispute reopens weeks later with the aircraft already flying revenue. Every unreconciled index line is a future argument about who owed what at handover, and by then the assembly team has dispersed.

How the work runs

What the buyer receives

• A supported exception list flagging every unresolved or dangling binder reference
• A source map showing where each binder element is backed, inside or outside the binder
• A closure plan prioritizing the gaps that would block acceptance

Who uses the output

• Asset managers deciding whether a binder is ready to present at redelivery
• Records teams assembling or receiving the binder who need a clean reconciliation
• Transaction stakeholders resolving whether return conditions were met on paper

How the work fits into the transaction or program

The binder review runs just before the acceptance walk, after the binder is assembled but before anyone signs against it. It turns an index that promises completeness into a checked account of what the binder holds, so the acceptance meeting argues over real gaps rather than discovering paper ones on the spot.

Aircraft-specific considerations

CRJ redelivery binders reflect the family's trading pattern: aircraft that pass through several regional operators arrive with binders assembled from more than one prior transfer, and older tabs carry forward references to records standards that no longer match the current agreement. High-cycle utilization means the discrepancy register tends to be heavy on landing-gear and structural inspection items, and engine records assembled at an earlier redelivery may not have been refreshed for the current cycle position.

Jurisdiction-specific considerations

A CRJ moving between an FAA operator and an EASA operator changes what the binder must carry: EASA acceptance expects EASA Form 1 release evidence and Part-CAMO status, while FAA acceptance leans on FAA Form 8130-3 and the operator's continued-airworthiness records. The review checks the binder against the receiving side's expectations, not just the assembling side's habits.

Regulatory limits

This work reconciles the binder against its supporting records and reports what is present and what is missing. It does not certify that return conditions are met, sign the acceptance, or make any airworthiness or contractual determination. Acceptance stays with the parties and their qualified staff.

What this review does not cover

• Signing or witnessing the acceptance of the aircraft
• Assembling the binder from scratch where records were never produced
• Interpreting the transfer agreement's legal terms

Specific to this review

• A binder index is written early and rarely re-checked, so the most reliable defect signal is an index line with no tab behind it rather than a missing item nobody indexed.
• Discrepancy registers close on status words far more often than on disposition records, so each closed entry is treated as unverified until its record appears.
• Binders assembled at a prior CRJ redelivery often reference a records standard from that deal, not the current one, so the standard itself has to be re-checked before the contents.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits