CFM56 shop visits
CFM56 engine shop-visit records review
This review confirms that a CFM56 shop-visit package tells a complete and consistent story from induction workscope to final release. It is run by or for an owner or buyer evaluating or transferring a specific engine serial number. It checks the workscope, module build records, test-cell data, part changes, and the release that returned the engine to service. You receive a shop-visit summary keyed to source documents, an exception list for gaps in the package, and a closure plan for the engine under review.
When this review is needed
- An engine's most recent shop visit sets its value and the package has to be verified before a sale.
- A workscope was agreed but the build records do not show it was carried out as specified.
- Test-cell performance is quoted in the marketing figures and the underlying data has to support it.
- Parts changed at the visit have to reconcile with the release and the LLP status sheet.
The problem
A CFM56 shop visit generates a package running to hundreds of documents, and its value depends on those documents agreeing with each other. A workscope that says one thing while the build records show another, test-cell data that does not match the marketed performance, or a part change that never made it onto the release, all sit buried in the package until a buyer's team reads it line by line and the story stops holding together.
What gets reviewed
- Induction workscope compared against the build records that closed it
- Module build records reconciled to the parts installed and removed
- Test-cell data checked against the performance the engine is marketed on
- Part changes at the visit tied to release documents and the LLP status sheet
- The final release confirmed to cover the complete workscope
- Any deviation or concession during the visit traced to its disposition
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 build records show the agreed workscope was carried out as specified
- Parts installed and removed at the visit reconcile across the build records and release
- Test-cell results support the performance figures quoted for the engine
- The release covers the full workscope with no task left outside it
- LLP changes at the visit agree with the updated status sheet
Evidence normally required
- The complete shop-visit package for the engine serial number
- The induction workscope and any workscope amendments
- Module build records and the parts-changed list
- Test-cell data and the final acceptance run
- The shop release and the updated LLP status sheet
Common discrepancies
- A workscope task with no corresponding entry in the build records
- A part change recorded in the build but absent from the release
- Test-cell data that does not support the marketed performance figures
- A concession taken during the visit with no disposition recorded against it
What is at stake
A shop-visit package that does not reconcile undermines the performance and life figures the engine is being sold on. If the build records contradict the workscope or the release omits a changed part, the buyer discounts the visit or reopens diligence, and the value the shop visit was supposed to add is called into question.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the workscope
Establish what the visit was contracted to do and any amendments made during induction.
Reconcile the build
Confirm the build records and parts-changed list show the workscope was carried out.
Check performance and release
Match test-cell data to marketed figures and confirm the release covers the full workscope.
List the gaps
Flag tasks, parts, or data that do not reconcile and set the document needed to close each.
What the buyer receives
- A shop-visit summary keyed to the source documents in the package
- An exception list for tasks, parts, or data that do not reconcile
- A closure plan naming the document needed to resolve each gap
Who uses the output
- Asset managers pricing the engine against a shop visit the package actually supports
- Records teams assembling the shop-visit evidence a buyer will interrogate
- Fleet planners confirming the visit delivered the workscope that was paid for
How the work fits into the transaction or program
The shop-visit review runs after the engine leaves the shop and before it is marketed or transferred, so gaps are found while the shop can still supply the missing document. Its exception list feeds the recovery of build or release records the sale depends on.
Aircraft-specific considerations
CFM56 shop visits are performed across a wide network of shops over a long service life, so packages differ in structure and completeness from visit to visit. The review is scoped to the specific serial number's visits, since the build records for one engine say nothing about how the same shop documented another.
Jurisdiction-specific considerations
A shop release acceptable to one authority may not carry the dual release an engine needs to transfer between an FAA and an EASA register, so the review notes where the shop-visit release would require a counterpart for the receiving system.
Regulatory limits
The review confirms that the shop-visit records are complete and internally consistent. It does not approve the maintenance performed, re-release the engine, or determine that the engine is airworthy.
What this review does not cover
- Re-performing or re-inspecting any shop-visit task
- Issuing a release for the engine or its modules
- Any airworthiness determination on the engine
Specific to this review
- The value a shop visit adds lives in the package agreeing with itself, so a workscope and build record that contradict each other erode the visit's worth regardless of the physical work done.
- A part changed during the visit but omitted from the release is a common CFM56 gap, because the release and the build sheet are produced by different steps in the shop.
- Test-cell data is the record buyers use to challenge marketed performance, so it is reconciled to the sale figures rather than taken at face value.
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
Why review the shop-visit package if the engine passed test?
Passing test proves performance at the shop, not that the package supports the value and life figures the engine is sold on. This review checks the workscope, build records, and release agree, so a buyer's diligence finds a coherent story rather than contradictions.
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.