AtWhatMileage
Adas · 47 owner reports

Other speed control problem on the 2001 Mercury Sable

9 crashes 3 injuries 12 of the 47 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 47
With an odometer reading 23
Reports per 1,000 built 0.3 per 1,000
Filed below 36,000 miles 26%
Mention a crash, fire or injury 12
Typical repair $250–$2,000
What it means when it happens Critical
Rank among this year's problems 3rd

When other speed control problem gets reported

Owners of the 2001 Mercury Sable report other speed control problem at a median of 90,000 miles. A quarter of the reports come in before 40,000 miles and a quarter after 140,000 miles, from 23 reports that carried an odometer reading.

A part like this is normally expected to survive 78,000 miles. It is the 3rd most-reported problem on this model year.

The mileage distribution

The reported range runs from 15,000 miles at the tenth percentile to 165,000 miles at the ninetieth, a spread of 148,611 miles across the middle 80% of reports.

A spread this wide points at use rather than design. Towing, climate, service history and city mileage all move a failure like this, so the median is a weak guide to any individual car.

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

The whole distribution

Percentiles of the 23 odometer readings owners gave.
10th25thMedian 75th90th
15,389 miles 39,500 miles 89,000 miles 137,500 miles 164,000 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, 9 a crash and 3 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 $250–$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.

This mode is classified as critical, which means a failure can leave the car unable to stop, steer, or stay out of the way of traffic. It is weighted accordingly in the risk score.

The same failure on other years

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

By volume the 2000 carries the most reports, with 54; the 2001 has 47. 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.

What owners wrote

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

Dt: consumer was driving through parking lot at low speed when the car suddenly accelerated at great speed. The consumer was unable to slow the vehicle down before it struck 2 vehicles, and sped over a 3 1/2 foot high wall where it went over and came to a rest. Upon inspection, the attending police officer discovered a broken throttle cable which he believed caused the vehicle to act the way that it did. The car was totaled. Currently awaiting insurance report. *ak *jb

29,500 miles NHTSA complaint 542494 filed 2005-07-05

Dt: consumer was driving through hotel parking lot at low speed when the vehicle quickly accelerated striking 2 cars and scaling a 3 1/2 feet wall, dropping over and finally coming to a rest. The attending officer discovered that there was a broken throttle cable and suspected this was the cause of loss of control of the vehicle. It was totaled. *ak

29,500 miles NHTSA complaint 542626 filed 2005-07-06

Dt: the contact states on occasion when he puts on the brakes instead of braking the car will accelerate and the engine will rev. Has to stomp on the brakes, turn off the ignition and/or put the car in neutral to get it to stop. The contact noticed this just after purchasing the car in june. It has gotten progressively worse. Vehicle is a 2001 mercury sable. The dealer cannot duplicate the problem. He has not talked to the manufacturer. *ak the cigarette lighter was inoperative, the fuse was replaced. *jb

49,500 miles NHTSA complaint 550101 filed 2005-08-17

Also reported on the 2001 Mercury Sable

Strut, shock or spring failure

107 reports median 68k

Other suspension problem

98 reports median 80k

Other brake problem

20 reports median 63k

Other electrical problem

19 reports median 52k

Cruise control failure

17 reports median 119k

Other engine problem

15 reports median 68k

How far this goes

Complaints are voluntary, so 47 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 speed control problem happen on the 2001 Mercury Sable?

Across 23 owner reports that included an odometer reading, half were filed by 90,000 miles. A quarter were filed before 40,000 miles and a quarter after 140,000 miles. These are the mileages owners reported when they complained, not a prediction for any individual car.

How common is other speed control problem on the 2001 Mercury Sable?

47 reports have been filed with NHTSA, about 0.3 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