3.3

definitely annoying
Crashes / Fires:
0 / 0
Injuries / Deaths:
0 / 0
Average Mileage:
41,516 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 (Page 2 of 2)

« Read the previous 20 complaints

problem #2

Apr 022018

Charger

  • 36,124 miles

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

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?