LEAP shop visits
Engine shop-visit records review for LEAP engine assets
This review checks the shop-visit package for a specific LEAP engine and confirms that each visit closes with a complete, internally consistent record. It is run for a lessor, airline, or manager assessing, moving, or maintaining the engine, typically after one or more shop visits have accumulated. It works through the shop reports, module build records, test-cell data, and release certificates, confirming that the workscope, the parts installed, and the release agree. You receive a supported exception list, a source map per visit, and a closure plan for this engine.
When this review is needed
- A LEAP engine has come out of a shop visit and the package has to be verified before it feeds a transaction.
- Several visits have accumulated and no one has reconciled the workscopes against the release evidence.
- A module was rebuilt and the parts installed have to reconcile with the release certificate and the build record.
- A prospective lessee or buyer needs each shop visit's paperwork confirmed before pricing the asset.
The problem
A LEAP shop visit generates a thick package: the incoming workscope, module strip and build sheets, piece-part dispositions, test-cell runs, and the final release. The parts that went into a module build have to tie back to their own release evidence, and the engine's release has to reflect what the workscope actually accomplished. When a build sheet, a piece-part release, and the final certificate disagree, the visit reads as unsettled even if the work was sound.
What gets reviewed
- Each shop visit's incoming workscope mapped to what the release says was accomplished
- Module strip and build records reconciled to the parts installed
- Piece-part dispositions and their release evidence for parts entering a build
- Test-cell data present and consistent with the release for the visit
- The engine release certificate tied to the visit it closes
- The shop-visit package cross-checked against the logbook entries that reference it
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 workscope and the release for each visit describe the same accomplished work
- Parts installed at a module build carry release evidence traceable to their own source
- Test-cell results on file support the performance the release certifies
- The engine release certificate identifies the visit and the shop that issued it
- Logbook entries referencing the visit agree with the package they point to
Evidence normally required
- The shop-visit package for each visit on the engine serial number
- Module strip, build, and disposition sheets from the visits
- Release certificates for the engine and for parts installed during a build
- Test-cell data associated with each visit
- Airframe or engine logbook entries referencing the shop visits
Common discrepancies
- A part installed at a module build whose release evidence does not accompany the build sheet
- A release certificate whose workscope does not match the incoming scope for the visit
- Test-cell data absent from a package that certifies a performance restoration
- A logbook entry that references a visit the package on file does not fully support
What is at stake
An unreconciled shop visit leaves the engine's post-visit status resting on a release that the underlying records do not fully support. That gap resurfaces at the next induction or sale, where it costs leverage and time, and a piece-part whose trace broke inside a module build can be nearly impossible to reconstruct once the shop's own retention window closes.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the visits
Lay out each shop visit on the engine with its incoming workscope and final release.
Reconcile scope to release
Confirm the release for each visit reflects the work the workscope called for.
Trace the build
Tie parts installed at a module build back to their own release evidence.
Flag the open visits
List visits and builds that do not reconcile and the evidence that would close them.
What the buyer receives
- A supported exception list of visits and builds that do not reconcile
- A source map linking each visit to its workscope, build records, and release
- A closure plan identifying the evidence needed to settle each open visit
Who uses the output
- Asset managers judging how firmly the engine's post-visit status is supported
- Records teams recovering piece-part release evidence from the performing shop
- Fleet planners relying on the release before the engine returns to service
How the work fits into the transaction or program
The shop-visit review anchors the engine's status history that AD, LLP, and configuration records all build on. It runs before that history feeds a lease redelivery, a sale data room, or the next induction, so the release the counterparty accepts is backed by a package that reconciles.
Aircraft-specific considerations
LEAP shop visits are documented largely in the shop's digital systems, so the review confirms that piece-part release evidence was carried into the package rather than left behind in a separate system. On this family the shop-visit release evidence is a primary value driver, and module build records get closer attention than on older engines where fewer parts move at each visit.
Regulatory limits
The review reconciles the shop-visit records and confirms they are internally consistent and supported. It does not certify the shop visit, issue or endorse a release, re-perform test-cell work, or make an airworthiness determination on the engine.
What this review does not cover
- Re-performing or auditing the physical shop work
- Issuing or endorsing any release certificate
- Any airworthiness determination on the engine or its modules
Specific to this review
- The weakest link in a LEAP shop-visit package is usually a piece-part whose release evidence sits in a different system than the build sheet that consumed it.
- A performance-restoration release without the test-cell data behind it is a common finding, because the run data is stored separately and not always attached.
- Once a shop's retention window closes, a broken piece-part trace inside a module build is one of the hardest records gaps to reconstruct.
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 check the parts inside a module build if the engine already has a release?
The engine release rests on the parts that went into it. If a piece-part installed at a build cannot be traced to its own release evidence, the engine's release is only as strong as that missing link, and the gap surfaces at the next sale or induction when a buyer works down into the package.
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.