OBD-II Code · Chassis
C0051
Steering Wheel Position Sensor Circuit
Severity
medium
Worth booking. It costs fuel, emissions or comfort until it is fixed.
Can you drive it
Only if running normally
A short trip to a shop may be reasonable if the light is steady and the car runs normally. Stop safely for a flashing light, severe shaking, overheating, loss of power, or another urgent warning. The code alone cannot confirm safety.
Indicative cost (USD)
$150–$400
Varies by vehicle, diagnosis, parts, and local labor. This is not a repair quote.
RR WSS range.
How a shop works this
Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed.
Note every code that is set, not just this one.
Codes that appear together usually narrow the cause faster than any one of them read alone.
Read the freeze frame — the conditions the fault was recorded under.
Cold or warm, idle or load, road speed and engine speed. A fault that only appears cold is a different fault from one that only appears under load, even with the same code on the scanner.
Confirm the fault is current rather than history.
Clear the code and see whether it returns under those same conditions. A code that does not come back may have been logged during a repair, a flat battery, or a bad connection that has since been disturbed.
Then work the likely-causes list in the order shown.
That order is what a shop checks first for this code — wiring and connections before the component they run to, because a connector costs nothing to inspect and is a common answer.
If the code comes back after a repair, the underlying fault is still there. That is the point to bring in a scanner with live data and freeze-frame, or a shop that has one.
Common symptoms
- ABS light
Likely causes
- Failing sensorMost common
- Tone ring
Read the full diagnostic procedureC0051 is a fault in the steering wheel angle sensor (SAS) circuit — the stability/traction control module is not receiving a valid steering angle sig…
C0051 is a fault in the steering wheel angle sensor (SAS) circuit — the stability/traction control module is not receiving a valid steering angle signal from the clockspring-mounted sensor or the SAS is reporting out-of-range data. The SAS is critical to stability control because the module uses it to compare driver intent (steering input) against vehicle behavior (yaw rate from the yaw sensor); without a valid signal the system has no idea whether you're trying to turn or whether the vehicle is sliding.
Cheapest-first ladder
- Scan for related codes — C0051 alone is one diagnosis, but C0051 with a yaw-sensor code or a network/communication U-code is a different problem entirely (often a steering-column bus connector issue, not a sensor failure).
- Live-data the SAS with the wheel pointing straight ahead — expect 0 +/- 5 degrees on a calibrated system. Most SAS units scale 0-720 degrees of total wheel travel (two full turns lock-to-lock on either side of center), and an uncalibrated or failed sensor reports either a fixed value, jumps non-linearly with rotation, or stays at 0 no matter where the wheel is pointed.
- Center-position check: drive the vehicle straight on a level road, then read the SAS — anything more than 5 degrees off zero with the steering wheel visually centered is either a sensor calibration issue (recalibrate via scan tool) or a mechanical alignment problem (toe adjustment off, wheel position wrong on the column).
- Inspect the clockspring connector at the top of the steering column — most C0051 faults in 10+ year-old vehicles trace to a corroded or partially-disconnected SAS pigtail at the clockspring rather than a failed sensor element. Expensive-misdiagnosis caveat: any vehicle whose airbag clockspring has been replaced or whose steering column has been pulled for service — the SAS almost always loses its center-zero memory during the service and MUST be recalibrated through a scan tool's chassis-relearn or steering-angle-reset routine, or the code will set immediately and a perfectly good sensor will look defective.
Vehicle-specific patternsany vehicle with stability control after airbag clockspring service requires an SAS recalibration — failing to do this is the single most common caus…
any vehicle with stability control after airbag clockspring service requires an SAS recalibration — failing to do this is the single most common cause of C0051 in independent-shop work.
- 2005-2012Toyota/Lexus (Camry, RAV4, Highlander, IS, GX, LX) use a clockspring-integrated SAS that scales 1-2.5V across its range; the recalibration routine is a Techstream/aftermarket-scan-tool drive-cycle with the wheel cycled lock-to-lock-to-center.
- 2006-2013BMW E-series (E60 5-series, E90 3-series, E70 X5) use an FLA-series steering-angle sensor that fails internally around 100k miles; the symptom is a stuck reading regardless of wheel position, and ISTA must be used to code in the replacement part.
- 1999-2007GM trucks (Silverado/Sierra/Tahoe) throw C0051 after tie-rod or steering-rack replacement when the SAS was not recalibrated — Tech 2 or GDS2 'steering angle sensor learn' procedure clears it without parts.
- 2008-2014Dodge Caravan/Chrysler 200 throws C0051 from a failed clockspring assembly that takes the SAS with it; the only fix is the combined $250-$450 part.
Estimated repair$0 (recalibration only) to $650.
Look up another code
C0051 — frequently asked
What does a C0051 code mean?
RR WSS range.
What causes a C0051 code?
Common causes: Failing sensor; Tone ring.
What are the symptoms of a C0051 code?
Typical symptoms: ABS light.
Is it safe to drive with a C0051 code?
Only if running normally. A short trip to a shop may be reasonable if the light is steady and the car runs normally. Stop safely for a flashing light, severe shaking, overheating, loss of power, or another urgent warning. The code alone cannot confirm safety. Estimated repair: $150-$400.
How do I diagnose a C0051 code?
Work from evidence to part, not the other way round. A code names a circuit or a symptom; it does not name the part that failed. 1. Note every code that is set, not just this one. 2. Read the freeze frame — the conditions the fault was recorded under. 3. Confirm the fault is current rather than history. 4. Then work the likely-causes list in the order shown.
More free tools