Redelivery binder
ATR 72 delivery and redelivery binder records review
This review checks that an ATR 72's delivery or redelivery binder is complete, internally consistent, and backed by the source records each index line points to. A records specialist runs it as a lease handover approaches, for either the returning or the accepting party. It walks the binder index, the acceptance evidence, and the discrepancy register, confirming every referenced record is present and every discrepancy is tracked. You receive a checked binder with an index-to-source reconciliation, a list of missing or unsupported references, and a discrepancy position both parties can work from.
When this review is needed
- A lease redelivery is approaching and the binder has to be complete before the handover meeting.
- The accepting party needs the binder checked against source before signing acceptance.
- A discrepancy register carries open items that have to be resolved or explicitly carried at handover.
- A prior binder was rejected for missing references and it needs a clean reconciliation before refiling.
The problem
The redelivery binder is the document a handover turns on, and it is assembled under deadline from records spread across the whole file. An index line points to a record that is not actually in the binder, acceptance evidence is filed without the discrepancy it resolves, or the discrepancy register lists items whose status no one has confirmed. On an ATR 72 moving between regional operators on a tight redelivery schedule, the binder gets built fast and the gaps between the index and the records behind it are where the handover stalls.
What gets reviewed
- The binder index reconciled line by line to the records it references
- Acceptance evidence checked for completeness and linkage to what it accepts
- The discrepancy register reconciled against the findings and their current status
- Source records confirmed present for each status the binder asserts
- Open items at handover confirmed as tracked and explicitly carried
- Duplicate or superseded records removed so the binder reads one way
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
- Every index line points to a record actually present in the binder
- Acceptance evidence links to the specific item or discrepancy it resolves
- Each discrepancy in the register carries a current, confirmed status
- Open items carried at handover are tracked with an owner and a basis
- No two records in the binder contradict each other on the same status
Evidence normally required
- The delivery or redelivery binder and its index
- Acceptance evidence and handover documentation
- The discrepancy register or open-item list
- The source records the binder references for each status
Common discrepancies
- An index line pointing to a record the binder does not contain
- A discrepancy in the register with no confirmed current status
- Acceptance evidence filed without the discrepancy it was meant to resolve
- A duplicate or superseded record left in the binder contradicting another
What is at stake
A binder with index lines that point nowhere reads to the accepting party as an incomplete asset, and every unresolved reference becomes a hold on acceptance or a carried discrepancy that follows the aircraft. A handover that stalls on binder gaps costs both parties, and a discrepancy accepted without a clear status can reopen after signing when the receiving operator finds it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Walk the index
Reconcile each index line to the record it references and confirm the record is present.
Check acceptance
Confirm acceptance evidence is complete and linked to what it accepts.
Reconcile discrepancies
Confirm each register item's current status and identify what is carried or open.
Report the position
Deliver the reconciliation and a discrepancy position both parties can work from.
What the buyer receives
- A checked binder with an index-to-source reconciliation
- A list of missing, unsupported, or contradictory references
- A discrepancy position both parties can work the handover from
Who uses the output
- Records teams assembling a binder that will survive the handover meeting
- Asset managers on either side confirming the binder before acceptance
- Transaction teams working a discrepancy position toward a clean signing
How the work fits into the transaction or program
The binder review is where the whole records file converges for a handover, drawing on the continuity, modification, deferral, and finding work that precedes it. Its index-to-source reconciliation is what lets the handover proceed on confirmed references, and any open discrepancy feeds the resolution the parties settle before or carry past signing.
Aircraft-specific considerations
ATR 72 redeliveries between regional operators tend to run on compressed schedules, so the binder is often assembled quickly from a file that has itself passed through several hands. That pace makes index-to-source gaps and unconfirmed discrepancy statuses the most common binder failures on this type, and the review concentrates on reconciling the index to the records actually present rather than assuming the assembly is complete.
Jurisdiction-specific considerations
A redelivery that crosses from an FAA to an EASA framework, or the reverse, means the binder has to satisfy the accepting operator's recordkeeping conventions beyond those of the returning operator. The review notes where a record acceptable in the origin system needs supplementary evidence to close the handover in the receiving one.
Regulatory limits
The review checks that the binder is complete, consistent, and traceable to source. It does not accept the aircraft on any party's behalf, resolve the commercial discrepancy position, or make an airworthiness determination on the asset.
What this review does not cover
- Accepting or rejecting the aircraft at handover
- Negotiating the commercial resolution of discrepancies
- Any airworthiness determination on the redelivered aircraft
Specific to this review
- The binder is the one record built specifically for the handover, so its failures are index-to-source gaps rather than maintenance gaps.
- A discrepancy accepted without a confirmed status can reopen after signing when the receiving operator finds it.
- Compressed ATR 72 redelivery schedules make fast binder assembly the source of most reconciliation gaps on this type.
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
What is the difference between this and a full lease-return audit?
A lease-return audit examines the underlying records against the return conditions across the whole file. This review checks the binder that presents them: whether every index line traces to a record actually in the binder and whether each discrepancy carries a confirmed status. The two are complementary, and the binder review is what the handover meeting works from directly.
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.