Lessor package acceptance
Repair-approval records review for lessors at work-package handback
A lessor whose aircraft picks up repairs during a maintenance visit needs the repair paperwork verified before the work package is accepted, because that paperwork defines the airframe at every future transition. This review checks the repair and alteration records in the handback: damage reports, the disposition and approved data behind each repair, return-to-service entries, and the repair map update the visit should have produced. It runs for the lessor's technical team during the acceptance window. The result is a verified repair record for the asset file, plus a deficiency list served on the operator or MRO while the visit's obligations are still live.
When this review is needed
- A visit on a leased aircraft generated structural findings and the lessor learns the details only through the handback package.
- The lease obliges the operator to keep the repair map current and this visit is the test of whether that happened.
- Repairs were approved through the operator's engineering channels and the lessor holds none of the substantiation.
- A redelivery or remarketing event is within sight and the airframe's repair story must be defensible before then.
The problem
Between transitions, a lessor's knowledge of its airframe is secondhand. Repairs happen at visits the operator manages, dispositions flow through the operator's engineering or the MRO's, and the lessor's asset file advances only if the handback package is complete and someone on the lessor's side verifies it. Packages reviewed lightly in year three of a lease produce the repair-map surprises that dominate year seven's redelivery.
What gets reviewed
- Damage reports and findings raised during the visit, each traced to a documented outcome
- Approval basis for each repair, whether SRM chapter, OEM disposition, DER approval, or other approved data
- Return-to-service entries for the repair work, with the certifying references
- The repair map or dent-and-buckle chart as updated for the visit
- Alterations embodied at the visit and their approvals
- Lease-clause obligations on repair documentation, checked against what was delivered
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 finding the package raises has a disposition, and every disposition has the data it cites attached or retrievable
- Approved data matches the damage described, in location, dimensions, and structure affected
- Repairs meeting major criteria carry the classification and associated filings
- The repair map update includes each new repair with an identifier that links back to the substantiation
- Delivered documentation meets the standard the lease's records clauses set
Evidence normally required
- The handback package with non-routine cards, damage reports, and dispositions
- Approved data packages referenced by the visit's repairs
- The current repair map or structural repair listing held in the asset file
- The lease's maintenance and records provisions
- Prior visit packages, where continuity of a known repair is in question
Common discrepancies
- A disposition referencing engineering approval that was never furnished with the package
- New repairs absent from the delivered repair-map update
- Approved data covering a different damage size than the report records
- Return-to-service entries that bundle repair work invisibly into the general visit release
What is at stake
Every undocumented or under-substantiated repair discovered at redelivery is negotiated at the worst possible moment, with the aircraft's next placement waiting on the answer. Approved data that was never collected during the lease can be genuinely unrecoverable if the approving engineer or organization has moved on, leaving the lessor to remarket an airframe with a repair it cannot substantiate.
How the work runs
Read the visit's repair story
Extract findings, dispositions, and repair work from the package into a single visit repair account.
Verify substantiation
Match each repair to its approved data, classification, and return-to-service entry.
Reconcile the map
Update the asset file's repair map and flag entries the package should have delivered and did not.
Serve the deficiencies
Issue the clause-referenced deficiency notice and track each owed document to receipt.
What the buyer receives
- A verified repair record for the asset file, repair by repair
- A deficiency notice for the operator or MRO citing the lease clause and the document owed
- An updated repair-map position the lessor's technical team maintains forward
Who uses the output
- The lessor's technical manager maintaining the asset file between transitions
- Transition and remarketing teams preparing the aircraft's next placement
- Legal and commercial staff enforcing the lease's records obligations
How the work fits into the transaction or program
This review is the lessor's checkpoint in a workflow the operator otherwise controls. It converts each handback into an asset-file update and an enforcement moment, so repair documentation accumulates verified during the lease instead of being reconstructed under redelivery pressure.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
Repair approval frameworks differ across the registries a leased aircraft may pass through. Data approved under the current operator's FAA framework may face re-examination if redelivery sends the aircraft to an EASA operator, and the reverse holds too. The review notes which repairs rest on approvals that travel well and which are anchored to the current registry, since that distinction shapes remarketing options.
Regulatory limits
The review assesses documents against the lease and the recordkeeping rules. It does not approve repair data, classify repairs for any authority, direct the operator's maintenance decisions, or determine airworthiness. Regulatory responsibility stays with the operator and its authority for the duration of the lease.
What this review does not cover
- Physical survey of the repairs or the surrounding structure
- Engineering review or re-approval of the repair designs
- Redelivery negotiation itself, beyond supplying the verified record
Specific to this review
- The gap between repairs performed and repairs mapped grows silently during a lease; each unverified handback adds to it, and redelivery reveals the total.
- Operators archive visit substantiation on their own retention schedules, which rarely align with a lease term; collecting data at handback beats requesting it years later when retention periods have run.
- A deficiency notice citing a specific lease clause and a specific missing document gets actioned; a general complaint about package quality does not.
- Repairs bundled into a general visit release without their own entries are the hardest to prove later, because the evidence was never separated from the visit's bulk paperwork.
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). Records an owner or operator must keep, including total time in service, current status of life-limited parts, and AD compliance.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
The operator holds regulatory responsibility during the lease. Why does the lessor need this?
Regulatory responsibility and asset value run on separate tracks. The operator satisfies its authority; the lessor answers to the next lessee's reviewers and the market. Documentation adequate for the first purpose falls short of the second often enough that lessors who verify at each handback redeliver faster than those who wait.
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.