Lease return conditions: how to turn the lease into a requirement matrix

What return conditions usually cover

The details differ by lease, aircraft type and lessor, but return conditions schedules commonly address:

• The general condition of the aircraft and its compliance with the approved maintenance programme.
• Maintenance status at return: checks completed and the minimum time or cycles remaining on the airframe, engines, APU, landing gear and life-limited parts.
• Airworthiness directives and service bulletins, including those that must be terminated rather than repeated.
• Records and documentation, often including back-to-birth traceability for life-limited parts.
• Configuration, paint and interior requirements.
• Inspections, the demonstration flight and the acceptance procedure.
• Financial adjustments where a condition is not met, such as compensation payments or the use of maintenance reserves.

Give every obligation the same structure

A useful matrix records the same fields for every obligation, so its status can be read and reported consistently:

• Requirement code: a stable reference such as RD-ENG-001.
• Category: records, maintenance, physical, engines, components, landing gear, modifications, commercial or other.
• Title and description: the obligation in plain operational language.
• Lease clause reference and contractual requirement: the exact source in the lease.
• Owner and owner team: who is accountable for delivering it.
• Priority and due date: when it must be met relative to the return date.
• Status, risk status and lessor status: where the work stands internally and with the lessor.
• Notes: assumptions, agreements and open questions.

Agree the expected evidence early

For each requirement, decide in advance what will prove it: a records extract, a work package, a certificate, a borescope report or a set of photos. Listing the expected evidence early shows what is missing long before the lessor asks for it.

Keep the matrix alive until acceptance

• Review status and risk regularly against the return date.
• Record lessor comments and decisions against the requirement they concern.
• Use the matrix as the basis of status reporting to management and to the lessor.

Common pitfalls

• Copying clauses into the matrix without turning them into checkable obligations.
• Requirements with no owner, or with a team named as owner instead of a person.
• Due dates that ignore the time the lessor needs to review the evidence.
• Evidence expectations agreed verbally and never recorded.
• Status kept in several versions of the same spreadsheet.

Start from the free template

The template below contains example requirements for each category. Its columns match Redelvia's requirement import, so you can work on it in Excel or Google Sheets and import it later. Replace every example with the wording, references and dates of your own lease.