Consumer Complaint Detail

PLYMOUTH / GRAND VOYAGER / 1998

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 005026969 Incident Date: Jun, 30 2005
Consumer's City: DUBLIN Consumer's State: OH
Vehicle Transmission Type: AUTO Manufacturers Name: Chrysler (FCA US, LLC)
Model Name: GRAND VOYAGER Model Year: 1998
Vehicle Involved in a Crash: No Component's Description: Engine and engine cooling
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: 2P4GP4434WR Date added to File: May, 23 2021
Date Complaint Received: Jun, 30 2005 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: Jan, 31 2001
Was Original Owner: No Anti-lock Brakes: Yes
Number of Cylinders: 4 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: The serpentine belt comes off this vehicle, leading to a sudden loss of power steering. so far, this has happened while on the entrance ramp to a freeway, while driing in light city traffic, and while idling at a bank (prior to taking a highway trip which had to be cancelled). in all cases the driver was female and had great difficulty controlling the vehicle. in all cases this was during wet weather. after the second case, we had the deale install a guide plate that is supposed to keep the belt on, but it came off anyway. we have now learned that there appears to be a defect in the mounting bracket for the power steering pump, leading this part to bend under normal wear and tear such that the serpentine belt will jump off in wet weather. in our vehicle, there was another with the exact same problem in at the same time, and the replacement part was on backorder with 18 customers waiting. this clearly seems to be a design flaw as this vehicle is becoming notorious for this problem among mechanics, with several discussion theads to be found on the internet. it is only a matter of time before someone loses power steering at a critical time, thereby losing cotrol of the vehicle and leading to a fatal accident. indeed, i would be surprsied if this hasn't already ahppened. a recall must be issued for this problem.