2010 Lexus Lx 570 Awd Navigation, Rear Dvd Entertainment on 2040-cars

Auto blog

2015 Lexus RC F

I didn't get a chance to drive the Lexus IS F until 2009, two years after the car had gone on sale, but I still vividly remember the day it happened. Having piloted almost every other vehicle in the Lexus lineup at that point, I was stoked to finally get some wheel time in the V8-powered, flared-fender muscle sedan, but fully expected the car to offer a quick, sanitized and ultimately un-driverly experience. Lexus built well-screwed-together, comfortable, quiet, reliable luxury cars for the timid, right?
As it turned out, I was 100-percent incorrect. When the premium brand's lauded "skunkworks team" crammed that massive V8 into the innocent IS, and then tuned the thing for competent hot laps at Fuji Speedway (F = Fuji, if you haven't heard), they seemingly forgot every brand value that Lexus had curated over the previous 20 years. It was raw and loud, had fast-twitch reflexes and a penchant for power slides, and it went unyieldingly across the road surface like a racecar cut loose from the paddock.
As far as Ur- models and origin stories go, the IS F and Lexus F has a pretty compelling, if new, set. A backdrop against which the sequel, this 2015 RC F, must inevitably be viewed. Sure, the otherworldly LFA may have intervened as the second F model, but the RC carries forward an evolution of the 5.0-liter V8 thumper, some shared body and chassis constructions, similar in-your-face design and a ticket price that's squarely in the mix for premium buyers with a hankering to smoke tires.

Lexus to reveal production NX crossover at Beijing in April

At the Frankfurt Motor Show last year, Lexus rolled out a concept crossover called the LF-NX. It then brought it back, with a new paint job and a turbocharged engine, at the Tokyo Motor Show a few months later. We got another glimpse a couple of months after that during a presentation from Jim Lentz. But now Toyota has confirmed that the finalized production version is just around the corner.
While all the attention is affixed on the Geneva Motor Show, Toyota released a statement (which you can read below) announcing that the NX (as it will officially be known) will debut next month at the Beijing Motor Show. Set to be positioned below the RX, the new NX will tackle what Lexus terms as "the growing segment of premium compact crossovers," taking on the likes of the Audi Q3, BMW X1 and Mercedes-Benz GLK.

Toyota settles first wrongful death suit related to unintended acceleration

Toyota's sales seem to have rebounded from the unintended acceleration issues from 2009 and 2010, but the automaker is far from done dealing with this situation. Following a settlement worth up to $1.4 billion for economic loss to affected vehicle owners, Toyota has settled rather than going to trial in a wrongful death lawsuit stemming from an accident in Utah in 2010 that left two passengers dead. This isn't the first case in which Toyota has settled, but it was the first among a consolidated group of cases being held in Santa Ana, CA.
According to The Detroit News, this case was scheduled to take place next month, and it was for a November 2010 incident in which Paul Van Alfen and Charlene James Lloyd were killed in a Camry when, based on findings by the Utah Highway Patrol, the accelerator got stuck causing the car to speed out of control and hit a wall; the terms of the settlement were not announced.
The article says that while Toyota will settle on some cases, it doesn't plan on settling on all of them as it still wants to be able to "defend [its] product at trial." This will probably be the case in suits claiming that software for the drive-by-wire accelerator was the cause of an accident in a Toyota or Lexus vehicle. The question of whether or not the electronic accelerator played any role in this problem has been a hot-button topic since the beginning. Toyota has issued recalls in the past to attempt to prevent unintended acceleration caused by trapped floor mats and faulty accelerator pedals, but it also says driver error was to blame in some instances.