Engine records at lease return
Engine shop-visit records review for airlines returning aircraft
Engines carry most of an aircraft's value at redelivery, and the shop-visit package is where that value is proven. This review works through each engine's shop reports, module build records, test-cell results, and release certificates so the returning airline can show the work claimed was performed and documented. It takes place before the redelivery date, giving the fleet technical team time to chase missing pages from the shop while the visit is still recent. The result is a package-by-package status with the specific documents each gap needs.
When this review is needed
- A leased aircraft is approaching its return date and the engines went through shop visits during the lease.
- The lessor's redelivery team has requested full shop-visit packages and the airline's copies have known holes.
- An engine was swapped during the lease and the package for the installed engine came from a third party.
- Redelivery conditions tie compensation to demonstrated shop-visit workscope, so the package has to prove what was paid for.
The problem
Shop-visit packages are assembled by the shop, forwarded in stages, and filed by whoever received them. Years later, the airline holds a package with the cover report and release certificate but without the disk sheets, the test-cell acceptance run, or the subcontracted repair records for modules sent out during the visit. The engineers who could reconstruct the visit from memory have often moved on.
What gets reviewed
- Each shop-visit package inventoried against the agreed workscope for that visit
- Module build records checked for serial continuity through disassembly and reassembly
- LLP movements during the visit traced onto the disk sheets and the post-visit status
- Test-cell data confirmed present, complete, and consistent with the released configuration
- Release certificates matched to the engine and module serial numbers actually returned
- Subcontracted work during the visit traced to its own release documentation
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
- The workscope invoiced and the workscope documented describe the same visit
- Module serial numbers are continuous through the build, with every substitution documented
- Each LLP installed at build appears on the disk sheets with part number, serial number, and cycles at installation
- The test-cell report covers the acceptance run for the released build standard, including any re-runs
- The final release certificate covers the engine as configured at release, dated consistently with the test-cell record
Evidence normally required
- Shop-visit packages for each engine visit during the lease
- Pre- and post-visit LLP status sheets
- Engine and module removal, installation, and swap records across the lease
- The lease's redelivery conditions for engine documentation
- Correspondence with the shop, including open document requests
Common discrepancies
- Test-cell data referenced by the shop report but never included in the delivered package
- A module exchanged mid-visit whose incoming history stops at the exchange
- Disk sheets showing cycles-at-installation figures that disagree with the LLP status sheet by a handful of cycles
- Subcontracted component work inside the visit with no release certificate of its own
What is at stake
A shop-visit package that cannot prove its workscope invites the lessor to treat the visit as unproven, which converts directly into compensation claims or escrow holdbacks at redelivery. LLP status also hangs on these packages: a cycle count that cannot be traced through the module build forces conservative assumptions that shorten paper life the airline paid to restore.
How the work runs
Inventory the packages
List every shop visit during the lease and index each package against its expected contents.
Trace the builds
Follow module and LLP serials through each visit, flagging every discontinuity.
Chase while sources hold files
Issue document requests to shops and third parties with the visit references they need to respond.
State the redelivery position
Report what each package proves, what remains open, and what that means for acceptance.
What the buyer receives
- An engine-by-engine package status against the redelivery documentation standard
- A gap list with the responsible source for each missing document, shop or third party
- A reconciled post-visit LLP position where the packages allow it
- A brief for redelivery negotiations on which claims the packages can and cannot support
Who uses the output
- Powerplant and records staff chasing shop documents while shops still hold their files
- Fleet technical management preparing the redelivery position on engines
- Commercial teams defending against compensation claims tied to workscope
How the work fits into the transaction or program
Engine package verification is usually the longest-lead item in an airline's redelivery preparation, because closure depends on shops and third parties outside the airline. Starting it when the return date is set, rather than when the lessor's team arrives, is the difference between document requests and financial settlements. Its output feeds the wider redelivery records package and the final LLP reconciliation.
Start with a single asset
Prove the review on a single tail, then scale across the fleet.
Jurisdiction-specific considerations
Shops release engines under the regime of their own approval, so a lease that ran through FAA-registered operation may still hold EASA Form 1 releases from European shops, and dual-release wording matters when the next operator sits under the other authority. The review reads each release against the bilateral arrangements the next placement will rely on.
Regulatory limits
This is a documentation review against 14 CFR Part 43, 14 CFR 91.417, and EU 1321/2014 records expectations. It does not assess engine condition, does not certify or re-release any work, and does not replace the borescope, trend, or performance assessments that belong to powerplant engineering.
What this review does not cover
- Engine condition monitoring, borescope review, or performance analysis
- Negotiating compensation or escrow terms with the lessor
- Commissioning new shop work to regenerate missing records
Specific to this review
- Shops retain visit records for defined periods; a package gap found two years after the visit is usually recoverable, one found at redelivery may no longer be.
- Module swaps inside a shop visit are where cycle traces break most often, because the incoming module's history was someone else's responsibility.
- Test-cell reports are the single most commonly missing element of delivered packages, and also the one lessors ask for first.
- A release certificate proves the engine left the shop serviceable; only the full package proves the workscope the lease compensation formula depends on.
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.
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
The engines are performing well. Does the paper really matter at redelivery?
Redelivery conditions are evidentiary. An engine can be healthy on wing and still generate claims if its shop-visit package cannot demonstrate the workscope, the LLP status, and the release chain the lease requires.
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.