Engine handback
Engine shop-visit package review for the redelivery binder
An engine shop-visit package is the densest document set in any redelivery binder, and this review reads it end to end against the rest of the source records. The reviewer reconciles incoming and outgoing configuration, module serial numbers, LLP disk sheets, test-cell acceptance results, and the final release against what the status lists and logbooks say the engine is today. It is performed as the binder comes together, giving asset managers and operator powerplant teams time to chase the shop before acceptance. The findings arrive as a per-engine, per-module discrepancy schedule.
When this review is needed
- An engine went through one or more shop visits during the lease and the packages have never been reconciled with the current LLP status list.
- Modules were exchanged, borrowed, or upgraded at a visit and the binder must show an unbroken identity trail for what is hanging on the wing now.
- The redelivery conditions specify performance-restoration workscopes and the lessor needs proof the visits actually delivered them.
- Engine values dominate the return economics and the counterparty has announced a full powerplant records audit.
The problem
A shop visit produces hundreds of pages assembled by the engine shop for its own release purposes, then filed by the operator and rarely reopened. Between the visit and redelivery, the engine's status keeps evolving in the tracking system while the package stays frozen. When acceptance begins, the two have drifted: a module serial in the build record disagrees with the status list, disk-sheet cycle counts do not line up with fleet utilization, or the workscope summary promises a restoration the test-cell data does not evidence. Reconciling all of that live, with the counterparty watching, is the worst possible setting.
What gets reviewed
- Reconciliation of inbound and outbound configuration tables in each shop-visit report against the engine's current build
- Module-by-module serial verification across build records, release certificates, and the operator's status list
- LLP disk-sheet review, comparing part cycles at the visit with accumulation since and with the redelivery status list
- Test-cell acceptance data checked against the declared workscope objectives
- Verification that the visit's release certificate covers the configuration actually shipped, including late substitutions
- Trace of any borrowed, exchanged, or customer-supplied modules and parts introduced at the visit
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 module serial installed at the last shop visit either remains on the engine or has a documented removal and replacement afterward
- Disk-sheet cycles plus post-visit utilization equal the LLP cycles claimed on the redelivery status list
- The test-cell report exists, is complete, and records an acceptance run for the build being released
- The shop's release document matches the outbound configuration table, with no unexplained serial substitutions
- Workscope performed, as evidenced in the package, matches the workscope the redelivery conditions or reserves agreement assume
Evidence normally required
- Complete shop-visit packages for each engine event during the lease, including build records and disk sheets
- Current engine and LLP status lists with cycle and time accumulation since each visit
- Engine logbooks and on-wing maintenance records covering the post-visit period
- Release certificates issued at each visit and for any module or LLP introduced separately
- The redelivery conditions and any maintenance-reserve provisions tied to shop-visit workscopes
Common discrepancies
- A module exchanged during the visit whose incoming identity is documented but whose cycle history begins at the exchange, with nothing behind it
- Disk sheets showing cycles that cannot be reproduced from the status list and post-visit utilization
- Test-cell data absent from a package whose cover summary claims a performance-restoration run
- Release paperwork describing a build configuration that a later borrow or substitution quietly changed
What is at stake
Engines carry most of the asset's value, so shop-visit discrepancies escalate faster than any other record dispute. A cycle count that cannot be reconciled at a module build casts doubt on every LLP in that module, and doubt about LLPs is priced in millions, through replacement demands, compensation, or an acceptance delay while a shop reopens its archive. Weak test-cell evidence similarly undermines any maintenance-reserve claim tied to workscope achievement.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Inventory the visit history
List every shop event per engine during the lease and confirm a package exists for each.
Rebuild the configuration timeline
Follow module and LLP identities from the earliest package through post-visit changes to the current build.
Reconcile cycles and workscope
Tie disk sheets to the status list and test the evidence behind each declared workscope.
Publish the discrepancy schedule
Hand over module-level findings with a targeted retrieval request for the shop archives.
What the buyer receives
- A per-engine discrepancy schedule organized by module and record class
- A reconciliation table tying disk-sheet cycles to the current status list for every LLP
- A shop-retrieval request list specifying the exact package sections needed to close each gap
Who uses the output
- Powerplant engineers on both sides of the return preparing for the engine records audit
- Asset managers quantifying exposure on reserve claims and LLP disputes
- Records staff who must fold the corrections back into the status lists and the binder
How the work fits into the transaction or program
This review anchors the powerplant side of the binder work. Its cycle reconciliations underpin the separate LLP back-to-birth effort, its configuration findings flow into the equipment-list review, and its workscope evidence feeds whatever reserves settlement the commercial teams are negotiating in parallel.
Jurisdiction-specific considerations
Shop visits performed at FAA-certificated repair stations release engines on 8130-3 forms under 14 CFR Part 43, while EASA-side shops release under Regulation (EU) 1321/2014 on Form 1, and many packages mix both across sub-tier vendors. The review notes where a receiving authority's operator will expect dual release or additional import documentation for modules sourced across regimes.
Regulatory limits
Nothing in this review constitutes an engineering assessment of the engine. It does not judge hardware condition, validate test-cell performance margins, approve the build, or issue any airworthiness determination; it establishes whether the documentation is internally consistent and complete.
What this review does not cover
- Borescope inspection or any physical assessment of the engine
- Performance analysis or EGT-margin interpretation beyond checking the data is present
- Commercial negotiation of maintenance-reserve or compensation amounts
Specific to this review
- Cycle-trace breaks concentrate at module builds, because a build is the one moment a shop can marry hardware histories from different owners into a single engine.
- Quick-turn and hospital visits produce the thinnest packages, and an engine with two quick-turns since its last full visit often has more documentation risk than one fresh from overhaul.
- Customer-supplied and borrowed parts introduced at a visit arrive with their own release documents, which frequently stay in the lender's file rather than the shop package.
- A test-cell report proves the engine that ran, not the engine that shipped; any post-test substitution has to be separately papered, and reviewers check the dates for exactly that.
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 engine shop no longer exists. Can gaps still be closed?
Sometimes. Successor organizations, the operator's own receiving records, release certificates held by module lenders, and the engine manufacturer's records can each replace parts of a lost package. The review's value in that situation is precision: knowing exactly which pages are missing determines whether alternate sources can cover them or whether the parties are negotiating around a permanent gap.
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.