Engine shop visits
Gulfstream G650 engine shop-visit records review
This review reconstructs each engine shop visit on a Gulfstream G650 from the induction workscope through the module builds to the test-cell release. It is run by or for the party evaluating or transferring a specific G650, or ahead of an engine coming off the wing, when the shop package has to stand up on its own. A records specialist checks that the module build records, the disk changes, the test-cell data, and the release certificate all describe the same event and the same parts. You receive an exception list where the package does not reconcile, a source map across the shop reports, and a closure plan for the missing build or release evidence.
When this review is needed
- An engine is due to come off the wing and the last shop package has to be settled before the shop opens it.
- A G650 is under offer and the buyer wants each shop visit shown to reconcile end to end.
- A disk was changed at a shop visit and the build record has to tie to the LLP status and release.
- The test-cell data or the release certificate for a prior visit is missing from the engine file.
The problem
An engine shop visit generates a thick package, and the value of that package depends on every piece describing the same event: the workscope, the module builds, the parts installed, the test-cell run, and the release. On a G650 those documents may come from a shop that has since reorganized, and a build record that lists a disk the LLP status does not show, or a release with no test-cell run behind it, breaks the chain the next event depends on.
What gets reviewed
- Each shop visit reconstructed from induction workscope to test-cell release
- Module build records checked against the parts installed and the disks changed
- Test-cell data matched to the release certificate and the recorded workscope
- Disk changes tied to the LLP status sheet and the release paperwork for each part
- Release certificate confirmed to describe the engine and the work the package records
- Shop visits with missing build, test, or release evidence logged with the source that should hold 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, module builds, and release certificate all describe the same shop event
- Every disk changed at the visit appears on both the build record and the LLP status sheet
- Test-cell data is present and consistent with the release for the engine
- Parts installed at the visit carry release paperwork matching the build record
- The engine time and cycle status after the visit reconciles with the shop report
Evidence normally required
- The engine shop-visit packages for each recorded visit
- Module build records and the parts lists for each build
- Test-cell data and the engine release certificates
- The LLP status sheet covering disks changed at the visits
- Engine logbooks showing installation, removal, and post-visit status
Common discrepancies
- A module build record listing a disk the LLP status sheet does not reflect
- A release certificate with no test-cell run behind it in the package
- A shop visit whose post-visit engine status does not reconcile with the logbook
- A part installed at the visit whose release paperwork is missing from the file
What is at stake
A shop package that does not reconcile forces a conservative view of the engine's condition and remaining life, which discounts the asset or triggers an early look inside. If a disk build cannot be tied to the LLP status, the whole engine's life position is in doubt, and reconstructing a shop package after the shop has changed hands is slow and often incomplete.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Rebuild each visit
Assemble the workscope, module builds, test-cell data, and release for every shop event.
Cross-check the parts
Confirm each disk and part installed appears on the build record and the LLP status.
Tie test to release
Match the test-cell run to the release certificate and the recorded workscope.
Flag the gaps
Log each visit whose package fails to reconcile and the evidence still needed.
What the buyer receives
- An exception list where a shop package fails to reconcile across its parts
- A source map across the workscope, build records, test data, and release for each visit
- A closure plan naming the missing build, test, or release evidence per visit
Who uses the output
- Engine planners deciding what the next shop visit will find before the engine opens
- Asset managers pricing the engine against a shop history that actually reconciles
- Records teams assembling the engine file a buyer or lessee will demand at transfer
How the work fits into the transaction or program
The shop-visit review sits between one engine event and the next, settling each prior package before the engine comes off the wing again. Its exception list drives recovery while the shops still hold the build and test evidence, and the reconciled packages support the LLP trace and the engine-program position the transaction rests on.
Aircraft-specific considerations
G650 engines are usually enrolled on an hourly maintenance program, so their shop visits are driven by program logic and event thresholds rather than by heavy airline utilization, and a business-jet engine may accumulate only a few shop visits over many years. That makes each package individually important, because there are fewer of them to cross-check against, and a single missing test-cell run or build record carries more weight than it would on a high-utilization fleet engine.
Jurisdiction-specific considerations
A G650 traded between an FAA register and an EASA register needs engine release evidence the receiving authority accepts, which for a shop visit means a release certificate and part paperwork acceptable to that system. The review flags any shop visit whose release will not satisfy the destination register.
Regulatory limits
The review reconciles the shop-visit records and grades the package behind each event. It does not certify the engine, set its condition or remaining life, or make an airworthiness determination on any module or part.
What this review does not cover
- Physical inspection, borescope, or test of the engine
- Assessing the engine's mechanical condition beyond what the records show
- Issuing release paperwork for a shop visit whose package is incomplete
Specific to this review
- A shop package is only as strong as its weakest tie: a missing test-cell run can undercut an otherwise complete visit.
- A disk changed at a visit has to appear on both the build record and the LLP status, or the engine's life position is in doubt.
- Business-jet engines see few shop visits over their life, so each package carries more diligence weight than on a high-cycle fleet.
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 does a disk change on the build record have to match the LLP status?
The build record proves the disk went into the engine, and the LLP status carries its remaining life for the whole asset. If the two disagree, the engine's life position cannot be trusted, which is exactly the figure a buyer or engine planner relies on.
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.