Consumer Complaint Detail
PLYMOUTH / GRAND VOYAGER / 1997

0 Injured

0 Death

No Fire
Components - Details | |
---|---|
NHTSA Complaint Number: 003295039 | Incident Date: Sep, 30 2003 |
Consumer's City: HAMPSTEAD | Consumer's State: NC |
Vehicle Transmission Type: AUTO | Manufacturers Name: Chrysler (FCA US, LLC) |
Model Name: GRAND VOYAGER | Model Year: 1997 |
Vehicle Involved in a Crash: No | Component's Description: Service brakes, hydraulic:antilock/traction control/electronic limited slip |
Vehicle Involved in a Fire: No | Persons Injured: 0 |
Vehicle's VIN#: 2P4GP44R9VR | Date added to File: May, 25 2021 |
Date Complaint Received: Aug, 21 2004 | Complaint Type: IVOQ |
Incident Reported To Police: No | Purchase Date: Dec, 27 2002 |
Was Original Owner: No | Anti-lock Brakes: Yes |
Number of Cylinders: 6 | Date of Manufacturer: - |
Was Vehicle Towed: - | Description of the Complaints: Vin #p4gp44r9vr169548 '97 plymouth grand voyager this vehicle has been to both d & e dodge in wilmington, nc and to national dodge in jacksonville, nc for repairs to the brakes, and the brakes still do not work. the brake system fluid, drums, rotars, master cylinder - everything seems to be ok, they say, when we pick it up, but, when you apply the brakes, brakes are "spongy" and sometimes there are no brakes at all. it seems pretty fair for a short period of time and then becomes increasingly worse. this has been appearing for approximately one year. please recommend someone in the chrysler organization that can fix the brakes on this vehicle. it is very dangerous, and we are tired of this problem. i am afraid my family is going to be killed and perhaps kill someone else, too. the car has an extended warranty purchased at the time the car was resold to us, which the dealerships say does not cover the brake system. however, it does cover at least some part of the brake system. the thing is, we have paid out money for its repair and have had to do without the car for days at a time and still have a braking system that is not working properly. there is something going on that is definitely a "safety-related defect" that no one can find as yet. *jb |