Lease returns
Recovering missing task cards ahead of a lease return
Lease return conditions commonly demand task-level evidence of heavy maintenance, and a check that closed years ago at package level, with a release certificate but no individual cards, fails that test. This remediation identifies which task cards are absent, traces each affected check to the MRO that performed it, and retrieves the cards from the shop's work-order archive before retention periods run out. Lessor asset and records teams run it in the lead-up to redelivery or remarketing. Each recovered package is verified against the check's workscope, and cards that cannot be recovered are documented with the strongest alternative evidence available.
When this review is needed
- The upcoming redelivery's return conditions call for full task-level records and the file holds only check summaries.
- A records audit found heavy checks evidenced by a single release page where the work package should be.
- The lessee that had the checks performed is exiting the lease, and access to its MRO relationships exits with it.
- A remarketing campaign is starting and the technical team wants the records challenge-proof before bidders arrive.
The problem
During the lease, the lessee dealt with the MRO and the lessor saw summaries. At return, the burden inverts: the lessor must now produce the dirty-fingerprint evidence of checks it never administered, performed by shops it holds no contract with, under work-order numbers it may not know. Meanwhile MRO archives run on retention clocks, and every year of delay quietly converts recoverable packages into destroyed ones.
What gets reviewed
- An inventory of heavy checks and shop visits whose task-level records are absent or partial
- Mapping of each affected check to its performing MRO, work-order number, and completion date
- Formal retrieval requests to shop archives, prioritized by retention-clock urgency
- Verification of recovered packages against the check's workscope, including non-routine cards raised
- Alternative-evidence assembly where the archive has already purged the job
- Integration of recovered packages into the aircraft's records set with an updated index
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
- Recovered packages carry the correct aircraft identity, check designation, and work-order reference
- Routine cards in the package reconcile with the approved workscope for that check
- Non-routine cards raised during the check are present and closed, with dispositions attached
- Certifying signatures and stamps on the cards align with the release certificate already on file
- Package completeness is confirmed against the MRO's own card count or job-file manifest where available
Evidence normally required
- The lease return conditions or transaction records standard defining what task-level evidence is owed
- The aircraft's check history with dates, MROs, and any surviving work-order references
- Release certificates and check summaries currently on file for the affected events
- Lessee cooperation obligations under the lease, which shape the retrieval route
- Prior redelivery or transaction records that may contain partial copies of the packages
Common discrepancies
- The complete package sitting intact in the MRO's archive, unrequested for years, one retention review from destruction
- Cards recovered for the routine workscope while the non-routine set was archived separately and needs a second request
- A package indexed under the lessee's internal check number rather than anything the lessor's records reference
- Checks performed by a shop since acquired, with archives transferred to a successor under new access procedures
What is at stake
A missing work package at redelivery gives the receiving party a standing objection, and standing objections at redelivery cost money: extended ground time, substitute evidence negotiations, or a demand that portions of the check be redone. In a sale, the same absence surfaces as a documentation exception that follows the aircraft through every subsequent bid.
Move from findings to resolution
Sequence the fixes and the documentation that closes each finding.
How the work runs
Inventory the absences
List every check whose task-level evidence falls short of the return condition standard.
Trace the archives
Match each check to its performing shop, work-order number, and current archive holder.
Retrieve on the clock
Issue and track requests in retention-urgency order, using lease cooperation rights while they exist.
Verify and file
Check recovered packages against workscope and signatures, then integrate them into the records index.
What the buyer receives
- Recovered work packages verified and filed into the records set per check
- A retrieval log recording each request, archive response, and chain of custody
- An alternative-evidence file for unrecoverable packages, with a stated position for the redelivery negotiation
Who uses the output
- Asset managers walking into redelivery negotiations without a known documentation exception
- Records teams maintaining a task-level-complete file through remarketing and sale
- The receiving operator or buyer, whose reviewers find the packages instead of the gap
How the work fits into the transaction or program
Task-card recovery belongs in the redelivery run-up, ideally starting when the return date is fixed rather than when the receiving party's review begins, because archive retrieval is measured in weeks and retention destruction is irreversible. Its output flows straight into the redelivery records index and closes what would otherwise be the review's largest finding category.
Jurisdiction-specific considerations
Operator recordkeeping rules under 14 CFR 91.417 and Regulation (EU) No 1321/2014 set minimum retention that is often shorter than what lease return conditions demand, which is precisely why the gap exists: everyone complied with their regulation and the task-level evidence still ended up held by a shop rather than the file. Retrieval therefore leans on the lease's records clauses and the MRO's quality-system retention rather than on regulatory compulsion.
Regulatory limits
Task-card recovery restores evidence of work already performed and released. It does not re-perform or re-certify maintenance, and it cannot conjure a release that was never issued; where a package is truly gone, the outcome is a documented alternative-evidence position, never a reconstruction presented as original.
What this review does not cover
- Re-accomplishment of maintenance tasks whose records cannot be recovered
- Enforcement of lease obligations against the lessee, which stays with counsel
- Negotiation of redelivery financial settlements
Specific to this review
- MRO retention commonly runs two to three years beyond contract requirements, so a check from five years ago is a coin flip that gets worse every quarter.
- A package-level release satisfies the regulation yet fails a return condition written for task-level evidence, and lessors discover the difference only at redelivery.
- Non-routine cards are the first casualty of partial recovery, and the first thing an experienced reviewer asks for, because that is where the check's real findings live.
- The lessee's cooperation clause is worth more than any archive search while the lease is still running, and worth almost nothing after the lessee has redelivered and moved on.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. FAA guidance on making and keeping maintenance records and acceptable recordkeeping practices.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
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.
Frequently asked questions
The check has a valid release certificate. Why are the individual cards needed at all?
The release proves the check was certified; the cards prove what the check contained. Return conditions and buyer reviews are written around the second question, because task-level records reveal the non-routine findings, the dispositions, and the actual scope accomplished. A release without its package answers the regulator's question while leaving the counterparty's question open.
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.