04 Srt-10 8.3l Engine 22k Driving Salvage Wrecked Donor Rolling Chassis 505 Hp on 2040-cars

Auto blog

Junkyard 1983 Dodge Rampage has Franco-American roots

Lee Iacocca and the K-Cars get most of the credit for saving Chrysler after the company's 1979 bailout by the US government, but the success of the Simca-derived Omnirizon platform was a large, if overlooked, component of Chrysler's early-1980s resurgence. The Dodge Omni and Plymouth Horizon were sold in the United States for the 1978 through 1990 model years, and variants included the 1983-1987 Dodge Charger and the Rampage, this well-worn example of which I spotted in a Denver self-service wrecking yard last week. The early Omnirizons came with a Volkswagen-sourced 1.7-liter engine, but all of the Rampage pickups (and their near-identical Plymouth Scamp siblings) came from the factory with a 2.2-liter K-Car engine making 96 horses. This truck has a 4-speed manual transmission, which would have made it reasonably quick by Malaise Era standards. This one had plenty of body filler and rust, even before the crash that sent it on that final tow-truck ride to this place, so it wouldn't have been worth restoring. Still, we can hope that some of its parts will live on in other L-body trucks. Related Video: Featured Gallery Junked 1983 Dodge Rampage in Denver View 16 Photos Chrysler Dodge Automotive History Truck Classics dodge rampage

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.

FCA UConnect fiasco could set over-the-air updates back years

Since cars have become more software dependent, most major automakers have been inching toward enabling over-the-air updates to keep vehicle electronics, ranging from infotainment systems to safety features, current. But there are only two car companies — Fiat Chrysler and Ford —± currently doing OTA updates, and on a limited basis. GM CEO Mary Barra announced last summer that the automaker will launch a new EV architecture and infotainment system capable of over-the-air updates "before 2020." The one exception, per usual, is Tesla. Since the release of the Model S almost six years ago, the maverick EV automaker has made routine OTA software updates a core part of its vehicle platforms and value proposition, and has sent out updates for everything from adjusting ride height to enabling Autopilot, largely without incident. When I've asked automakers why they can't do the same thing, I've heard reasons ranging from running afoul of their dealers (and archiac regulation) to security concerns. Automakers like Ford and General Motors say they want to act like tech companies, which routinely send out OTA updates for a wide range of devices, but overall the car industry still moves at a very cautious snail's pace. And when automakers do try to move faster and take more risks — unlike with a smartphone update, which people bitch about but live with — the consequences can be significant when things go wrong. That's the case with Fiat Chrysler America and its recent public-relations nightmare when an OTA update went awry. The update went out at the end of last week for the Uconnect system in late-model vehicles, and it made head units go into a near continuous reboot, which caused owners to not only lose access to entertainment features, but also critical functions like emergency assistance. Almost immediately, owners took to Twitter to express outrage, and FCA was caught flatfooted. A tweet went out on Monday on the UconnectCares Twitter account that read, "Certain 2017 & 2018 Uconnect systems may experience a reboot every 45-60 seconds. Our Engineering teams are investigating the cause and working towards a resolution.