1997 CHRYSLER CONCORDE — Complaint #302574
Open-data reference.
NHTSA Complaint about SUSPENSION:MULTIPLE AXLE:TORQUE ARM filed July 11, 2001
NHTSA complaint #302574 (ODI reference 892476) concerns a 1997 CHRYSLER CONCORDE and was filed on July 11, 2001. The owner reports the failure occurred on July 8, 2001. The report was geocoded to Pennsylvania based on the filer's self-reported location. The affected component is categorized as suspension:multiple axle:torque arm, 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. Because a VIN was supplied, this complaint is tied to a specific vehicle and not just a model-year cohort.
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 CHRYSLER CONCORDE cohort independently describe similar suspension:multiple axle:torque arm 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 1997 CHRYSLER CONCORDE shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
WHILE DRIVING 60 TO 65 MPH CONSUMER HEARD A CLANKING NOISE . LEFT REAR CONTROL ARM BROKE. CONSUMER ALSO STATED HAD IT WELDED BACK ON. CONTACTED DEALER.*AK *SLC
Complaint Details
| NHTSA Complaint ID | 302574 |
| ODI Number | 892476 |
| Date Filed | July 11, 2001 |
| Failure Date | July 8, 2001 |
| VIN | 2C3HD56F8VH |
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.