Control module (ECM/PCM/BCM) failure on the 2005 Subaru Legacy
Only 4 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 control module (ecm/pcm/bcm) failure gets reported
There are 5 reports of control module (ECM/PCM/BCM) failure on the 2005 Subaru Legacy, 4 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 92,000 miles. It is the 16th most-reported problem on this model year.
The whole distribution
| 10th | 25th | Median | 75th | 90th |
|---|---|---|---|---|
| — | — | 89,600 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
Putting it right typically runs $700–$3,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 4 model years of this car. It shows up earliest on the 2011, at a median of 100 miles, and latest on the 2005 at 90,000 miles.
By volume the 2005 is the worst of them, which makes this a problem of this specific year rather than of the model as a whole.
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.
Tl*the contact owns a 2005 subaru legacy gt purchased in 2009. The passenger side air bag would not operate with an occupant in the passenger's side seat. The vehicle was taken to the dealer and they were unable to make repairs to correct failure. There were no recalls on the year, make and model for frontal airbags, only side and window airbags. The current and failure mileages were under 62,793. Updated 01/29/10. *lj updated 01/29/10.*jb
Car has been very slow to reduce rpms when shifting gears or when stopped (and in neutral) for the past few weeks. Today, when pulling into a starbucks, the car surged forward. Luckily I have a stick shift and just pushed the clutch in. After surging, the check engine light came on. Using a diagnostic tool, I found that the car is throwing error code p2138. This indicates that the accelerator pedal position (app) sensor is either bad or has a poor connection. The detail on the error stats "the ECM has detected that the app sensor 1 and app sensor 2 disagree more than 4.5% for less than 1 second." essentially, one or both throttle-by-wire circuits isn't functioning properly. I went online and found that this is an all too common problem and some folks have found that their cars are surging forward, threatening safety. *tr
Car has been very slow to reduce rpms when shifting gears or when stopped (and in neutral) for the past few weeks. Today, when pulling into a starbucks, the car surged forward. Luckily I have a stick shift and just pushed the clutch in. After surging, the check engine light came on. Using a diagnostic tool, I found that the car is throwing error code p2138. This indicates that the accelerator pedal position (app) sensor is either bad or has a poor connection. The detail on the error stats "the ECM has detected that the app sensor 1 and app sensor 2 disagree more than 4.5% for less than 1 second." essentially, one or both throttle-by-wire circuits isn't functioning properly. I went online and found that this is an all too common problem and some folks have found that their cars are surging forward, threatening safety. *tr
Also reported on the 2005 Subaru Legacy
Turbocharger or supercharger failure
Other engine problem
Wiring harness or short circuit
Other electrical problem
Other fuel system problem
Fuel leak or fuel odor
How far this goes
This page is kept out of search results because 5 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 5 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 control module (ecm/pcm/bcm) failure happen on the 2005 Subaru Legacy?
Across 4 owner reports that included an odometer reading, half were filed by 90,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 control module (ecm/pcm/bcm) failure on the 2005 Subaru Legacy?
5 reports have been filed with NHTSA, about 0.2 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