07 Rx350 Awd Premium Plus Pkg Navigation Heated Leather Xenon Loaded Maintained on 2040-cars

Auto blog

Lexus planning second flagship alongside LS sedan

Lexus is planning to launch another flagship to slot alongside the LS sedan, but we don't know if it will be a coupe or a crossover. The coupe has been the persistent rumor. Lexus showed the two-door LF-LC concept in 2012 and a production model could borrow its underpinnings from the LS sedan. It's tipped to wear the letters LC or to revive the SC nameplate. The previous SC launched in 1991 as a fixed-roof coupe and offered inline-six or V8 engines. It was replaced in 2001 with the SC430 that had a V8 and a folding hardtop. While the coupe idea may seem like the leading candidate, the company's ambiguity is leading to speculation that the new flagship could adopt a different body-style altogether. "We need a flagship," Lexus general manager Jeff Bracken told Reuters. "It doesn't have to be a sedan." "In addition to the LS, there could be another flagship in our lineup," Bracken said. "We'll define what it is in January." The comments suggest something will be revealed at the Detroit auto show and could open the door to a new flagship SUV or crossover. That position is currently held by the LX 570, which is closely based on the Toyota Land Cruiser. However, sales of the LX have been less than stellar. From the 14,000-plus units Lexus sold of the original LX 470 when it launched in the US back in 2000, annual sales have dropped to just over 4,000 the last few years. Mercedes regularly sells over 25,000 of its GL-Class crossovers each year in the US alone. Last year Audi sold 18,000 Q7s here despite its imminent replacement. Land Rover sold nearly 13,000 Range Rovers last year and another 18,000 Range Rover Sports. Meanwhile, Cadillac typically sells between 20,000 and 30,000 Escalades every year, down from the 50,000-60,000 it sold a decade ago. A facelift is due for the LX that ought to spike sales a little, but Lexus will need more than a refresh to catch up with those rivals. In the meantime, it reportedly plans to roll out a three-row variant of the new RX before its lifespan is over. "We don't want to wait for a next generation" to give the RX the added seating capacity many customers are demanding, said Bracken. Related Video:

Ever wonder how to really pronounce Japanese automaker names?

People tend to get very set in their ways when it comes to the pronunciation of words. Just look at the endless debates over whether or not to say the final 'e' in Porsche (which you should in terms of correct German enunciation). Or the argument about whether to follow the British convention and give the 'u' in Jaguar a special delivery or to say the 'ua' diphthong as more of a 'w' sound, as usually happens in the US.
This short video doesn't answer either of those automotive questions, but it does allow a native Japanese speaker to demonstrate the accepted pronunciations for several, major automakers from the country. One benefit is that it clears up the occasional debate over whether Nissan should be said with a long or short 'i' sound. Also, listen closely to how the female host says Mazda as Matsuda, the way it's actually said in the language. Even if this doesn't change the way you enunciate these brands, at least now you know the accurate way in Japanese.

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.