Engine Noise problems of the 2012 Hyundai Santa Fe

I went grocery shopping on wed April 21,2021 came out tried starting my 2012 Hyundai Santa Fe and it wouldn't start I proceeded to try again and it started making this high pitched noise ,peaked out really loud a puff of smoke came out from underneath my hood and the car was completely dead. I had it towed to my mechanic where he replaced the starter thinking that was the problem which it wasn't he informed me the engine was seized up . I then had the Santa Fe towed to the Hyundai dealership where it was purchased new from the original owner all service from day one has been done at this Hyundai dealership we bought this car knowing the service records and history of car we also knew it came with a 10 year 100000 mile drive train warranty. Motor failed at 96128, would of been covered under manufactures drive train warranty if I was original owner I was told. After doing research we have discovered this is a common problem with the Hyundai Santa Fe motors locking up. Service writer advised us to contact Hyundai directly which I did my case #18222696 was told someone would call me within 3-5 business days which I haven't heard from anyone.

I was driving on the highway when the engine began to make a noise. It is an engine failure and has to be replaced.

Mileage around 82,000 miles | always had routine, on time, maintenance | no engine light on (or any others) | on a trip driving down the highway going around 65mph with cruise control set (2 adults and 1 child in the car, not towing anything), our SUV started making a strange noise when accelerating, then progressed to a consistent noise whether accelerating or not. We decided we needed to stop in the next town (about 20 miles away) to take a look, but before we could reach the next town the car without warning shut down, started smoking, and pieces of the car fell from below the car. My husband raised the hood and noticed the engine was on fire, and quickly put it out. We had the car towed to a Hyundai dealership and just by raising the hood the mechanic knew the engine exploded, and informed us it would be around $6500 for a used engine. From the time the noise first started until the engine blew up we drove 12 miles. We have tried contacting Hyundai to notify them of the issue, after waiting on hold for 30+minutes all they can say is there is nothing they can do since we are out of warranty, when we ask to speak to a manager one is never there and they promise that will have the manager call us back, but we have not received a phone call. After researching this issue, it seems we are not the only ones having issues with the engine. My husband used to sell Hyundai's and knows for a fact that the Santa Fe and sonata's have the same engine - the 2011-12 sonata engine had a recall, why didn't the Santa Fe have a recall? the Santa Fe is my second Hyundai to own, I will not buy another due to the issues with my Santa Fe and lack of customer service. Side note, why would I spend $6500 on another engine, when there seems to be an exploding pattern.

4/1/2016: driving on interstate I-40 westbound in las cruces in a construction zone, the car engine died, but I was able to get to shoulder. Car towed to auto repair shop, but problem could not be diagnosed; car eventually restarted. 2nd attempt to diagnose on 4/11/16; none could be found. Car started to make occasional loud engine noise over ensuing months. I contacted Hyundai, and in October 2016 was told to bring car 100 miles back to las cruces, nm (borman autoplex) for further diagnosis. Borman diagnosed metal shavings in engine (similar or identical to problem for the 470,000 sonatas with metal shavings in the engine). A full engine failure and engine replacement was recommended. I contended that the engine should be replaced free of charge, as it was a manufacturing defect and the vehicle dying without notice while being driven could prove dangerous or fatal to the driver/passengers. The engine failed fully, and the vehicle is not drivable. Again, issue began 4/1/2016; engine failed completely 12/28/2016.