Lease return preparation
How to prepare records for a lease return
Preparing for a lease return means getting the records to satisfy the redelivery conditions before the aircraft is offered back, while the party holding the asset still has the leverage to fix what is wrong. It is read by operators and lessors working an end-of-lease handover. The work covers the return conditions, the AD and Service Bulletin evidence, the life-limited part releases, the components installed during the lease, and the binder the receiving side will inspect. You arrive at handover with a return binder, a discrepancy register tied clause by clause to the lease, and a closure plan dated to finish before acceptance.
When this review is needed
- A lease is nearing its end and the return conditions name a records standard the aircraft will be measured against.
- An operator wants to close records gaps while the aircraft and its maintenance history are still under its control.
- A return date is set and the team needs a schedule that finishes the records work before the asset is offered back.
- A prior redelivery slipped because the binder was assembled after status lists rather than from source.
The problem
Return conditions are written against records that took years to accumulate and now have to be assembled under a deadline. Status lines look complete, but each clause is satisfied by assembled evidence, and pulling that evidence together is the work that gets left until the binder is due. Once the aircraft is offered back, the leverage to make the outgoing maintenance organization produce a missing release or correct an entry falls away, and what was a quick fix becomes a negotiation.
What gets reviewed
- The return conditions and every clause that turns on a record
- AD and Service Bulletin status reconciled against accomplishment evidence
- Life-limited part status and the release documentation that supports it
- Component release certificates for anything installed during the lease term
- The maintenance program currency and how the records reflect it
- The return binder structure the receiving party expects to inspect
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 return-condition clause maps to a records test with a pass or fail result
- Status lists agree with the source documents before they enter the binder
- Open findings carry a closure owner and a date that lands before redelivery
- Components installed during the lease show release paperwork in the binder
- Life-limited part life remaining reconciles with the supporting releases
- The binder structure follows the order the receiving side will inspect in
Evidence normally required
- The lease return conditions and any agreed records standard
- Current AD, Service Bulletin, and modification status reports
- Life-limited part status and supporting release certificates
- The history of components installed across the lease term
- The maintenance program and its revision history during the lease
Common discrepancies
- A return clause with no matching evidence assembled to satisfy it
- Status lists that disagree with the documents they summarize
- Components installed during the lease with the release paperwork missing
- Closure items scheduled to land after the return date rather than before it
- A binder ordered by record system rather than by the clauses it has to answer
What is at stake
A binder built from status lines rather than source documents fails inspection on the clauses that matter, and the items that surface late are the hardest to close. A finding left open past the return date moves from a maintenance task into a commercial dispute, and its cost shifts to whichever party can least avoid it.
How the work runs
Translate the conditions
Read every return clause and turn each one that touches a record into a pass-or-fail records test.
Reconcile to source
Check the AD, life-limited part, and component status lists against the documents behind them before anything enters the binder.
Build the binder
Assemble the evidence in the order the receiving side inspects, with each clause backed by its supporting documents.
Drive closure
Track open findings against a schedule that finishes before the return date, with an owner on each.
What the buyer receives
- A return binder structured against the redelivery conditions
- A discrepancy register mapped clause by clause to the lease
- A closure plan with owners and dates ahead of handover
Who uses the output
- Records and airworthiness teams assembling the binder
- Fleet managers tracking closure against the return date
- Asset managers confirming the aircraft is ready to offer back
How the work fits into the transaction or program
Preparation runs ahead of the formal acceptance check and ahead of any independent audit the receiving side commissions. The binder and register it produces are the documents the audit and the technical acceptance work from.
Aircraft-specific considerations
Which clauses bite hardest depends on the type. An aircraft with several engine shop visits during the lease carries more life-limited part and release exposure, while a heavily modified airframe puts the weight on configuration and approval evidence, so the binder is built around the clauses that the specific aircraft's history makes hard.
Regulatory limits
Preparation aligns the records with the contractual return conditions. It does not make an airworthiness determination, does not substitute for the receiving party's own acceptance, and a well-built binder confirms records readiness rather than guaranteeing the return will be accepted.
What this review does not cover
- Negotiating the lease return conditions themselves
- Physical inspection or borescope of the aircraft
- Any airworthiness determination or regulatory approval
Specific to this review
- The leverage to fix a records gap is highest before the aircraft is offered back, because the preparing party still controls the documents and the maintenance organization.
- A return condition is satisfied by assembled evidence rather than a status line, so each clause needs its supporting documents pulled together before the binder is sealed.
- Components installed during the lease are a frequent gap, because their release paperwork is filed in the maintenance system and not always carried into the return binder.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
Why start before the return date instead of at handover?
Because the leverage to correct a record sits with whoever controls the aircraft and its maintenance organization. Once the asset is offered back, getting a missing release or a corrected entry becomes a negotiation rather than a task, and the cost of the gap rises.
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.
Adapt the checklist to your asset, event, and jurisdiction.