Before redelivery
Making the delivery and redelivery binder ready for transaction review
MRO teams assembling a redelivery binder run this check before the lessor's or buyer's representatives sit down with it. The review reads the binder index against the documents actually filed behind it, tests acceptance evidence and discrepancy registers for completeness, and confirms each index line resolves to a current, supported record. It is scheduled in the final weeks before redelivery, while the check package and shop records are still at hand. The result is a line-item exception report and a closure sequence the records team can finish before commercial sign-off.
When this review is needed
- The redelivery date is fixed and the counterparty's records team arrives within weeks.
- The binder was assembled from several departments' outputs and no one has read it end to end.
- Lease return conditions specify a binder structure the MRO has not delivered to before.
- An earlier redelivery drew heavy findings and this one cannot repeat them.
The problem
Redelivery binders get assembled at the end of a heavy check, when the hangar's attention has moved to the next induction. Index lines are written from work orders before the paperwork behind them is final, and a certificate revised at the last minute leaves the binder citing a version that no longer exists. The counterparty reads the binder cold, and every line that fails to resolve becomes their finding instead of the MRO's correction.
What gets reviewed
- The binder index read line by line against the filed documents
- Acceptance evidence for work performed during the check, including certifications and release references
- Discrepancy and deferred-item registers reconciled to their closure records
- Source-record references pointing outside the binder, tested for retrievability
- Revision status of certificates and reports filed against each index line
- Binder structure against the lease return conditions or delivery standard in force
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 resolves to a document present in the binder or retrievable on request
- Filed documents carry the revision the index cites, with superseded versions removed or marked
- Each discrepancy raised during the check appears in the register with a closure or an agreed deferral
- Certification statements and release references cover all work the binder claims
- The binder satisfies the specific structure and content the return conditions require, item by item
Evidence normally required
- The draft binder and its index in current form
- The check package: work orders, task cards, and certification records
- The discrepancy register with closure documentation
- The lease return conditions or agreed delivery standard
- Points of contact for departments still finalizing documents
Common discrepancies
- Index lines written from planned work that was later descoped, citing documents never produced
- Closure evidence for discrepancies signed but never filed into the binder
- Certificates superseded by revision after the index was frozen
- Return-condition items the binder structure simply does not address
What is at stake
Binder findings at redelivery stall acceptance, and a stalled acceptance holds the aircraft on the ramp while the lessor's and operator's costs accrue against the delay. Repeat findings also follow the MRO commercially: counterparties scope deeper reviews and longer on-site visits for shops whose binders have failed before.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the index cold
Resolve every index line to its filed document exactly as the counterparty will, recording each failure.
Test the registers
Reconcile discrepancy and deferred-item registers to closure evidence and written concurrences.
Sequence the fixes
Order exceptions by document owner and lead time against the redelivery date.
Confirm readiness
Re-check closed items and issue the readiness statement for the redelivery meeting.
What the buyer receives
- A line-item exception report against the binder index
- A closure sequence ordered by document owner and lead time
- A readiness statement the program manager can take into the redelivery meeting
Who uses the output
- Records control staff finishing the binder against the exception report
- MRO program management deciding whether the redelivery date holds
- Quality leadership tracking systemic causes across redeliveries
How the work fits into the transaction or program
The check runs between binder assembly and the counterparty's review, close enough to redelivery that the content is near-final but early enough that document owners are still on site. Exceptions closed in this window never appear in the counterparty's findings, which is the entire point.
Jurisdiction-specific considerations
Return conditions typically demand records satisfying both the 14 CFR 91.417 and 91.419 retention and transfer duties and EU 1321/2014 continued-airworthiness requirements, since the aircraft may change registry at redelivery. The binder is judged against the stricter reading wherever the two differ, because the receiving side chooses which lens to apply.
Regulatory limits
This is a records completeness check against the index and the agreed standard. It does not certify the maintenance performed, release the aircraft, or determine airworthiness, and it does not substitute for the counterparty's own acceptance review.
What this review does not cover
- Performing or certifying maintenance tasks found incomplete
- Negotiating return conditions with the lessor or operator
- Building the binder itself, which remains the records team's work
Specific to this review
- Binder indexes frozen before the last work-order revisions are the single most common source of unresolvable lines at redelivery.
- Counterparty reviewers sample the binder in a predictable order, LLP and AD sections first, then discrepancy closures, so exception effort is sequenced the same way.
- A deferral agreed verbally during the check has no standing at redelivery unless the register carries the counterparty's written concurrence.
- Documents referenced as retrievable on request must actually be retrievable within the review visit, or they count as missing.
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
How close to the redelivery date should this run?
Late enough that the binder content is substantially final, early enough that document owners can still act. In practice that means starting when the index is frozen, typically two to four weeks before the counterparty review, with re-checks as exceptions close.
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.