2006 Mitsubishi Lancer Evolution Other or unknown Problems
- Complaints
- 1about this part
- Share
- 4%of 24 total for the year
- Median mileage
- 12,000miles
- Trend
- Not enough dataFewer than 15 complaints, too few for a reliable trend.
NHTSA recorded 1 complaints about the other or unknown of the 2006 Mitsubishi Lancer Evolution, 4% of the 24 complaints for this model year. Where a mileage was given, the median is 12,000 miles.
Fewer than 15 complaints name this part, so treat the figures as a rough indication only.
Example complaints
Selected from NHTSA records; personal details are removed. They are consumer reports, not findings.
“1. Driving 2. Irritating ticking from passenger side of engine bay. Seems to cause wear and tear on belts on engine. So far no consequences as belt hasn't broken. 3. No part have been replaced as of yet. 4. In short it seems almost all evo ix's are affected by this belt wear on the idler pulley, power steering pulley, and possibly others. I just don't want to see one of these belts break on this performance turbo car at high speeds... Could cause many injuries in my opinion. …”
NHTSA complaint #10291153, filed 2009-11, 12,000 milesRelated service bulletins
- 10211530Apr 7, 2022This Technical Service Bulletin was sent to dealers to explain the difference between normal dew condensation, which is a natural phenomenon, and water penetration caused by…
Other or unknown: other model years
Other parts of the 2006 Mitsubishi Lancer Evolution
10 complaintsBrakes
3 complaintsEngine
3 complaintsSuspension
3 complaintsTransmission and drivetrain
3 complaintsElectrical system
2 complaintsBody and structure
2 complaintsSteering
1 complaintsVehicle speed control
1 complaints
← All problems reported for the 2006 Mitsubishi Lancer Evolution
About this data. Data from NHTSA (ODI) complaints, recalls, TSBs and investigations, updated Oct 29, 2026. Complaints are unverified consumer reports and may be duplicated or inaccurate.
To check a specific vehicle for open recalls, use its VIN at nhtsa.gov/recalls. Methodology