1992 Lexus Sc400 Collector Not Sc300 Pristine Condition Low 82k Miles on 2040-cars

Auto blog

Lexus CT 200h could be replaced by sub-compact hybrid CUV

The Lexus CT 200h is an interesting vehicle that never really caught on. It's a sporty Prius in sleeker hatchback clothing and was aimed at the Audi A3 when it hit the market in 2011. Since then, though, the CT has averaged a meager 16,000 sales per year. For that reason, the hybrid hatch won't be redesigned at the end of its life cycle. And according to Lexus' European brand boss, Alain Uyttenhoven, it could be replaced by a crossover. While you may lament yet another CUV hitting the market, Lexus needs a small car that sells in big numbers. Uyttenhoven told Autocar the brand aims to move 100,000 units per year in Europe to "give us visibility in the market." For 2016, European sales are on pace to hit just 70,000 units, with 10,000 of those coming from the CT 200h. He sees an opportunity for the right little Lexus based on the recent nature of the European luxury market. View 29 Photos According to Uyttenhoven, "a full 50 percent of the European luxury car market exists below the [$44,600] mark," and the only model Lexus has at that point is the CT. Put another way, the company has a remarkably slow seller as its sole representative for half of an entire continent's luxury market. Enter the crossover. Replacing the CT with a crossover makes a great deal of sense. The body style is getting more and more popular by the day, especially in the sub-compact and compact markets. Adding a smaller model – below the current NX crossover but larger than the LF-SA concept shown in Geneva – would allow Lexus to challenge the Mercedes-Benz GLA, the BMW X1, and the Audi Q3. We're betting the small crossover would use the Toyota C-HR as its basis and add a Lexus-correct heavily creased skin. Hybrid power is a given for the European market, where almost all Lexuses sold are gas-electric, but a conventional gas variant could join it in the US. That would give Lexus three hybrid CUVs in three popular sizes, alongside the NX and RX. With a forthcoming RX-based three-row on the horizon, the brand would have a full lineup of crossovers ready to take over the world. We'll miss the quirky CT when it goes, but it's hard to stop volume-driven progress. Related Video:

Autoblog Podcast #339

Farewell, Zach Bowman; Pikes Peak 2013; Datsun; 2014 Ram lineup
Episode #339 of the Autoblog Podcast is here, and it's the last rodeo for Zach Bowman before he departs for other pastures. The crew this week consists of Dan Roth, Zach Bowman and Jeff Ross, who talk about the astounding records set at this year's Pike's Peak hill climb, the return of the Datsun brand name and the recently-announced 2014 Ram truck lineup. Of course, we start with the garage and end with your questions and comments. For those of you who hung with us live on our UStream channel, thanks for taking the time. You can follow along after the jump with our Q&A. Thanks for listening!
Autoblog Podcast #339:

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.