2005 SAAB 9-3 — Complaint #626255
Open-data reference.
NHTSA Complaint about SERVICE BRAKES, AIR:DISC:PADS filed June 4, 2007
NHTSA complaint #626255 (ODI reference 10192442) concerns a 2005 SAAB 9-3 and was filed on June 4, 2007. The owner reports the failure occurred on May 29, 2007. The report was geocoded to Georgia based on the filer's self-reported location. The affected component is categorized as service brakes, air:disc:pads, one of NHTSA's standardized taxonomy codes used to group defect patterns across make, model, and year.
The filer flagged the following severity indicators: crash: no, fire: no, injuries: 0, fatalities: 0. No crash, fire, or fatality was associated with this report, which places it in the early-warning stream rather than the priority-review stream. Because a VIN was supplied, this complaint is tied to a specific vehicle and not just a model-year cohort.
Individual complaints are consumer-submitted and unverified by NHTSA engineers — the agency's role at this stage is to collect, index, and make them searchable. What matters for federal action is the pattern: when many owners of the same SAAB 9-3 cohort independently describe similar service brakes, air:disc:pads failures, defect investigators have grounds to open a PE and request manufacturer data. Related filings for the same vehicle and component appear below, and the detail page for the full 2005 SAAB 9-3 shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
ROUTINE MAINTENANCE OF 2005 SAAB 9-3 WITH 23,000 MILES REVEALED "FRONT AND REAR BRAKE PADS AND ROTORS NEEDED TO BE REPLACED. WORN BELOW LIMITS." *TR
Complaint Details
| NHTSA Complaint ID | 626255 |
| ODI Number | 10192442 |
| Date Filed | June 4, 2007 |
| Failure Date | May 29, 2007 |
| VIN | YS3FB79N256 |
Similar SERVICE BRAKES, AIR:DISC:PADS Complaints for 2005 SAAB 9-3
Source: NHTSA Vehicle Complaints Database. Component taxonomy and severity codes are standardized by NHTSA Office of Defects Investigation.
Read our methodology — how this data is sourced, computed, and verified.