P0132
PowertrainO2 Oxygen Sensor Circuit High Voltage (Bank1, Sensor1)
The bank 1 sensor 1 (front) oxygen sensor is reporting voltage stuck high. Either the engine is genuinely running rich (sensor reporting truthfully) or the sensor itself has failed in a high-voltage state.
ⓘ Information only. This page provides general educational information about fault code P0132. We do not assess the urgency or safety implications of any specific fault. That requires in-person diagnosis by a qualified mechanic. Full terms.
Recommended next steps
Whether a fault is urgent, drivable, or routine depends entirely on the cause on a specific vehicle, and that can only be determined by a qualified mechanic with diagnostic equipment. If a warning light is illuminated, the most reliable next step is professional diagnosis.
What does P0132 mean?
P0132 is a Powertrain (engine, transmission, fuel system) fault code. It indicates: O2 Oxygen Sensor Circuit High Voltage (Bank1, Sensor1).
This is a standardised OBD-II code. The technical definition is the same regardless of the make or model of vehicle, although specific causes and symptoms can vary between vehicles.
Symptoms commonly associated with this code
Symptoms that drivers often report alongside this code. Not all may apply to every case:
- • Engine warning light
- • Black smoke from the exhaust under load
- • Strong smell of petrol from the exhaust
- • Significantly worse fuel economy
- • Rough running, hesitation
- • Spark plugs fouling rapidly with black soot
- • Sometimes the rear sensor also reads high (P0138) as the rich condition passes through the cat
Possible causes
Causes commonly associated with P0132, listed in approximate order of typical investigation. The actual cause on a specific vehicle can only be confirmed by professional diagnosis.
- 1. Genuine rich condition: leaking injector, stuck-open injector, fuel pressure too high, or coolant temp sensor reading too cold (ECU thinks engine is cold and runs rich)
- 2. Failed oxygen sensor stuck high
- 3. Sensor wiring shorted to power
- 4. Coolant or oil contamination on the sensor itself (head gasket leak, valve seal failure)
- 5. Vacuum leak elsewhere making the sensor read incorrectly
How mechanics typically diagnose
A typical diagnostic sequence used by mechanics, provided here for educational reference only. Diagnostic work should be performed by a qualified mechanic with the appropriate tools and training.
- 1. Check live fuel trim. Long-term trim well below zero (-15% or worse) means the engine is genuinely rich and the sensor is reporting honestly
- 2. Inspect injectors for leaks (visually, or by leak-down test)
- 3. Verify fuel pressure is in spec, not too high
- 4. Check coolant temperature sensor reading at full operating temperature, should be around 90°C
- 5. If fuel trims are healthy but the sensor reads high, the sensor itself is the likely fault
Common questions about P0132
Will my fuel consumption be obviously worse? +
Yes, often dramatically. A rich-running condition can cost 20-40% in fuel economy. If you're noticing the tank emptying noticeably faster, it's a genuine rich problem rather than a faulty sensor. The ECU is dumping fuel based on what the sensor is telling it.
Could a coolant leak cause this? +
Yes, two ways. A failing head gasket can let coolant into the cylinder, which contaminates the oxygen sensor and damages it (silicates from coolant poison the sensor element). And a coolant temperature sensor reading too cold makes the ECU run the engine rich during what it thinks is warm-up. Worth checking coolant level and condition if P0132 appears.
Will it damage my catalytic converter? +
Eventually yes. Sustained rich running sends unburned petrol into the cat, which damages the substrate over time. Persistent rich-running codes alongside P0420/P0430 (cat efficiency) often appear together as a result. Fix the rich condition before the cat is damaged enough to need replacing, that's a £400-£1,500 job in itself.
Information only, not professional advice
The information on this page is provided for general guidance and educational purposes only. It is not a substitute for diagnosis or repair advice from a qualified mechanic. Always verify any fault before paying for repairs. carfaultcodes.co.uk accepts no liability for decisions made based on this information. Full terms →