10.0

really awful
Crashes / Fires:
0 / 0
Injuries / Deaths:
0 / 0
Average Mileage:
0 miles

About These NHTSA Complaints:

The NHTSA is the US gov't agency tasked with vehicle safety. Complaints can be spread across multiple & redundant categories, & are not organized by problem. See the Back button — blue bar at the very top of the page — to explore more.

Get notified about new defects, investigations, recalls & lawsuits for the 2010 Mitsubishi Lancer:

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

problem #8

Oct 012014

Lancer 4-cyl

  • miles
2011 Mitsubishi Lancer due to the build material of the drive belt, the pulleys in the drive belt system can experience unusual wear, resulting in possible detachment of the drive belt. The consumer stated the parts were not available to satisfy the recall.

- Aguadilla, PR, USA

problem #7

Oct 062014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received notification of NHTSA campaign number: 14V562000 (engine and engine cooling) however, the part 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. The VIN was not available.

- Ponce , PR, USA

problem #6

Dec 152014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received a notification of NHTSA campaign number: 14V562000 (engine and engine cooling) however, the part 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.

- Cincinatti, OH, USA

problem #5

Dec 112014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received a notification for NHTSA campaign numbers: 14V562000 (engine and engine cooling) and 12E012000 (exterior lighting). The contact stated that the parts needed were unavailable to repair the vehicle under the recall remedy. The dealer was unable to inform when the parts would become available. The manufacturer was not notified of the issue. The contact had not experienced a failure.

- Richmond , VA, USA

problem #4

Dec 092014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received notification of NHTSA campaign number: 14V562000 (engine and engine cooling); however, the part 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.

- Millsboro, DE, USA

problem #3

Nov 222014

Lancer

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

- Meadow Vista , CA, USA

problem #2

Oct 272014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received notifications for NHTSA campaign id numbers: 14V562000 (engine and engine cooling) and 12E012000 (exterior lighting) however, the parts for the recall repairs were not available. The contact stated that the manufacturer exceeded a reasonable amount of time for the recall repairs. The manufacturer was made aware of the delay. The contact did not experience a failure.

- Middletown, OH, USA

problem #1

Oct 232014

Lancer

  • miles
The contact owns a 2010 Mitsubishi Lancer. The contact received notification of NHTSA campaign number: 14V562000 (engine and engine cooling:engine) however, the part 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 not made aware of the issue. The contact had not experienced a failure.

- Bongor, ME, USA