P2167 – Throttle/Pedal Position Sensor “E” Maximum Stop Performance

P2167 is a Powertrain (P) diagnostic trouble code that points to a vehicle speed signal plausibility problem as interpreted by the Powertrain Control Module (PCM) or Engine Control Module (ECM). In plain terms, the computer thinks the vehicle speed information it’s receiving (or calculating) doesn’t make sense compared to other data it trusts. SAE J2012 defines the structure of the code, but the exact sensor, data path, and strategy used can vary by make, model, and year—so you confirm it with scan data and basic power/ground/signal integrity tests.

What Does P2167 Mean?

Under SAE J2012-DA wording conventions, P2167 is commonly used for a Vehicle Speed Signal Plausibility type fault—meaning the PCM/ECM detects that the speed signal is not rational when compared against other inputs (for example, engine speed, transmission output, gear ratio, or network-reported speed). Because this is a plausibility/rationality condition, it’s distinct from a simple “voltage high/low” electrical fault: the signal may look electrically “present” yet still be considered wrong or inconsistent.

This guide follows SAE J2012 formatting, and standardized DTC descriptions are published in the SAE J2012-DA digital annex. P2167 is shown without a hyphen suffix, so no Failure Type Byte (FTB) is provided here. If your scan tool shows a suffix (for example, a “-xx” subtype), that FTB would further describe the failure mode (such as a particular plausibility pattern or condition) and can change the exact test path—use it to narrow when and how the fault sets on your specific vehicle.

Quick Reference

• Code type: Powertrain (P-code), plausibility/rationality fault
• System-level meaning: Vehicle speed signal does not correlate with expected values
• Commonly involved: Vehicle speed sensing source, wiring/connectors, network message path, PCM/ECM input processing
• Typical triggers: Erratic/implausible speed reading, dropouts, mismatch versus engine/trans output calculations
• Primary confirmation method: Compare live-data vehicle speed against a known-good reference and other sensor PIDs while checking signal integrity
• Driveability impact: Can affect shifting, cruise control, traction strategies, and speedometer behavior (varies by vehicle)

Real-World Example / Field Notes

In the shop, P2167 often shows up as a “ghost” complaint: the customer reports a momentary harsh shift, cruise canceling, or a speedometer flicker, but the vehicle drives mostly fine. One common pattern is a speed value that briefly drops to zero or spikes while other data (like engine RPM) stays steady. Depending on the vehicle, the speed used by the PCM/ECM may be commonly associated with a transmission output speed sensor, a wheel-speed-derived vehicle speed message over the Controller Area Network (CAN), or an instrument/ABS module-supplied speed signal. The quickest wins usually come from confirming the mismatch with scan tool data during a road test, then finding a connector issue (moisture, fretting, loose terminals) or a harness rub where the signal intermittently degrades under vibration.

Symptoms of P2167

• Check Engine Light: The Malfunction Indicator Lamp (MIL) illuminates after the Powertrain Control Module (PCM) detects an implausible or conflicting sensor signal correlation for more than one drive cycle.
• Reduced power: Noticeable loss of acceleration or a “limp” strategy when the PCM limits torque to protect the engine/transmission because sensor inputs don’t agree.
• Unstable idle: Idle speed hunting, stalling on decel, or rough idle when airflow/fueling calculations are based on a signal that doesn’t match expected values.
• Poor throttle response: Delayed response to pedal input or surging, especially during tip-in, if the PCM can’t reconcile expected load versus actual readings.
• Hard starting: Extended crank or occasional no-start if a key input is out of correlation at crank (varies by make/model/year and strategy).
• Fuel economy drop: Increased fuel consumption as the PCM substitutes default values and enriches mixture to maintain drivability.
• Intermittent behavior: Symptoms that come and go with vibration, moisture, or heat-soak, consistent with connector contact issues or harness movement.

Common Causes of P2167

Most Common Causes

• Connector fretting/corrosion or poor terminal tension at a sensor commonly associated with load, airflow, pressure, or position inputs (exact sensor depends on vehicle calibration)
• Wiring harness damage causing high resistance, intermittent opens, or intermittent shorts to ground/power affecting a 5-volt reference, sensor ground, or signal circuit
• Vacuum/air leak or intake tract issue creating a real-world mismatch between expected airflow/load and sensor feedback (where applicable to the engine design)
• Contamination at a sensor element (oil, dust, water intrusion) causing skewed readings and failed plausibility/correlation checks
• Low system voltage or charging instability shifting sensor reference/signal behavior during cranking or under electrical load

Less Common Causes

• Sensor internal drift or non-linear output that still “works” but no longer tracks within the PCM’s correlation window
• Aftermarket calibration/modified intake components causing expected-versus-actual correlation to fall outside learned limits
• Mechanical engine issue (restricted exhaust, timing-related mechanical fault, or severe misfire) creating legitimate airflow/load disagreement
• Powertrain Control Module (PCM) possible internal processing or input-stage issue, but only after all external power, ground, reference, and signal integrity tests pass

Diagnosis: Step-by-Step Guide

