Engine value evidence
Engine shop-visit packages behind an owner-managed aircraft file
This review confirms that every engine shop visit claimed in a managed aircraft's file is backed by a complete package: workscope, teardown findings, module build records, LLP disk sheets, test-cell acceptance, and the release that returned the engine to service. Engine paper carries most of the asset's value, so the check runs early in sale preparation or before a management transition. The owner representative receives a per-engine completeness matrix and an exception list mapped to whoever holds the missing content.
When this review is needed
- The engines run on an hourly program and the owner holds only coverage statements and invoices for past visits.
- A buyer's engine specialist has requested full shop-visit packages and nobody is certain who has them.
- A program transfer or buyout is being negotiated and the claimed engine status needs documents behind it.
- A mid-life engine had its last visit at a shop that has since closed, merged, or changed hands.
The problem
Engine shop visits on managed aircraft are settled between the program administrator and the shop. What the owner sees is a coverage statement and an invoice for the uncovered portion. The full package, hundreds of pages of build records, disk sheets, and test-cell results, rarely lands in the owner's file, and years later it is genuinely unclear which of three parties holds it or whether anyone still does.
What gets reviewed
- Inventory of claimed shop visits per engine, drawn from tracking history and logbook entries
- Internal consistency of each package: workscope against findings against build records
- LLP disk sheets reconciled to the current LLP status list and accumulated cycles
- Test-cell acceptance data present and coherent with the release issued
- Release certificates checked against the as-built module configuration and serials
- Documentation for modules swapped, loaned, or built from used serviceable material
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
- Module serial numbers in the last build records match the engine's configuration as tracked today
- LLP cycles recorded at the visit reconcile with cycles accumulated since, arriving at the current status figure
- The release covers the engine as actually built, including work subcontracted to other shops
- Test-cell parameters were recorded and sat within limits when the release was signed
- The invoiced workscope agrees with the workscope the package documents
Evidence normally required
- Engine tracking exports showing visit history and current status
- Shop-visit packages held by the owner, the management provider, and the program administrator
- Current LLP status lists for each engine
- Logbook entries covering engine removals and installations
- Program contract statements defining coverage and record custody
Common discrepancies
- A package that consists of the cover letter and release certificate while the substance stayed at the shop
- One module built with used serviceable parts whose disk sheets never joined the package
- A release referencing test-cell acceptance for which no test-cell data can be produced
- Current module serials that differ from the last documented build with nothing explaining the change
What is at stake
An engine history that cannot be documented collapses toward the worst supportable assumption. LLP status without disk sheets gets discounted, module provenance questions multiply, and a buyer may price the engine near core value or condition the deal on a borescope and records rebuild. Every week spent locating packages is a week added to the transaction.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
List the claimed visits
Compile every shop visit asserted by tracking, logbooks, and status summaries for each engine position.
Gather from all custody points
Request packages from the owner's files, the management provider, the program administrator, and the shops themselves.
Test completeness module by module
Verify workscope, build records, disk sheets, test-cell data, and release against each other and against current configuration.
Report with retrieval routes
Issue the completeness matrix and exceptions, flagging the items that gate engine value in the transaction.
What the buyer receives
- A per-engine package completeness matrix, visit by visit
- An exception list mapped to the holder: shop, program administrator, or management provider
- A note tracing the LLP evidence chain as it stands, for use in the handover baseline
Who uses the output
- The owner representative defending engine value at the negotiating table
- Buyer and lender engine reviewers working from a mapped rather than raw file
- The incoming management provider setting day-one engine status
How the work fits into the transaction or program
Engine packages anchor the highest-value portion of the owner-managed file review. Findings here routinely send the LLP traceability review deeper into specific modules, and the completeness matrix feeds directly into how the handover baseline states engine status.
Jurisdiction-specific considerations
Engines and modules released in the United States carry FAA Form 8130-3s, while EASA-bound transactions expect Form 1 or dual-release coverage on the same events. Retention duties also split differently: FAA rules place summary records with the owner while detail stays with the performing organizations, and EASA continuing-airworthiness rules push more of the burden toward the party managing airworthiness. Custody questions therefore have different answers depending on where the paper was created.
Regulatory limits
This is a records exercise. It does not certify engine condition, extend or approve LLP lives, or make any airworthiness determination. On-wing performance and hardware condition are matters for borescope and test, and the review's conclusions about paper say nothing about metal.
What this review does not cover
- Borescope inspection or any physical engine assessment
- Valuation of program coverage or buyout economics
- Negotiating package release with the program administrator, which the exception list informs but does not execute
Specific to this review
- Custody is the central problem: program contracts often let the administrator hold shop-visit detail, and retrieval rights weaken sharply once the contract terminates.
- A release certificate by itself carries no LLP status; disk sheets and their back-to-birth references do, and experienced buyers price the difference without hesitation.
- Shops consolidate over an engine's life, so a fifteen-year-old visit may now be answerable only by a successor organization with different retention rules.
- Subcontracted module work is where packages thin out most, because the prime shop's release covers work whose detail lives in another company's records.
- An engine exception moves sale price more than an airframe records gap of similar apparent size, which is why this review runs before the airframe checks when time is short.
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
Our program administrator says the engines are fully covered. Why review the packages at all?
A coverage statement is a contractual position, and buyer diligence tests documents rather than contracts. Program terms can also change at sale, and a buyer who does not assume the program will want the underlying evidence regardless. Knowing package status before those conversations start is what keeps the engine from being priced on assumptions.
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.