10.0

really awful
Crashes / Fires:
0 / 1
Injuries / Deaths:
0 / 0
Average Mileage:
42,231 miles

About These NHTSA Complaints:

This data is from the NHTSA — the US gov't agency tasked with vehicle safety. Complaints are spread across multiple & redundant categories, & are not organized by problem.

So how do you find out what problems are occurring? For this NHTSA complaint data, the only way is to read through the comments below. Any duplicates or errors? It's not us.

2010 Mitsubishi Lancer engine problems

engine problem

Find something helpful? Spread the word.
Get notified about new defects, investigations, recalls & lawsuits for the 2010 Mitsubishi Lancer:

Unsubscribe any time. We don't sell/share your email.

2010 Mitsubishi Lancer Owner Comments

problem #13

Jul 012018

Lancer

  • miles

A D V E R T I S E M E N T S

The car started flashing a warning sign and loosing power. When trying to accelerate it stops. Eventually it puts the car into a limp mode and will stall altogether. This happens any long distance trip. My car year and model is not the only Lancer being effected by this computer glitch. It-€™s very dangerous due to the fact that the cars loosing power while you-€™re driving. It doesn-€™t matter if you-€™re in the middle of the highway it will just stop working. All research I have done points to an error within the computer that tells the car when to cool down the transmission. I have seen many blogs, forums and actually know another Lancer owner who-€™s model is a 2012 and has the exact same issue. I don-€™t know why this hasn-€™t been addressed yet when it-€™s affecting more than just one Lancer here or there. Bad for the engine bad for the transmission bad for my travel. And the worst part is that any mechanic is unable to detect the issue unless the car is actively coding. I-€™ve had this car for 3 years now and I feel it-€™s a big safety concern and needs to looked into. First occurrence was on a trip down to a local lake car stalled on the side of a highway this was in 2018. Now any trip further than over 30 miles or more the car will throw this code it looks like a gear and it has a exclamation point in the middle. It-€™s progressively getting worse and effecting the over all performance more each time I wish to travel. Please find out why this issue is occurring in multiple years of the same model of car because it inconvenient and dangerous. I would hate for myself and my kids to get killed in an accident due to not being able to get out of the way of a bigger vehicle or a truck.

- St. Charles, MO, USA

problem #12

Jun 112016

Lancer 4-cyl

  • 161,000 miles
Warning message "too hot slow down" appears when inclining uphill in above 70 degrees (F) at 45mph or more. Transmission begins to lose power, deceleration occurs, temperature gauge reads normal on dashboard menu, vehicle transmission runs on high RPM above 3000, transmission sounds are louder than normal, and when vehicle reaches complete stop, vehicle warning message does not go away. When vehicle is manually shut off, message will still appear. When the vehicle is turned on to electrical only, message will still appear. After 5 minutes or more in power off, vehicle will restart like normal, message is cleared, and gauges for temperature and oil pressure is normal range. No error codes are discovered when pulling codes when issue occurs. Emissions is okay and vehicle is regularly maintained according to vehicle's suggested maintenance plans. Issue has been a recurring issue for the last 4 years and the dealership has not responded with a suggested resolution or advisement on the issue.

- Albuquerque, NM, USA

problem #11

Jun 232019

Lancer

  • 93,000 miles
Hello NHTSA, I have a 2011 Mitsubishi Lancer ralliart sportback. I have just came across a crack in my exhaust manifold which is causing exhaust fumes to enter the cabin of the vehicle if my windows are up. I don't seem to be the only person with this type of car/engine that has a crack in the exhaust manifold. My car is not modified in any way that effects the performance that could cause such a crack to happen. This also appears to be the case for several thousand others. I have brought my vehicle into Mitsubishi who has confirmed the crack and has not been able to explain to me why or how this happened. I have been told from my local Mitsubishi dealership and the next closest one that they can replace the manifold for $2K. I have contacted Mitsubishi usa who has told me the exhaust manifold shouldn't crack and has gotten no other complaints about the issue. There are several thousand posts with photo proof that I am not alone with this issue. Mitsubishi has had a similar issue with their all wheel drive pump where there was a defect of some sort and extended the warranty to 100,000K. I have already had my all wheel drive pump fail and replaced under that warranty. When I spoke with Mitsubishi usa a supervisor named jennifer informed me to put in a complaint here. Since Mitsubishi has not had any internal testing on the manifold going this route may speed the process up. This issue is quite serious since with the crack - photo attached: It causes carbon monoxide to enter the cabin if the windows are up or if the ac is on and the car is at a stand still. Thank you for your time.

