3.2

definitely annoying
Crashes / Fires:
0 / 0
Injuries / Deaths:
0 / 0
Average Mileage:
43,116 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.

2015 Dodge Charger engine problems

engine problem

Find something helpful? Spread the word.
Get notified about new defects, investigations, recalls & lawsuits for the 2015 Dodge Charger:

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

2015 Dodge Charger Owner Comments

problem #5

Aug 012017

Charger

  • miles

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

Takata recall. The seatbelt, once buckled, will not unfasten unless you repeatedly yank at the belt itself. There was repeated clicking in the engine and I could not exceed over 45mph. When the heat is turned on in the car the cool A/C blows on the drivers side of the car and when I tried to adjust the temperature on driver side of car I am unable to do that.

- Fort Bragg, NC, USA

problem #4

Feb 012018

Charger

  • 105,535 miles
The contact owns a 2015 Dodge Charger. While starting the vehicle or while driving at unknown speeds, there was an abnormal ticking noise and the check engine warning indicator illuminated. The vehicle was taken to a local dealer (snethkamp Chrysler Dodge Jeep Ram, 11600 telegraph rd, redford charter twp., mi 48239, (888) 455-6146) where it was diagnosed that the camshaft was worn, the lifter was the cause of the ticking noise, and the engine needed to be replaced. The vehicle was not repaired. The manufacturer was not notified. The failure mileage was 105,535.

- Redford, MI, USA

problem #3

Apr 102018

Charger 6-cyl

  • 56,922 miles
I started a uconnect system update while I was still parked. The disclaimer said nothing about to not update while driving. I started the update and started driving (my commute is about 25 minutes). It took about 10-15 minutes to download the update. Once it downloaded, the system reset. At this time I was in cruise control on a freeway that was ending, so I turned off my cruise control and then my car jolted forwarded as if it were in a very low gear and almost caused me to crash. I then was stuck in 1st gear while the system was rebooting and couldn't automatically or manually shift past 1st gear leaving me stuck on the side of the road. Then a screen popped up saying there was 50 minutes left on the update. I was stuck on the side of the road until the update finished. After that, my gears were shifting normally. During this time, I called Dodge and opened a case letting them know what happened. The picture I provided was a picture after I was already stopped on the side of the road. Updated 10/29/18

- Fresno, CA, USA

problem #2

Apr 022018

Charger

  • 36,124 miles
The contact owns a 2015 Dodge Charger. While driving at an unknown speed, the contact heard a loud thumping noise from the front of the vehicle. There were no warning indicators illuminated during the failure. The vehicle was taken to ourisman Chrysler Jeep Dodge of alexandria (5900 richmond hwy, alexandria, va 22303) where it was diagnosed that the struts and motor mount failed. The vehicle was repaired. The manufacturer was notified and referred the contact to a case manager to assist with her claim. The failure mileage was 36,124.

- Washington, DC, USA

problem #1

Aug 062016

Charger

  • 17,000 miles
Upon arriving home after an 800 mile trip, (in the evening around 10:30 pm) when shifting into reverse to back into driveway, I experienced a complete ECU controller failure and everything went black. And engine died. After a few seconds it appears the computer rebooted itself and the dash came back up and the car restarted. It appears there is a real-time program bug in the car and the firmware needs to be investigated. Had this happened on the road, it would have cause a serious crash. I was then able to back into the driveway. No error code was posted! I believe that the realtime software is experiencing frame overruns and we know that causes runaway conditions like in the Toyota Camry. I believe the NHTSA should review every car firmware before release to insure spare time requirements are met and runaway conditions can not exist. (yes, I used to develop real time software for control systems)

- Deltona, FL, USA

Not what you are looking for?