List of TSBs and Recalls for 2017s

[smr2112]

Ford has some pretty amazing pricing, rebates and incentives now for (some of) the 2017s. Seems the more

higher end the car, the better the savings. Especially the Platinums if you can find them. Maybe would

go for an Energi now over the Hybrid.

 

Was considering a Trade-In of my 2017 if it makes sense, but being wiser now from

the TSBs and recalls of the 2017 (all of them fixed and car is great!) - I was wondering

what surprises await if I buy a 2017, or at least wait 6 months maybe?

 

Anybody have a list or know of known issues with the Energis and Hybrids already for 2017?

It's early in the model year, but I figured these would start showing up soon!

 

[Texasota]

There could be some new problems with the 2017s due to the minor changes but overall most of the problems and bugs were squashed by the 2015 model year. They seem to be very trouble free now and are getting good reliability ratings in Consumer Reports magazine. My 2015 with 30k miles has been back to the shop for the steering bolt corrosion recall but other than that no trips to the dealership service department. I may have just jinxed myself.

[Cobra348]

Right now my '15 is nearing 37K miles and will most likely be about 40K when my 17 arrives. BUT ... no issues with the current car at all.

[talmy]

Other than a mild style change and Sync 3 are the 2017's that much different than earlier years? Probably won't see major problems, but it doesn't hurt to wait a few months after any new model comes out.

 

We were considering a 2017 (probably MKZh but possibly Fusion) since Sync 3 was announced, but probably will wait for 2018s since our 2014 Fusion Hybrid is doing so well. (50k miles and no repairs.)

Edited August 19, 2016 by talmy

[James Kelker]

There was a recall for the daytime running lights (LEDs). Apparently could overheat (I believe?) and dim. The replaced both headlight assemblies. I also had a problem with the heat not working correctly (would not heat at anything but hi) but that was apparently fixed with a software update over the air.