There are 3 stored owner reports matching the speed control & cruise leading-label group for the 2016 Dodge Durango in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 3 of 3 matching reports.
Open the full vehicle complaint log (all categories)5TH TIME EVENT HAS OCCURRED. AFTER EXTENDED DRIVING WHEN PULLING INTO A PARKING SPOT THE VEHICLE WILL COMMENCE TO ACCELERATE. ONLY BY AGGRESSIVELY APPLYING THE BRAKE TO PREVENT THE VEHICLE FROM PLOWING AHEAD CAN I PLACE THE TRANSMISSION INTO PARK AND TURN OFF THE VEHICLE. CHRYSLER PREVIOUSLY ACKNOWLEDGED CRUISE CONTROL PROBLEMS. I THINK THE PROBLEM STILL EXISTS. THIS IS A DANGEROUS VEHICLE. PREVIOUS FILE NUMBER #10916715.
WHILE DRIVING ON THE INTERSTATE ,WITH THE CRUISE CONTROL ENGAGED,TRAFFIC WAS SLOWING DOWN DUE TO ROAD REPAIR, I APPLIED MY BRAKES LIGHTLY TO DISENGAGE THE CRUISE CONTROL, BUT THE VEHICLE REMAINED IN A FORWARD THRUST. I WAS FAST APPROACHING A VEHICLE AHEAD OF ME, AND BEFORE I REALISED I WASNT GOING TO STOP WITH FURTHER APPLICATION OF MY BREAKS, I HIT THE VEHICLE IN FRONT OF ME RESULTING IN A NEAR FATAL COLISION. I WAS SAVED BY MY SEAT BELT AND THE AIR BAGS. I CAN ONLY ESTIMATE MY SPEED AT THE TIME OF COLLISION TO BE BETWEEN 40 OR 50 MPH, AS MY CRUISE CONTROL WAS SET AT 62 MPH *TT
TL* THE CONTACT OWNS A 2016 DODGE DURANGO. WHILE DRIVING 10 MPH, THE VEHICLE INDEPENDENTLY ACCELERATED TO 35 MPH WITHOUT WARNING. IN ADDITION, THE RPMS REVVED AND THE INSTRUMENT PANEL ILLUMINATED. THE VEHICLE WAS TOWED TO THE DEALER, BUT WAS NOT DIAGNOSED OR REPAIRED. THE MANUFACTURER WAS NOTIFIED OF THE FAILURE. THE FAILURE MILEAGE WAS 981. THE VIN WAS UNAVAILABLE.
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: Apr 28, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.