Engine shop-visit records review

When this review is needed

• An engine transaction or return depends on the shop-visit history establishing condition and remaining life.
• A recent shop visit changed the workscope, modules, or LLPs and the resulting status has not been reconciled.
• A status list claims a build standard or life that the shop-visit packages have not been checked to support.
• An engine is being assigned to a different airframe and its shop-visit and module history has to be confirmed.

The problem

A shop-visit package is the densest record on the aircraft: a workscope, a teardown and findings, module and parts replacements, LLP changes, test-cell results, and a release. The engine status that everyone relies on is the output of those packages stacked over the engine's life. When a package is incomplete, when an LLP replaced at the shop never updated the status, or when the build standard claimed does not match what the workscope actually did, the headline engine status is unsupported in a way that only reading the packages reveals.

What gets reviewed

• Each shop visit by date, with the workscope performed and the findings recorded
• Modules and parts replaced, repaired, or retained at each visit
• Life-limited-part changes at the shop reconciled into the engine LLP status
• Build standard and configuration claimed against what the workscope supports
• Test-cell or post-overhaul performance evidence where the workscope requires it
• Release at exit from the shop covering the work actually performed
• The engine status list reconciled against the stacked shop-visit packages

What gets validated

• Each shop-visit package is complete, with workscope, findings, parts, and release present
• Modules and parts replaced at the shop are reflected in the current engine configuration
• LLPs changed at a visit are carried correctly into the engine LLP status and life figures
• The claimed build standard is consistent with the workscope and findings recorded
• Test-cell or performance evidence is present where the workscope calls for it
• The release at shop exit covers the scope of the work performed
• The engine status reconciles with the shop-visit history rather than standing alone

Evidence normally required

• Shop-visit reports and workscope packages for each visit in the engine's life
• Engine logbook and configuration or build-standard records
• LLP status list and the LLP change records at each shop visit
• Test-cell or post-overhaul performance data where applicable
• Release certificates at exit from each shop visit

Common discrepancies

• A shop-visit package missing the workscope, findings, or release for the work claimed
• An LLP replaced at a shop visit that never updated the engine LLP status or life figures
• A build standard claimed that the recorded workscope and findings do not support
• Module or parts replacements that are not reflected in the current configuration
• A release that does not cover the full scope of the work performed at the visit
• An engine status list that disagrees with the stacked shop-visit packages

What is at stake

Engine status is the largest single value line on most aircraft. A shop visit that overstated the build standard, an LLP change that never reached the status list, or a release that does not cover the work done can move engine value materially and force a return or removal that was supposed to be years away. The gap is far cheaper to find before the engine is priced into a deal.

How the work runs

What the buyer receives

• A shop-visit-by-shop-visit reconciliation with workscope, parts, and release trace
• A reconciled engine status showing build standard, configuration, and LLP life
• A list of incomplete packages, unposted LLP changes, and workscope or release discrepancies
• A closure path for each gap with the shop record needed identified

Who uses the output

• Acquisition and asset teams pricing engine condition and remaining life into a deal
• Continuing-airworthiness teams confirming engine configuration and status
• Records teams assembling the engine package for a transaction or return

How the work fits into the transaction or program

The review establishes the engine condition and configuration that the LLP history and traceability reviews rest on, and feeds the engine status into the wider transaction file or return binder.

Aircraft-specific considerations

Engine families differ in module architecture, LLP populations, and how workscope and build standard are defined, so the decisive evidence in a shop-visit package changes by engine type. The review is scoped to the specific engine rather than applied identically across a fleet.

Regulatory limits

The review confirms that the shop-visit records and the resulting engine status are complete, consistent, and supported. It does not test, inspect, or overhaul the engine, certify a build standard, make an airworthiness determination, or guarantee an authority's acceptance.

What this review does not cover

• Physical inspection, borescope, or test-cell running of the engine
• Overhaul, repair, or certification of any module or part
• Any airworthiness determination on engine status

Specific to this review

• Engine status is the output of every shop-visit package stacked over the engine's life, so a single incomplete or misposted package propagates into the headline build standard and life figures.
• LLPs are commonly replaced during a shop visit, and the engine LLP status is only correct if every such change was posted from the package into the status list.
• The build standard claimed for an engine is a conclusion that must follow from the recorded workscope and findings, not an entry that can stand on its own.
• Because engine value is usually the largest single line on the aircraft, an unsupported shop-visit record moves value more than almost any other records gap.

Sources

Frequently asked questions

Relevant glossary terms

Related pages

Where this fits