Pre-auction, Last Chance, on 2040-cars

Auto blog

2016 Lexus RC 200t Quick Spin

Cars like the BMW 4 Series, Cadillac ATS coupe, and Audi A5 exist not as volume cars, but as aspirational products designed to draw in the young and the young at heart. The humble four-cylinder turbo, offered in each car listed above, provides an accessible point of entry for lifestyle buyers that want the statement of a sporty coupe without the eagerness, fuel inefficiency, or cost of a big six-cylinder engine. Now, Lexus is throwing its hat in the ring with a turbocharged version of its polarizing RC coupe. We took the new RC 200t out for a day on the winding roads of the Pines to Palms Highway near Palm Springs, CA, and found that while Lexus' new engine will draw new customers, they probably won't like what they find. Driving Notes The RC joins the IS, GS, and NX as members of Lexus' four-cylinder turbo clan. There's 241 horsepower and 258 pound-feet of torque on offer here, numbers that compare favorably with the BMW 428i (240 hp and 260 lb-ft) and Audi A5 (220 hp and 258 lb-ft). None of that matters, though, because the turbocharged RC is easily the slowest car in its class. You'll struggle to keep pace with stuff like the Hyundai Veloster Turbo. The RC 200t somehow takes 7.3 seconds to get to 60 miles per hour. That's a second slower than the A5, and over half a second slower than the 4 Series or Cadillac ATS. You can't drive a car that looks as wild as this and take that long to get to 60. Blame it on the RC's 3,737-pound weight. Lexus only saved 11 pounds by switching out a 3.5-liter V6 for the 2.0-liter turbo. The BMW and Cadillac both weigh well under 3,500 pounds. Even the RC's four-door fraternal twin, the IS 200t, is 150 pounds lighter (and only takes 6.9 seconds to get to 60). The RC needs a diet, plain and simple. If Lexus truly wants to compete against the Germans and Cadillac, a snappier transmission is in order. Like the GS we talked about yesterday, the Aisin eight-speed is fine on upshifts – it's still not as fast as the 4 Series' ZF eight-speed auto – but it suffers when it's time to change down. Around town, it's less of a problem, but on the twisty mountain roads outside of Palm Springs and on the freeways, the RC's gearbox kept tripping over itself. We'd love to see what the 2.0-liter turbo engine could do in a lighter car, because it's a real charmer. The broad 1,650-to-4,400-rpm torque peak gives drivers a lot of space to play, although the RC does feel flat-footed as you crest 5,000 rpm.

2014 Lexus IS prototype

No one was comparing the IS to the BMW 3 Series, and for Lexus that was a problem.
At the beginning of 2011, we rocked up to the parking lot at Southern California's Santa Anita Raceway to test the 2012 Lexus GS. This was the first sedan in the luxury brand's lineup to reset its intentions on the balance of sport and luxury. The previous GS had blanched into mute tepidity, and the new generation we drove on an autocross course and on a canyon road corrected just about everything; we liked its looks, and the Variable Gear Ratio Steering- and Adaptive Variable Suspension-equipped car moved its abilities into the realm of a true sports sedan, and it was great to drive. They absolutely nailed it.

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.