2008 Lexus Es350 Base Sedan 4-door 3.5l on 2040-cars

Auto blog

A car writer's year in new vehicles [w/video]

Christmas is only a week away. The New Year is just around the corner. As 2014 draws to a close, I'm not the only one taking stock of the year that's we're almost shut of. Depending on who you are or what you do, the end of the year can bring to mind tax bills, school semesters or scheduling dental appointments. For me, for the last eight or nine years, at least a small part of this transitory time is occupied with recalling the cars I've driven over the preceding 12 months. Since I started writing about and reviewing cars in 2006, I've done an uneven job of tracking every vehicle I've been in, each year. Last year I made a resolution to be better about it, and the result is a spreadsheet with model names, dates, notes and some basic facts and figures. Armed with this basic data and a yen for year-end stories, I figured it would be interesting to parse the figures and quantify my year in cars in a way I'd never done before. The results are, well, they're a little bizarre, honestly. And I think they'll affect how I approach this gig in 2015. {C} My tally for the year is 68 cars, as of this writing. Before the calendar flips to 2015 it'll be as high as 73. Let me give you a tiny bit of background about how automotive journalists typically get cars to test. There are basically two pools of vehicles I drive on a regular basis: media fleet vehicles and those available on "first drive" programs. The latter group is pretty self-explanatory. Journalists are gathered in one location (sometimes local, sometimes far-flung) with a new model(s), there's usually a day of driving, then we report back to you with our impressions. Media fleet vehicles are different. These are distributed to publications and individual journalists far and wide, and the test period goes from a few days to a week or more. Whereas first drives almost always result in a piece of review content, fleet loans only sometimes do. Other times they serve to give context about brands, segments, technology and the like, to editors and writers. So, adding up the loans I've had out of the press fleet and things I've driven at events, my tally for the year is 68 cars, as of this writing. Before the calendar flips to 2015, it'll be as high as 73. At one of the buff books like Car and Driver or Motor Trend, reviewers might rotate through five cars a week, or more. I know that number sounds high, but as best I can tell, it's pretty average for the full-time professionals in this business.

'Next Lexus F' teased ahead of Detroit debut

We've got absolutely zero actual information from the automaker on what its "Next Lexus F" will be, other than what was just released today in this brief press release and lone teaser image, but our best guess is that it's the next-generation IS-F sedan. The timing would make sense, considering that the latest IS just hit the market earlier this year as a 2014 model.
Since we know so little, we'll just share some of the exuberant marketing speak contained in the press release for your reading pleasure:
Designed from the asphalt up, to strike at the heart, the newest Lexus F model will debut at the January 2014 North American International Auto Show in Detroit.

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.