Binder verification
Delivery and redelivery binders verified against data-room source files
Delivery and redelivery binders summarize an aircraft's transaction history, and this review tests whether the binder index in a seller's data room is honest. In the diligence window before signing, a buy-side records specialist opens each row of the binder index and confirms the document behind it exists, is current, and is supported elsewhere in the room. Rows that point to missing, superseded, or contradictory files become entries on the diligence exception schedule while the seller can still respond.
When this review is needed
- The asset has been through several leases and each redelivery produced a binder that later transactions copied forward.
- The binder index lists hundreds of rows and nobody on the buy side has time to open them all unaided.
- Documents in the binder disagree with fresher status lists elsewhere in the room.
- A prior redelivery was contested and the buyer needs to know whether its paper trail is intact.
The problem
Binders are assembled once, under redelivery pressure, and then travel with the aircraft as received wisdom. Each new transaction inherits the previous binder, adds a layer, and rarely re-verifies the older material. By the third or fourth trade the index promises documents that were superseded, replaced by placeholders, or lost in a records migration, and the data room reproduces the promise without the substance.
What gets reviewed
- Binder index rows enumerated and each one opened against the underlying upload
- Delivery condition documents from the most recent transaction read for currency
- Redelivery certificates and acceptance statements from prior leases confirmed present
- Cross-checks between binder contents and the room's independent status lists
- Version control across binder layers where multiple transactions overlap
- Q&A answers touching binder completeness reconciled with what is actually uploaded
Scope this review
Tell us the asset, the event, and the evidence in scope, and we will outline a focused first engagement.
Send a representative, redacted record set and we will scope the review.
What gets validated
- Each index row resolves to a real, legible file for this serial number
- Dates inside binder documents are consistent with the transaction the binder claims to record
- Acceptance and redelivery certificates carry the signatures and parties the index attributes to them
- Status summaries inside the binder do not contradict fresher lists elsewhere in the room
- No index row relies on a placeholder page, a duplicate upload, or a file from another aircraft
Evidence normally required
- The delivery binder index and every binder layer the room contains
- Full data-room access so binder rows can be traced beyond the binder folder
- The Q&A log where binder gaps have been raised or answered
- Prior transaction closing documentation available to the buyer, where any exists
Common discrepancies
- Index rows pointing at documents that were removed or renamed during a records migration
- A redelivery certificate present as an unsigned draft, standing in for the executed version
- Binder status summaries frozen at a prior redelivery and contradicted by current lists
- Pages from a sister aircraft bound in during a portfolio redelivery and never caught
What is at stake
Accepting a binder at index value means the buyer discovers the hollow rows at the next redelivery, when a lessee or follow-on buyer opens them. At that point the original counterparties are gone, replacement evidence costs research time at whichever organizations still hold source records, and unsupported rows convert directly into negotiation leverage against the then-seller.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Enumerate the index
Extract every binder row into a working checklist, including rows inherited from earlier layers.
Open and match
Resolve each row to its uploaded file and record legibility, identity, and execution status.
Cross-check status
Compare binder summaries against the room's current status lists and note contradictions.
Report by row
Deliver failing rows as exception entries with the precise seller ask for each.
What the buyer receives
- A row-level verification report on the binder index with the failing rows identified
- Exception schedule entries for every unsupported or contradicted binder item
- A request set naming what the seller must produce or re-execute before closing
Who uses the output
- Transaction managers converting binder gaps into conditions precedent or price points
- Lessor technical teams preparing the binder they will hand the next lessee
- Buy-side records staff who will own the binder after transfer under 14 CFR 91.419
How the work fits into the transaction or program
Binder verification anchors the document-completeness half of a data-room review, while the AD, LLP, and review-file checks handle technical status. Together they populate one exception schedule. Whatever the deal accepts unresolved becomes an opening entry in the buyer's post-closing records baseline, so the binder report is written to survive past the transaction.
Jurisdiction-specific considerations
Record transfer at sale is an explicit obligation on FAA-registered aircraft under 14 CFR 91.419, which makes binder completeness a compliance question as well as a commercial one. Under EASA oversight, Regulation 1321/2014 places the continuing-airworthiness record burden on the operator and CAMO, so an incomplete binder shifts effort onto whichever organization accepts the aircraft next.
Regulatory limits
The review establishes whether the binder is supported by its sources. It makes no airworthiness determination, does not certify the aircraft's delivery condition, and does not settle contractual disputes about what a prior redelivery required. Contract interpretation stays with counsel; condition stays with the responsible authority and operator.
What this review does not cover
- Re-assembly or remediation of the binder itself
- Judgment on whether prior redelivery conditions were contractually satisfied
- Review of records that exist only outside the data room
Specific to this review
- Binder indexes are usually spreadsheets exported to PDF; the export freezes errors that the working spreadsheet would have shown as broken links.
- The oldest binder layers get the least scrutiny at each trade, so defects concentrate in exactly the material hardest to replace.
- Portfolio redeliveries are a known contamination point: two aircraft closing the same week can swap pages permanently.
- A signed redelivery acceptance is the hardest binder document to reconstruct later, because it needs a counterparty that no longer has any duty to sign.
Sources
U.S. Government (eCFR). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
U.S. Government (eCFR). Requirement to transfer maintenance records with an aircraft on sale or transfer of ownership.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The seller says the binder was accepted at the last redelivery. Does that not settle it?
Acceptance settled the last transaction between those parties. It does not bind this buyer, and it does not regenerate documents that have since gone missing or been superseded. The current room has to support the binder on its own terms.
Relevant glossary terms
Related pages
Where this fits
Talk to an engineer who has done this work
We will walk through your current state, the records or evidence involved, and a scoped first engagement.
Talk through the aircraft, records, evidence, deadline, and next useful step.