Consumer Complaint Detail
DODGE / SPORT UTILITY / 1994
0 Injured
0 Death
No Fire
| Components - Details | |
|---|---|
| NHTSA Complaint Number: 007117392 | Incident Date: May, 30 2007 |
| Consumer's City: GRANBY | Consumer's State: CT |
| Vehicle Transmission Type: AUTO | Manufacturers Name: Chrysler (FCA US, LLC) |
| Model Name: SPORT UTILITY | Model Year: 1994 |
| Vehicle Involved in a Crash: Yes | Component's Description: Steering |
| Vehicle Involved in a Fire: No | Persons Injured: 0 |
| Vehicle's VIN#: 1J4GL48K42W | Date added to File: May, 23 2021 |
| Date Complaint Received: Aug, 28 2007 | Complaint Type: IVOQ |
| Incident Reported To Police: Yes | Purchase Date: Jan, 09 2006 |
| Was Original Owner: No | Anti-lock Brakes: Yes |
| Number of Cylinders: 6 | Date of Manufacturer: - |
| Was Vehicle Towed: - | Description of the Complaints: In november of 2006, i had a recall fixed for the "front:control arm:lower ball joint" when the parts became available. i brought the car back 3 days later having issues with the steering and hearing a noise. the dealership took the car for a few days and did a complete inspection and assured me the new parts were sufficient. every now and then (not constant, but scarcely) when i would turn the wheel just a little, the car would turn as if i had turned my wheel all the way. it scared me a few times, but it didn't happen often at all, so i didn't think much of it. on may 31, 2007, i was merging onto i-91 in connecticut driving only 22 miles per hour, and my car did that very thing. i went up and over the curb, up the embankment and crashed into a steel connecticut state sign. if it wasn't for the sign, i would have continued to lose control and possibly been killed. hitting the sign swung my back end around, where i rolled down the embankment and to a complete stop on the side of the highway. my car sustained over $7,000 worth of damage and has damaged my perfect driving record. no other car was involved and no one was hurt, including myself. i was very fortunate, but i feel there needs to be further investigation into the previous recall and possibly a new recall should be posted to eliminate this problem. the problem still exists despite the recall from last year. *jb |