Low Miles 79k**pearl White**navigation**chrome Wheels**shipping Quotes Available on 2040-cars

Auto blog

Only 240 of these Lexus RC F will be built | 2018 Chicago Auto Show

To celebrate its decade-long life so far, a pair of also-V8-powered Lexus F models, the RC F and GS F, will get special editions. These 10th-anniversary edition cars are extremely limited production. Matte paint that can be taken through a car wash included. Chicago Auto Show Lexus Autoblog Minute Videos Original Video

Lexus fans vote Solar Flare for new RC F hue

What's in a name? When it comes to model nameplates, quite a lot, and automakers go to considerable lengths to find just the right one. Same goes for the names of the colors in the catalog (save for maybe the Rape Yellow in the extensive Bugatti palette), but every once in a while, an automaker will open it up for suggestions from the public.
SRT did that when it introduced a new shade of blue for its Viper, as did Chevy for the pale green on the Volt. And last month, Lexus followed a similar path when it asked fans on Facebook to come up with a name for the new shade of orange for the RC F.
Fans suggested names like Tangerine Flame, Outrageous Orange and Fiery Orange, but ultimately the winning submission that Lexus selected was Solar Flare. The name was suggested by five individuals and will now enter the catalog of colors for the new luxury muscle coupe with its 450-horsepower 5.0-liter V8.

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.