Shop-visit closeout
Engine shop-visit evidence checklist
This checklist tests the evidence package from an engine shop visit, tying the agreed workscope to the parts replaced, serviceable tags, test-cell results, and the final release. Work it before accepting the engine back so the package and the invoice line up with the work. You finish with a workscope-to-evidence map, a tag and release exceptions list, and the items to resolve with the shop.
When this review is needed
- An engine is coming back from a shop visit and the package has to be accepted.
- The shop report and the invoice need reconciling against the agreed workscope.
- LLP and module changes from the visit have to be reflected in the records.
- A performance restoration or overhaul is closing out and the build standard has to be evidenced.
The problem
A shop-visit package arrives as a thick binder and a long invoice, and it is tempting to accept it on weight. The workscope was agreed up front, but the binder rarely lines those lines up against what was actually reported. A replaced part can arrive without its serviceable tag, a tag can arrive without its matching release, and test-cell data can be quoted without the acceptance criteria it was read against.
What gets reviewed
- Agreed workscope mapped to the work actually reported
- Parts replaced with serviceable tags and release evidence
- Run results from the test cell against the acceptance criteria
- LLP and module status changes resulting from the visit
- The final engine release and the updated status sheet
- The invoice reconciled to the workscope and the parts actually replaced
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
- Each workscope line shows a corresponding entry in the shop report
- Replaced parts carry a serviceable tag and a valid release
- Test-cell results meet the stated acceptance criteria for the build
- Post-visit LLP and module status reconcile with the disk sheets
- Invoice lines map to workscope items and reported parts, with no orphan charges
Evidence normally required
- The agreed shop-visit workscope and any amendments
- The shop report, parts list, and serviceable tags
- Final run and test-cell data sheets
- Updated LLP, module, and engine status sheets
- The shop-visit invoice and its supporting detail
Common discrepancies
- A workscope line with no corresponding evidence in the shop report
- A replaced part fitted without a serviceable tag in the package
- Test-cell data that does not state the acceptance criteria it was read against
- Post-visit LLP status that does not reconcile with the disk sheets
- An invoice line with no matching workscope item or reported part
What is at stake
Accepting an engine on an incomplete package means the gap is now the owner's, and reopening it after the engine ships back is slow and contested. Reconciling the package to the workscope at handback keeps the shop on the hook for the missing tag, the absent release, or the unexplained invoice line.
How the work runs
Map workscope to report
Walk each agreed workscope line and confirm a corresponding entry in the shop report.
Check tags and releases
Confirm each replaced part carries both a serviceable tag and a valid release appropriate to the installation.
Reconcile status and runs
Confirm post-visit LLP and module status against the disk sheets and that test-cell results meet the stated criteria.
Close out with the shop
List tag, release, status, and invoice exceptions as a handback action list to resolve before acceptance.
What the buyer receives
- A workscope-to-evidence map line by line
- A tag and release exceptions list for replaced parts
- A handback action list of items to resolve with the shop
Who uses the output
- Powerplant engineering accepting the engine back
- Technical-records teams updating the engine status after the visit
- Asset management reconciling the visit against its cost expectation
How the work fits into the transaction or program
The checklist closes out a shop visit and updates the engine record. Where the visit changed life-limited parts, the LLP trace review checklist confirms the new trace, and individual release documents route to a focused release-document review.
Aircraft-specific considerations
Workscope evidence is organized by engine module. A package for a high-bypass turbofan is checked module by module, since each module carries its own build records, test-cell expectations, and LLP changes, and a performance-restoration scope is evidenced differently from a full overhaul.
Regulatory limits
The checklist reconciles the package against the workscope. It does not re-perform the maintenance, issue the engine release, or make an airworthiness determination on the build.
What this review does not cover
- Re-performing or witnessing the shop work itself
- Issuing the engine release certificate
- Any airworthiness determination on the engine
Specific to this review
- The check reconciles the package and the workscope; it does not re-perform the maintenance or issue the engine release.
- A serviceable tag without the matching release is a common gap, because the tag and the release certificate travel separately.
- Test-cell data is only meaningful with its acceptance criteria attached, so a run sheet quoted without the criteria it was read against is flagged.
Sources
U.S. Government (eCFR). Maintenance recordkeeping content and approval-for-return-to-service requirements, including 43.9, 43.11, and Appendix B.
Federal Aviation Administration. Completion and use of FAA Form 8130-3, Authorized Release Certificate, for new and used parts.
European Union Aviation Safety Agency. EASA authorised release certificate for components, equivalent in function to FAA Form 8130-3.
Frequently asked questions
Why check the invoice as part of a records review?
An invoice line with no matching workscope item or reported part is often the first sign that the package and the work do not agree. Reconciling it surfaces gaps the binder alone can hide.
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.
Adapt the checklist to your asset, event, and jurisdiction.