P2166 – Throttle/Pedal Position Sensor “D” Maximum Stop Performance

P2166 is a Powertrain (P) diagnostic trouble code that points to a throttle actuator control signal plausibility issue—meaning the engine control system has detected a mismatch or implausible relationship within the electronic throttle control signals it monitors. SAE J2012 defines the DTC structure and broad categories, but the exact monitored circuit(s), thresholds, and “implausible” criteria can vary by make, model, and year. Your job is to confirm which signal failed the plausibility test using scan data and basic electrical checks (power, ground, reference, and signal integrity) before replacing parts.

What Does P2166 Mean?

Using SAE J2012 formatting, P2166 is a powertrain fault that generally indicates the control module detected an implausible or incorrect relationship in the signals used to control or verify electronic throttle operation (often called Electronic Throttle Control (ETC)). The standardized DTC descriptions and formatting conventions are published in the SAE J2012-DA digital annex, but many powertrain “plausibility” monitors are manufacturer-calibrated, so the exact affected input/output may differ by vehicle.

This code is shown without a hyphen suffix, so it’s displayed without a Failure Type Byte (FTB). If an FTB were present (for example, a “-xx” subtype on some platforms), it would further qualify the failure mode (such as the specific signal behavior the module detected). What makes P2166 distinct is that it’s not just a simple “high/low” voltage complaint—it’s a correlation/plausibility failure where two or more signals (or a commanded state vs. actual feedback) don’t agree within an expected window.

Quick Reference

• Code type: Powertrain (SAE J2012 format), plausibility/correlation fault
• System-level meaning: Throttle actuator control signal relationship is implausible
• Commonly associated with: Electronic Throttle Control (ETC) throttle body, accelerator pedal position sensing, wiring/connectors, control module inputs
• Typical driver complaints: Reduced power, poor throttle response, intermittent limp mode
• What to verify first: Battery voltage stability, clean power/grounds, connector condition, scan data plausibility at idle and with slow pedal sweep
• Best first test: Compare commanded throttle vs. throttle position feedback and pedal sensors for smooth, matching changes

Real-World Example / Field Notes

In the bay, P2166 often shows up as an intermittent reduced-power event rather than a constant no-start. One common pattern is the code setting during light throttle tip-in or during a steady cruise where the module expects a stable relationship between accelerator input and throttle movement. I’ve seen it caused by something as simple as a slightly spread throttle body connector pin (one possible cause), where vibration creates brief dropouts that only show up on a graphing scan tool. Another frequent “gotcha” is low system voltage during cranking or after a battery replacement; the throttle control system is very sensitive to unstable voltage and ground integrity. The most time-saving approach is to confirm the implausibility with live data (pedal sensors vs. throttle position vs. commanded angle) and then prove whether the issue is signal integrity (wiggle test, voltage drop, scope) or a mechanical throttle plate concern before considering any module-related possibilities.

Symptoms of P2166

• Check Engine Light (Malfunction Indicator Lamp) illuminated, sometimes after a cold start or during steady cruising.
• Reduced Power limited throttle response or a “limp” strategy if the Powertrain Control Module (PCM) can’t trust correlated sensor inputs.
• Hesitation stumble on tip-in or during light acceleration when the PCM transitions between control strategies.
• Poor Fuel Economy increased fuel consumption if the PCM falls back to default values or enriched operation.
• Unstable Idle idle flare, hunting, or intermittent roughness when plausibility checks fail at low airflow/load.
• Hard Starting extended crank in some cases if the PCM delays fueling/spark decisions waiting for plausible signals.
• Intermittent Behavior symptoms that come and go with vibration, moisture, heat soak, or harness movement.

Common Causes of P2166

Most Common Causes

• Sensor signals that do not agree within expected limits (a correlation/plausibility failure), often involving commonly associated airflow, throttle, pedal, or pressure-related inputs depending on vehicle design.
• Connector issues: backed-out terminals, fretting/corrosion, water intrusion, poor pin fit causing intermittent high resistance or dropouts.
• Wiring faults: chafing near brackets, engine movement points, or tight bends causing intermittent opens/shorts to ground/voltage.
• Reference voltage or sensor ground problems (shared 5 V reference or low-reference circuits affecting multiple sensors at once).
• Unmetered air or mechanical airflow issues (vacuum leaks, intake duct leaks) that make measured values disagree, depending on strategy.

Less Common Causes

• Charging system noise or low system voltage causing sensor readings to shift or the PCM to reset plausibility monitors.
• Aftermarket tuning, non-OE sensors, or modified intakes altering expected sensor relationships.
• Signal integrity issues: electromagnetic interference, poor shielding/grounding, or routed wiring too close to ignition components.
• Mechanical engine problems (restricted exhaust, low compression on a cylinder group) creating unexpected airflow/load relationships.
• PCM issue: possible internal processing or input-stage issue, considered only after power/ground and all related signal circuits test good.

