- March 13: Stolen Kia Lawsuit Says Matthew P. Moshi Was Killed By Kia Design Flaws news | 15 days ago
- March 9: Kia Turbo Engine Problems Cause K900 and Stinger Recall recalls | 19 days ago
- March 3: Kia Sedona 3.3L Engine Problems May Be Investigated investigations | 25 days ago
- March 3: Kia Telluride Headlight Recall Involves 2020 Model Year recalls | 25 days ago
- February 29: Hyundai Kia Theft Lawsuit Preliminarily Approved news | 28 days ago
CarComplaints.com Notes: The 2012 Kia Sedona received a poor rollover rating from the IIHS.
10.0
really awful- Typical Repair Cost:
- No data
- Average Mileage:
- 30,000 miles
- Total Complaints:
- 1 complaints
Most Common Solutions:
- replace pcm (1 reports)
engine problem
Helpful websites
- No one has added a helpful site for this 2012 Sedona problem yet. Be the first!
A D V E R T I S E M E N T S
May 14 2013, the van had just under 30,000 miles and I as was driving with my 2 children, I lost all power. Dash lights also came on (check engine, battery, etc.). I pulled off to a side street and it was very difficult to steer and the brakes were not working. I tried restarting it to see if that would clear any problems. It did start but the check engine light, battery light and some others were still on. I called a tow truck. As I was waiting for the truck I decided to try starting it again. This time it would not start. It was towed to the dealer.
The dealer told me that the PCM was out and needed to be replaced. In the end the PCM, fuel pump and front area module were replaced. The PCM needed to be replaced twice before I got the van back.
Called the service dept. back on May 24, 2013, told them that ESC light was coming on and I wanted to make sure that it was safe to drive.
May 25, 2013 the ABS and brake light came on.
May 26, 2013 the door locks started to lock and unlock while I was in the van.
May 27, 2013 the “D†light in the odometer area would not stay lit.
May 28, 2013 dropped van off at dealer for repair.
May 29, 2013 picked the van back up. Was told on the phone that it was a terminal problem.
- francisk, Champlin, MN, US