P2105 – Throttle Actuator Control System Forced Engine Shutdown

P2105 is a Powertrain Diagnostic Trouble Code (DTC) that points to a problem with how the engine’s throttle actuation system is being commanded and how that command correlates with what the control system expects to happen. Under SAE J2012 structure, this is a powertrain control-related fault, but the exact component-level meaning can vary by make, model, and year. Before you assume a bad part, confirm the basics: stable battery voltage, clean power and ground to the control unit, and a reliable throttle command/feedback signal path.

What Does P2105 Mean?

SAE J2012 defines how DTCs are formatted and categorized, and standardized DTC descriptions are published in the SAE J2012-DA digital annex. For P2105, the system-level takeaway is that the vehicle has detected an abnormal condition involving throttle actuation command correlation or management, not necessarily a single failed component.

This code is shown without a hyphen suffix, meaning no Failure Type Byte (FTB) is provided here. If an FTB were present (for example, “-xx”), it would act as a subtype that further describes the failure mode the module detected (such as an electrical characteristic or plausibility issue). Without an FTB, you must rely on scan data, freeze-frame, and electrical testing to determine the specific failure mode on your vehicle.

Quick Reference

• Code: P2105
• System: Powertrain (throttle actuation management/correlation)
• What it usually means: The control system doesn’t like the relationship between throttle command and expected throttle actuation behavior
• Common driver complaint: Reduced power/limited throttle response
• Most common root areas: Power/ground integrity, connector/wiring issues, throttle command/feedback plausibility
• First checks: Battery/charging voltage under load, module grounds, harness routing near throttle body, scan tool data plausibility

Real-World Example / Field Notes

In the bay, P2105 often shows up after a low-voltage event (weak battery, jump start, or charging issue) or after work near the intake where the throttle body harness gets tugged. One common pattern is intermittent reduced power that disappears after a key cycle, then returns when vibration or heat increases under the hood. Another pattern is a clean-running engine at idle but limited throttle response on tip-in, where scan data shows the throttle command and feedback are not tracking the way the control logic expects. The fix is frequently found by proving power/ground integrity and verifying signal plausibility at the connectors before considering any part replacement.

Symptoms of P2105

• Reduced power: Noticeably limited acceleration, especially on tip-in.
• Limp mode: The vehicle may feel “stuck” at a low throttle opening and won’t respond normally to the pedal.
• High idle: Idle speed may be higher than normal depending on how the control system fails safe.
• Stalling: Engine may stall coming to a stop or when the throttle closes unexpectedly.
• Poor throttle response: Delayed, inconsistent, or “dead” accelerator pedal feel.
• Warning lamp: Malfunction Indicator Lamp (MIL) on; some vehicles also display an electronic throttle/traction message.
• Intermittent drivability: Symptoms may come and go with vibration, moisture, or heat soak.

Common Causes of P2105

Most Common Causes

• Electronic throttle control is intentionally inhibited by the Powertrain Control Module (PCM) due to a detected fault in a related input, plausibility, or safety monitor (varies by make/model/year).
• Low system voltage or unstable charging voltage causing the throttle control system to be disabled as a protective action.
• Poor power or ground integrity to the PCM and/or throttle actuator control circuits (voltage drop under load).
• Connector issues (backed-out terminals, corrosion, water intrusion) at the throttle body, accelerator pedal sensors, or PCM (exact devices vary by application).
• Harness damage near common rub points leading to intermittent signal loss or noise.

Less Common Causes

• Throttle body contamination or mechanical binding that triggers a safety response (confirm with commanded vs actual movement checks).
• Intermittent internal fault in the throttle actuator motor or dual position sensors (confirm with scan data and signal testing).
• Accelerator Pedal Position (APP) sensor signal correlation issue (confirm with dual-track voltage behavior and plausibility).
• Network Communication (CAN) disturbance causing the PCM to inhibit throttle control (confirm with UDS scan health, bus voltages, and message plausibility).
• Possible internal processing or input-stage issue in the PCM only after external power/ground, wiring, and sensor signals test good.

Diagnosis: Step-by-Step Guide

Tools you’ll want: scan tool with live data and bi-directional controls, digital multimeter (DMM), back-probing pins or piercing probes, wiring diagram/service information, battery/charging system tester (or DMM with min/max), basic hand tools for intake access, contact cleaner/dielectric grease, and (if available) an oscilloscope for signal integrity checks.