Diagnosis: Step-by-Step Guide

Tools you’ll use: a scan tool with live data and freeze-frame access, a Digital Multimeter (DMM), a 2-channel oscilloscope (helpful for correlation), back-probe pins, wiring diagrams/service info, a smoke machine (or propane/enrichment tool) for intake leaks, a basic battery/charging tester, and contact cleaner with dielectric grease.

1. Verify the complaint and record freeze-frame data (RPM, load, coolant temp, vehicle speed). Note when the plausibility monitor ran and failed; this often points to a specific operating window.
2. Check battery and charging health first. Measure key-off battery voltage and running system voltage; excessive ripple or low voltage can skew multiple sensors and trigger correlation faults.
3. Run a full visual inspection: intake ducting, vacuum hoses, harness routing, and connectors for commonly associated sensors on your vehicle. Perform a gentle wiggle test while watching live data for dropouts.
4. On the scan tool, graph the relevant live PIDs (whichever sensor pair/group your service info ties to P2166). Look for disagreement, flat-lines, sudden spikes, or slow response compared to engine changes.
5. Key on/engine off: verify 5 V reference (if used) and sensor ground integrity with the DMM. Load-test grounds with a headlamp bulb or similar load where appropriate; a “good” ground on a meter can fail under load.
6. Check signal circuits for shorts to voltage/ground and for excessive resistance. If the fault is intermittent, flex the harness at suspected rub points while monitoring ohms/voltage.
7. If correlation involves airflow/load plausibility, smoke-test the intake for unmetered air leaks. Any leak downstream of an airflow meter (if equipped) can create implausible relationships.
8. Use an oscilloscope to compare suspect signals under the conditions that set the code (snap throttle, steady cruise simulation). Look for noise, dropouts, and phase/response mismatches.
9. If wiring, power/ground, and mechanical air path test good, substitute known-good sensor inputs only when you can confirm the sensor is the outlier (for example, the signal deviates while the reference and ground remain stable).

Professional tip: Don’t condemn a sensor or PCM from a single “wrong” live-data number—confirm the shared 5 V reference and low-reference stability first, because one corroded splice or loose ground can make multiple sensors disagree and trigger a correlation fault even when the sensors themselves are fine.

Possible Fixes & Repair Costs

Fixes for P2166 should be driven by what you measure, because the exact affected circuit can vary by make/model/year even though the code format follows SAE J2012 conventions. Low cost ($0–$60): clean and reseat connectors, repair minor terminal fit issues, correct pin drag, or restore harness routing after you confirm a poor connection with a wiggle test and a voltage-drop test (power/ground) or by catching signal dropouts on a scan tool graph. Typical ($80–$350): repair/replace damaged wiring, replace a commonly associated sensor only after you verify improper signal plausibility (for example, an out-of-range value that doesn’t match operating conditions) while power, ground, and reference voltage remain stable. High ($350–$1,200+): extended harness repairs, intensive diagnostics time, or a control module replacement only after all external inputs (power, ground, reference, signal integrity) test good and you have evidence of a possible internal processing or input-stage issue.

Costs vary with access, connector type, corrosion severity, and whether the fault is intermittent. Avoid parts-cannon replacement; a five-minute confirmation test can prevent the most expensive mistake.

Can I Still Drive With P2166?

Sometimes you can drive with P2166, but you should treat it as a reliability and drivability risk until you confirm what signal is failing plausibility on your vehicle. If the vehicle enters reduced-power mode, has unstable idle/throttle response, harsh shifting, or stalling, don’t keep driving—those symptoms indicate the control module is no longer trusting a key powertrain input. If it drives normally and the code is history, you may be able to drive short distances while scheduling diagnosis, but monitor for worsening behavior and avoid heavy loads or high-speed merging.

What Happens If You Ignore P2166?

Ignoring P2166 can turn an intermittent plausibility fault into a hard fault: corrosion spreads, a harness rub-through becomes a short, or a marginal sensor drifts further out of range. Over time you may see more frequent limp mode, poor fuel economy, drivability complaints, and possible catalytic converter damage if fueling control is affected on your application.

Last updated: February 13, 2026

Vehicles Commonly Affected by P2166

P2166 is commonly seen across many OBD-II vehicles rather than being limited to one platform, but it’s often reported on manufacturer families with complex sensor plausibility monitoring and tight emissions/drivability strategies. You’ll frequently see it in some Ford, General Motors, Volkswagen/Audi, and Hyundai/Kia applications, especially where multiple sensors are cross-checked for reasonableness. Differences in engine management architecture, connector sealing, and harness routing can influence how often plausibility faults show up and how intermittent they feel.