AtWhatMileage
Adas · 23 owner reports

Other speed control problem on the 2005 Mercury Sable

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

When other speed control problem gets reported

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

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

The mileage distribution

The reported range runs from 25,000 miles at the tenth percentile to 150,000 miles at the ninetieth, a spread of 121,031 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.

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

The whole distribution

Percentiles of the 18 odometer readings owners gave.
10th25thMedian 75th90th
26,869 miles 64,500 miles 96,000 miles 140,585 miles 147,900 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 crash is 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 2005 has 23. 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.

Tl*the contact owns a 2005 mercury sable. The contact stated that the accelerator pedal vibrates when accelerating; the greater the speed, the more vibration occurs. The dealer repositioned the cable underneath the pedal, but the failure persists. The failure has occurred each time the vehicle is driven since the date of purchase. The engine size was unknown. The current mileage is 19,800 and failure mileage was 19,564.

19,564 miles NHTSA complaint 626385 filed 2007-06-06

Tl* the contact owns a 2005 mercury sable. While traveling 40 MPH, the contact noticed that the throttle had become stuck causing the vehicle to accelerate abnormally. In order to stop the failure, the contact had to depress the accelerator pedal vigorously 3-4 times. The vehicle was not diagnosed and no repairs were performed. The current mileage was 140,000 and the failure mileage was 19,000.

19,000 miles NHTSA complaint 909177 filed 2012-03-12

Tl* the contact owns a 2005 mercury sable. The contact stated that while driving above 60 MPH, the vehicle would unexpectedly accelerate without warning. The contact had to apply extreme pressure to the brake pedal to stop the vehicle. The vehicle would then have to be shut off in order to stop the vehicle from accelerating. The vehicle was not diagnosed or repaired. The dealer was not notified. The failure mileage was 145,000 and the current mileage was 147,585.

145,000 miles NHTSA complaint 909515 filed 2012-03-13

Also reported on the 2005 Mercury Sable

Cruise control failure

16 reports median 68k

Other powertrain problem

12 reports median 61k

Torque converter failure

7 reports median 95k

Other engine problem

6 reports median 77k

Other brake problem

6 reports median 64k

Oil leak

3 reports median 136k

How far this goes

Complaints are voluntary, so 23 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 2005 Mercury Sable?

Across 18 owner reports that included an odometer reading, half were filed by 95,000 miles. A quarter were filed before 65,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 2005 Mercury Sable?

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