AtWhatMileage
Suspension · 79 owner reports

Other suspension problem on the 2002 Mercury Sable

1 fire 1 injury 2 of the 79 reports for this failure mention a crash, a fire, an injury or a death. Those are the owner's words on the complaint form, not a verified finding, and one report can mention more than one.

Reports of this failure 79
With an odometer reading 75
Reports per 1,000 built 0.7 per 1,000
Filed below 36,000 miles 1%
Mention a crash, fire or injury 2
Typical repair $350–$2,000
What it means when it happens Moderate
Rank among this year's problems 2nd

When other suspension problem gets reported

Owners of the 2002 Mercury Sable report other suspension problem at a median of 82,500 miles. A quarter of the reports come in before 67,500 miles and a quarter after 97,500 miles, from 75 reports that carried an odometer reading.

A part like this is normally expected to survive 100,000 miles. It is the 2nd most-reported problem on this model year.

The mileage distribution

The reported range runs from 57,500 miles at the tenth percentile to 112,500 miles at the ninetieth, a spread of 55,428 miles across the middle 80% of reports.

A window that narrow is the signature of a part that fails on its own schedule rather than on how the car is driven — which is usually a design or supplier problem rather than wear and tear.

1% of the dated reports were filed under 36,000 miles.

The whole distribution

Percentiles of the 75 odometer readings owners gave.
10th25thMedian 75th90th
56,510 miles 67,264 miles 83,736 miles 97,975 miles 111,938 miles

Read the 10th percentile as “one report in ten arrived this early”. Exact figures are shown in this table because it is the table of record; everywhere else on the site they are rounded to the precision the sample can carry.

What a percentile can and cannot tell you here

These five numbers describe the readings owners gave, in order. The median is the middle one: half the reports arrived below it. The 10th and 90th are the edges of the bulk of the distribution, and the distance between them is the part worth reading. A tight spread — say 70,000 to 95,000 miles — points at something that wears out on a schedule, and the schedule is knowable. A wide one, 20,000 to 190,000, points at a fault that hits some cars and never troubles others, which means the mileage on the listing in front of you tells you very little about your odds.

What these figures are not is a survival curve. Every reading here comes from a car whose owner filed a complaint, so the sample contains only failures: it cannot say what share of the fleet made it past 150,000 miles untouched, because those owners had nothing to report. Nor is the mileage the moment of failure — it is the odometer reading as recalled at the time of filing, which may be weeks later and is sometimes rounded to the nearest ten thousand by the person typing it.

Percentiles are shown at all only once 8 readings exist for the vehicle and mode. Below that the middle of a handful of numbers is noise wearing a decimal point, so the figures are withheld rather than dressed up.

What happens, and what it costs

Of these reports, 1 a fire and 1 an injury are mentioned. Owners write their own complaints and the agency does not verify them, so read this as what the reports say happened rather than as a confirmed count.

Putting it right typically runs $350–$2,000 at an independent US shop. That range is an editorial estimate held in this site's failure-mode catalogue, not a figure from NHTSA, and it is a repair cost rather than a diagnosis cost.

The same failure on other years

The same failure is reported on 8 model years of this car. It shows up earliest on the 2009, at a median of 35,000 miles, and latest on the 2003 at 85,000 miles.

By volume the 2001 carries the most reports, with 98; the 2002 has 79. A mode that appears across most years of a model is usually a design choice rather than a bad batch.

If one year stands out to the left, that is the year to avoid; if the whole line sits at a similar mileage, this is wear rather than a defect in one production run.

Median
  1. 1996 Mercury Sable other suspension problem
    no odometer readings given
    —
  2. 1997 Mercury Sable other suspension problem 79k
  3. 1998 Mercury Sable other suspension problem 73k
  4. 1999 Mercury Sable other suspension problem 68k
  5. 2000 Mercury Sable other suspension problem 81k
  6. 2001 Mercury Sable other suspension problem 80k
  7. 2002 (this one) 84k
  8. 2003 Mercury Sable other suspension problem 85k
  9. 2004 Mercury Sable other suspension problem 140k
  10. 2005 Mercury Sable other suspension problem
    no odometer readings given
    —
  11. 2008 Mercury Sable other suspension problem
    no odometer readings given
    —
  12. 2009 Mercury Sable other suspension problem 34k

Tick median reported mileage Solid middle half of reports Faint 10th to 90th percentile Colour how bad the failure is when it happens

What owners wrote

Verbatim from NHTSA complaint narratives, trimmed for length. The mileage is the one the owner gave.

Dt: I am ware of a recall of 1999-2001 for mercery sable vehicle for the springs corroding and breaking. I had the same issue with 2002 mercery sable in which I have had to pay out a exorbitant amount of money to repair, $550.61. I have been denied refund because there was no recall.*ak

68,500 miles NHTSA complaint 535535 filed 2005-05-18

The car had a noise in the rear sounded like a lose pipe was waiting to have the car look at. Some days later all of a sudden one day the spring must have moved and flattened the tire. Installed the spare tire and drove to the dealer turns out that both rear coil springs were broken.

70,000 miles NHTSA complaint 537389 filed 2005-06-01

Dt*: the contact stated while in the driveway, the front driver's side spring broke and punctured a tire. The vehicle was towed to the dealership were the spring was replaced. The dealer suggested replacing both sides at the same time. Updated 03/22/06. *jb

42,933 miles NHTSA complaint 571700 filed 2006-02-06

Also reported on the 2002 Mercury Sable

Strut, shock or spring failure

176 reports median 79k

Other speed control problem

37 reports median 86k

Other engine problem

18 reports median 51k

Other body or interior problem

17 reports median 56k

Cruise control failure

16 reports median 93k

Other powertrain problem

16 reports median 34k

How far this goes

Complaints are voluntary, so 79 is a floor and not a count of affected cars. Mileages are typed in by owners and cluster on round numbers. And the mode itself is assigned by software reading the complaint text, which is reliable in bulk and fallible one report at a time.

Questions this page answers

At what mileage does other suspension problem happen on the 2002 Mercury Sable?

Across 75 owner reports that included an odometer reading, half were filed by 82,500 miles. A quarter were filed before 67,500 miles and a quarter after 97,500 miles. These are the mileages owners reported when they complained, not a prediction for any individual car.

How common is other suspension problem on the 2002 Mercury Sable?

79 reports have been filed with NHTSA, about 0.7 per 1,000 vehicles. Complaints are voluntary, so this is a floor rather than a count of affected cars.

What this is and is not. These are the mileages at which owners chose to complain to a federal agency, which is not the same as the mileage at which the part fails on every car. It skews toward failures that happened outside warranty, cost real money, or frightened someone. It is still the only public dataset that carries failure mileage at all, and the shape of a few hundred readings is informative even when a single one is not. Methodology · JSON · this failure on other cars

Source Owner complaints and recall records published by the US National Highway Traffic Safety Administration, model years 1996–2027 Figures rebuilt Published by AtWhatMileage How every figure is computed