- Toyota recalls 44,000 Tundra trucks for potentially faulty V6 engines.
- The engines could have debris inside that could damage a main bearing.
- This is Toyota’s third recall for the twin-turbocharged 3.4-liter V6 engine.
Toyota has issued another recall for its troubled twin-turbocharged 3.4-liter V6 engine. The automaker announced today that it will recall certain 2024 Tundra trucks in the United States.
The voluntary recall affects 44,000 non-hybrid Tundra pickups. According to Toyota, “There is a possibility that certain machining debris may not have been cleared from the engine when it was produced.” This could result in a catastrophic failure and has been affecting the automaker for two years now.
Photo by: Toyota
The automaker issued its first recall related to the engine in May 2024 for the 2022-2023 Tundra and Lexus LX, affecting 102,000 vehicles. It had to replace the engines. The second recall came in November 2025, this time for 127,000 vehicles, which expanded to include the GX.
What makes Toyota’s latest recall interesting is that these engines should not be affected by this problem. According to the press release announcing the recall:
‘The engines involved in this new recall were produced using additional controls for removing manufacturing debris. We have found that, even after these additional controls, the remaining debris could be sufficient to cause damage to the #1 main bearing and lead to this issue. Engines produced after those included in this recall were manufactured with an improved #1 main bearing to help resist certain debris that might remain.’
So far, Toyota has repaired 77,000 vehicles. Once the company finalizes the remedy details, Toyota will begin contacting customers in “phases” once it becomes available.
Motor1’s Take: Toyota’s twin-turbocharged 3.4-liter V6 engine, which it markets as a 3.5-liter, has been a pain point for the company. The engine powers several large models for the company, and there might have to be additional recalls for those models if some of the fixes did not resolve the problem.
