Consumer Complaint Detail

FORD / EXCURSION / 2001

Recalls
0 Injured
Investigations
0 Death
Complaints
No Fire
Components - Details
NHTSA Complaint Number: 000057168 Incident Date: Oct, 23 2000
Consumer's City: AUSTIN Consumer's State: TX
Vehicle Transmission Type: Manufacturers Name: Ford Motor Company
Model Name: EXCURSION Model Year: 2001
Vehicle Involved in a Crash: No Component's Description: Vehicle speed control
Vehicle Involved in a Fire: No Persons Injured: 0
Vehicle's VIN#: 1FMNU42F91E Date added to File: May, 25 2021
Date Complaint Received: Oct, 23 2000 Complaint Type: IVOQ
Incident Reported To Police: No Purchase Date: Aug, 31 2000
Was Original Owner: Yes Anti-lock Brakes: Yes
Number of Cylinders: 0 Date of Manufacturer: -
Was Vehicle Towed: - Description of the Complaints: The cruise control was activated at aproximately 65-70mph. after applying the foot brake the vehicle failed to disengage the cruise control. i was fortunate enough to be able to reduce the speed even as the rpm continued to stay at 2000 rpm, although it took a much greater distance than normal. i brought the vehicle to a stop and the engine continued to rev at 2000 rpm. the cancel button on the steering wheel would not disengage and neither would the brake. i pulled to the side of the road and placed the transmission in park, and the engine continued to rev at 2000 rpm. i applied more fuel and was able to rev the engine between 2000 and 3000 rpm only. the cancel button on the steering wheel continued to be inoperable. finally at one point i released my foot from the brake pedal and the rpm then dropped to the normal idle range. i then opened the hood and inspected the engine compartment but was unable to see anything significant to have caused this to have occurred. i consider myself quite lucky to have been in the particular driving situation where i had ample room to bring the vehicle to a stop without having been involved in an accident or to have involved others in an accident. having worked with computers for most of my life i suspect that the code was somehow fouled up that may or may not be involved in monitoring the status of the cancel switches...just a hunch. have there been any other reports of such an incident on ford excursion or ford f250 from which this model is derived?