on 2040-cars

Auto blog

Lexus talks LFA successor

Did you just miss out on purchasing one of the 500 Lexus LFA supercars built between 2010 and 2012? "No big deal," you're probably thinking, "I'll just wait until the next time Lexus builds a supercar." Well, we're afraid that you'll be waiting quite a long time. And by long time, we mean about 30 years.
That's according to a report from Bloomberg, which indicates that yes, Lexus is looking at a follow-up to the V10-powered, carbon-fiber-bodied LFA.
"Akio [Toyoda] believes that every generation deserves to have a car like an LFA, so we're building an LFA for the generation we have today," Lexus Executive Vice President Mark Templin told Bloomberg. "At some point, there may be another special car for another generation."

40+ cars that barely avoid the gas guzzler tax

The Gas Guzzler schedule, with mpg ratings and charges that haven't changed since 1991, lays out which fuel-swillers owe what to Uncle Sam.
I started thinking about the "Gas Guzzler Tax" - considerably less well known as The Energy Tax Act of 1978 - when I was driving Dodge's new Challenger SRT Hellcat last week. Unsurprisingly for a car that can burn 1.5 gallons of gas per minute at max tilt, theoretically able to empty a full tank of premium in about 13 minutes, the Hellcat will be subject to the Gas Guzzler Tax schedule when it goes on sale.

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.