Consumer Complaint Detail

FORD / RANGER / 2003

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 004314056 Incident Date: Dec, 14 2004
Consumer's City: Consumer's State: NJ
Vehicle Transmission Type: Manufacturers Name: Ford Motor Company
Model Name: RANGER Model Year: 2003
Vehicle Involved in a Crash: No Component's Description: Suspension
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: 1FTZR45E03T Date added to File: May, 25 2021
Date Complaint Received: Dec, 16 2004 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: -
Was Original Owner: Yes Anti-lock Brakes: Yes
Number of Cylinders: 0 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: There is no incident and perhaps this may not be the correct place to file this complaint but you can be the judge of that. my complaint is i own a 2003 ford ranger 4wd super cab with goodyear factory installed tires which are wearing unusually (cupping/chopping). tires have been rotated by ford dealer, balanced, proper air pressure maintained and alignment checked. vehicle has 16,500 miles on it. tires are causing vibration and noise. i believe there is a safety hazard because i can't feel or hear if another component is failing. dealer has told me he sees an average of 6 ford rangers with the same problem each week. ford tells me there is no recall or directive to replace the tires and they will not replace them. goodyear tells me that ford has issued a broadcast service bulletin to its dealers to replace these tires with a larger size. have no access to this bulletin but questioned ford customer service and they said they have no access to broadcast bulletins. ford customer service said this type of tire is not expected to wear normally because of its design. why then put it on the vehicle? conversation with ford was on the phone and i should have written exactly what they said but this is pretty much it. if the dealer is seeing this many vehicles each week there must be a huge problem somewhere. *jb