2008 Lexus Ls460 Base Sedan 4-door 4.6l on 2040-cars

Auto blog

Lexus LF-NX gets turbocharged second act [w/video]

Don't let its supremely polarizing appearance fool you, this is not the Lexus LF-NX Concept that you (probably) had a strong reaction to when it debuted at the Frankfurt Motor Show. The German version of the concept car featured a variant of the Lexus Hybrid Drive system, while this LF-NX Turbo, well, it has "turbo" in the name, you see?
If fact, the namesake turbo would appear to be the first for Lexus; getting off the line in the forced-induction race with a 2.0T four-cylinder engine that "paves the way for the introduction of turbocharged powerplants in future Lexus models." Sounds good to us. The new turbo four has plenty of tricky tech, too. Lexus tells us that the engine makes use of an advanced high tumble port, fan spray fuel injection, VVT-iw variable valve timing, an exhaust manifold integrated into the cylinder head and, of course, a twin-scroll turbo with active wastegate valve. The result is said to be a blown engine that offers quick throttle response and "exhilarating" performance, along with excellent fuel economy and low tailpipe emissions.
As for the rest of the LF-NX Turbo concept? Well, you've seen this angular concept crossover before, basically. There's a slightly tweaked front end and new wheels sitting in slightly cleaned-up wheel wells. The boldest-yet version of the spindle grille still bears an uncanny resemblance to The Predator, and the slightly revised exterior visuals won't change your made-up-mind about this vision of Lexus' future.

Auto News Recap for 9.9.16 | Autoblog Minute

A recap of the week in automotive news, including Honda Civic Type R spy shots, Toyota Supra spy shots, and a teaser of the Lexus UX crossover concept. Honda Lexus Toyota Crossover Autoblog Minute Videos Original Video honda civic type r supra hot hatch lexus ux concept

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.