Boeing 747 engines
Boeing 747 family engine shop-visit records review
This review works through the engine shop-visit packages behind a Boeing 747's powerplants and confirms each visit closes with the build, test, and release evidence a buyer will expect. It is run for the party evaluating or holding the asset when engine value and remaining life drive the deal. The work reads shop reports, module build records, test-cell data, and release certificates, and follows LLP trace through each disk change. You receive an exception list per shop visit, a source map tying status back to the packages, and a closure plan for the events whose evidence does not yet hold together.
When this review is needed
- An engine's remaining life is a major part of the asset value and the shop-visit history has to substantiate it.
- A powerplant is coming off for separate sale or lease and its build records must stand alone.
- A recent shop visit closed under time pressure and the package was never fully reconciled.
- LLP trace has to be confirmed through a module build before a transaction can price the engine.
The problem
An engine's paper is only as good as its last shop visit, and on a 747 that history can span multiple shops and several overhauls. Module build records, test-cell sheets, and release certificates arrive as thick packages that rarely reconcile themselves. When a disk changes at a build and the trace does not carry cleanly through the shop report, the status list can claim remaining life the package cannot prove.
What gets reviewed
- Each shop-visit package reconciled to the work the release certificate claims
- Module build records checked for the parts installed and removed at each build
- Test-cell data present and consistent with the release for the visit
- LLP trace followed through every disk change at a module build
- Release certificates checked for the correct form and authorizing signature
- The workscope of each visit reconciled against the reason it entered the shop
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 closes with a release certificate on the correct form for the jurisdiction
- Module build records account for the parts the release certificate lists
- Test-cell results are present and support the release for that visit
- LLP part and serial numbers trace through the build without a break
- The recorded remaining life on each LLP follows from the build history, not the summary alone
Evidence normally required
- The engine shop-visit packages for each visit on file
- Module build records and the parts lists for each build
- Test-cell data sheets for the relevant visits
- Release certificates issued at each shop visit
- The current LLP status list with supporting release documents
Common discrepancies
- An LLP whose trace breaks at a module build with no supporting release
- A shop visit closed without the test-cell data the release implies
- A release certificate on a form that does not match the receiving jurisdiction
- A build record that lists a part the status summary does not reflect
What is at stake
A shop visit whose evidence does not close forces the current status onto a conservative assumption, and an LLP whose trace breaks at a module build cannot be relied on for its remaining life. In a transaction that turns directly into price, and reconstructing the missing sheet after the shop has moved on is slow and sometimes impossible.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Order the visits
Assemble each engine's shop-visit packages in sequence and match them to the status summary.
Reconcile the build
Check module build records and test-cell data against the release for each visit.
Follow the LLP trace
Track each life-limited part through its disk changes to a supporting release.
Close the exceptions
List the visits and traces that need recovery and plan the document chase.
What the buyer receives
- An exception list per shop visit with the missing or inconsistent evidence
- A source map tying each engine status figure back to its shop-visit package
- A closure plan for the visits and LLP traces that need document recovery
Who uses the output
- Asset managers pricing engine value against the shop visits the records substantiate
- Records teams assembling a shop-visit file an engine buyer will accept
- Continuing-airworthiness teams confirming LLP standing before the next induction
How the work fits into the transaction or program
The review runs where engine value is set, before a sale, a green-time lease, or an off-wing event. Its exception list drives recovery of the missing build or release sheet while the shop link still holds, and the confirmed LLP trace feeds the status the next owner will price and operate against.
Aircraft-specific considerations
A 747 carries four engines, which multiplies the shop-visit history and the number of module builds a review has to follow. Long service lives mean several overhauls per powerplant and a mix of shops, so the review scopes to each serial number's own visit chain rather than treating the four positions as interchangeable.
Jurisdiction-specific considerations
A release issued on FAA Form 8130-3 and one issued on EASA Form 1 are not automatically interchangeable, and dual-release status is what an engine crossing registers usually needs. The review notes where a shop visit's release form will require attention for the jurisdiction the engine is moving toward.
Regulatory limits
The review reconciles the shop-visit evidence and reports what the packages support. It does not certify an engine, set or restore remaining life on an authority's behalf, or determine that a powerplant is airworthy.
What this review does not cover
- Physical inspection, borescope, or test of any engine
- Re-life or re-certification of any life-limited part
- Any airworthiness determination on the powerplants
Specific to this review
- The module build is where LLP trace most often breaks on an engine, because a disk change there depends on a supporting release that is easy to omit from the package.
- Test-cell data missing from a shop visit weakens the whole release even when the mechanical work was sound, because the visit cannot be shown to have closed.
- With four engines and repeated overhauls, a 747 shop-visit file is large enough that duplicated or superseded packages routinely contradict the status summary.
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
Does this replace an engine records audit by the buyer's own team?
No. It gives the holder a clear picture of what the shop-visit packages actually support before a buyer's team looks, so gaps can be closed on the seller's own terms rather than surfacing mid-diligence with less leverage.
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.