I bought this 2000 Nissan Altima new. Since approximately December of '03 the instrument cluster has repeatedly (too many times to keep track of) malfunctioned at arbitrary times giving either no info (gauges all go to 0) or incorrect info (130 mph at 1K RPM w/no water temp and suddenly full tank of gas). Problem can last any where from minutes to 24 hours+. the cruise control also malfunctions whenever this occurs. First took to dealer on 12/31/03, they could not diagnose problem, told me to bring it back while malfunctioning. Finally was able to get the car while malfunctioning to same dealership on 8/1/05. Problem has started to increase in frequency and duration. The second they hooked diagnostic equip to it the cluster corrected. They kept for 2 days, did not malfunction again so they could not diagnose 100%. they want to try replacing the speedometer head at $320, but 1) can't guarantee it will solve problem and 2) can't get part. They estimate 6-8 wks minimum to get part. When I went to leave dealership cluster malfunctioned showing no information, but no technician was available to diagnose. Showed zero on all gauges except gas which arbitrarily read 3/4 tank for entire 20-25 mile trip home. This car is an accident, or worse, waiting to happen.

- Cedarville, OH, USA

My vehicle is a 2000 Nissan Altima SE. (also I have heard there are other Nissan with this problem not just Altima) the problem is the guages on the instrument panel failing during operation, ie. Speedometer, tachometer, gas guage, and temp guage. The first time it happened and just like every other time it happens there is nothing different the guages will just shut off and normally fall to the zero postion. Sometimes the will freeze in place. After the first month I owned the car (bought as a preowned vehicle) the check engine light came on during the guage failures I had the code checked and it was determined the speed sensor was bad. I bought and replaced the speed sensor with an oem part. However the guage failure was not fixed it still happens. The incident date started 21feb2003 and still persists and the numbers of failures I haven't kept count but about average of everyother day it goes out.

- Toledo, OH, USA