P0500 - Vehicle Speed Sensor Malfunction
P0500 is a vehicle speed or idle control fault. Separate sensor data, airflow leaks, throttle/IAC behavior, and load inputs before replacing parts.
Code first. Confirm symptoms and checks before pricing parts.
Explore Related Systems
Compare nearby repair families.
Common Next Steps
Turn the code into the next check.
Compare trims at idle, 2500 RPM, and cruise before pricing sensors.
Check intake boots, PCV hoses, and post-MAF leak paths.
Inspect MAF contamination and airflow data after intake leaks are considered.
Look for cracked ducts, loose clamps, and unmetered air after the MAF.
Related Inspection
Code Overview
P0500 is a vehicle speed or idle control fault. Separate sensor data, airflow leaks, throttle/IAC behavior, and load inputs before replacing parts.
Common Causes
- Dirty throttle body, sticking throttle plate, or idle air control valve issue
- Vacuum leak, PCV leak, brake-booster leak, or intake gasket leak
- MAF data error, throttle position error, or idle relearn issue
- Electrical load, charging voltage, or A/C request affecting idle control
- Vehicle speed sensor or wheel speed data fault where idle or shift strategy is affected
Symptoms
- High idle
- Low idle or stalling
- Speedometer dropout for VSS faults
- Harsh or delayed shifts on some vehicles
- Rough idle when loads are applied
Diagnostic Steps
- Check for air leaks and fuel trims before replacing idle or throttle components
- Inspect throttle body deposits, cable binding where applicable, and idle air passages
- Verify commanded idle versus actual idle with A/C, steering, and electrical loads applied
- Perform throttle or idle relearn only after mechanical and air-leak issues are corrected
- For speed sensor faults, compare scan-tool vehicle speed to wheel speed and instrument cluster behavior
- Verify repair with hot idle in park/drive, decel to stop, A/C load, and road test
Repair Difficulty
Moderate
General difficulty estimate for the most common repair path.
Related OBD Codes
Browse nearby codes when systems overlap.
Next Steps
Move from code to checks, then estimate.