Engine shop visits
Engine shop-visit records reviewed against the module source file
A shop-visit source review establishes whether the engine shop-visit package holds together as evidence: workscope, findings report, module build records, test-cell data, and release all describing the same engine. It is run by or for the engine records lead when a visit closes out or the file transfers with the asset. Every claim in the package is traced to the document behind it, from disk serials on the build sheets to the acceptance run recorded at the test cell. What comes back is an exception list naming each point where the released configuration and its supporting paperwork part ways.
When this review is needed
- An engine is being sold or novated with the aircraft and the buyer's team will read the shop-visit package first.
- A visit has just closed and the operator wants the package proven before invoices settle and the file is archived.
- Redelivery conditions call for a full shop-visit package and the lessor needs to know what is actually in it.
- A maintenance-adjusted valuation rests on the last visit and the analyst needs the package verified.
The problem
A shop-visit package arrives as several hundred pages assembled by the shop at release, and it usually reads clean until someone matches documents against each other. The workscope promises a module exposure the build sheets never show. A disk serial on the LLP sheet differs by one digit from the build record. Nobody notices until a counterparty does, at which point the whole visit is treated as suspect.
What gets reviewed
- Workscope against the executed work: each planned module exposure matched to a corresponding build record
- Module build sheets read against LLP status pages and disk sheets for part and serial agreement
- Shop findings reconciled with the dispositions that cleared them
- Test-cell acceptance data checked against the released engine configuration and rating
- The release certificate compared with the package it claims to summarize
- Installation history after release matched to the configuration the shop documented
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 the workscope opened has a build sheet, and every build sheet belongs to a module the workscope opened
- Disk and LLP serials agree across build records, the LLP status, and the release paperwork
- Test-cell records carry the correct engine serial, rating, and acceptance limits for the released build
- Findings that drove part replacement are matched to release certificates for the parts installed
- Dates inside the package run in a possible order, from induction through disassembly, build, test, and release
Evidence normally required
- The complete shop-visit package as released, including workscope, findings, build records, and test-cell data
- Current LLP status pages and disk sheets for the engine and its modules
- The release certificate set, FAA Form 8130-3 or EASA Form 1, covering the engine and replaced parts
- Removal and installation history spanning the visit
- Any prior exception lists or review notes attached to the engine file
Common discrepancies
- A module exposure claimed in the visit summary that no build sheet in the package substantiates
- An LLP serial that changed at the visit without a matching release certificate for the incoming part
- Test-cell data referencing a different rating than the one on the release
- Findings reports that list conditions the disposition record never addresses
What is at stake
An unverified package becomes the weak point of the engine file. Valuations that assumed a full overhaul get repriced against a lesser workscope, redelivery arguments reopen a visit that closed years earlier, and the cost of obtaining corrected paperwork from the shop climbs the longer the request waits.
How the work runs
Index the package
Inventory every document in the shop-visit package and map it to the workscope line or module it belongs to.
Cross-read the sources
Compare build sheets, LLP pages, disk sheets, findings, and test-cell data for serial, part, and date agreement.
Isolate exceptions
Record each claim the package makes that its own contents do not support, with the specific documents in conflict.
Report and route
Deliver the exception list and reconciliation table, flagging items best raised with the shop immediately.
What the buyer receives
- An exception list keyed to the shop-visit package, one entry per unsupported claim
- A reconciliation table linking workscope lines, build sheets, and release documents
- A short narrative of the visit as the evidence actually supports it
- Recommended requests to the shop, drafted while its retained records are still reachable
Who uses the output
- Engine records leads deciding whether the package can anchor the trace file
- Asset managers pricing the engine on the strength of its last visit
- Counterparty reviewers who will receive the package during a transfer
How the work fits into the transaction or program
The shop-visit package is normally the anchor document of an engine-module file, so this review runs before the file is used to support anything else. Exceptions found here flow into the engine trace support file, and unresolved items become the questions a buyer or lessor will otherwise ask at the worst possible time.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Under FAA rules the package leans on 14 CFR 43.9 entries and Form 8130-3 releases, while an EASA-managed engine will close through a Part-145 release on EASA Form 1. Engines that cross registries mid-life often carry both formats in one package, and the review checks that dual-release documents actually cover the work performed rather than only the final test.
Regulatory limits
The review reports what the package evidences and where it falls short. It does not certify the engine as airworthy, approve or reject the shop's work, or issue any release; those determinations stay with the certificate holders and the responsible authority.
What this review does not cover
- Borescope, hardware, or any physical inspection of the engine
- Commercial disputes with the shop over workscope or invoicing
- Re-performing the shop's engineering dispositions
Specific to this review
- Shops retain their own copies of visit records for a limited period, so a package review done years after release has fewer recovery options than one done at close-out.
- A single transposed digit in a disk serial can sever LLP trace for an entire module, and it is found by comparison across documents, never by reading one page alone.
- Test-cell sheets are the least-read pages in most packages and one of the more common places for the released rating to go unsupported.
- The visit summary is a narrative written at release; where it disagrees with the build sheets, the build sheets govern.
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 package came from a well-regarded shop. Why review it?
Shop quality lowers the error rate but does not remove assembly mistakes, and the package is compiled under release-date pressure. Most exceptions are clerical, a wrong serial or a missing sheet, and they are cheap to fix at close-out and expensive to fix at redelivery.
How long does a review of one package take?
A single-engine package with a normal workscope typically reviews in days rather than weeks. The variable is response time on documents that must be requested from the shop or a prior operator.
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.