Consumer Complaint Detail

PONTIAC / SUNFIRE / 2002

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 004101581 Incident Date: Jul, 31 2004
Consumer's City: SCHOHARIE Consumer's State: NY
Vehicle Transmission Type: AUTO Manufacturers Name: General Motors, LLC
Model Name: SUNFIRE Model Year: 2002
Vehicle Involved in a Crash: No Component's Description: Visibility:defroster/defogger/hvac system:fan/motor
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: Date added to File: May, 23 2021
Date Complaint Received: Apr, 08 2007 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: Jul, 19 2002
Was Original Owner: No Anti-lock Brakes: Yes
Number of Cylinders: 4 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: Checked out this site before i decided to post this and saw someone else complaining about it, and frankly, i really thought i would find more people with the complaint. i bought the 2002 pontiac sunfire with 22000 miles on it. upon purchase i noticed that out of the 5 settings for the blowers the first one didn't work. honestly, i didn't care that much at that point- all the others worked, so no biggie. through out the past couple of years, slowly one by one all the others stopped working too, except the highest blower. basically, i was either on high or not one at all. still, at this point, i could not complain that much. but when i mentioned the problem to both my mother and a friend they both had the same problem. my mom's car, a grand am, was down to 3 settings, and my friends vehicle, a pontiac, was on the last setting too. when this winter began i figured i should break down and get it looked at. the nice man at the pontiac dealership informed me it was going to be a good chunk of change to fix the problem, though he opted against telling me what exacally the problem is, and i neglected to ask. but after hearing other complains i started to wonder if it was a pontiac thing. and though it may not be considered a 'safty' issue, if not fixed it probably could become one. *ak