Lease return & redelivery
Lease-return aircraft records audit
A lease-return records audit checks an aircraft's maintenance and compliance records against the redelivery conditions in the lease before the asset changes hands. It is run by or for the lessor near end of lease. It covers AD status, life-limited part traceability, shop-visit and release evidence, and the status lists the return is built on. You receive a discrepancy register, a return-condition gap list, and the evidence needed to close each item.
When this review is needed
- An aircraft is approaching end of lease and the return conditions reference a defined records standard.
- A redelivery has been offered and the technical acceptance team needs an independent read before signing.
- A return was accepted under time pressure and the lessor wants to confirm what was actually delivered.
- A transition between operators or registries is planned and the records must support the next lease.
The problem
Return conditions are written against the records, but the records are large, fragmented, and assembled by the outgoing operator. Status lists are generated from a maintenance-tracking system whose underlying source documents are rarely checked at return. Discrepancies that surface after acceptance become the lessor's cost, and they reduce what the asset can be re-leased or sold against.
What gets reviewed
- Lease return conditions and the records standard they reference
- Airworthiness Directive compliance status against source accomplishment evidence
- Service Bulletin and modification status and effectivity
- Life-limited part status with back-to-life traceability where required
- Engine, APU, and landing-gear records and shop-visit packages
- Authorized release certificates for installed and replaced components
- Status lists reconciled against the underlying source documents
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 open and closed AD is supported by accomplishment evidence with the method of compliance shown
- Life-limited part status traces to release documentation and consistent time and cycle history
- Component releases use a valid FAA Form 8130-3 or EASA Form 1 appropriate to the installation
- Shop-visit reports reconcile with the recorded part numbers, serial numbers, and removal history
- Maintenance-tracking status matches the source records rather than standing alone
- Time-since-new and cycles-since-new are internally consistent across logbooks and status lists
Evidence normally required
- Current AD and SB status reports
- Life-limited part status list and supporting release certificates
- Engine and APU shop-visit reports and trend data where applicable
- Airframe, engine, and APU logbooks or their digital equivalents
- Last airworthiness review or export airworthiness documentation if available
- The lease return conditions and any agreed records standard
Common discrepancies
- Unsupported AD closure where the accomplishment evidence is missing or does not match the method
- Life-limited part trace that breaks at a prior operator or shop visit
- Release certificates absent for components installed during the lease
- Status lists that disagree with the source documents they summarize
- Repairs recorded without the approval or substantiation data behind them
- Logbook gaps across an operator or maintenance-program change
What is at stake
An accepted return with broken life-limit traceability or unsupported AD closure transfers cost and risk to the lessor. The asset may need rework before it can move to the next lessee, and the gap is harder to recover once the previous operator has been released.
How the work runs
Scope against the lease
Read the return conditions and the records standard they reference, and define the record sets in scope for the specific aircraft.
Reconcile status to source
Compare AD, SB, LLP, and component status lists against the underlying accomplishment and release evidence.
Register discrepancies
Structure each finding with its source document, evidence trace, and the lease clause it touches.
Map closure
Recommend a closure path and responsible party for each item so the return can be accepted or driven to resolution.
What the buyer receives
- A discrepancy register with each finding, its source, and its evidence trace
- A return-condition gap list mapped to the specific lease clauses
- A recommended closure path for each discrepancy with the responsible party identified
- A reconciled status view that ties tracking output back to source records
Who uses the output
- Asset managers deciding whether to accept the return
- Technical-records teams closing gaps before re-lease
- Transaction and legal stakeholders pricing residual risk
How the work fits into the transaction or program
The audit runs ahead of technical acceptance so findings can be priced into the return or driven to closure by the outgoing operator while there is still leverage. It feeds the redelivery binder and the records baseline for the next lease.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Aircraft-specific considerations
Records architecture differs by aircraft family. Engine LLP structure, landing-gear overhaul cycles, and modification history change which evidence is decisive, so the audit is scoped to the specific type rather than applied identically across a portfolio.
Jurisdiction-specific considerations
A return that crosses authorities is not complete on release paperwork alone. Configuration, approval basis, and acceptance of the prior maintenance program have to line up with the receiving authority, and a component released on one authority's form is not automatically acceptable under another.
Regulatory limits
A records audit confirms completeness, consistency, and traceability. It does not issue an airworthiness determination, replace the operator or the authority, and does not by itself make the aircraft airworthy or guarantee that the return will be accepted.
What this review does not cover
- Physical inspection of the aircraft or borescope of the engines
- Negotiation of the lease return conditions themselves
- Issuance of any regulatory approval or airworthiness determination
Specific to this review
- Return conditions are written against records, but status lists at return are usually generated from tracking systems whose source documents are not re-verified.
- Back-to-life life-limited part traceability is a contractual and traceability expectation rather than a single uniformly named regulatory requirement.
- An accepted return moves cost to the lessor, so the leverage to close findings is highest before technical acceptance.
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.
U.S. Government (eCFR). The legal basis for issuing and enforcing Airworthiness Directives on U.S.-registered products.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union / EASA. Continuing airworthiness, maintenance records, CAMO responsibilities, and the airworthiness review process in the EASA system.
Frequently asked questions
How is a lease-return records audit different from accepting the return?
Technical acceptance is the lessee's or lessor's sign-off. The audit is the independent check that the records actually support the return conditions before that sign-off, so findings can still be closed by the outgoing operator.
Do you need the physical aircraft?
No. The audit works from the records and status evidence. It is complementary to a physical survey and is often run before or alongside one.
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.
Walk through your situation with an engineer who has done this work.