| Components - Details | |
|---|---|
| NHTSA Complaint Number: 005048592 | Incident Date: Jun, 05 2005 |
| Consumer's City: BALLWIN | Consumer's State: MO |
| Vehicle Transmission Type: AUTO | Manufacturers Name: Toyota Motor Corporation |
| Model Name: AVALON | Model Year: 2005 |
| Vehicle Involved in a Crash: No | Component's Description: Power train:automatic transmission:control module (tcm, pcm) |
| Vehicle Involved in a Fire: No | Persons Injured: 0 |
| Vehicle's VIN#: 4T1BK36B15U | Date added to File: May, 23 2021 |
| Date Complaint Received: Dec, 02 2005 | Complaint Type: IVOQ |
| Incident Reported To Police: No | Purchase Date: Jun, 05 2005 |
| Was Original Owner: Yes | Anti-lock Brakes: Yes |
| Number of Cylinders: 6 | Date of Manufacturer: - |
| Was Vehicle Towed: - | Description of the Complaints: Since purchasing the avalon in early june, i have been frustrated with how the car operates between 20 and 40 miles per hour. the car does not always know what gear it needs to shift into. it will frequently race 1000 rpm ahead without any change in speed. then suddenly it will accelerate and the rpm's will drop back to normal rpm. it seems to happen most often in rush traffic when trying to change lanes. the hesitation in acceleration will cause me to lose most of my margin of safety in the process of changing lanes. in this regard, the car is not safe. there is no way to predict when the problem will occur, and therein, lies the safety hazard. it would seem that the last effort by the service department to update my computer programming failed to achieve any level of improvement to my satisfaction with one exception. since the first computer upgrade, i have not experienced the complete loss of gear at high speeds. is this a problem in all 2005 avalons? is toyota aware of the problem and do they have plans to resolve it? serviced on friday, october 21. toyota reset the computer learning back to factory default. technical support in ca explained that there are no current plans to address the issue. once the learning process develops a bad pattern, it must be reset back to factory default and the relearning started over. the problem started all over again and there is no "unlearning" the problem. *jb |
