Engine shop visits
Engine shop-visit package reconciliation within the CAMO source file
This review reconciles the engine shop-visit packages in a continuing-airworthiness file against the configuration each visit released. It is run for CAMO managers and powerplant engineers when engine status must be defensible: before an engine transaction, a workscope decision, or an airworthiness status baseline. Within each package, the inbound findings, module build records, LLP listings, test-cell results, and release paperwork are checked for internal agreement and against the status the CAMO carries today. Packages that do not reconcile are reported visit by visit, with the specific mismatch identified.
When this review is needed
- An engine is being sold, exchanged, or returned and the shop-visit history will be read closely.
- Workscope planning needs to know what the last visit actually built, as opposed to what was quoted.
- The CAMO status shows module times that nobody can tie back to a shop document.
- A mid-life engine arrived with visit packages from three shops in three formats.
The problem
A shop-visit package is assembled by the shop to close its work order, then filed by the operator as history. The two purposes diverge: what reconciles for the shop's invoicing may not reconcile as configuration evidence, and the CAMO's module times, LLP figures, and build standard all descend from how that package was read on arrival. Mistakes made when the paperwork was inducted propagate silently into every status report since.
What gets reviewed
- Each shop-visit package in the file: workscope, findings, build records, test results, and release
- Module serial numbers and times at build against the CAMO's current module status
- The visit's LLP listing against the LLP status sheet the CAMO maintains
- Test-cell acceptance results against the release and any stated limitations
- Parts consumed and installed at the visit against release certificates in the package
- Continuity between consecutive visits: what one visit released is what the next visit received
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 in each package matches the next package's inbound configuration, with interim changes documented
- Module times and cycles at release, plus subsequent operation, arithmetic through to today's status figures
- The LLP listing at build agrees with the disk sheets and release certificates inside the same package
- Test-cell results support the release, and any penalties or limitations were carried into the CAMO status
- The release document covers the workscope actually reported, at the approval level that workscope requires
Evidence normally required
- All engine shop-visit packages held in the CAMO file, however formatted
- Current engine and module status from the CAMO system
- The LLP status sheet and utilization history since the last visit
- On-wing maintenance records between visits, for interim configuration changes
- Engine condition or trend data referenced by workscope decisions, where available
Common discrepancies
- A module swapped on-wing between visits, present in line records but never folded into the shop-derived status
- LLP listings at build that disagree with the disk sheets in the same package
- Test-cell margins or limitations noted by the shop but absent from the CAMO's operating status
- A visit package that closes against a workscope revision the file does not contain
What is at stake
When a visit package and the current status disagree, everything downstream of that visit is in question: module times, LLP remaining life, even which serial numbers sit inside the engine. Resolving it late means arguing configuration with a shop years after the visit, or opening the engine to look, and both options have a way of surfacing during a transaction.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Assemble the visit timeline
Order every shop-visit package chronologically and note the interim on-wing events between them.
Reconcile inside each package
Check build records, LLP listings, disk sheets, test results, and release for internal agreement, visit by visit.
Reconcile across the timeline
Confirm each visit's released configuration matches the next visit's inbound state and carries through to current status.
Report mismatches with routes
Describe each irreconcilable item and state whether shop correspondence, retrieval, or a documented assumption resolves it.
What the buyer receives
- A visit-by-visit reconciliation report with each mismatch located and described
- A corrected configuration and times view where the packages support one
- An exception list for items needing shop correspondence or record retrieval
Who uses the output
- CAMO and powerplant staff defending engine status at reviews and transactions
- Workscope planners building the next visit on verified configuration
- Asset teams presenting shop-visit history to buyers or lessors
How the work fits into the transaction or program
Shop-visit reconciliation is where the CAMO file's engine story is proven or broken: the LLP trace review depends on its build records, the release-document review on its certificates, and the maintenance-program review on the intervals it resets. Running it before an engine transaction turns the visit packages from a stack of PDFs into evidence.
Jurisdiction-specific considerations
Shop visits performed in the United States are documented under 14 CFR Part 43 with releases governed by FAA Order 8130.21, while EASA-environment visits close to an EASA Form 1 under Regulation (EU) 1321/2014; 14 CFR 91.417 keeps the resulting records with the aircraft. Engines routinely cross between the two systems mid-life, so a single file can hold visits closed under different rules, and the review reads each package against the framework it was released under.
Regulatory limits
The review reconciles documents. It does not determine the engine's airworthiness, does not validate the shop's release or test results, and does not approve any configuration or workscope.
What this review does not cover
- Borescope, inspection, or any physical verification of the engine
- Commercial disputes with the shop over workscope or invoicing
- Performance analysis beyond checking that recorded results were carried into status
Specific to this review
- Visit-to-visit continuity is the fastest health test for an engine file: if one visit's inbound configuration matches the prior visit's release, most other things are probably in order.
- On-wing module swaps between visits are the leading cause of irreconcilable status, because line records and shop records are filed in different places by different teams.
- Shops assemble packages to close work orders, so internal contradictions, such as a disk sheet disagreeing with the LLP listing, can pass shop QA and still fail a records review.
- The oldest visit in the file sets the floor for what can be proven; effort spent reconciling forward of a broken early visit is often wasted until that visit is settled.
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
Can you reconcile packages from shops that no longer exist?
The documents can still be reconciled internally and against adjacent visits; what is lost is the option to ask the shop for corrections or missing pages. Where a defunct shop's package fails, the report states whether adjacent-visit evidence can bridge the gap or whether the status must carry a documented assumption.
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.