2001 Lexus Ls 430 on 2040-cars

Auto blog

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.

Lexus files to copyright LC 500 nameplates [UPDATE]

UPDATE: Reached for comment, Lexus told Autoblog that it "cannot offer comment on the potential naming of a production version of the LF-LC concept" and pointed out that automakers trademark nameplates as a matter of course. Some automakers already slap a production-ready name on their concepts, but not Lexus. The Japanese automaker typically labels its show cars with the letters LF-XX. So when we heard that Toyota had green-lit the LF-LC concept for production, we naturally started wondering what name the production version would carry. But if the latest intel is any indication, we can stop wondering. According to Lexus Enthusiast, the automaker has filed to trademark the names LC 500 and LC 500h in a variety of markets – including the United States, Canada and Australia. The application tells us a number of things: first of all, that the LF-LC will retain that second set of letters along the road to production (like the NX but unlike other recent Lexus concepts). And secondly, it indicates what engines we can expect to find under the hood. The 500 designation would seem to suggest that the base version of Lexus' upcoming halo sports car will pack the 5.0-liter V8 from the RC F. The bigger question mark is over the hybrid version. Current gasoline-electric models in the company's lineup include the RX 450h (based on a 3.5-liter V6) and the LS 600h (with a 5.0-liter V8). For the LC 500h, Lexus could be planning a more potent electric motor to mate to the 3.5L V6, or planning a new powertrain altogether.