CarComplaints.com Notes: Whenever a new product is introduced, there's bound to be some problems. And man oh man, does the 2006 Commander have some problems.
It's the plight of the 1st-generation adopter: you get the newest and shiniest in exchange for a handful of issues that get ironed out in future versions. But what happens when that handful of issues becomes a bucketload? The 2006 Commander has quality control issues like the door handles breaking off and the sunroof leaking. But what's truly worrisome is the electrical problems like the vehicle shutting down unexpectedly, gauges going crazy or the cruise control having a mind of its own.
Bottom line: if you want a Jeep Commander, you're better off looking at a later model year.
10.0
really awful
Crashes / Fires:
1 / 0
Injuries / Deaths:
1 / 0
Average Mileage:
18,090 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.
Engine stalled while starting to driving into a parking space. Was able to immediately restart vehicle and move out of the traffic lane and fully into the parking spot. Service department indicated that they would not do anything unless they were able to replicate the problem on a short test drive.
My wife and I purchased a new 2006 Jeep Commander lt with a 5.7 liter V8 on July 24, 2006. Four days later we went on a road trip from Washington DC to boston, MA. Just outside New York city, the Commander stalled (went dead, no power brakes, steering) in rush hour traffic. Scared us both. Managed to get to the side of the road. Put it in park and turned the ignition and started the Commander and continued driving. The Commander had less than 800 miles on it. We called the dealer. They said to bring it in when we got back. The next day on our way back home we stopped in a Jeep dealership in mystic conn. They ran a diagnostic and came up with 2 codes P1684 and P0884. They cleared the history, tested again and found nothing. We took it in to the dealership on Monday July 31. They said that they could not duplicate the problem. The car stalled again on August 15th, 2006. The Commander now has 1350 miles and is back in the shop and the dealership doesn't know what the problem is. We called daimler Chrysler customer service to lodge a compliant, the customer service advisor said that he had not ever heard that there was a stalling problem with the 2006 Commanders. My wife is afraid that the Commander will stall again and cause a serious accident and kill someone including us. We believe there is a serious problem with this car and others according to others on jeepforum.com.
: the contact stated that the vehicle stalled unexpectedly after approaching a stop sign on 06/20/06. The contact depressed the accelerator which made the vehicle leap forward, then stall out. The 2nd incident also occurred during attempted acceleration. On 07/13/06 the vehicle stalled unexpectedly while cruising 55 mph on a dry and flat road surface. There were no warnings prior to the three incidents. The contact pulled over and contacted the dealer. The engine restarted with no delay after all 3 incidents. The vehicle was taken to the dealer on 07/13/06 who could not duplicate the problem. The dealer has attempted to repair the vehicle 3 times but could not determine the cause of the problem. The vehicle was equipped with an automatic transmission.
Took new car in for the first oil change. Drove 30+ miles and the engine disintegrated requiring a total engine replacement. Dealer denies any wrongdoing and blames it on a manufacturing defect from Chrysler. This is a new Jeep Commander 4.7L 2006 vehicle.
A D V E R T I S E M E N T S
- Portland, OR, USA