Engine shop visits
Embraer E-Jet engine shop-visit records review
This review examines an Embraer E-Jet engine shop-visit package and confirms the work, the module builds, and the release hold together as one supported event. It is run by or for a party evaluating, transferring, or maintaining the engine, where the shop visit drives both life status and value. It covers the shop report, the module build records, the test-cell data, and the release certificate that closed the visit. You receive a supported view of the shop visit, a list of gaps where the build or life status does not reconcile, and a source map from the package to its supporting records.
When this review is needed
- An E-Jet engine is being traded and its last shop visit sets the life and value story.
- A module build during the visit is where the LLP cycle trace is suspected to break.
- The shop report claims a work scope the test-cell data does not appear to support.
- The engine is transferring and the visit package has to satisfy the receiving records.
The problem
An engine shop visit produces a thick package, and a thick package can still fail to reconcile. The shop report claims a work scope, but the module build records do not show the parts it names, the LLP cycles carried out of the build do not match what went in, or the test-cell data does not support the performance the release asserts. A buyer or receiving operator inherits the engine on whatever the package actually proves, not what it claims.
What gets reviewed
- The shop report and the work scope it claims for the visit
- Module build records reconciled against the parts and life carried in and out
- LLP cycle trace across the build for parts that changed
- The test-cell data supporting the performance the release asserts
- The release certificate closing the visit against the work performed
- Gaps where the build, the life status, or the release do not reconcile
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 work scope matches the module build records for the visit
- LLP cycles carried out of the build reconcile with what went in
- Recorded test-cell data supports the performance shown on the release
- Serial numbers on the build records match the release and the status sheet
- The release certificate closes the exact work the shop report describes
Evidence normally required
- The engine shop-visit package for the visit under review
- The shop report and work scope for the visit
- Module build records and the parts list for the build
- Test-cell data from the visit
- The release certificate and the LLP status carried out of the visit
Common discrepancies
- A module build record that does not show a part the shop report claims was worked
- An LLP cycle count carried out of the build that does not match what went in
- Test-cell data that does not support the performance on the release
- A serial-number mismatch between the build records and the release certificate
What is at stake
A shop visit that does not reconcile undermines the engine's life status and its value, and a broken cycle trace at a module build forces a conservative life on the affected parts. A release that outruns the test-cell evidence can be challenged at induction, and an unreconciled build can reopen the engine's history exactly when a sale or transfer depends on it.
Move from findings to resolution
Move from findings to a documented resolution path.
How the work runs
Read the work scope
Establish what the shop report claims the visit performed on the engine.
Reconcile the build
Match the module build records and LLP cycles against the work scope and the parts moved.
Check release to evidence
Confirm the test-cell data and the release certificate support the work claimed.
Report the gaps
Deliver the reconciled view, the gap list, and the source map for the package.
What the buyer receives
- A supported view of the shop visit as a reconciled event
- A list of gaps where the build or life status does not reconcile
- A source map from the package to its supporting records
Who uses the output
- Asset managers and traders pricing the engine's life and shop-visit story
- Records teams reconciling the visit package for a sale or transfer
- Continuing-airworthiness staff confirming the engine's status after the visit
How the work fits into the transaction or program
The shop-visit package is where an engine's life status and value are set, so it anchors the LLP trace and the engine's contribution to the aircraft records review. What this check surfaces feeds the trace reconciliation and the value case a buyer will test before paying for the engine.
Aircraft-specific considerations
E-Jet engines under regional utilization reach shop visits on cycles rather than calendar, so a mid-life engine can already carry several visits whose packages have to reconcile against each other, not just individually. Because the same engine may have been leased separately from the airframe, the shop-visit history has to be read across custody changes to keep the module build and LLP trace continuous.
Jurisdiction-specific considerations
A shop visit performed under one authority's approval may need its release re-presented for a receiving register, and a package that ran through both FAA and EASA shops will mix release forms accordingly. The review notes where the visit is supported for the outgoing side but would need dual-release evidence or a bridging assessment for the destination.
Regulatory limits
The review confirms whether the shop-visit package reconciles and is supported by evidence. It does not certify the engine, validate the maintenance performed, or make an airworthiness determination on the engine or its modules.
What this review does not cover
- Performing or re-performing any engine maintenance
- Issuing a release certificate for the engine or a module
- Any airworthiness determination on the engine
Specific to this review
- The module build is where cycle trace breaks: parts move between builds and the life carried out has to reconcile with what went in.
- A release can outrun its test-cell data, so the performance the certificate asserts is checked against the evidence rather than accepted.
- E-Jet engines reach shop visits on cycles, so a mid-life engine carries several packages that have to reconcile against each other.
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 reconcile the build if the engine has a valid release?
A valid release closes the visit, but it does not by itself prove the module build and the LLP cycles reconcile. A broken cycle trace at a build forces a conservative life on the affected parts regardless of the release, which is why the build records are checked against what the release asserts.
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.