1994 MAZDA 626 — Complaint #416119
Open-data reference.
NHTSA Complaint about SUSPENSION:FRONT:SPRINGS:LEAF SPRING ASSEMBLY:LEAF filed July 3, 2003
NHTSA complaint #416119 (ODI reference 10026556) concerns a 1994 MAZDA 626 and was filed on July 3, 2003. The owner reports the failure occurred on June 27, 2003. The report was geocoded to Illinois based on the filer's self-reported location. The affected component is categorized as suspension:front:springs:leaf spring assembly:leaf, 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. No VIN was supplied by the filer, so this complaint contributes to model-year trend data but cannot be tied to a specific vehicle.
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 MAZDA 626 cohort independently describe similar suspension:front:springs:leaf spring assembly:leaf 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 1994 MAZDA 626 shows the complete component-level complaint distribution alongside any active investigations or recalls.
Complaint Description
CONSUMER STATED THAT WHEN VEHICLE WAS PARKED THE SPRING SNAPPED, PUNCTURING THE FRONT DRIVER'S SIDE TIRE. DEALER WILL BE NOTIFIED. *AK
Complaint Details
| NHTSA Complaint ID | 416119 |
| ODI Number | 10026556 |
| Date Filed | July 3, 2003 |
| Failure Date | June 27, 2003 |
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.