2010 Lexus Es 350 Certified Leather Xm 24k Miles Heat & Cooled Seats Moon 6cd on 2040-cars

Auto blog

2014 Infiniti Q50, Lexus IS 250 fail to achieve Consumer Reports 'Recommended' rating

Infiniti and Lexus might be a little concerned now that both of their new luxury sedans, the Q50 and IS250, were unable to net Consumer Reports vaunted "Recommended" rating during their first year on the market. In fact, not only did the two fail to earn a "Recommended" rating, they finished behind the vast majority of the competition after testing, including the BMW 328i, Mercedes-Benz C250, Lincoln MKZ and Volvo S60 T5.
The Q50 managed to snag a "Very Good" rating overall, but CR criticized it's road manners for not being as thrilling as the car it (sort of) replaces, the G37. The mag called the handling mundane and the steering dull, while also remarking on the poor controls. According to CR, the interior quality is "nothing special." Shade was also thrown at the Q50's reportedly poor ride.
Compared to the IS, though, the Q50 got off easy. CR called it "neither sporty nor luxurious," while criticizing the 2.5-liter V6's lack of oomph and poor fuel economy. The mag then went on to lambaste the IS's handling, steering, interior, cabin space and infotainment system.

New Lexus small CUV may have been behind moving ES production to Kentucky

Lexus may have had another big reason - in addition to the financial incentives potentially worth up to $146.5 million that Kentucky offered - to move ES production to its Georgetown, KY plant. The ES has always been built in Japan, and a report at TheDetroitBureau.com claims that the Kyushu facility will be tooling up to build a new model thought to be a compact hybrid crossover expected to go on sale next year. While ES300h production would remain in Japan, shedding 50,000 units of traditional ES production would free capacity for what many think will be an important model in the Lexus lineup.
The new CUV will come in below the RX and be built on the platform of the RAV4. Speculation is that there will be an NX200t and an NX300h, the former possibly getting the 2.0-liter turbo Toyota engine due in 2014 - matching the predicted timeline for the CUV and supposedly also meant for an RX200t - and latter getting the same 2.5-liter hybrid powertrain in the ES300h. We'll see a preview of the Audi Q3 and BMW X1 fighter at this year's Tokyo Motor Show; the production version should be unveiled at the 2014 Geneva Motor Show.

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.