P2299 Code: Brake and Accelerator Pedal Input Conflict
When a P2299 code appears, the powertrain controller has logged conflicting brake and accelerator pedal inputs. This incompatibility can trigger reduced engine power, warning lights, or unpredictable throttle response. Because the code is a plausibility failure rather than a direct component diagnosis, the actual cause may be a faulty switch, sensor, wiring issue, or even pedal obstruction. Understanding how the vehicle monitors these inputs helps you work safely with a technician toward an accurate repair.
What P2299 Means for Your Vehicle
Before assuming the meaning of P2299, confirm the definition for your exact year, make, model, and powertrain. Some applications label it 'Brake/Accelerator Pedal Position Incompatibility,' while others specify a circuit range or signal plausibility fault. Service information also lists the exact setting criteria: how long the invalid combination must persist, engine load requirements, and whether the brake switch must be closed while the accelerator sensor reports a certain voltage. Without this verification, a generic explanation could send diagnosis down the wrong path.
A controller normally expects brake and accelerator activity to be mutually exclusive during most driving conditions. Pedal-position sensors and brake switches report continuously, allowing the ECM or PCM to cross-check plausibility. If both inputs indicate active operation beyond a brief overlap tolerated for maneuvers like left-foot braking on a grade, the controller flags P2299. This is an interpretation of signals, not proof that a specific part failed. The code simply says the combination is outside the programmed acceptable window.
Symptoms and Decisions About Driving
Depending on the vehicle, a P2299 may trigger a check engine light, a specific message, or a limp mode that cuts throttle response. Some systems reduce engine power to a safe level because they cannot trust the driver's pedal commands. Drivers may notice the engine accelerates slowly, holds lower RPM, or refuses to rev while the brake is applied. Not every vehicle behaves identically; some store the code without immediate drivability changes, so observing what happens after the light appears is an important diagnostic clue.
Note the exact circumstances when symptoms first appear. Does the vehicle hesitate after hard braking, during gentle acceleration, or only when pressing both pedals accidentally? Keep a written record of weather, road conditions, and any recent repairs. Do not attempt to recreate the fault by overlapping pedals, as this could produce unsafe acceleration or braking. If the brake pedal feels stiff, the accelerator sticks, or the vehicle does not respond predictably, stop in a safe location and have the vehicle towed rather than continuing to drive.
Inputs and Conditions That Can Trigger a Conflict
Simultaneous brake and accelerator application is a common trigger for this plausibility fault. Drivers who rest a foot on the brake pedal while accelerating, often without realizing it, can send both signals at once. Worn pedal bushings or a misadjusted brake switch may also cause the brake circuit to remain active during acceleration. The controller's setting criteria define how much overlap is acceptable; exceeding that window even briefly can store the code, especially under specific engine load or vehicle speed conditions.
An inaccurate accelerator pedal position sensor can report voltage that indicates a pressed pedal even when it is released. Likewise, a brake switch that sticks closed or has internal resistance may keep the brake input active. Damaged wiring, corroded connectors, or pinched harnesses can introduce intermittent signals that mimic both pedals being applied. A floor mat wedged under the pedal or a damaged pedal return spring can also hold the physical pedal in a partly applied position. None of these causes can be confirmed by the code alone; each requires targeted testing.
Safe Observations Before a Shop Visit
With the vehicle parked safely, engine off, and ignition key removed, visually inspect the pedal area. Check for loose floor mats, debris, or aftermarket accessories that could obstruct accelerator or brake pedal travel. Press each pedal by hand to feel for unusual stiffness, binding, or failure to return smoothly. Do not use excessive force, and never place your head under the dashboard while testing. Clearing obstructions may prevent an intermittent conflict, but it does not prove that obstruction was the original cause if the code persists.
Brake light behavior can provide a useful clue. With the vehicle stationary, have a helper observe the rear lights while you press and release the brake pedal. If the brake lights stay illuminated without pedal pressure, the switch or circuit may be reporting a false active state. However, the controller may use separate switch contacts for brake lights and input monitoring, so normal light operation does not rule out a switch fault. Write down any recent warning messages, unusual pedal feel, or repairs when the code first appeared to give the technician a complete timeline.
How Professional Testing Finds the Cause
A professional diagnosis begins with recording all stored and pending codes along with freeze-frame data. This snapshot captures engine conditions when the fault set—such as vehicle speed, engine rpm, brake switch state, and accelerator pedal voltage. Clearing codes erases this evidence, so no data should be removed before documentation. Additional brake or accelerator circuit codes may point toward a shared power supply, ground, or communication issue, but their presence does not prove a common cause; each must be investigated individually against the wiring diagram.
Live data is essential for interpreting pedal inputs. A scan tool can display brake switch status, accelerator pedal position percentage, and whether the controller is seeing plausible transitions. Comparing these readings to manufacturer-specified voltages and timing often reveals a sensor that drifts out of range, a switch that remains closed, or a wiring fault that appears only when the harness is flexed. Vehicle-specific service information provides connector pinouts and test procedures. Only after isolating a confirmed defect should a switch, sensor, or harness repair be recommended.
Confirming the Repair and Handling a Returning Code
Clearing a P2299 code removes the warning lamp and stored freeze-frame data, but it does not address the underlying signal problem. If the conflicting input occurs again, the code will return. After any repair—whether replacing a brake switch, repairing a connector, or repositioning a floor mat—the technician should confirm that live brake and accelerator data now match expected states during a road test. Some manufacturers specify a particular drive cycle or relearn procedure for pedal-position sensors, which must be completed before declaring the repair successful.
Intermittent P2299 occurrences are challenging because the fault may not be present during initial testing. If no defect is found, the technician may recommend a data recorder or enhanced scan tool that captures inputs when the code sets. Returning to the shop with updated notes about speed, pedal use, road conditions, and temperature can help direct a more focused diagnosis. If the code or reduced-power symptoms reappear, avoid clearing it yourself; the stored freeze-frame data gives the next diagnostician the best chance of finding the true cause.