2007 Lexus Ls460 L on 2040-cars

Auto blog

Autoblog Podcast #339

Farewell, Zach Bowman; Pikes Peak 2013; Datsun; 2014 Ram lineup
Episode #339 of the Autoblog Podcast is here, and it's the last rodeo for Zach Bowman before he departs for other pastures. The crew this week consists of Dan Roth, Zach Bowman and Jeff Ross, who talk about the astounding records set at this year's Pike's Peak hill climb, the return of the Datsun brand name and the recently-announced 2014 Ram truck lineup. Of course, we start with the garage and end with your questions and comments. For those of you who hung with us live on our UStream channel, thanks for taking the time. You can follow along after the jump with our Q&A. Thanks for listening!
Autoblog Podcast #339:

Lexus says it's not worried about LS sales decline in face of S-Class, Model S

The Lexus LS is old. Sure, it received a refresh for model year 2013, but it hasn't had a clean-sheet redesign since George W. Bush was in office. It's the oldest vehicle in its segment, debuting in 2007, a full year before the current-gen BMW 7 Series, two years before the Hyundai Equus and Jaguar XJ and three years before the Audi A8.
This is particularly troubling as buyers flock to the heavily redesigned Mercedes-Benz S-Class, which debuted late last year, and the all-electric Tesla Model S. Despite this move, though, Lexus is (worryingly in our minds) not at all concerned.
"We don't feel it's a problem with the car," Brian Smith, VP of marketing for Lexus, told Wards Auto. "Many of the buyers in that segment want what's new and they're trying it."

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.