Engine shop visit
Geared turbofan engine shop-visit records review
This review confirms that a geared turbofan's shop-visit package documents the work the engine actually received. It works through the shop report, the module build records, the test-cell data, and the release certificates, checking that the workscope, the parts installed, and the final release all reconcile to one another. It is run for a party whose valuation or transfer depends on a shop visit being fully evidenced. You receive a supported shop-visit exception list, a source map across the package, and a closure plan for the build or release evidence that is missing or inconsistent.
When this review is needed
- A geared turbofan is being valued on the strength of a recent shop visit and its package has to be confirmed complete.
- A module build changed the engine's configuration and the build records have to reconcile to the shop report.
- A buyer requires the test-cell data and final release before pricing the post-visit condition.
- A release certificate closes a shop visit whose module build records are incomplete.
The problem
A shop visit is priced on its workscope and proven by its package. On a geared turbofan, the package spans a shop report, module build records, test-cell data, and a release, assembled by a shop under its own conventions, and the pieces do not always agree: a build record can show a part the shop report does not mention, or a release can close a visit whose test-cell data is missing. The reader valuing the post-visit engine sees the release long before they can confirm the work behind it.
What gets reviewed
- The shop report reconciled to the workscope the visit was contracted for
- Module build records confirmed to match the parts and configuration installed
- Test-cell data checked for the performance run that closes the visit
- Release certificates confirmed to cover the engine and the work performed
- LLP and configuration changes from the visit reconciled to the build records
- Missing or inconsistent build and release evidence identified explicitly
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 shop report reconciles to the module build records for the parts installed
- Module build records match the configuration and LLP status the engine left with
- Test-cell data documents a performance run consistent with the release
- The release certificate covers the engine and the workscope the report describes
- A gap between the build records and the release is flagged with the specific inconsistency
Evidence normally required
- The shop-visit package: shop report, build records, test-cell data, and release
- The contracted workscope for the visit
- Module build sheets and parts lists
- Test-cell performance data
- The engine's pre-visit and post-visit configuration and LLP status
Common discrepancies
- A module build record showing a part the shop report does not account for
- A release closing a visit whose test-cell data is not in the package
- Post-visit LLP status that does not reconcile to the build records
- A shop report describing a workscope the build records only partly cover
What is at stake
A shop visit that cannot be fully evidenced undercuts the value the workscope was supposed to add, and a buyer who cannot reconcile the build to the release will price the uncertainty down. If module build records are incomplete, the configuration and LLP status coming out of the visit are unprovable, which reopens the very questions the shop visit was meant to settle, usually at the next transaction.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Set the workscope
Establish the contracted workscope the visit was meant to accomplish.
Reconcile the build
Confirm the module build records match the shop report and the parts installed.
Confirm the run and release
Check the test-cell data and the release against the work the package describes.
Flag the gaps
Identify missing or inconsistent build and release evidence and plan its recovery.
What the buyer receives
- A supported shop-visit exception list across the package
- A source map linking the report, build records, test data, and release
- A closure plan for the missing or inconsistent build and release evidence
Who uses the output
- Asset managers valuing an engine on its post-shop-visit condition
- Records teams reconciling the build records to the shop report and release
- Continuing-airworthiness staff confirming the post-visit configuration and LLP status
How the work fits into the transaction or program
The shop visit is where a geared turbofan's configuration, LLP status, and release evidence are set for the next period of operation, so its package feeds the AD, LLP, and release reviews that follow. Confirming the package reconciles internally means the post-visit status can be relied on, and the exception list drives the build or test evidence that has to be recovered before a buyer will pay for the workscope.
Aircraft-specific considerations
A geared turbofan sees frequent, module-level shop visits, so its history is a sequence of build events rather than a few heavy overhauls, and each visit's package has to stand on its own for the configuration it produced. The review reconciles the build records to the release for the specific visit under examination, because on this engine family the value hinges on the module build being fully documented, and an unsupported build record undoes the trust the release was meant to carry.
Jurisdiction-specific considerations
A shop visit released under FAA approvals produces different release paperwork than one released under EASA, and an engine that will transfer across the boundary may need the release basis restated for the receiving system. The review confirms the shop-visit release matches the authority governing the current registration and flags where the package will need added evidence to satisfy the receiving side.
Regulatory limits
The review reports whether the shop-visit package is complete and internally consistent. It does not accept the shop's work, re-release the engine, or make an airworthiness determination on the engine or its modules.
What this review does not cover
- Re-performing or accepting the shop's work
- Issuing or re-issuing the engine release
- Any airworthiness determination on the engine
Specific to this review
- On a geared turbofan the shop-visit history is a sequence of module builds, so each package has to stand alone for the configuration it produced rather than lean on a single overhaul record.
- A release can close a visit whose test-cell data never made it into the package, so the release proves the engine ran without proving the run is documented.
- The post-visit LLP status is only as good as the module build records, so a build record that does not reconcile to the report leaves the engine's life position unprovable.
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 holds a valid shop release. Why review the whole package?
The release states the engine was returned to service; it does not on its own prove the build behind it. If the module build records or test-cell data do not reconcile to the report, the post-visit configuration and LLP status are unprovable, which is exactly what a buyer valuing the workscope will test.
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.