2010 Is 250c-convertible-navigation-heated & Cooled Seats-xenon-back-up Cam on 2040-cars

Auto blog

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.

Autoblog Podcast #318

Toyota back on top, Barrett Jackson, Crowdsourcing your Dodge Dart payments, Nissan and Toyota double down on pickups
Episode #318 of the Autoblog Podcast is here, and this week, Dan Roth, Zach Bowman and Michael Harley talk about Toyota regaining the No. 1 sales crown, getting your friends and family to buy you a Dodge Dart, Barrett-Jackson, and Toyota and Nissan remaining committed to their pickup trucs. We wrap with your questions, and for those of you who hung with us live on our UStream channel, thanks for taking the time. Keep reading for our Q&A module for you to scroll through and follow along, too. Thanks for listening!
Autoblog Podcast #318:

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.