1. Confirm the customer complaint and capture freeze-frame data. Note battery voltage, engine load, throttle angle (commanded vs actual), and accelerator pedal position data at the time the fault set.
2. Verify the code is shown without a hyphen suffix (no Failure Type Byte). If your scan tool displays a suffix on some platforms, treat it as a subtype that refines the failure mode, but keep the base P2105 meaning separate.
3. Check battery condition and charging voltage first. Measure key-off voltage and running voltage; use min/max to catch drops. If voltage is unstable, correct that before chasing throttle faults.
4. Perform a visual inspection of the throttle body connector, harness routing, and any nearby grounds. Look for oil saturation, broken locks, corrosion, and rubbed-through insulation.
5. With key on, back-probe power and ground at the throttle actuator/related circuits (vehicle-specific). Use voltage-drop testing under load (command an actuator test if available) to confirm solid power and ground integrity.
6. Check accelerator pedal dual-track signals for smooth, linear change and correct correlation. Use a DMM or scope to look for dropouts, noise, or flat spots while slowly pressing the pedal.
7. Compare commanded throttle angle to actual throttle angle on live data. A large mismatch suggests a control inhibit event or a mechanical/electrical limitation; don’t assume a bad throttle body without confirming inputs and supply.
8. If your scan tool supports it, run an actuator sweep/ETC function test. Listen for binding and watch for consistent movement; stop if the throttle behaves erratically or the test aborts.
9. Check for communication health and plausibility. Verify the scan tool maintains stable communication and inspect CAN bus voltages at the diagnostic connector if network issues are suspected.
10. After any repair, clear the code and perform a drive cycle that recreates the original conditions while monitoring voltage, APP correlation, and throttle commanded/actual values to confirm the inhibit condition does not return.

Professional tip: Treat P2105 as a “system inhibit” result, not a parts verdict—prove stable battery/charging voltage and low voltage-drop on PCM/throttle powers and grounds first, then verify APP and throttle position signals are smooth and correlated before condemning the throttle body or considering a possible PCM input-stage issue.

Possible Fixes & Repair Costs

Repairs for P2105 should be based on what you can prove with voltage, ground, and signal checks in the throttle actuation control system rather than replacing parts on a hunch. Low cost ($0–$80) covers cleaning and securing connectors, repairing minor harness chafing, restoring terminal tension, and correcting loose battery/engine grounds—justified when you find voltage drop, corrosion, or an intermittent wiggle-test reaction. Typical cost ($120–$450) often includes replacing a damaged throttle body pigtail/connector, repairing a harness section, or servicing a sticking throttle plate—justified only after you confirm power/ground integrity but see unstable command/feedback correlation or a mechanical bind during inspection.

High cost ($500–$1,500+) can apply when testing points to a control-module-side issue (Powertrain Control Module (PCM) / Engine Control Module (ECM) depending on vehicle) or a network/power distribution problem that requires deeper diagnostics. This should be considered only after all external wiring, powers, grounds, and actuator/sensor circuits test good and the inhibit behavior can be reproduced with verified inputs. Cost varies widely with access, parts availability, whether programming is required by the manufacturer, and how much time is needed to pinpoint an intermittent fault.

Can I Still Drive With P2105?

Sometimes you can limp the vehicle to a safe place, but you shouldn’t assume it’s “okay to drive.” P2105 is typically associated with the vehicle intentionally limiting throttle response to protect the powertrain when the control system sees a condition it can’t trust. That can mean reduced power, limited RPM, or delayed throttle response—situations that can be dangerous in traffic or when merging. If you notice poor response, stalling, or sudden power reduction, stop driving and diagnose it.

What Happens If You Ignore P2105?

Ignoring P2105 can lead to repeated reduced-power events, unpredictable throttle response, and additional stress on wiring/connectors from heat and vibration if the root cause is an intermittent connection. In some cases, the condition that triggered the inhibit can worsen until the vehicle won’t accelerate normally or may stall, increasing the risk of a hazardous situation.

Last updated: February 13, 2026

Vehicles Commonly Affected by P2105

P2105 is commonly seen on vehicles using electronic throttle control, and it’s often reported on some Ford and GM applications, as well as various European turbocharged platforms. The reason isn’t that one brand is “bad,” but that modern throttle actuation depends on multiple inputs (pedal sensors, throttle position feedback, torque management) and stable power/ground and network behavior. The more complex the architecture and the hotter the engine bay environment, the more likely an intermittent connection or plausibility issue can trigger an inhibit event.