There are 2 stored owner reports matching the speed control & cruise leading-label group for the 2006 Acura MDX 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 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)TL* THE CONTACT OWNS A 2006 ACURA MDX. THE CONTACT STATED THAT WHILE PARKING HER VEHICLE, SHE HEARD A LOUD POPPING NOISE AND THE VEHICLE ERRONEOUSLY ACCELERATED CAUSING HER TO CRASH INTO A BUILDING. THE CONTACT RECEIVED MINOR ABRASIONS. THE POLICE WERE CONTACTED AND A REPORT WAS AVAILABLE. THE VEHICLE WAS LATER TOWED TO AN INDEPENDENT MECHANIC. AFTER DIAGNOSIS, THEY ADVISED HER THAT THE FAILURE OCCURRED DUE TO HER POSSIBLY DEPRESSING ON THE ACCELERATOR VERSUS THE BRAKES. THE MANUFACTURER WAS CONTACTED AND THEY OFFERED NO ASSISTANCE. THE FAILURE MILEAGE WAS APPROXIMATELY 98,000. THE CURRENT MILEAGE WAS APPROXIMATELY 103,000. THE VIN WAS UNAVAILABLE. *TR
DT*: THE CONTACT STATED WHILE DRIVING 65 MPH, THE ACCELERATOR PEDAL BECAME STUCK IN THE DOWN POSITION. AS THE VEHICLE ACCELERATED, THE CONTACT APPLIED THE VEHICLE BRAKES FOR 5 MILES, RESULTING IN THE BRAKES AND ROTORS OF THE VEHICLE BURNING OUT. THERE WERE NO WARNING SIGNALS PRIOR TO THE INCIDENT. THE VEHICLE WAS TAKEN TO A SERVICE DEALER, WHO WAS UNABLE TO DETERMINE THE PROBLEM, AND CONSIDERED IT TO BE DRIVER ERROR.
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.