definitely annoying
Crashes / Fires:
0 / 0
Injuries / Deaths:
0 / 0
Average Mileage:
34,716 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.

2005 Toyota Prius brakes problems

brakes problem

Find something helpful? Spread the word.
Get notified about new defects, investigations, recalls & lawsuits for the 2005 Toyota Prius:

Unsubscribe any time. We don't sell/share your email.

2005 Toyota Prius Owner Comments

problem #11

Sep 232014


  • 103,000 miles


The contact owns a 2005 Toyota Prius. While driving approximately 25 mph, the vehicle made a loud popping noise. The contact noticed that the steering wheel was tilted and the anti skid and anti lock braking system warning indicators illuminated. When the contact attempted to merge to the emergency lane, the steering wheel separated from the steering column and caused a complete loss of steering ability. The vehicle was towed to the dealer and the technician stated that the failure was unrelated to NHTSA campaign number: 12V537000 (steering). The vehicle was repaired. The manufacturer was notified of the failure. The approximate failure mileage was 103,000.

- San Miteo, CA, USA

problem #10

Jul 122010

(reported on)

Prius 4-cyl

  • miles
2005 Toyota Prius. Consumer states brake problems the consumer stated within a month of purchasing the vehicle, she noticed the brakes would engage, then fail, then engage again. The vehicle was taken to the service department, but they were unable to duplicate the problem.

- Saint Louis, MO, USA

problem #9

Apr 012006

Prius 4-cyl

  • 3,370 miles
