Consumer Complaint Detail

MITSUBISHI / LANCER EVOLUTION / 2005

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 005050971 Incident Date: Nov, 08 2005
Consumer's City: DELAND Consumer's State: FL
Vehicle Transmission Type: MAN Manufacturers Name: Mitsubishi Motors North America, Inc.
Model Name: LANCER EVOLUTION Model Year: 2005
Vehicle Involved in a Crash: No Component's Description: Power train:clutch assembly
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: JA3AH86D15U Date added to File: May, 23 2021
Date Complaint Received: Dec, 27 2005 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: Sep, 21 2005
Was Original Owner: Yes Anti-lock Brakes: Yes
Number of Cylinders: 4 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: I purchased a brand new 2005 mitsubishi lancer evolution, and two months later @ 1847 miles, the clutch went out. mitsubishi refused to warranty repair the failure, so i started investigating their clutches. it turns out six local repair shops as well as 4 mitsubishi technicians advised me the clutches are weak/defective from the factory, and mitsubishi is aware of the problem on my model, but refuses to recall them or repair them. i also went on-line and found several web-site complaints about evolution clutches, including "www.mitsubishisucks.com" i contacted mitsubishi's consumer complaint dept, who generated file#[xxx] and i was never contacted again. they refuse to acknowledge their product failure! my vin# [xxx]. i ended up having to pay $606.80 to daytona mitsubishi or they would not give me my car back! they head service manager ron, told me "its a little car, with too much power, so mitsubishi had to design it in a way where something would have to break, and unfortunately its the clutch". with hundreds of existing complaints, i would respectfully request mitsubishi have to recall all lancer evolution clutches, and replace them with a unit that will not fail. *jb updated 07/17/2012 *js information redacted pursuant to the freedom of information act (foia), 5 u.s.c. 552(b)(6)