really awful
Crashes / Fires:
2 / 1
Injuries / Deaths:
1 / 0
Average Mileage:
19,582 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.

2004 Mitsubishi Lancer seat belts / air bags problems

seat belts / air bags problem

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

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

2004 Mitsubishi Lancer Owner Comments

problem #11

Sep 012016


  • miles


Takata recall. The contact owns a 2004 Mitsubishi Lancer. The contact received notification of NHTSA campaign number: 15V321000 (air bags) and was unable to schedule a repair with a dealer in a reasonable location. The contact indicated that the dealer was more than 150 miles away. The contact was waiting for a response from the manufacturer to determine if they could provide a closer location to schedule the repair. In addition, the contact was uncertain as to when the manufacturer would supply the parts to the dealer for the recall repair. The contact had not experienced a failure. VIN tool confirms parts not available.

- Idaho Falls, ID, USA

problem #10

Aug 142015


  • 100,000 miles
The contact owns a 2004 mitsubushi Lancer. The contact stated that the air bag warning indicator illuminated. The vehicle was serviced per NHTSA campaign number: 15V321000 (air bags), but the air bag warning indicator remained illuminated after the repair. The manufacturer was not notified of the failure. The failure mileage was approximately 100,000.

- Peoria, IL, USA

problem #9

Aug 032015


  • miles
The contact owns a 2004 Mitsubishi Lancer. The contact received notification of NHTSA campaign number: 15V321000 (air bags) and stated that the part was not available within a reasonable timeframe to schedule the recall repair. The dealer did not give a specific date for when the part would become available. The manufacturer could not provide an estimated date for when the vehicle would receive the recall repair. The contact was not experiencing a failure. Updated 11/18/15

- Mcminnville, TN, USA

problem #8

Jun 232015


  • miles


I am an owner of two Mitsubishi cars; one bought new at a mits. Dealer in tucson, AZ 11 years ago and the other bought just a couple of months ago at a used car lot in tucson, AZ. Yesterday, I received an 'important safety recall' notice for both cars via mail. It's recommended to take care of the recall of the passenger air bag, that is described as causing serious injury or death. Yet, there is currently no local dealer where I live. Therefore, I called the phone number listed on the notice to address my concern. I was told I'd have to travel to another city over 80 miles one way to have this remedied. This would be much too inconvenient, unlike the promised 'every effort to minimize inconvenience' the notice reference. Shouldn't they allow this to be done by a certified mechanic in the city of tucson where I purchased the cars and reside; it's not my fault that they've had maultiple dealerships close down here? I am very unhappy with mits. Right now for causing me to have fear and not helping with the problem they informed me of... not sure what to do...updated 08/25/15

- Tucson, AZ, USA

problem #7

Oct 062014


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

- Chesterfield, MO, USA

Search CarComplaints.com for these popular complaint phrases...

problem #6

Jan 012015


  • miles
2004 Mitsubishi Lancer. Consumer would like manufacturer to pay for shipping the vehicle and getting it repaired due to air bag recall. The consumer has not received a response from Mitsubishi. Updated 03/11/15

- Wailuku, HI, USA

problem #5

Dec 222014


  • miles


Dear administrator: There has been no accident....I am following instruction from letter. I recently received a letter notifying me of a safety recall regarding the passenger air bag inflater housing for 2004-2005 Mitsubishi Lancer vehicles. I currently still own a 2004 Lancer Mitsubishi and I am extremely concerned for the safety of any front seat occupants. Therefore, I immediately responded to the letter from Mitsubishi and followed your instructions. Unfortunately, the response that I received was shocking and quite frankly, ridiculous! I was informed that I would be responsible to pay to ship my car from maui to honolulu in order to get my car repaired! the notification letter clearly states under the reason for notice that the safety recalls are in the areas of Hawaii, Florida, puerto rico, and the us virgin islands. Mitsubishi should assume that "special arrangements? would have to be offered to service and repair in order to meet the requirements of the national traffic and motor vehicle Safety Act. If you recognized that this recall affects island customers why are you penalizing them for your manufacturing mistake, forcing them to ship their cars inter-island for repair" I am asking that Mitsubishi please assume their responsibility and comply with the national traffic and motor vehicle Safety Act and pay for the shipping of my car from maui to honolulu to have my car repaired. At a minimum allow a certified Mitsubishi motor dealer or certified mechanic in maui to make the necessary repair. Please keep this letter in your archives as my attempt to find a solution to get my car repaired to avoid injury or any life changing events as a result of negligence on your behalf. Best regards [xxx] information redacted pursuant to the Freedom Of Information Act (FOIA), 5 U.S.C. 552(B)(6).

- Wailuku, HI, USA

problem #4

Feb 062010


  • 36,400 miles
The contact owns a 2004 Mitsubishi Lancer. While the contact was driving out of her driveway the vehicles front passenger side airbag deployed without warning filling the inside of the vehicle with white smoke. Due to the deployment of the airbag which blocked the vision of the contact the vehicle crashed into a nearby utility pole. The contact suffered injuries to her face and body. A police report was filed for the incident. The contact called the manufacturer and a report was filed for the failure. The current and failure mileages were 36400.

- Newport , RI, USA

problem #3

Nov 232006

Lancer 4-cyl

  • Automatic transmission
  • 45,000 miles
: the contact stated while parked with the engine idling, the driver air bag deployed without warning. It was removed and an hour later while driving 45 mph, the passenger side air bag deployed, which fractured the windshield. The vehicle was towed to the residence. Although the vehicle was not inspected, the dealer was alerted and indicated the problem was most likely an electrical short due to flooding.

- High Point, NC, USA

problem #2

Aug 152005


  • Manual transmission
  • 34,000 miles
: the contact stated while driving 55 mph, the vehicle's app sensor went out, which caused the vehicle to decelerate rapidly and not rev past 2500 rpms. The service department was contacted but could not find the cause of the problem. The app sensor was replaced 5 times. The contact had repair invoices available upon request. Updated 10/25/2006 - the brake light indicator on the dash remained on at all times. The dealer replaced the alternator. The ses light illuminated intermittently and the vehicle lacked power. The clutch slipped at time. The dealer replaced the clutch disc.

- Alamosa, CO, USA

problem #1

Feb 142005

Lancer 4-cyl

  • miles
The vehicle was involved in a front collision accident. The air bag did not deploy upon impact. Manufacturer was contacted by consumer.

- Chittenango, NY, USA

Not what you are looking for?