2002 DODGE DURANGO — Complaint #604971
Open-data reference.
NHTSA Complaint about SUSPENSION:REAR:SPRINGS:LEAF SPRING ASSEMBLY:LEAF filed December 1, 2006
NHTSA complaint #604971 (ODI reference 10174947) concerns a 2002 DODGE DURANGO and was filed on December 1, 2006. The owner reports the failure occurred on November 27, 2006. The report was geocoded to Virginia based on the filer's self-reported location. The affected component is categorized as suspension:rear:springs:leaf spring assembly:leaf, one of NHTSA's standardized taxonomy codes used to group defect patterns across make, model, and year.
The filer flagged the following severity indicators: crash: no, fire: no, injuries: 0, fatalities: 0. No crash, fire, or fatality was associated with this report, which places it in the early-warning stream rather than the priority-review stream. No VIN was supplied by the filer, so this complaint contributes to model-year trend data but cannot be tied to a specific vehicle.
Individual complaints are consumer-submitted and unverified by NHTSA engineers — the agency's role at this stage is to collect, index, and make them searchable. What matters for federal action is the pattern: when many owners of the same DODGE DURANGO cohort independently describe similar suspension:rear:springs:leaf spring assembly:leaf failures, defect investigators have grounds to open a PE and request manufacturer data. Related filings for the same vehicle and component appear below, and the detail page for the full 2002 DODGE DURANGO shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
REAR LEAF SPRING (DRIVER'S SIDE) BROKE OFF FROM THE SHACKLE CAUSING THE VEHICLE TO WANDER TO THE RIGHT! *JB
Complaint Details
| NHTSA Complaint ID | 604971 |
| ODI Number | 10174947 |
| Date Filed | December 1, 2006 |
| Failure Date | November 27, 2006 |
Source: NHTSA Vehicle Complaints Database. Component taxonomy and severity codes are standardized by NHTSA Office of Defects Investigation.
Read our methodology — how this data is sourced, computed, and verified.