Other speed control problem on the 2000 Acura TL
3 crashes 2 injuries 5 of the 8 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.
Only 3 reports for this mode came with an odometer reading, which is too few for percentiles to mean anything. The page is here because someone linked to it; treat the figures as anecdotes, and see the full report for this year instead.
When other speed control problem gets reported
There are 8 reports of other speed control problem on the 2000 Acura TL, 3 with a mileage attached. That is too few to place the failure on the odometer with any confidence.
A part like this is normally expected to survive 78,000 miles. It is the 10th most-reported problem on this model year.
The whole distribution
| 10th | 25th | Median | 75th | 90th |
|---|---|---|---|---|
| — | — | 121,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, 3 a crash and 2 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 11 model years of this car. It shows up earliest on the 2004, at a median of 15,000 miles, and latest on the 2000 at 120,000 miles.
By volume the 2002 carries the most reports, with 14; the 2000 has 8. 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.
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.
Recently, even when driving at about 35 miles an hour and came to a crossroad and braked, the car kept accelarating. Despite having the brakes pressed the car was behaving like a wild bronco. Even when I shifted the automatic gear to park, the engine was racing. After I put of the ignition & then re-started, the problem disappeared. *ak
Was driving my vehicle which I just purchased on may 26th 2012, and my car began to have shifting problems in 2nd and third gear racing rpms and would not stay engaged in 2nd, 3rd, 4th and 5th gear and violently downshifted into second gear at freeway speeds causing me even restrained by the seat beat to fly into the steering wheel and windsheild bumping my head and hurting my back due to whip lash. This occurrence happened several times. Then the d5 would start flashing and check engine light became lite. After calling acura customer care, brian informed me of the recall that had to do with this matter and was supposedly fixed. My car is unsafe to drive because of the rapid change of speed at the cars desire. I could injure not just myself but others around me. *tr
Today june 2, 2013, my 2000 acura 32tl had sudden acceleration that resulted in a crash with a parked vehicle on the road while I was backing out of the driveway. After hitting the parked car, I tried to pull the car forward and tried to stop. Instead, it started moving forward uncontrollably, even though I was pushing on the brake pedal. I lost control of the vehicle to stop. It took control and started moving forward through road, driveway and neighboring lawn. I steered for about 100 feet and hit the corner of the neighboring home and finally stopped. It was for about 5 seconds of frightening moment that my family and I went through. It was sunny and 85 deg f. The car had severe damages on back and front bumpers. Tire marks on the road, driveway, and lawn, plus property damage to the corner of the house were sustained. Front airbags deployed and hit my wife and I in the face. I am wondering if there are ongoing investigations by NHTSA on similar incidents. Please advise. *tr
Also reported on the 2000 Acura TL
Other powertrain problem
Other visibility problem
Complete transmission failure
Airbag warning light or occupant sensor fault
Control module (ECM/PCM/BCM) failure
Airbag inflator rupture
How far this goes
This page is kept out of search results because 8 reports is not enough to publish percentiles from. It stays reachable because somebody looking at this exact car would rather see the reports than be told there are none.
Complaints are voluntary, so 8 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 2000 Acura TL?
Across 3 owner reports that included an odometer reading, half were filed by 120,000 miles. A quarter were filed before — and a quarter after —. 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 2000 Acura TL?
8 reports have been filed with NHTSA, about 0.1 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