2008 Lexus Es 350 4dr Sdn Power Windows Alloy Wheels Air Conditioning on 2040-cars

Auto blog

2016 Lexus GS F revealed ahead of Detroit debut

The last time we heard about Lexus' new Detroit Auto Show-bound performance car debut, all signs pointed to GS F. Now, the cat's out of the bag, and we've got the first official images and details of the Japanese automaker's latest performance sedan, and honestly, it's exactly what you'd expect – though that isn't necessarily a bad thing. Power comes from the automaker's 5.0-liter naturally aspirated V8 – the same eight-pot that powers the RC F – good for 467 horsepower at 7,100 rpm and 389 pound-feet of torque that comes on strong between 4,800 and 5,600 rpm. That force is sent to the rear wheels via Lexus' eight-speed automatic transmission. In order to make this F a significantly better-handling vehicle than the standard GS, Lexus is fitting its Torque Vectoring Differential from the RC F, which uses three modes – Standard, Slalom, and Track – to alter torque delivery to better suit different driving dynamics. Lexus has released a few preliminary specifications about the GS F, so we know the sedan tips the scales at 4,034 pounds and will ride on 19-inch wheels with 255/35-series tires up front, and 275/35 rubber out back. This all sounds pretty good, but we can't help feel a wee bit disappointed, especially considering the numbers being thrown down by competitors like the BMW M5 and Mercedes-Benz E63 AMG, not to mention the new 640-hp, 200-mph Cadillac CTS-V that'll also debut at next week's Detroit show. Still, if the Lexus RC F is any indication of the brand's future performance offerings, we don't doubt the GS F will, at the very least, be a super fun car to toss around. Stay tuned for the GS F's official unveiling, next week.

Judge halts Toyota unintended acceleration cases, triggers time for settlement negotiations

So far, the lawsuits brought forth against Toyota for unintended acceleration have gone both ways: the automaker was found not at fault in a 2009 California crash and liable for a 2007 crash in Oklahoma. Both cases involved a Camry and resulted in fatalities. With a big chunk of these UA cases (around 200) set to his the docket of US District Judge James V. Selna in Santa Ana, California, Bloomberg is reporting that the judge has halted the lawsuits until March after Toyota and its lawyers have had extra time to try and settle the cases.
According to the article, Toyota is looking to take care of the cases out of court with an "intensive settlement process." Having already paid out $1.6 billion in "economic loss" suits, this latest settlement process is aimed at the wrongful death and personal injury cases allegedly associated with unintended acceleration. A hearing for the settlements will be held on January 14 with conferences on the matter commencing in February. There is no word as to when lawsuits may start back up if settlements can't be agreed upon.

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.