Consumer Complaint Detail

DODGE / DURANGO / 2005

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 006065193 Incident Date: May, 11 2006
Consumer's City: WASHINGTON Consumer's State: DC
Vehicle Transmission Type: AUTO Manufacturers Name: Chrysler (FCA US, LLC)
Model Name: DURANGO Model Year: 2005
Vehicle Involved in a Crash: No Component's Description: Engine and engine cooling:engine:gasoline
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: 1D8HB48N75F Date added to File: May, 23 2021
Date Complaint Received: May, 12 2006 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: Aug, 20 2005
Was Original Owner: No Anti-lock Brakes: Yes
Number of Cylinders: 8 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: On several occasions, my wife's 2005 dodge durango (4.7 liter 8 cylinder - non-hemi) suv has stalled in the middle of traffic. the problem has occurred on several occasions and the vehicle has been brought to the dealer for servicing and this problem has been expressly noted. the service manager maintains he knows nothing about a problem and he can find nothing wrong with the vehicle. just yesterday, the vehicle stalled in the middle of a busy washington, dc intersection and my wife was almost broadsided as a result. this is a huge problem and chrysler (at least this dealer - tysons dodge jeep) does not seem to care one bit about it. the vehicle was purchased new and now has approximately 8,000 miles. i understand there is an active investigation into the problem and my question is: what is it going to take for someone to take corrective action? are lives going to have to be lost? it appears that chrysler is well aware of the situation and is choosing to close its eyes to the problem. nhtsa should not allow this to happen. too much is at risk and chrysler is making a great deal of money off of these vehicles. we paid well over $30k for this vehicle. please provide any suggestions that you may have for fixing this problem. *nm