There are 2 stored owner reports matching the speed control & cruise leading-label group for the 2010 Ford Expedition in our NHTSA-sourced dataset. These are unverified consumer reports and may not reflect confirmed defects.
This group counts stored reports whose component label starts with one of this site's matching prefixes, ignoring case. Each matching report counts once within the group. Components mentioned later in the label or only in the narrative are not searched. How component counts work
Loaded 2 of 2 matching reports.
Open the full vehicle complaint log (all categories)TL* THE CONTACT OWNS A 2010 FORD EXPEDITION. WHILE DRIVING 75 MPH, THE VEHICLE SEIZED UP WITHOUT WARNING AND WOULD NOT ACCELERATE. THE VEHICLE WAS NOT DIAGNOSED OR REPAIRED. THE MANUFACTURER WAS MADE AWARE OF THE FAILURE. THE FAILURE MILEAGE WAS 117,000.
I WAS ATTEMPTING TO ACCELERATE FROM AN IDLE POSITION TO ENTER A HIGHWAY. IN THE PROCESS OF ACCELERATION, MY ENGINE BEGAN TO KICK AND STUTTER LIKE IT WAS NOT TAKING IN ENOUGH GAS. I HAVE REPORTED THIS MATTER TO MY FORD DEALERSHIP WITHOUT A SATISFACTORY ANSWER. A COLLEAGUE OF MINE WHO OWNS THE EXACT SAME STYLE, MODEL AND YEAR VEHICLE EXPERIENCED THE SAME EXACT ACTIONS AND ALSO VISITED THE SAME FORD DEALERSHIP (WORLD FORD) AND WAS ADVISED THAT THE KICKING OR BUCKING OF THE ENGINE WAS DUE TO A DEFECTIVE TORQUE CONVERTER THAT FORD IS UNWILLING TO REPLACE (A $2000 JOB). THE DEALERSHIP HAS PLACED FLUID IN THE ENGINE WITHOUT ANY RESOLUTION. THIS IS MY 3RD EXPEDITION. WHILE I AM HAPPY WITH FORD, THERE IS CLEARLY A DEFECT (DUE TO SIMILAR ACTIONS IN ITS OTHER MODELS). THEY CHOSE TO IGNORE THE PROBLEM. I NEED A RESOLVE IMMEDIATELY. *TR
Complaints are unverified consumer reports submitted to NHTSA. A high complaint count may reflect vehicle popularity, not defect severity. Data sourced from NHTSA public records.
NHTSA source checks for this vehicle year
Checks are recorded separately for each dataset, not for the whole page. Dates use UTC. A missing check date does not mean no records exist.
Vehicle import recorded: May 4, 2026. This is the stored import date, not confirmation that every source was successfully refreshed.