| Components - Details | |
|---|---|
| NHTSA Complaint Number: 005037174 | Incident Date: Sep, 04 2005 |
| Consumer's City: ARLINGTON | Consumer's State: MA |
| Vehicle Transmission Type: | Manufacturers Name: Toyota Motor Corporation |
| Model Name: PRIUS | Model Year: 2005 |
| Vehicle Involved in a Crash: No | Component's Description: Engine and engine cooling |
| Vehicle Involved in a Fire: No | Persons Injured: 0 |
| Vehicle's VIN#: | Date added to File: May, 23 2021 |
| Date Complaint Received: Sep, 04 2005 | Complaint Type: IVOQ |
| Incident Reported To Police: No | Purchase Date: - |
| Was Original Owner: No | Anti-lock Brakes: No |
| Number of Cylinders: 0 | Date of Manufacturer: - |
| Was Vehicle Towed: - | Description of the Complaints: Possibly relevant to current prius software reliability investigation number : pe05029 i spoke to gilles labelle of westboro toyota in westborough massachusetts regarding the toyota prius (this was a pre-sales conversation; i do not at present own a prius though until this conversation i was very close buying one; now i find myself taking a step back to ensure i've done my own due diligence). he mentioned the use of a reset sequence to "reboot" the car in the event of problems as a way to avoid the need to have the car serviced; i asked him how often he had to reboot his own prius; he didn't answer directly but instead said that he had helped about 100 customers through the reboot process. i am a operating systems software engineer by profession and was alarmed at this "just hit reset" attitude towards systems failures; ideally crashes in the field should be rare enough that each one can be root-caused, rather than shrugged off. *jb |
