Redelivery binders
Delivery and redelivery binder reviewed against the maintenance-control export
A binder index review audits the delivery binder at three levels: whether every indexed item is actually in the binder, whether each document is the current issue given later system activity, and whether the required-documents list from the transfer conditions is fully covered. Documents are compared against the maintenance-control data so a status report bound months ago is flagged when the system has moved past it. Records teams run it before the counterparty's inspection begins, while regeneration is still routine. The output is an index-level defect list ordered by how quickly each gap can be closed.
When this review is needed
- Redelivery conditions list required documents and nobody has checked the binder against them line by line.
- The binder was assembled months ago and the aircraft has kept flying since.
- Two revisions of the same document sit in the binder with no note of which governs.
- The counterparty's records team starts its inspection soon, and index gaps are the fastest findings it will make.
The problem
Binders get built early, because assembly takes months, and then the aircraft keeps generating history the binder does not capture. Placeholder pages stand in for documents that never arrived, superseded revisions sit beside their replacements, and the index promises contents that a spot check disproves in minutes. The team that assembled it has usually rotated to the next project by the time anyone reads it critically.
What gets reviewed
- Every index line checked against the physical or digital binder contents
- Document dates compared with subsequent maintenance-control activity to catch superseded status reports
- The transfer or lease agreement's required-documents list mapped to binder items
- Certificates and release documents inspected for legibility and completeness
- Duplicate and superseded revisions identified with the governing copy marked
- Placeholder and pending items surfaced with their actual availability established
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 indexed item opens to the document it claims, at the revision the index states
- Status reports in the binder match what the system would produce for the same effective date
- Every agreement-required document is either present or tracked as an open procurement item
- No two conflicting revisions of a document coexist without a governing note
- Certificates are complete, legible, and attributable to this airframe and its components
Evidence normally required
- The delivery binder and its index at the current state of assembly
- The transfer or lease agreement's records and delivery conditions
- The maintenance-control system export for status comparison
- Any prior delivery binder from the aircraft's last transaction, as precedent
Common discrepancies
- An index entry resolving to a placeholder page inserted during assembly and never replaced
- A bound status report superseded by months of subsequent system activity
- The same certificate filed at two revisions with no indication of which one governs
- An agreement-required item absent from both the binder and the index entirely
What is at stake
Index defects are the cheapest findings a counterparty can score, and early easy findings set the tone: a binder that fails its own index invites line-by-line distrust of everything else delivered. Missing agreement-required items can hold redelivery acceptance open, with the daily cost that implies, over documents the system could have regenerated in an afternoon.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Prove the index
Open every indexed item and confirm the document, revision, and legibility the index promises.
Map the requirements
Lay the agreement's required-documents list over the index and mark the uncovered lines.
Date-check the contents
Compare bound status documents against system activity and schedule the stale ones for regeneration.
Order the closure
Deliver the defect list sequenced by closure speed so the team spends its remaining days on the right gaps.
What the buyer receives
- An index-level defect list ordered by closure speed, from regenerate-today to chase-externally
- A coverage matrix mapping agreement-required documents to binder items
- A stale-document schedule naming each report to regenerate and its target effective date
Who uses the output
- Records teams closing gaps in the days before the counterparty inspection
- Fleet management tracking delivery-condition compliance toward the redelivery date
- The counterparty's inspectors, who receive a binder whose index has already been proven
How the work fits into the transaction or program
The binder is the assembled face of everything the other maintenance-control export reviews examine at source, so this audit is most effective after the status-level checks have run and their corrections exist to be bound. Its stale-document schedule loops back to the system for regeneration, and its coverage matrix goes to the commercial team managing delivery conditions.
Jurisdiction-specific considerations
Record-transfer obligations set the floor: 14 CFR 91.419 requires specified records to move with an FAA-registered aircraft, and Regulation (EU) 1321/2014 places equivalent continuing-airworthiness record duties on EASA operators and their CAMOs. Lease and transfer agreements then build well above that floor, and it is usually the contractual layer, rather than either regulation, that defines what the binder must contain.
Regulatory limits
The audit addresses presence, currency, and support of documents. It offers no opinion on the aircraft's condition or airworthiness, does not interpret disputed contract language, and does not certify that delivery conditions are met; it shows where the binder does and does not support such claims.
What this review does not cover
- Assembling or scanning the binder from scratch
- Legal interpretation of delivery conditions or lease language
- Commercial negotiation with the counterparty over disputed items
Specific to this review
- The freshest documents are the ones most often missing, because binders are assembled early and events keep happening after the tabs are set.
- Index auditing is high-leverage sequencing: checking an index finds absences in hours, while reading contents finds defects over weeks, so the index pass always goes first.
- The binder is a derived artifact; when it disagrees with the maintenance-control data, the system is usually right, and the fix is regeneration rather than argument.
- Counterparty inspectors habitually open the index at random and pull five items; surviving that sampling is worth more than any cover letter.
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
Should we wait until the binder is complete before reviewing it?
No. Reviewing a binder at eighty percent assembly finds the structural problems, uncovered agreement items and stale generation dates, while there is still time to fix them. A review after completion mostly documents problems the team no longer has runway to close, which benefits the counterparty more than the operator.
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.