Lessor induction
Engine shop-visit records review when a lessor inducts an aircraft
A lessor inducting an aircraft into its portfolio verifies the engine shop-visit records before those records set green-time and remarketing assumptions. The review reconstructs each engine's shop-visit history from shop reports, build records, test-cell acceptance data, and release certificates, then compares the result with the delivered status summary. It happens at induction, ahead of the next placement. Output is a substantiated shop-visit history per engine, an open-items register, and the requests needed to complete each package.
When this review is needed
- An aircraft has come off lease or out of a purchase and its engines' documentation must stand behind the next marketing effort.
- Green-time assumptions in the placement model rest on shop-visit outcomes nobody has reconstructed from source.
- The previous operator's redelivery package arrived complete on paper but unverified in substance.
- A future lessee's technical team will audit the engine records at delivery, and the lessor wants no surprises in that meeting.
The problem
Between transactions, engine documentation is the lessor's asset file, and the file is only as good as the shop-visit packages inside it. Redelivery pressure produces packages that satisfy a checklist without necessarily proving the workscope, the build content, or the release coverage a future lessee's reviewers will test. The lessor's team inherits the file at induction with no operational contact with the engines and limited time before marketing begins.
What gets reviewed
- Shop-visit history per engine reconstructed from primary documents rather than summaries
- Workscope, findings, and build content verified within each visit package
- Test-cell acceptance records and their consistency with the claimed workscope
- Release certificates covering each visit and each part introduced
- LLP movements through module builds reconciled with current status sheets
- Inter-visit utilization checked against the operating history
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 shop visit in the engine's life has a package, and every package describes a visit in the engine's life
- Build records account for module serial numbers consistently from visit to visit
- Claimed workscope levels are supported by the findings and work descriptions in the shop report
- Releases carry the approvals a future operator under FAA or EASA oversight would need to accept
- Status-sheet LLP cycles reconcile with the build records and utilization between visits
Evidence normally required
- The engine documentation delivered at redelivery or closing
- Shop-visit packages, test-cell records, and release certificates per engine
- Current LLP status sheets and disk sheets where available
- Utilization data across the operating history
- The redelivery conditions or purchase terms still enforceable against the counterparty
Common discrepancies
- A module swap during a mid-life visit that the status sheet never picked up
- Visit packages complete except for the test-cell sheets, which stayed with the shop
- Release certificates present for the engine but absent for parts introduced at the build
- Summaries created at redelivery that restate earlier summaries instead of source records
What is at stake
Engine records gaps found by a prospective lessee's reviewers cost twice: the delivery slips while documents are chased, and the lessor negotiates from behind on an asset the lessee now trusts less. Gaps found at induction cost a request letter to a counterparty that, at that point, may still owe redelivery obligations.
How the work runs
Assemble the engine file
Gather everything delivered at redelivery or closing and index it by engine and visit.
Reconstruct each history
Build the visit-by-visit record from shop reports, builds, test-cell data, and releases.
Reconcile with status
Tie the reconstruction to current LLP status sheets and the delivered summaries, logging every divergence.
Drive closure with leverage
Issue requests against surviving obligations and track each open item to resolution or documented acceptance.
What the buyer receives
- A substantiated shop-visit history file per engine
- An open-items register with the responsible counterparty for each item
- Request letters framed against surviving redelivery or purchase obligations
Who uses the output
- Asset managers setting green-time and placement assumptions on verified ground
- Technical-records leadership maintaining the portfolio asset file
- Delivery teams preparing for the next lessee's records audit
How the work fits into the transaction or program
Induction is the lessor's one quiet interval between counterparties, and the engine file work done here is what the next delivery runs on. The substantiated history feeds the marketing package, the open-items register drives closure while leverage remains, and the whole file transfers cleanly when the aircraft moves to its next operator.
Start with a single asset
Start with a single tail and expand once the workflow is proven.
Jurisdiction-specific considerations
A lessor rarely knows which registry the next lessee will fly under, so the review reads release coverage with both FAA and EASA acceptance in mind. Visits released for one authority only are flagged as placement constraints rather than defects, since their significance depends on where the aircraft goes next.
Regulatory limits
This is documentary verification of the engine records. It does not assess the physical condition of any engine, issue or endorse release certificates, determine airworthiness, or substitute for the borescope and performance reviews a placement may separately require.
What this review does not cover
- Engine condition monitoring or physical inspection
- Maintenance-reserve or green-time financial modeling
- Negotiation of outstanding redelivery claims
Specific to this review
- Redelivery packages are assembled to close a lease, which is a different objective from surviving the next lessee's audit, and the difference shows up in exactly the documents this review targets.
- A lessor's leverage over missing engine documents decays on a schedule set by the old lease's survival clauses, so the open-items register is effectively time-stamped.
- Module-level history is where summaries and source records diverge most, because a swapped module carries its own past that a top-level engine summary flattens.
- An engine file verified once at induction shortens every subsequent delivery, because later reviews only need to cover the period since.
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 redelivery review already accepted these records. Why review them again?
Redelivery acceptance answers whether the lease conditions were met, under time pressure and against a checklist. Induction asks a different question: whether the file will satisfy the next lessee's reviewers, who owe this lessor nothing and will read the packages from scratch.
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.