Shop-visit reconciliation
Engine shop-visit records review against the component-history source file
An engine shop-visit records review reconciles each shop-visit package in a component history against the configuration the engine actually left the shop with. Workscope documents, module build records, LLP movement sheets, findings, and test-cell results are read against installed-part lists, releases, and the serial-number trail. Operators, lessors, and MRO teams run it when the history is being assembled for a transaction, a build, or a dispute. Where the package and the released configuration disagree, the review records the conflict, and the exceptions land with the component records lead for the trace support file.
When this review is needed
- An engine's value case rests on a recent shop visit and the buyer's team will dissect the package.
- Module swaps during the visit moved LLPs between assemblies and the movement paperwork must line up.
- Test-cell margins quoted in marketing material need the underlying acceptance data confirmed.
- The shop-visit package arrived as thousands of unindexed pages and nobody has verified it tells one consistent story.
The problem
A shop-visit package is assembled by the shop to close its work order, and it is organized around the shop's processes rather than the questions a later reviewer asks. Parts move between modules mid-visit, workscopes change after teardown findings, and the documents recording each decision are internally consistent but rarely cross-referenced. Reading the package against the engine's own history is the only way to know whether the released configuration, the LLP sheets, and the build records describe the same engine.
What gets reviewed
- The final workscope reconstructed through its amendments and set against the work the records show
- Module build records checked for part identity, position, and continuity through the visit
- LLP movements between assemblies traced with cycles carried correctly at each transfer
- Findings and dispositions from teardown followed to their resolution in the build
- Acceptance data from the test cell matched to the released configuration and any quoted margins
- The release certificate compared against the as-built records for the engine that left the shop
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 released configuration matches the module build records part for part on serialized items
- Every LLP that changed assemblies during the visit has movement documentation with consistent cycle figures
- Workscope amendments are documented and the completed work reflects the final amended scope
- Teardown findings that required disposition show one, and the disposition is reflected in the build
- Test-cell results correspond to the final build standard rather than an intermediate configuration
Evidence normally required
- The complete shop-visit package: workscope, findings, build records, LLP sheets, test-cell data, and release
- The engine's component history and installed-part lists before and after the visit
- LLP status documentation spanning the visit
- Any correspondence recording workscope changes or commercial decisions during the visit
Common discrepancies
- A disk shown in one module by the build records and a different module by the release paperwork
- Cycle figures that changed by a small unexplained amount as a part crossed between assemblies mid-visit
- Workscope items quoted and invoiced but with no completion evidence in the package
- Test-cell data from a run performed before a final configuration change, presented as acceptance of the delivered build
What is at stake
A reconciliation failure inside a shop-visit package undermines the visit's entire value claim: if the build records and the release disagree about one disk, every remaining-life figure derived from that visit is suspect. Buyers respond by discounting to the worst consistent interpretation, and disputes over shop-visit documentation are among the costliest records arguments in engine trading because the sums attached to each finding are large.
How the work runs
Assemble the visit narrative
Order workscope, amendments, findings, build records, and test data into the visit's actual sequence.
Reconcile the configuration
Compare build records, LLP sheets, and the release part by part on serialized items.
Close the loops
Follow each finding, movement, and amendment to its documented resolution.
Report and query
Deliver the reconciliation report, exceptions, and the question set for the shop.
What the buyer receives
- A visit reconciliation report tying workscope, build, LLP movements, and release into one account
- An exception list for every disagreement between package documents and the component history
- A question set for the shop, phrased to obtain the specific missing or clarifying records
Who uses the output
- Component records leads finalizing the trace support file
- Asset managers and buyers testing the value claims attached to the visit
- Powerplant engineering and quality staff resolving configuration questions before the next build
How the work fits into the transaction or program
Shop-visit reconciliation sits downstream of the LLP trace and release-document reviews and consumes both: the trace establishes what entered the visit, the release file establishes what certified it, and this review establishes whether the package in between holds together. Its exceptions frequently resolve fastest of any trace finding because the shop still holds the records.
Start with a single asset
Confirm release certificates and component traceability are complete.
Jurisdiction-specific considerations
Shop visits performed under FAA repair-station approvals and those under EASA maintenance-organization approvals document differently, and engines that visited shops under both systems carry packages with different structures and release conventions. The review reads each package against the standard its shop worked to, then maps the result onto the questions the current jurisdiction's reviewers will ask.
Regulatory limits
The review reconciles documentation. It does not certify the visit's workmanship, does not re-release the engine, and does not adjudicate commercial disputes with the shop; it produces the factual record those processes rely on.
What this review does not cover
- Borescope, inspection, or any physical verification of the engine
- Re-performance of test-cell analysis or performance engineering
- Commercial negotiation with the shop over warranty or invoice matters
Specific to this review
- Mid-visit LLP movements between modules are where cycle errors enter engine histories most often, because the transfer happens inside one shop's paperwork.
- The release describes the engine at one moment; build records describe a process. Gaps between them are normal, contradictions are findings.
- Shops retain visit records on their own schedules, so the reconciliation window for a visit narrows every year after redelivery.
- Quoted test-cell margins lose meaning when the run predates a configuration change; matching run data to final build standard is a routine catch.
- Amendments to a workscope are commercial documents as well as technical ones, and reviews that ignore the amendment trail misjudge what the visit was supposed to deliver.
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 shop is reputable and the release is signed. What would this review add?
Reputable shops still assemble packages for their own workflow, and honest inconsistencies survive signature. The review adds a reading of the package against the engine's independent history, which is what a buyer's reviewer will do anyway; doing it first means the shop's answers arrive before the negotiation instead of during it.
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.