There are 2 stored owner reports matching the suspension leading-label group for the 2003 Mazda MPV in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)TL* THE CONTACT OWNS A 2003 MAZDA MPV. THE CONTACT STATED THAT THE ENGINE WAS MISFIRING DUE TO A COIL SPRING FRACTURE THAT RANDOMLY OCCURRED SEVERAL TIMES. THE CONTACT STATED THAT THE PREVIOUS OWNER HAD TO REPLACE FOUR COIL SPRINGS THAT PREMATURELY FRACTURED. THE CONTACT LATER OWNED THE VEHICLE IN MID APRIL 2015 AND ALSO HAD TO REPLACE TWO COIL SPRINGS THAT FRACTURED PREMATURELY. THE DEALER ALSO REPLACED A GASKET COVER. IN ADDITION, THE DEALER DIAGNOSED THAT THE CATALYTIC CONVERTER NEEDED TO BE REPLACED DUE TO THE FAILURE. THE MANUFACTURER WAS NOTIFIED OF THE FAILURE AND PROVIDED NO PERMANENT SOLUTION. THA MANUFACTURER INDICATED THAT THE CATALYTIC CONVERTER WAS ON BACK ORDER SO THE CONTACT WAS UNABLE TO DETERMINE WHEN THE VEHICLE WOULD BE REPAIRED. THE FAILURE MILEAGE WAS NOT AVAILABLE.
BAD VIBRATION CAUSED BY THE FRONT BRAKE ROTORS BEING OUT OF ROUND. DEALER RESURFACED ROTORS TWO TIMES AND NOW NEEDS RESURFACING A THIRD TIME. THE MPV ONLY HAS 31,000 MILES ON IT. THE DEALER WILL NOT REPLACE UNDER WARRANTY. THIS SHOULD NOT HAPPEN AT APPROXIMATELY EVERY 10,000 MILES. IT IS A 2003 PURCHASED NEW IN 2004. THE TIRES ARE WEARING IN THE FRONT DUE TO THE ALIGNMENT TO THE POINT OF NEEDING REPLACED. THE ALIGNMENT SHOULD NOT OF GONE BAD IN THIS SHORT OF TIME. *JB
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: Apr 28, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.