Owner-reported complaints naming the driver-assistance system, filed with NHTSA
Data refreshed
Driver assistance reportsComplaints are reports submitted to NHTSA by owners and drivers. NHTSA does not verify most reports before publishing them, and a complaint does not establish that a defect exists. Volume is influenced by how many of a vehicle were sold, how long it has been on the road, and how much attention an issue has received.
16
Latest Jul 8, 2011
Share of all reportsThis category as a share of every owner report on file for this model year. One report can name more than one component, so the categories overlap.
7%
of 233 total
Crash or fire reportedReports in this category whose submitter recorded that a crash or a fire occurred. The reporter's own answer on the NHTSA form, not a verified finding.
9
Injuries or deaths reportedTotals the submitters entered on their own reports in this category. Not verified by NHTSA and not a casualty statistic.
1
What this page shows
Reports naming forward-collision avoidance, lane keeping, back-over prevention, cruise control and related electronic driver-assistance systems. Every record below is an owner-reported complaint about the 2000 Ford F-250 Sd submitted to NHTSA — not a confirmed defect, not a recall and not a manufacturer bulletin. 16 reports on file name it.
Complaints are reports submitted by owners and drivers to NHTSA. They are not verified and do not establish that a defect exists.
Owner reports naming driver-assistance
Shown in the owner’s own words, exactly as filed
AirbagsBody & structureDriver assistance
Filed Jul 8, 2011
WIRING IN THE STEERING COLUMN HAS BEEN COMING APART AND PIECES FALLING OUT OF THE COLUMN. THE CRUISE CONTROL, AIRBAG AND HORN ARE ALL NOT WORKING AS A RESULT OF THIS FAILURE. IT IS A FLAT (RIBBON WIRE) WIRE THAT APPEARS TO RUN FROM THE STEERING WHEEL THROUGH THE CENTER OF THE COLUMN. *TR
NHTSA ID
10411562
Incident
Jul 14, 2009
Mileage
172,000 mi
Driver assistance
Filed Jul 2, 2011
Fire reported
OUR UNATTENDED FORD F-250 PICKUP CAUGHT FIRE IN OUR CONSTRUCTION YARD. THE SUBSEQUENT FIRE COMPLETELY DESTROYED IT AND AN ADJACENT VEHICLE. THE VEHICLE HAD BEEN PARKED AND NOT MOVED FOR DAYS. I WAS THE LAST PERSON TO DRIVE IT AND I AM NOT AWARE OF ANY DEFECTS THE LAST TIME IT WAS DRIVEN. VIDEO SURVEILLANCE DID NOT CAPTURE THE FIRE OF THE FIRST VEHICLE, HOWEVER IT DOES PROVIDE A TIME LINE FOR THE EVENT AND SUBSEQUENT FIRE OF THE ADJACENT VEHICLE. *TR
NHTSA ID
10410316
Incident
Jun 30, 2011
Mileage
200,000 mi
Driver assistanceEngine
Filed Mar 13, 2011
THERE WERE NO PARTICULAR EVENTS LEADING UP TO THE FAILURE. WHEN STARTING THE VEHICLE ENGINE, THE ENGINE WILL NOT KEEP RUNNING ON ITS OWN. TO KEEP THE ENGINE RUNNING LIGHT PRESSURE MUST BE APPLIED TO THE ACCELERATOR TO MAINTAIN AN 800 TO 1000 RPM. THE VEHICLE CAN BE DRIVEN, HOWEVER, THE LEFT FOOT MUST BE USED FOR BRAKING SINCE THE RIGHT FOOT MUST BE USED TO KEEP CONTINUOUS PRESSURE ON THE ACCELERATOR TO PREVENT THE ENGINE FROM STALLING. THE ACCELERATOR ISSUE WILL SOMETIMES CORRECT ITSELF AFTER THE ENGINE HAS BEEN RUNNING FOR A PERIOD OF TIME AFTER STARTUP, HOWEVER, IN MOST CASES THIS PRESENTS A DANGEROUS SITUATION. WHEN THE ENGINE IDLE CORRECTS ITSELF, THE RPMS WILL TAKE A +1000 RPM JUMP FROM THE CURRENT RPM POSITION. FOR EXAMPLE, IF YOU ARE STOPPED AT A STOP LIGHT ONLY A FEW FEET FROM THE CAR IN FRONT OF YOU WITH LIGHT PRESSURE ON THE BRAKE, THE JUMP FROM 1000 RPM TO 2000 RPM MAY SEND THE VEHICLE LURCHING FORWARD REAR-ENDING THE VEHICLE IN FRONT OF YOU IF YOU DO NOT SLAM ON THE BRAKES QUICKLY! ANOTHER SITUATION THAT HAS ALSO CAUSED A "CLOSE CALL" IS WHEN DRIVING THE VEHICLE 5 MPH AT 1000 RPM IN A PARKING LOT. THE REASON THIS SITUATION IS EVEN MORE DANGEROUS IS DUE TO THE FACT THAT THE BRAKE IS TYPICALLY NOT BEING APPLIED AT ALL, SO WHEN THE +1000 RPM JUMP TO 2000 RPMS OCCURS IT CAN SEND YOUR VEHICLE LURCHING FORWARD INTO ANOTHER VEHICLE OR PEDESTRIAN THAT IS CROSSING IN FRONT OF THE VEHICLE. I ATTEMPTED TO FIX THE FAILURE BY REMOVING THE AIR BREATHER ASSEMBLY AND CLEANING THE INTAKE THROAT WITH CARBARATOR CLEANER, HOWEVER, THIS DID NOT RESOLVE THE FAILURE. *TR
NHTSA ID
10390000
Incident
Dec 15, 2010
Mileage
117,000 mi
Driver assistance
Filed Sep 1, 2009
Fire reported
1. FAILURE OF CRUISE CONTROL IT WOULD STOP WORKING THEN STOP 2. JUST WHEN TRIED TO USE IT WOULD EITHER WORK OR NOT THEN IT CAUGHT FIRE IN THE DRIVE WAY 3. NOTHING YET WE THINK THE TRUCK IS TOTALED OUT. *TR
NHTSA ID
10282546
Incident
Aug 31, 2009
Driver assistance
Filed Aug 18, 2008
Fire reported
CRUISE CONTROL CEASED WORKING. SINCE THIS DID NOT APPEAR TO BE A SERIOUS ISSUE, OTHER THAN SIGNIFICANT DISCOMFORT ON LONG TRIPS, AND THE TRUCK CONTINUED TO OPERATE ACCEPTABLY EXCEPT FOR THE CRUISE CONTROL, I CONTINUED DRIVING. APPROXIMATELY THREE WEEKS LATER SMOKE WAS DETECTED WHEN TRUCK WAS STARTED. UPON FURTHER INSPECTION (STILL IN MY DRIVEWAY, TRUCK STILL RUNNING), FLAMES WERE SEEN UNDER THE HOOD AT THE WIRING BESIDE THE MASTER CYLINDER. THE FIRE SOON STOPPED, AND THE WIRING WAS COOL. TRUCK WAS STILL SEEMED TO OPERATE PROPERLY, INCLUDING BRAKES, SO I PROCEEDED WITH MY PLANS AND DROVE THE TRUCK. THE NEXT MORNING AFTER THE INITIAL FIRE INCIDENT, A SIGNIFICANT AMOUNT OF SMOKE CAME OUT FROM UNDER THE HOOD OF THE TRUCK WHEN STARTED, CAUSING BRIEF BUT WELL VOICED DISCOMFORT FROM MY DAUGHTER. THE SMOKE CAME FROM THE SAME WIRING. THE FOLLOWING MORNING, THE SECOND DAY AFTER THE INITIAL FIRE INCIDENT, I TOOK THE TRUCK TO AN AUTO REPAIR SHOP (MONDAY MORNING). THE OWNER TOLD ME THERE WAS A RECALL FOR THE SPEED CONTROL SWITCH AND I SHOULD TAKE IT TO FORD. FORD TOLD ME THERE WAS NO RECALL FOR THIS SWITCH FOR MY TRUCK BECAUSE IT IS A DIESEL. THE RECALL 06V286000 MATCHES THE CONDITIONS AND DESCRIPTION IN THAT THE CRUISE CONTROL SWITCH COULD OVERHEAT, RESULT IN SMOKE, OR BURN IN AN UNDERHOOD FIRE. AFTER RETURNING TO THE AUTO REPAIR SHOP, THE SWITCH WAS REPLACED AND A FUSED WIRING HARNESS WAS INSTALLED, PURCHASED FROM FORD. THE FORD DEALERSHIP I HAD CONTACTED, THE ONE WHERE THE PART WAS SUBSEQUENTLY PURCHASED FROM, HAD 1,200 OF THEM IN STOCK, ACCORDING TO THE PHONE CONVERSATION I OVERHEARD. *TR
NHTSA ID
10238811
Incident
Aug 16, 2008
Mileage
205,426 mi
Driver assistance
Filed Mar 4, 2008
Fire reported
TL*THE CONTACT OWNS A 2000 FORD F-250 SD. THE CONTACT STATED THAT HIS VEHICLE CAUGHT FIRE WHILE IN HIS DRIVEWAY. THE FIRE ORIGINATED IN THE SENSOR OF THE MASTER CYLINDER. HE BELIEVES THAT THE VEHICLE SHOULD HAVE BEEN INCLUDED IN NHTSA CAMPAIGN ID NUMBER 06V286000 (VEHICLE SPEED CONTROL), ALTHOUGH IT WAS A DIESEL ENGINE. FORD STATED THAT HIS VEHICLE WAS NOT INCLUDED IN THE RECALL AND THE CONTACT WOULD NOT RECEIVE ANY REIMBURSEMENT FOR DAMAGES. THE VEHICLE WAS NOT DESTROYED. THE PURCHASE DATE WAS UNKNOWN. THE CURRENT AND FAILURE MILEAGES WERE 130,000.
NHTSA ID
10220044
Incident
Mar 3, 2008
Mileage
130,000 mi
Driver assistance
Filed Feb 15, 2008
TL*THE CONTACT OWNS A 2000 FORD F250 HD. THE CONTACT RECEIVED A FORD SAFETY RECALL NOTICE FOR THE VEHICLE SPEED CONTROL IN FEBRUARY OF 2008. THE SPEED CONTROL WAS DISCONNECTED AT THAT TIME, AND HE HAS BEEN INFORMED EVERY MONTH THEREAFTER THAT THE PART WILL NOT BE AVAILABLE UNTIL THE FOLLOWING MONTH. THERE HAD BEEN NO FAILURE TO DATE. THE RECALL NUMBER WAS UNKNOWN. THE CURRENT MILEAGE WAS 57,000.
NHTSA ID
10218114
Incident
May 31, 2000
Driver assistance
Filed Oct 26, 2007
Fire reported
WHILE I WAS DRIVING MY FORD F-250 DIESEL OF 2000 I SMELL LIKE A OIL BURNED. WHEN I REACHED MY HOUSE I OPENED THE HOOD BUT I ONLY SAW SOME SMOKE COMING NEAR THE BRAKE RESERVOIR. I SAID TO MY SON THAT TURNED "ON" THE VEHICLE AND THEM I SAW WHEN THE ELECTRICAL CONNECTION NEAR THE BRAKE SYSTEM BEGIN TO BURN IN FIRE. WE TURNED "OFF" THE VEHICLE AND EXTINGUISHED THE FIRE WITH WATER. I FOUND IN THE SERVICE MANUAL OF THE VEHICLE THAT THE CONNECTION IS OF THE BRAKE PRESSURE SWITCH THAT IS USED TO DEACTIVATE THE SPEED CONTROL. I CALLED THE FORD COMPANY AND EXPLAINED THE SITUATION BUT WHEN I GAVE THEM MY VEHICLE VIN NUMBER THEY SAID THAT THERE ARE NO RECALLS FOR THAT SITUATION AND THAT REFER THE CASE TO MY INSURED COMPANY. I REPORTED THE SITUATION TO MY INSURED COMPANY "SEGUROS MULTIPLES DE PUERTO RICO". *TR
NHTSA ID
10207041
Incident
Oct 25, 2007
Mileage
93,426 mi
Driver assistance
Filed Aug 6, 2006
Fire reported
I OWN A 2000 FORD F-250 DIESEL IT HAS NOT BEEN RECALLED BUT IT CAUGHT ON FIRE AT THE CRUISE CONTROL CANCEL SWITCH LIKE THE OTHERS, FORD NEEDS TO RECALL DIESELS ALSO. I HAVE THE RECEIPT FROM A LOCAL REPAIR SHOP & ALSO HAVE THE BURNT SWITCH. *JB
NHTSA ID
10164643
Incident
Jul 6, 2006
Mileage
226,000 mi
Driver assistance
Filed Jul 13, 2006
DT*: THE CONTACT STATED THAT THE BRAKE FLUID LEAKED INTO THE SPEED CONTROL MODULE, CAUSING THE CRUISE CONTROL TO FAIL. THE VEHICLE WAS TAKEN TO A SERVICE DEALER, WHERE THE PROBLEM WAS DETERMINED TO BE CAUSED BY THE SAME ISSUE THAT CAUSED NHTSA RECALL #05V388000, RELATING TO THE VEHICLE SPEED CONTROL. THE VIN WAS NOT INCLUDED IN THE RECALL. UPDATED 8/16/2006 - THE VEHICLE WAS REPAIRED ON 7/14/2006. *NM
NHTSA ID
10162320
Incident
Apr 1, 2006
Mileage
56,000 mi
Driver assistance
Filed Aug 18, 2005
MY 2000 F-250 SUPER DUTY HAD THE FAULTY CRUISE CONTROL DEACTIVATION BURN UP. THE F150 HAS THE RECALL BUT NOT THE 250, EVEN THOUGH ITS THE SAME FAULTY PART ON BOTH VEHICLES. THERE WAS A LOT OF SMOKE, BUT NO VISIBLE FLAMES. I WAS ABLE THE UNPLUG THE DEVICE BEFORE ANY MAJOR DAMAGE HAPPENED. *NM
NHTSA ID
10133355
Incident
Jul 30, 2005
Mileage
209,000 mi
Driver assistanceEngine
Filed Jul 8, 2005
Crash reported1 injury reported
DT: WHILE BRAKING THE VEHICLE LURCHES FORWARD AND THEN IT SHUTS DOWN, WHICH CAUSES LIMITED STEERING AND BRAKING ABILITIES. THE CONSUMER HAS TAKEN THE VEHICLE TO THE DEALER APPROXIMATELY THREE TIMES, AND WAS TOLD THAT THEY COULDN'T DO ANYTHING ABOUT IT UNLESS THE PROBLEM OCCURRED FOR THEM. ON MAY 30, 2005 THE CONSUMER WAS DRIVING THE VEHICLE AND HAD TO BRAKE BECAUSE OF THE TRAFFIC IN FRONT OF HIM, WHEN THIS OCCURRED, THE VEHICLE LURCHED FORWARD AND THE ENGINE JUST CUT OUT, LIKE IT WAS NEVER STARTED. THIS CAUSED THE CONSUMER'S VEHICLE TO REAR END THE VEHICLE IN FRONT OF HIM. THE VEHICLE WAS TAKEN TO A BODY SHOP AND IT WAS REPAIRED. THE CONSUMER SPOKE TO FORD AND WAS TOLD THAT THERE WAS NOTHING THEY COULD DO. *AK *JB *NM PER CONSUMER, NONE OF THE ABOVE IS ACCURATE. THE CONSUMER WROTE: WHILE BRAKING, THE RPM REVVED UP, THE VEHICLE LURCHED FORWARD, THEN THE RPM DROPPED AND THE ENGINE HAD SHUT DOWN. THE CHECK ENGINE LIGHT ILLUMINATED. IT WOULD TAKE SEVERAL ATTEMPTS TO START THE VEHICLE . THIS WOULD OCCUR INTERMITTENTLY. EACH TIME THE CONSUMER HAD TAKEN THE VEHICLE IN FOR REPAIRS, THE DEALER WOULD BE UNABLE TO FIND THE PROBLEM. OTHER PROBLEMS: THE CRUISE CONTROL WAS INOPERATIVE AND THE VEHICLE WOULD DIE WHEN THE BRAKES WERE APPLIED AT TIMES. FORD RECALLED THE SAME MAKE MODEL YEARS 2003-2005. THE CONSUMER FELT THAT THE RECALL STARTED WITH HIS VEHICLE'S YEAR MAKE AND MODEL. *SC *JB
NHTSA ID
10124962
Incident
Feb 13, 2005
Mileage
66,581 mi
Driver assistance
Filed Jun 9, 2005
Fire reported
OCCUPANTS WERE DRIVING THE VECHICLE WHEN ALL OF A SUDDEN IT STARTED TO FLAME UP. THE FIRE WAS PUT OUT. BUT BEFORE THAT WAS COMPLETED THE FIRE HAD CONSUMED THE WIRING HARNESSES, FUSE PANEL, CRUISE DEACTIVACTION MECH. AND MISC. OTHER COMPONENTS, COMPUTER ETC. SHORTLY AFTER THIS FORD WAS ON THE NEWS ABOUT A RECALL OF THE EXACT THING THAT HAD HAPPENED TO THIS TRUCK. AT THE TIME THERE WAS ONLY LIABILITY INSURANCE ON THE VECHICLE. IT WAS PAID FOR... AND THAT IS ALL THAT IS REQUIRED. EXCEPT FOR THE FACT WHEN FORD DON'T WANT TO COVER THEIR MISTAKES... IN CONCLUSION FORD SAYS IT IS NOT THE RIGHT TYPE OF TRUCK BUT IF THE CRUISE MECHANISIM IS WHAT CAUSED THE FIRE AND THEN THEY DO A RECALL I THINK THEY SHOULD BE RESPONSIBILE FOR THE ITEM IN QUESTION, NO MATTER WHAT YEAR THEY SAY......
NHTSA ID
10124827
Incident
Nov 22, 2004
Mileage
77,228 mi
Driver assistance
Filed Mar 2, 2005
Fire reported
PARKED VEHICLE ABOUT AND 25 MINUTES LATER SMOKE WAS COMING FROM UNDER THE HOOD OF THE VEHICLE. OPENED THE HOOD TO FIND THE CRUISE CONTROL SERVO WAS SMOKING. DISCONNECTED THE WIRES TO THE SERVO AND IT STOPPED. HAAD THE BURNED PART FOR INSPECTION. DURING THE TRIP BEFORE THE FIRE THE CRUISE CONTROL LIGHT ON THE DASHBOARD WAS COMING ON AND OFF AND WAS NOT USED. *AK THE CONSUMER STATED THAT THE CANCEL SWITCH WAS LEAKING. *TC
NHTSA ID
10109292
Incident
Nov 20, 2004
Mileage
128,000 mi
AirbagsDriver assistanceElectrical
Filed Jun 1, 2004
APRIL 2004. FAULTY CABLE IN STEEING COLUMN. THIS CABLE CAUSES A FAILURE WHICH DISABLES THE DRIVER SIDE AIR BAG IT ALSO DISABLES THE HORN AND CRUISE CONTROL. AFTER GOING TO SEVERAL DISCUSSION FORUMS THIS IS A COMMON PROBLEM AFFECTING 100'S PERHAPS 100 OF FORD SUPER DUTY F250, F350 VEHICLE. PER THE CHAT PAGES FORD WAS ABLE TO GET AROUND THIS ISSUE BY STATING THE FAULTY CABLING EFFECTS THE CRUISE CONTROL ONLY. THIS IS A MISCONSEPTION. ALSO BASED ON THESE CHAT PAGES THIS PROBLEM EFFECTS MOST F250,350 FROM 1999 - 2003. THE AVERAGE FAILURE TIMELINE IS 45000 - 70000 MILIES. MINE OCCURED AT 68000. *AK
NHTSA ID
10074618
Incident
Apr 3, 2004
Mileage
68,000 mi
AirbagsBody & structureBrakes+1 more
Filed Nov 16, 2000
THE AIR BAG LIGHT WAS ON WHEN THE VEHICLE WAS DELIVERED, REQUIRED REPLACEMENT OF THE AIR BAG MODULE ON TWO OCCASIONS. *MJS
NHTSA ID
557709
Higher-selling and older vehicles accumulate more reports. Counts are not failure rates and are not directly comparable between vehicles that sold in very different numbers.
Other components reported on this vehicle
Categories with enough reports to have a page of their own