Consumer Complaints
| Fail date | miles | occurences | Purchase date |
|---|---|---|---|
| VEHICLE SPEED CONTROL | |||
| 11/01/2011 | 98000 | ||
| 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. | |||
| 11/01/2011 | 98000 | ||
| 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. mah | |||
| 11/01/2011 | 98000 | ||
| 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 accelerated and she crashed into a building. the contact receive 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. tb | |||
| 01/17/2011 | 71000 | ||
| Recently purchased 06 mdx. didn't notice the transmission issue right away. about month after purchase, i noticed shutter/grinding/judder/whistling coming from the transmission. took it into acura dealer. acura replaced torque converter and updated pcm software under warranty. about week later, started noticing the same shuttering noise coming from transmission again but its not as noticeable but definitely noticeable and the problem is still there. acura did not fix the problem. it seems acura had fixed the severity of it to the point where you can only slightly hear it. after being thoroughly frustrated with this issue, i started researching the internet and found out there are many many many many others with this same problem. it seems that there is no permanent fix. numerous owners have same repeat problems even after replacing the entire transmission. the problem seems to be that of a design of transmission error by the acura so essentially, only permanent fix would be to replace the transmission with the newly redesigned transmission. if you replace the same parts over and over, you will have same problems over and over. acura fails to acknowledge this. if you take the car to any acura dealer, they will vehemently deny there is transmission problems(i am sure they're trained by the corporate to deny, deny, deny). unfair. essentially, my car is a lemon albeit a used lemon.... | |||
| VEHICLE SPEED CONTROL - ACCELERATOR PEDAL | |||
| 09/09/2006 | 9000 | 1 | 12/07/2005 |
| 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. | |||