2005 Lexus Sc 430 on 2040-cars

Auto blog

Autoblog Podcast #396

Episode #396 of the Autoblog Podcast is here, and this week, Dan Roth, Steven Ewing, and Chris Paukert talk about the 2016 Mazda MX-5 Miata, the 2016 Jaguar XE, and the 2015 Lexus RC. We start with what's in the garage and finish up with some of your questions, and for those of you who hung with us live on our UStream channel, thanks for taking the time. Check out the rundown below with times for topics, and you can follow along down below with our Q&A. Thanks for listening!
Autoblog Podcast #396:
Topics:

Lexus RX replacement to debut in Detroit?

The 2015 Detroit Auto Show is shaping up to be a big one for Lexus, with Group Vice President Jeff Bracken confirming to Ward's Auto that the Japanese luxury marque will have at least one, and possibly two, all-new-model introductions. Ward's seems to think that one of those vehicles will be the new RX crossover, one of the brand's most popular (and oldest) offerings. The complete and utter lack of spy photos of the new RX doesn't necessarily support Ward's argument, although if the new CUV ends up being based on the JDM Toyota Harrier, as previously reported, the absence of camouflaged images might make some sense. As for that other vehicle, it's hard to say what we might see. Were we to put our money on it, though, the long-awaited GS F would be a strong contender for a Detroit debut. The high-performance challenger to the BMW M5 and Mercedes-Benz E63 AMG has been spotted almost completely undisguised as recently as October. On top of that, Detroit's reputation as a performance-focused show (last year's show saw debuts of the Ford Mustang, BMW M3 and M4, Chevrolet Corvette Z06, Volkswagen Golf R and Porsche 911 Targa) makes the GS F's appearance there a fair bet. One thing we can count on at least hearing about when Detroit rolls around is Lexus' strong sales position. The company's 2014 sales should crest 305,000 units by the end of the year, marking the first time the company had passed the 300,000-unit mark since 2007. Bracken told Ward's that should be an easy task, particularly with the brand's "best month of the year," December, still to come.

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.