P0106 Code: MAP Sensor Circuit Range Issue

Quick answer

Code P0106 indicates the engine control module (ECM) detected an issue with the manifold absolute pressure (MAP) sensor's output signal being outside its expected range or not performing as intended. This means the sensor's voltage or pressure readings are abnormal compared to what the ECM anticipates for the current engine conditions.

What the P0106 Code Means for Your MAP Circuit

The MAP sensor measures intake manifold pressure to help the ECM calculate engine load and adjust fuel delivery and ignition timing. Under normal conditions, the sensor outputs a voltage signal that correlates to manifold pressure: low pressure (high vacuum) at idle produces a low voltage (around 0.5-1.5V), while high pressure (low vacuum or boost) produces a higher voltage (up to 4.5-5V). The ECM continuously compares this signal to expected values based on throttle position, RPM, barometric pressure, and other inputs.

When P0106 sets, the ECM has determined the MAP sensor's signal is irrational for the operating conditions. This could be due to the sensor reporting pressure that's too high or too low, or the signal fluctuating erratically. Unlike a simple circuit fault (e.g., P0107 for low voltage or P0108 for high voltage), P0106 specifically flags a range or performance issue; meaning the signal is present but doesn't match what the ECM's logic predicts. For example, if the engine is at idle (high vacuum), the ECM expects a low MAP voltage, but the sensor reports a voltage consistent with wide-open throttle (low vacuum). This mismatch triggers the code.

Common scenarios that trigger P0106 include a MAP sensor with internal damage (e.g., a cracked diaphragm or contaminated sensing element), a vacuum leak causing false pressure readings, or wiring/intermittent connection issues that distort the signal. In some cases, a faulty barometric pressure sensor (often integrated into the MAP sensor) can also cause this code, as the ECM may use barometric pressure as a reference point for MAP readings.

The ECM's diagnostic strategy for P0106 typically involves cross-checking the MAP signal against the throttle position sensor (TPS), mass airflow (MAF) sensor, and engine speed. If the MAP reading deviates by a set threshold (often 10-20% or more) from the expected value for a given duration (e.g., 5-10 seconds), the code is stored. This ensures the issue isn't a momentary glitch but a consistent performance problem.

It's worth noting that P0106 is not a circuit failure code (like P0105 for a circuit malfunction). Instead, it's a performance code, which means the sensor and its wiring are likely intact; but the data it's providing is unreliable. This distinction is critical for diagnosis, as it narrows the focus to the sensor's accuracy or external factors affecting its readings (e.g., vacuum leaks).

Common Symptoms of P0106

When P0106 is active, you may notice rough idle or stalling, as the ECM struggles to maintain the correct air-fuel ratio with inaccurate manifold pressure data. Acceleration can feel sluggish or hesitant, since the ECM may enrichen or lean the fuel mixture incorrectly. In some cases, the check engine light is the only symptom, especially if the deviation is minor but persistent. See the full P0106 symptoms guide for a detailed breakdown.

Typical Causes of P0106

P0106 is most often caused by a faulty MAP sensor, but other culprits include vacuum leaks near the sensor, damaged wiring or connectors, or a clogged intake manifold. Less commonly, a failed barometric pressure sensor or ECM software issue may be to blame. Repairs typically range from $150 to $1,000+ depending on the cause. See the full P0106 repair cost guide for a detailed breakdown.

Can You Still Drive With Code P0106?

You can usually drive with P0106 in the short term, but it's not advisable for long. The ECM will default to substitute values for the MAP sensor, which can lead to poor fuel economy, reduced power, or even stalling. In severe cases, prolonged driving with this code may cause catalytic converter damage due to an incorrect air-fuel mixture.

Details that improve the diagnosis

Compare the reported value with engine temperature, barometric pressure, throttle position and related sensors. A signal that is electrically valid can still be implausible. Fuel trims at idle and at a steady higher speed help separate an intake leak from a fuel-delivery or measurement problem.

Before clearing anything, record whether the code is current, pending, history or permanent. Save companion codes and freeze-frame conditions, then note recent repairs, a weak battery, weather changes and the exact moment the symptom appears. After a confirmed repair, clear only the erasable codes and complete the appropriate drive cycle. A permanent code normally clears only after the onboard monitor verifies that the fault is gone.

Related trouble codes

Information to record before any repair

Write down the exact code, its status and every companion code reported by a complete vehicle scan. Save the freeze-frame values, including engine speed, load, coolant temperature, vehicle speed, battery voltage and fuel trims when available. Note whether the warning appeared during a cold start, at idle, under acceleration, after refueling, in wet weather or immediately after other work. These details help separate an intermittent electrical problem from a repeatable mechanical or operating-condition fault.

Identify the exact year, make, model, engine, transmission and market version before using a wiring diagram or specification. Connector pinouts, monitor thresholds, component locations and test procedures can change within the same model line. Check current manufacturer service information and relevant technical service bulletins. A bulletin can improve the test sequence, but it should not be treated as proof that the same fault exists on every vehicle.

How to verify the repair

A warning light that stays off immediately after codes are cleared does not by itself confirm a repair. Recheck live data, repeat the operating condition that originally set the code when it is safe to do so, and confirm that no pending code returns. Some monitors need a specific drive cycle before they run. Permanent codes are normally removed by the control module only after it sees enough successful monitor results. If symptoms remain or the code returns, continue testing instead of replacing another part by guesswork.