2000 Mitsubishi Eclipse: what breaks, and at what mileage

The failures owners actually file about

Owners have reported 42 named failure modes on the 2000 Mitsubishi Eclipse, and the three most-reported carry 53% of everything filed.

Other wheel or tire problem leads with 140 reports, about 2.5 per 1,000 vehicles and with the middle half of reports between 24k to 50,000 miles.

Other body or interior problem follows with 43 reports, usually reported between 47k to 70,000 miles.

Other powertrain problem follows with 18 reports, median 45,000 miles.

By system, the reports fall mostly into wheels (146), body (67) and lighting (21).

How bad it is when it goes

Across the named modes, 15 mention a crash, 13 a fire, 13 an injury and 2 a fatality. Those are the words owners used in their own complaints, and NHTSA does not verify them, but they are the closest thing in this data to a measure of what a failure actually did.

The average severity weight across every report on this year is 4.27, where a stalled engine or a failed airbag weighs many times more than a rattling trim panel, and a figure this high means the reports are dominated by failures with safety consequences rather than annoyances. The weighting is set out in full on the methodology page.

What the top failures cost to put right, as editorial estimates for an independent US shop rather than figures from NHTSA: other wheel or tire problem at $200–$1,500, other body or interior problem at $200–$2,000, other powertrain problem at $400–$4,500 and other visibility problem at $150–$1,400. Dealer labour, a seized bolt or a part that is no longer made can push any of these past the top of its range.

9% of the reports on this year sit in the engine, transmission, drivetrain or cooling systems — the four where a repair bill is usually four figures.

How often, against how many were built

Scaled by an estimate of how many of these cars exist, the 2000 Mitsubishi Eclipse draws about 6.7 per 1,000 vehicles, which puts it in the 83rd percentile of complaint rates among 2000 vehicles we can rate.

That denominator is the weakest number on the page and it is fair to say so plainly. Rate per 1,000 uses a fleet-size estimate derived from recall paperwork for this exact model year. It is a lower bound.

The working figure is 57,073 vehicles. If the true number is twice that, every rate on this page is half what it says; the ranking against other 2000 vehicles, which is what the risk score uses, is far more robust than the rate itself.

Recalls on the 2000 model year

NHTSA has issued 10 recall campaigns covering the 2000 Mitsubishi Eclipse, affecting an estimated 179,553 vehicles. A recall is a different kind of evidence from a complaint: it is the regulator and the manufacturer agreeing that something has to be fixed, and the fix is free for as long as the car exists.

The campaigns cover air bags:frontal:passenger side:inflator module and exterior lighting. Whether the work was actually done on the car in front of you is a question only the VIN can answer, and the manufacturer or NHTSA will answer it free.

One caution about reading these together: a recall usually raises the complaint count for the same part, because owners who read about it go and file. The mileages stay informative; the counts get noisy.

Better and worse years of the same car

High risk for a 2000 — 178th riskiest of the 327 2000 vehicles we can rate. The comparison is always within the same model year, so an older car is never penalised for having had longer to break.

Across the 13 model years of this car that carry enough reports to score, 1996 comes out best at 64 and 2003 worst at 73, with 2000 itself at 66.

No other year of this model scores meaningfully better than 2000, so if this generation is what you want, the year is not the lever.

Within the 2000–2005 generation specifically, 2002 is the strongest year at 65 and 2003 the weakest at 73.

What to look at before buying one

The mileages below are where the first quarter of reports for each mode had already been filed, which makes them the point at which a fault is worth looking for rather than the point at which it happens: other wheel or tire problem from about 24k and other body or interior problem from about 47k.

On a 2000 Mitsubishi Eclipse with more miles than that on it, the useful question to put to a seller or a mechanic is whether other wheel or tire problem has been dealt with, and if so with what parts and at whose expense. A car that has already had the repair is in a different position from one that has not.

Treat it as where to point the inspection, not as a prediction. A well-maintained example can sail past every mileage on this page, and a neglected one can fail well before the first of them.

What this page cannot tell you

380 owner reports; fleet size estimated from this year's own recall paperwork. Every count on this page is therefore a floor: it is the number of owners who went to the trouble of filing with a federal agency, which is a small and self-selected fraction of the owners who had the fault.

Of those 380 reports, 126 carried an odometer reading, so the mileages here describe 33% of the sample rather than all of it. Owners also round: readings pile up on multiples of ten thousand, which is why this site publishes "about 90,000 miles" and not "91,438".

The failure modes are assigned by software reading the owner's own words, which is accurate in bulk and wrong in individual cases. A mode with a handful of reports may contain a misfiled one.

And nothing here predicts what one car will do. These are other people's complaints, filed years apart, on cars maintained by strangers. Read the page as a map of where this model year has previously gone wrong, then have the specific car in front of you inspected.