- Grandville, MI, USA

problem #10

Jul 012018

Lancer

  • 186,000 miles

A D V E R T I S E M E N T S

The contact owns a 2010 Mitsubishi Lancer. While driving approximately 70 mph, the vehicle suddenly shut off. The vehicle was examined by an independent mechanic who diagnosed that the bolts to the I-beam connecting rod became loose and damaged the engine block. The vehicle was not repaired. The local dealer (kelly Mitsubishi, 536 state ave, emmaus, pa) was notified of the failure. The manufacturer was not notified. The failure mileage was 186,000.

- Allentown, PA, USA

problem #9

Jul 062016

Lancer 4-cyl

  • miles
2010 Mitsubishi Lancer. Consumer writes in regards to vehicle fails emissions due to service engine warning light indicates catalytic converter/sensor circuit slow response malfunction also passenger windows and key fob battery problems. The consumer stated the dealer advised that the 02 sensors and the catalytic converter needed to be replaced. The passenger's window was inoperable. The rear passenger window was slow to open. The key fob also is inoperable. Updated 06/21/2017

- Temple Hills, MD, USA

problem #8

Sep 022013

Lancer 4-cyl

  • 39,000 miles
There was no incident. I received a notice from Mitsubishi for the recall. The problem is/was Mitsubishi didn't make easy for the consumer to have the recall issue fixed. My dealer (glendale Mitsubishi) said they don't do recalls on saturdays. So myself and four other consumers got told they don't do recalls on saturdays. It was done there is also a recall on the transmission, I don't remember for what. I received a letter saying nothing would be done unless something broke.

- Panorama City, CA, USA

problem #7

Oct 132014

Lancer

  • miles

A D V E R T I S E M E N T S

The contact owns a 2010 Mitsubishi Lancer. The contact received a notification for NHTSA campaign id number: 14V562000 (engine) and stated that the part needed was unavailable to perform the recall repair. The manufacturer was notified of the issue. The contact had not experience a failure.

- Juncos, PR, USA

problem #6

Jan 272015

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received a notification for NHTSA campaign number: 14V562000 (engine and engine cooling) and stated that the part needed was unavailable to repair the vehicle. The dealer was unable to inform when the part would become available. The manufacturer was notified of the issue. The contact had not experienced a failure.

- Clermont, FL, USA

problem #5

Oct 242014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact stated that the service engine warning light illuminated. The vehicle was repaired under NHTSA campaign id number: 14V562000 (engine and engine cooling) but the service engine warning light remained illuminated. The contact stated that the recall remedy failed to repair the vehicle. The manufacturer was notified of the failure. The failure mileage was not available.

- Jacksonville, FL, USA

problem #4

Oct 012014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received a notification for recall NHTSA campaign number: 14V562000 (engine and engine cooling). However, the part needed was unavailable. The contact stated the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was notified of the failure. The contact had not experienced a failure.

- Hockessin , DE, USA

problem #3

Aug 042014

Lancer

  • miles

A D V E R T I S E M E N T S

The contact owns a 2010 Mitsubishi Lancer. The contact received a notification for NHTSA campaign number: 14V562000 (engine and engine cooling). However, the part needed to do the repair was unavailable. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repair. The manufacturer was made aware of the issue. The contact had not experienced a failure.

- Wilkes, WV, USA

problem #2

Nov 062014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received notification for NHTSA campaign number: 14V562000 (engine) and stated that the part needed was unavailable to perform the recall remedy. The manufacturer was not notified of the issue. The contact had not experienced a failure.

- Leesburg , FL, USA

problem #1

Oct 012014

Lancer

  • 70,000 miles
The contact owns a 2010 Mitsubishi Lancer. The contact stated that burning fumes were emitted into the vehicle. The contact received a notice for NHTSA campaign number: 14V562000 (engine). However, the parts needed were not available. The contact mentioned that the manufacturer had exceeded the reasonable amount of time for repair. The dealer was contacted and confirmed that the parts were not available. The manufacturer was not made aware of the failure. The vehicle was not repaired. The failure mileage was 70,000.

- Aibonito, PR, USA

Not what you are looking for?