Friday, 25 September 2015

Hyundai Recalling 569,500 Sonatas, Accents Over Separate Defects

Leave a Comment
http://ift.tt/1LDuqB2

2011 Hyundai Sonata SE 2.0T

Hyundai is recalling a total of 569,500 Sonatas and Accents for two separate issues. According to recall filings with NHTSA, certain 2011 and 2012 Sonatas were manufactured with too much metal flashing on certain engine components, which can break off and wreak havoc on the motors’ internals. As for the affected Accents, those cars (model years 2009–2011) could suffer from a faulty brake switch. As a result, 470,000 Sonatas and 99,500 Accents are being recalled.

NHTSA says that the Sonatas, built between December 11, 2009, and April 12, 2012, and with either the 2.0- or 2.4-liter four-cylinder engines, could have been assembled with engine crankshafts that weren’t fully cleared of “metallic debris” that can block oil flow to the connecting rod bearings. Sans oil, these components can damage the rods and “produce a metallic, cyclic knocking noise from the engine and possible engine failure.” Since unforeseen engine failure counts as a safety issue, we have a recall.



As it concerns the Accent, NHTSA says that the faulty brake-light switch leads to a host of potential issues, the biggest of which is, if an Accent driver is using cruise control, the switch might not trip when the brake pedal is pressed and cruise control won’t disengage. Besides that, the brake lights may not illuminate, and owners with automatic-transmission-equipped models could face trouble trying to move the shifter out of park. The recall affects models built between March 1, 2009, and February 11, 2011.

Hyundai will fix either issue free of charge, replacing the brake-light switch on the Accents and inspecting Sonatas, replacing “the engine assembly as necessary.”


This entry passed through the Full-Text RSS service - if this is your content and you're reading it on someone else's site, please read the FAQ at http://ift.tt/jcXqJW.



from Car and Driver Blog http://ift.tt/1Ju7vSX
via IFTTT

0 comments:

Post a Comment