Tools you’ll use: bidirectional scan tool with live data, Digital Multimeter (DMM), oscilloscope (helpful for intermittent dropouts), battery/charging system tester, back-probe pins or breakout leads, smoke machine (or regulated low-pressure leak tester), basic hand tools, and wiring diagrams/service info for your exact make/model/year.

1. Confirm the concern: scan for P2167 and record freeze-frame data (RPM, load, throttle angle, manifold pressure, airflow, battery voltage). This tells you what correlation failed and under what conditions.
2. Verify the code definition for your vehicle: SAE J2012 defines DTC structure and generic wording in the SAE J2012-DA digital annex, but manufacturer implementations vary. Use service information to identify which sensor set is being correlated on your application.
3. Do a quick under-hood inspection: check for loose intake boots, disconnected vacuum lines, damaged harness routing, and oil/water intrusion at connectors.
4. Check battery and charging stability: measure key-off battery voltage and running voltage under load. Low or unstable voltage can cause multiple sensor signals to disagree.
5. On the scan tool, compare live data for the commonly associated inputs (for example, airflow/load/pressure/position signals) at idle and at a steady 2,000 RPM. Look for one value that is erratic, pegged, or implausible compared to the others.
6. Test 5-volt reference and sensor ground at the suspect sensor(s): with key on, measure reference voltage and ground voltage drop. You’re looking for a steady reference and a clean low-drop ground (excess drop suggests resistance in the ground path).
7. Signal integrity test: back-probe the signal wire and check for smooth voltage change with engine running and during a gentle snap throttle. Use a scope if the problem is intermittent; look for dropouts, noise, or flat spots that match the symptom.
8. Wiggle test and load test the circuit: manipulate the harness/connectors while monitoring live data and the meter/scope. Then perform a loaded voltage drop test (using a test light or known load where appropriate) to uncover high resistance that an ohmmeter may miss.
9. If airflow or vacuum plausibility is part of the correlation on your vehicle, perform a smoke test for unmetered air leaks and verify the intake path is sealed and the filter/ducting is not restricted or collapsing.
10. After repairs, clear the code and run a drive cycle that matches the freeze-frame conditions. Confirm the correlation remains stable and P2167 does not reset.

Professional tip: When P2167 is intermittent, prioritize capturing the failure in live data or on a scope while reproducing the freeze-frame conditions—then test power/ground/reference first, because a brief reference or ground dropout can make multiple “good” sensors look wrong at the same time.

Possible Fixes & Repair Costs

Repair costs for P2167 depend on what your test results prove. Keep the diagnosis test-driven: you should only replace parts after confirming power, ground, reference voltage (if used), and signal plausibility under the same conditions that set the code.

• Low ($0–$80): Clean and reseat connectors, correct pin fit issues, repair minor terminal corrosion, secure routing away from heat/chafe points. Justified when a wiggle test or visual inspection changes the signal, resistance, or scan data.
• Typical ($120–$450): Repair/replace a damaged section of harness, replace a commonly associated sensor (vehicle-dependent), or restore a poor ground/voltage feed. Justified when you measure excessive voltage drop on power/ground, intermittent opens/shorts during a load test, or a sensor signal that’s out of plausible range while supplies are correct.
• High ($600–$1,800+): Control module replacement or reconfiguration (Powertrain Control Module (PCM) / Engine Control Module (ECM) depending on vehicle). Only justified after all external wiring, power, grounds, and input signals test good and you can reproduce an incorrect interpreted value or processing behavior.

Labor rates, access difficulty, corrosion severity, and whether the fault is intermittent can swing the final bill. If the code only sets during certain temperature/vibration conditions, expect extra diagnostic time.

Can I Still Drive With P2167?

Sometimes you can, but you shouldn’t assume it’s safe. P2167 is a powertrain sensor circuit signal plausibility fault, meaning the PCM/ECM is seeing a sensor-related signal that doesn’t make sense compared to expected operating conditions. That can trigger reduced power, harsh shifting (if the transmission strategy is affected), or unstable idle depending on the system involved. If the vehicle enters limp mode, stalls, hesitates badly, or the throttle response becomes unpredictable, stop driving and diagnose it.

What Happens If You Ignore P2167?

Ignoring P2167 can turn an intermittent plausibility issue into a no-start, stalling, or reduced-power condition, especially if the underlying cause is a harness rub-through, water intrusion, or a worsening connector problem. Long-term driving with incorrect sensor plausibility can also lead to poor fuel economy, drivability complaints, and potential catalyst or transmission stress if the control strategy compensates incorrectly.

Last updated: February 13, 2026

Vehicles Commonly Affected by P2167

P2167 is commonly seen across multiple makes because plausibility monitoring is built into modern powertrain strategies. It’s often reported on vehicles from Ford, General Motors, Volkswagen/Audi, and some BMW applications, especially where sensor signals are cross-checked against other inputs and operating models. Higher network and sensor complexity (more shared references, more correlated sensors, tighter plausibility thresholds) increases the chance that a small wiring or connection issue triggers this kind of fault.