Engine shop-visit records
Boeing 737 MAX engine shop-visit records review
This review works through an engine shop-visit package from a Boeing 737 MAX and confirms the visit's outcome is supported end to end. It runs when an engine is valued, separated for sale, or accepted after a shop event, run by or for the party relying on the shop-visit history. It covers the shop report, the module build records, the test-cell data that closed the visit, and the release certificate that returned the engine to service. You receive an exception list per visit, a source map from the shop report to its supporting records, and a closure plan for the visits the package cannot fully support.
When this review is needed
- A 737 MAX engine is being separated for sale and its shop-visit package sets what a buyer will pay.
- The engine came back from a shop visit and the package has to be accepted before it flies.
- A module build during the visit combined parts whose histories the package has to carry.
- The workscope claimed in the shop report has to be matched to the test-cell data that closed it.
The problem
A shop visit is documented across several packages that have to agree, and a 737 MAX engine visit is where they most often do not. The shop report states a workscope while the module build records, the disk sheets, and the test-cell data behind it tell a slightly different story, or one of them is missing from the package that changed hands. A visit that reads as complete can rest on a release certificate that does not reflect the build the report describes.
What gets reviewed
- The shop report and the workscope it claims for the visit
- Module build records and the parts installed during the visit
- Test-cell data supporting the engine's return-to-service condition
- The release certificate that closed the visit and returned the engine
- Life-limited parts touched during the visit and their carried trace
- Serial and part-number agreement across the package
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 shop report's workscope agrees with the module build records for the visit
- Test-cell data supports the return-to-service condition the report claims
- The release certificate reflects the build the shop report describes
- Life-limited parts touched during the visit carry a trace that survives it
- Serial and part numbers reconcile across the shop report, build records, and release
Evidence normally required
- The engine shop-visit package for each recorded visit
- The shop report and its workscope statement
- Module build records and disk sheets for the visit
- Test-cell data closing the visit
- The release certificate returning the engine to service
Common discrepancies
- A shop report workscope the module build records do not fully support
- A release certificate that does not reflect the build described in the report
- Test-cell data missing from a package that otherwise reads as complete
- A life-limited part touched at the visit whose trace does not carry across it
What is at stake
An engine whose shop-visit package cannot be tied together prices down or holds a transaction open until the missing records surface. A build the test data does not support, or a workscope the release does not match, is a finding a buyer will press, and the parts that passed through that visit inherit the doubt until the package reconciles.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the shop report
Establish the workscope and outcome the report claims for the visit.
Match build and test data
Confirm the module build records and test-cell data support the report's claims.
Tie to the release
Check the closing release reflects the build described and carries the trace of parts touched.
Report the exceptions
Deliver the per-visit exception list, source map, and closure plan.
What the buyer receives
- An exception list per shop visit graded by where the package fails to agree
- A source map from the shop report to its supporting build and test records
- A closure plan for the visits the package cannot fully support
Who uses the output
- Asset managers pricing an engine against the shop-visit history that supports it
- Records teams assembling the build and test records behind an incomplete package
- Receiving teams accepting an engine after a shop visit on a supported package
How the work fits into the transaction or program
The shop-visit package is where an engine's condition and its life-limited part trace are set, so it underpins both the AD picture and the LLP status the transaction reads. This review confirms the package agrees with itself and closes to a matching release, and its exception list drives the record recovery an engine sale or acceptance waits on.
Aircraft-specific considerations
The 737 MAX engine's build standard and part-number configuration are set and refreshed at each shop visit, so the module build records are the spine the rest of the package hangs on. A visit that advanced the build standard has to show the release and the configuration record moving with it, and a package that documents the work but not the resulting standard is the common 737 MAX shop-visit gap.
Jurisdiction-specific considerations
A 737 MAX engine returned to service under an FAA-basis shop needs release evidence a receiving EASA operator recognizes, so the review checks the closing release for dual-release status rather than assuming it carries across the boundary.
Regulatory limits
This review confirms the shop-visit package is internally consistent and closes to a matching release. It does not approve the workscope, certify the engine, or make any airworthiness determination on the engine or its parts.
What this review does not cover
- Performing or re-performing any engine work
- Issuing a release certificate for the engine
- Any airworthiness determination on the engine or its components
Specific to this review
- A shop-visit package is several documents that have to agree, so the failure mode is a workscope, a build record, and a release that tell three slightly different stories.
- On the 737 MAX engine the module build records are the spine, because the build standard set there governs what the rest of the package must show.
- A package that documents the work but not the resulting build standard is the gap that surfaces when an engine is separated for its documented condition.
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
The engine came back with a release. Why review the whole package?
The release closes the visit, but a buyer or a receiving operator will test whether the shop report, the module build records, and the test-cell data behind it agree with that release. This review reconciles the package so a visit that reads complete actually holds together end to end.
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.