2010 Lexus Rx350 3.5l V6 24v Automatic Fwd Suv Premium Moonroof Dvd Navigation on 2040-cars

Auto blog

What's in a trademark? Sometimes, the next iconic car name

The United States Patent and Trademark Office is a treasure trove for auto enthusiasts, especially those who double as conspiracy theorists.
Why has Toyota applied to trademark "Supra," the name of one of its legendary sports cars, even though it hasn't sold one in the United States in 16 years? Why would General Motors continue to register "Chevelle" long after one of the most famous American muscle cars hit the end of the road? And what could Chrysler possibly do with the rights to "313," the area code for Detroit?

Drifting on a frozen lake with a studded Lexus looks like fun

Sometimes you come across a list of ingredients and you don't even need to know what's being made, you just know you need to be there when it's done. So if you saw a recipe for a Vimeo video that was one snow-covered frozen lake, one Lexus IS, four studded tires, two ice fisherman and one guy lounging on a couch, do you think you'd have any questions?
We didn't. The dish was cooked up by the Wide Open Drift Team and KSP Productions, and it's exactly what you'd think it is. Right down to the guy on the couch. We're glad we got to partake, and you can too in the video below.

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.