← Back to list

P0175 Diagnostic Issue on 2011 Chevrolet Tahoe After Front End Collision

Model: 2011 Tahoe Fault Code: P0175 Posted: 2019-01-23 17:50

I own a 2011 Chevrolet Tahoe with 45,000 miles and has been garage kept with minimal use. It has never had any prior issues until August 2017, when it sustained a minor front-end impact on the driver's side fender. The vehicle was repaired by Service King and subsequently began running roughly. After checking the diagnostic codes, I found P0175 — indicating a rich fuel condition in Bank 2 (passenger-side engine). Initial troubleshooting pointed to the Accelerator Pedal Position (APP) sensor, which I replaced once. For several months, the vehicle ran smoothly. However, the check engine light returned and the same P0175 code reappeared. I later replaced the APP sensor a second time after consulting this forum, where users suggested that a bad APP sensor could cause inconsistent throttle response. Despite this, the issue persisted. Recently, I received a diagnosis from Goodyear indicating a faulty APP sensor — leading me to replace it for the third time within just 1.5 years. The vehicle has seen less than 1,500 miles since the accident, yet the problem continues to recur every few months. This raises concerns: is there a root cause related to the collision? Could heat or electrical stress from the impact be damaging the sensor repeatedly? I'm seeking clarity on how to properly diagnose this recurring issue and whether the APP sensor is actually the source of P0175, as technical sources indicate that APP sensors primarily affect throttle control, not fuel mixture richness. I suspect a deeper underlying problem — possibly wiring issues or a faulty air intake system — that may be masked by the APP sensor failure. I am now planning to take it to an ASE-certified diagnostic shop with proper equipment and expertise to perform a full circuit analysis, including voltage checks and signal validation using a lab scope. Any insights into how to identify whether the APP sensor is truly at fault or if another component (like the Mass Air Flow Sensor) should be investigated would be greatly appreciated.

Related fault codes
P0175
Comments (17)
Anonymous 2019-01-24 12:09

The P0175 code specifically affects Bank 2, so focus your troubleshooting on the passenger-side engine. Confirm that the issue is isolated to that side and not affecting both banks. For more details, refer to official OBD-II documentation for P0175.

Anonymous 2019-01-25 18:23

I took it to Goodyear, who diagnosed a faulty APP sensor. After replacing the sensor, the issue resolved temporarily — lasting about six months before returning.

Anonymous 2019-01-26 07:15

The Accelerator Pedal Position (APP) sensor does not directly cause a rich fuel condition. It is an input signal for throttle body control. A failing APP sensor would typically trigger specific DTCs like P2120, P2122, P2123, P2125, P2127, P2128, or P2138 — not P0175. These are manufacturer-specific codes and cannot be read with generic OBD-II scanners. If the same sensor keeps failing repeatedly, it may indicate electrical stress from the accident. Consider a professional diagnostic using proper tools like a lab scope and wiring diagrams to verify signal integrity. A bad APP sensor would cause throttle inconsistencies or poor fuel economy, but not directly lead to P0175. Check for any indication of 'Reduced Engine Power' or limp mode in the dashboard.

Anonymous 2019-01-26 09:26

Agreed — this point is critical. The presence of a P0175 code without corresponding APP-related DTCs suggests that the root cause may not be the APP sensor at all.

Anonymous 2019-01-26 16:11

Thanks for the helpful input. Your guidance has been very valuable — I appreciate it!

Anonymous 2019-01-26 21:31

No other diagnostic codes are present. The issue returns consistently after about six months, which suggests a recurring or environmental cause rather than a simple sensor failure.

Anonymous 2019-01-27 09:53

A failing APP sensor would result in throttle inconsistencies and reduced fuel efficiency — but it should not trigger P0175. For an APP-related code to appear, there must be corresponding DTCs such as P2120 or P2138. These are manufacturer-specific codes that require a professional scan tool with full diagnostic capability. Given the repeated sensor replacements and lack of other codes, I suspect physical damage from the accident is causing intermittent electrical faults in the wiring or sensor harness. I recommend checking all connections, connector integrity, and performing voltage and signal tests using a digital multimeter or lab scope. A proper wiring diagram and circuit analysis are essential to determine if the issue lies with the sensor itself or its associated circuits.

Anonymous 2019-01-27 14:08

Perform a visual inspection of the dual APP sensors. If you have a digital volt-ohmmeter (DVOM), conduct continuity and signal voltage checks on both sensors to verify proper operation.

Anonymous 2019-01-29 08:01

It's frustrating when people ask questions but don't respond — it wastes time and reduces the value of community discussions.

Anonymous 2019-01-29 09:22

Sometimes it’s just Joe — but those who follow up and share outcomes make our efforts truly worthwhile.

Anonymous 2019-01-29 19:29

True, only a few users respond. It's a common issue in online forums.

Anonymous 2019-01-29 21:10

No other codes are present. The problem returns after about six months. I will now take it to a certified diagnostic shop for proper evaluation.

Anonymous 2019-01-29 21:12

I truly appreciate the help and guidance. Unfortunately, life has kept me from replying earlier — I'm grateful for your patience.

Anonymous 2019-01-31 09:52

We understand — it would be helpful if you could share how the issue was resolved in case others face a similar situation.

Anonymous 2019-04-21 17:05

I finally took the vehicle to a professional shop. They cleared old codes and performed a full system relearn. The car now runs smoothly — I can feel the improvement immediately. Thanks again for all the advice. Having a company car helped, as we didn’t need another vehicle until I found a qualified shop.

Anonymous 2019-04-23 08:27

Great to hear you resolved it! Did you document the old diagnostic codes in case they return? Let’s hope this issue doesn’t reoccur.

Anonymous 2019-04-23 17:06

Yes, I wrote down all the old codes and saved them in my file. Thanks again for your support.