777 family shop visits
Boeing 777 family engine shop-visit records review
This review checks that each engine shop visit on a Boeing 777 family aircraft is documented with a package that ties module builds, test-cell results, and release evidence to the parts that came out. It is run for a lessor, airline, or asset manager evaluating, transferring, or holding a specific tail. The work reads the shop-visit reports against module build records and the LLP trace running through them. You receive a supported exception list, a source map linking each visit to its build and release evidence, and a closure plan for the serial number under review.
When this review is needed
- A 777 engine is being valued and the shop-visit history has to prove what was built and released.
- A module build changed the disks and the package must show the LLP trace held across the swap.
- A buyer wants each shop visit reconciled before the engine value is priced into the deal.
- An engine is coming off for separate sale and its build records drive what it will fetch.
The problem
An engine's documented value lives in its shop-visit packages, and each visit generates build sheets, test-cell data, and release forms that have to agree with each other and with the LLP status. A module build that swapped a disk but left the build sheet and the status sheet out of step breaks the story a buyer relies on, and the packages are often thick, mixed-language, and scattered across shops that no longer hold the originals.
What gets reviewed
- Each shop visit documented with a package covering induction, build, and release
- Module build records reconciled to the parts and disks recorded as installed
- Test-cell data present and consistent with the release for each visit
- The LLP trace confirmed to carry across every module build in the history
- Release certificates matched to the engine and modules returned to service
- Workscope and findings reconciled to the build actually accomplished
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
- Each shop visit in the history has a package covering induction through release
- Module build sheets agree with the parts and disks the status records show installed
- Test-cell results are present and consistent with the release issued for the visit
- The LLP trace holds across every build without a break at a module change
- Release evidence matches the engine and serial numbers returned to service
Evidence normally required
- The engine shop-visit reports and build packages for the history
- Module build sheets and disk sheets for each visit
- Test-cell data and workscope records
- The LLP status sheet for the engines
- Release certificates for the engine and its modules
Common discrepancies
- A module build whose sheet disagrees with the disks the status sheet records
- A shop visit with a release but no test-cell data behind it
- An LLP trace that breaks at a build where a disk was changed
- A workscope that does not reconcile to the findings and the build accomplished
What is at stake
A shop visit that cannot be reconciled undermines the remaining-life figure the engine is priced on, and a build with an incomplete package may force a conservative life assumption or a discount. Recovering test-cell data or a build sheet after the engine has moved on is slow, and a gap discovered at sale weakens the position exactly when leverage is lowest.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the visit history
Lay out the engine's shop visits in sequence and confirm a package exists for each.
Reconcile the builds
Match module build sheets to the disks and parts the status records show installed.
Confirm test and release
Check test-cell data and release evidence agree with the build accomplished.
List the exceptions
Flag visits that do not reconcile and sequence the build records to recover.
What the buyer receives
- A supported exception list of shop visits whose packages do not reconcile
- A source map linking each visit to its build, test, and release evidence
- A closure plan sequencing which build records to recover before the next milestone
Who uses the output
- Asset managers pricing the engine against a reconciled build and life history
- Records teams closing shop-visit gaps before a redelivery or a separate engine sale
- Buyers confirming the engine's documented value before they pay against it
How the work fits into the transaction or program
The shop-visit history is where the engine value and the LLP trace meet, so this review runs before a deal prices the engine or the engine is split from the airframe for its own sale. The exception list drives recovery while the shops that ran the visits can still be reached, and the reconciled packages become the evidence an engine buyer verifies.
Aircraft-specific considerations
The 777 flies long sectors, so its engines spend more time between shop visits than a short-haul type but return with heavier workscopes when they do, and each visit's package is correspondingly dense. The most valuable records are the high-pressure module build sheets carrying the life-limited disks, so those are reconciled to the LLP status first, and the packages are scoped to this engine's actual visit chain rather than a family average.
Jurisdiction-specific considerations
An engine released under an FAA-accepted shop and one released under an EASA-accepted shop carry different acceptance history, and a 777 engine that has visited shops under both systems needs its release evidence lined up with the register the aircraft is heading toward.
Regulatory limits
The review reconciles the shop-visit records to the builds and releases they document. It does not approve a build, certify a module, or determine that the engine or the aircraft is airworthy.
What this review does not cover
- Physical inspection or test of the engine or its modules
- Re-certification or re-life of any engine part
- Any airworthiness determination on the engine or airframe
Specific to this review
- The heaviest reconciliation on a 777 engine file is the high-pressure module build, because that is where the life-limited disks are carried and swapped.
- Test-cell data is the record most often missing from an otherwise complete shop-visit package, and its absence weakens the release it should support.
- A 777 engine's long on-wing intervals mean fewer shop visits but denser packages, so a single unreconciled visit carries more weight than on a short-haul type.
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 missing shop-visit package matter if the engine runs fine?
The engine's value at sale rests on documented build and life history, not just condition. A shop visit that cannot be reconciled forces a conservative remaining-life assumption or a discount, so the paperwork carries as much value as the hardware.
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.