We Finance Certified Excellent Condition Clean Warranty Reduced Price Must Sell on 2040-cars

Auto blog

Toyota to pay $17.35M federal fine for delayed Lexus RX recall

This summer, we brought you news that Lexus was recalling over 150,000 RX and RX hybrid crossovers tied to its massive pedal entrapment issue. An update to that story included word from the National Highway Traffic Safety Administration that it was considering launching a federal investigation into potential delays by the automaker in notifying owners about the problem. Now comes news that parent company Toyota will pay a hefty $17.35 million in fines for delaying its recall of the 2010 Lexus RX 350 and RX 450h. According to The Detroit News, the Japanese automaker is being forced to pay the maximum fine for delaying recalls - and this isn't the first time. In fact, this is the fourth time since 2010 that Toyota has been required to do so, including paying $48.8M in civil penalties in 2010 for failing to recall vehicles in a timely manner - in three separate campaigns.
In addition to the fines, Toyota has agreed to restructure the way it handles quality control and review "safety-related issues." Though the Japanese automaker has not admitted any wrongdoing, Toyota has agreed to meet with NHTSA for six months on the matter and may extend the meetings another six months.
US Transportation Secretary Ray LaHood says he is counting on Toyota to improve its ability to address such safety issues: "With today's announcement, I expect Toyota to rigorously reinforce its commitment to adhering to the United States safety regulations," he said in a statement.

We drive the Bronco Sport Sasquatch, Hummer EV SUV and more | Autoblog Podcast #846

In this episode of the Autoblog Podcast, Editor-in-Chief Greg Migliore is joined by Road Test Editor Zac Palmer. Zac recently went down to Tennessee to drive a prototype of the 2025 Ford Bronco Sport Sasquatch. Meanwhile the two also spent time in the 2024 GMC Hummer EV SUV, 2024 Mercedes-AMG GLA 35 and 2024 Lexus LS 500h out of the fleet in Michigan. In the news, Rivian deals with a fire at its Normal, Illinois plant, Formula 1 comes back strong, and Volkswagen prices the ID.Buzz. Lastly, the two debate what old, executive sedan you should buy in a Spend My Money segment. Send us your questions for the Mailbag and Spend My Money at: Podcast@Autoblog.com. Autoblog Podcast #846 Get The Podcast Apple Podcasts – Subscribe to the Autoblog Podcast in iTunes Spotify – Subscribe to the Autoblog Podcast on Spotify RSS – Add the Autoblog Podcast feed to your RSS aggregator MP3 – Download the MP3 directly Rundown Cars we're driving 2025 Ford Bronco Sport Sasquatch 2024 GMC Hummer EV SUV 2024 Mercedes-AMG GLA 35 2024 Lexus LS 500h News Fire at the Rivian factory Formula 1 is back Volkswagen ID.Buzz gets a very high price Spend My Money Feedback Email – Podcast@Autoblog.com Review the show on Apple Podcasts Autoblog is now live on your smart speakers and voice assistants with the audio Autoblog Daily Digest. Say “Hey Google, play the news from Autoblog” or "Alexa, open Autoblog" to get your favorite car website in audio form every day. A narrator will take you through the biggest stories or break down one of our comprehensive test drives. Related Video:  We check out the Rivian R1S and R1T along with 3 other surprises This content is hosted by a third party. To view it, please update your privacy preferences. Manage Settings.

Google shares more details on self-driving car accidents

Google has pledged to release monthly reports on the status of its self-driving car program, and says these updates will include information on accidents involving the vehicles. But the company won't release the actual accident reports, a sore point for activists who recently have clamored for the company to be more transparent in the way it tests this promising technology on public roads. "Google is dribbling out bits of information in the hope to silence legitimate calls for full transparency," said John Simpson, privacy director for Consumer Watchdog, a nonprofit that has asked Google to release reports from the 12 accidents the company says it has been involved in over the past six years. "They are testing on public roads, and the public has a right to know exactly what happened when something goes wrong." Under California law, the accident reports are not considered public records. Google has attributed all accidents to human error, and says drivers of the other cars involved caused 11 of the 12 accidents. In eight of those, the Google cars were rear-ended, and the autonomous vehicles were sideswiped in two other crashes. One of the accidents occurred at an intersection when a human driver failed to yield at a stop sign, and in one incident, a Google driver accidentally rear-ended another car while manually driving. Google had previously provided those details. The first monthly report installment sheds new light on which types of self-driving vehicles were involved, directions of travel, locations, and whether the cars were operating in autonomous or manual mode. Update: Google says this information comes directly from the OL 316 forms used to report accidents involving autonomous cars in California, though it has "edited the summaries lightly to protect other drivers' information." But Google still will not release the original OL 316 forms, nor the "traffic collision report" forms used in California to report accidents. Another company that has been involved in a single self-driving car accident, Delphi Automotive, has released this information, which verified its car was not at fault. Regarding Google, Simpson said, "We now know a few more details of what happened. The problem is that it's Google's version and they want us to take their word for it." The Google self-report adds information that goes beyond accidents, with further details on the company's overall program.