I have reviewed my service records and it is quite clear that I have had problems with the "electrical" system in my car since April 2006 @ 3,370 miles. This was also the same time it began to accelerate from a stopped position for the first time, when I noticed that the braking system began to "feel" different, when the car began "slipping" on perfectly dry roads, and when my steering wheel would lock up. I find it difficult to believe that the failure of my brakes and my intermittent acceleration issues are not somehow related to the cars "computer" system and not mechanical issues. I have filed complaints with Toyota for these issues (cases # 200807100210, 200811030088). I experienced my first braking issue on 27-Jun-2008 (25,133 miles). While I was able to bring the car to a stop eventually, the slowing of my car was a very gradual process requiring heavy pressure on the brake with minimal braking response. I went to the Toyota dealership. The dtc code at the time was C1247 with "code 179" stored, there was "no brake assist." The dealership reset the memory and reinitialized the linear solenoid valve and calibration. The brakes were reported to have returned to "normal." On 09-Jul-2008 (25,551 miles), I returned to the dealership because my brakes failed again. This time my brake failure resulted in a car accident (the person I hit stated at the time of the accident he had whiplash but he never contacted me afterwards). Toyota replaced the skid control ECU and rechecked operation reassuring me once again that the brakes had returned to "normal." On 03-Nov-2008 (29,575 miles) as I was driving over 65 on a major highway my brakes again failed (dtc C1247, code 179). Toyota case #08300402. At this point the repair shop replaced the brake stroke sensor. I am concerned because my car had an acceleration issue on 13-Feb-2010 and I find it to be "slipping" again on dry roads. Similar problems to those I had before my brakes failed. Please help. Updated IVOQ 04/02/10 updated 04/08/10.

- Berkeley, CA, USA

problem #8

Jan 102010

Prius 4-cyl

  • 107,415 miles


The contact owns a 2005 Toyota Prius. He was driving 30 mph on a rainy day when he started to apply the brakes and the vehicle surged. The dealer test drove the vehicle and stated that the ABS needed to be replaced. No repairs were made to the vehicle. The failure mileage was 107415. The current mileage was unknown. Updated 4/5/10 updated 07/01/10.

- Brea, CA, USA

problem #7

Sep 102009


  • 45,000 miles
ABS system failure while preparing to stop from 40 mph in 05 Toyota Prius last September. Had at least three occurrences during the summer of the brake pedal going quickly and easily to the floor, making a "thunk" noise, sounding and feeling like metal on metal, but this would not happen again when I stepped on the brakes again immediately, and certainly didn't happen for my mechanic to hear. Toyota diagnosed a computer failure that cost me $2000 to replace.

- Webster, MA, USA

problem #6

Nov 132008


  • 53,200 miles
Driving down a hill next to our home. The red brake light came for a short period at the top of the hill. When brakes were applied more aggressively towards the bottom of the hill they did not respond. The brake pedal was pushed to the floor (the road was dry and the temp. Was in the 60S, there were no leaves etc on the road) and the brakes still did not respond sufficiently to stop the car...it slowed us some but we would have run into the car in front of us if we did not swerve sharply to avoid it and then drive into an adjacent parking lot. The car was turn off and then on again. When it was turned on again, the brakes responded correctly. The car was immediately brought to the Toyota dealership for inspection. The mechanic said that he had found an error code (the ABS system) in the commuter and they tech's at the dealership said that they had seen this happen with a few other Prius (this is what I found concerning?there were also similar incidents posted on the web). No mechanical problem was found with the brakes. The mechanics spoke to Toyota head office (??) and they were told to reset the computer and run a number of tests. The car responded correctly after the reset and it was given back to me no mechanic problem was found..

- San Diego, CA, USA

problem #5

Jan 082007

Prius 4-cyl

  • Automatic transmission
  • 12,000 miles


Every time our 2005 Prius is operated in rain snow slush the rear brakes are so grabby that it makes the car unstable. On dry days brakes are fine when you start out on wet days the antilock brakes act normal as time goes on they get more and more grabby to where it is unsafe.

- Sicklerville, NJ, USA

problem #4

Dec 042006

Prius 4-cyl

  • Automatic transmission
  • 18,000 miles
- the contact has a 2005 Toyota Prius, with an odometer reading of 18000 miles complained about a a massive brake failure. The contact stated that on 12-4-06, under dry conditions, while driving at 25 mph, she tried to apply the brakes which failed. The contact was able to use the emergence brake to stop the vehicle without a crash. The contact had the vehicle towed to the dealer., she had taken the vehicle to the dealer several times because the brake warning light kept turning on while she was driving. The dealer told her that she did not have a problem with her braking system. The dealer had the regional Toyota representative check the vehicle, who was unable to find a problem as well. The contact also stated that when the brake light turned on the cruise control was inoperable.

- Compass, OH, USA

problem #3

Dec 142006


  • Automatic transmission
  • 25,568 miles
On December 14th, 2006, I was driving my 2005 toytota Prius from berkeley, ca to monterey, ca. At 18 miles outside of monterey. Ca, and while still on the freeway traveling at 65 mph, a continuous loud and high frequency buzzer went on and the panel warning lights went on including the red brake light on the panel. I pulled off a freeway exit near castroville, ca and stepped on my brakes to slow into the exit, the brakes did not work until I stomped on them with much pressure. I turned off the engine, waited a few minutes and turned the engine back on. I drove back onto the freeway to monterey, ca at approximately 35-40 mph, when I drove into town once again the buzzer and red brake lights went on.I pulled over to the curb and had to stomp on the brake again. The car was towed to a Toyota dealership in seaside ca. The vehicle was tested and I was shown a test form indicating that there was a computer malfunction listed as CM1300. The conclusion of the mechanic was that it was possible that a replacement part may be needed which would take a few days and that there was some reference to my use of skid control at the time of the malfunctions that I experienced. I was told that I could drive the car home and that I should stop every 15 miles to stop and reboot the car again to prevent the malfunction from occurring again. I was told that if the malfunction occurred again that I should stomp on the brake really hard and the skid control would somehow be activated. I made it home safely and drove as advised to. I took the car the next morning to berkeley, Toyota and was informed that the test drive and their testing showed no malfunction and that I should take the car home, but the malfunction might occur again. I find this an unsatisfactory response. I am extremely fearful of driving the car without an explanation to why the car malfunctioned in a very dangerous way where it was difficult to use my brakes!!

- Berkeley, CA, USA

problem #2

May 162006

Prius 4-cyl

  • Automatic transmission
  • 14,318 miles
While stopped at a stop light, my brakes failed and pedal released to the floor. Toyota of visalia service manager stated that computer showed codes C1357 and detail code 28. They were unable to determine case of brake failure, or duplicate problem. Although I requested they replace components that may be responsible for the incident, given the catastrophic possibilities associated with brake failure at high speeds, they refused.

- Visalia, CA, USA

problem #1

Nov 082005

Prius 4-cyl

  • Automatic transmission
  • miles
The contact stated while stopping the brakes released. The parking brake was used to stop the vehicle. The vehicle was taken to the dealership, but they could not duplicate the problem. There have been no repairs made at this time.

- Victorville, CA, USA

Not what you are looking for?