1969 Dodge Coronet Superbee A12 on 2040-cars

Auto blog

High-performance 2018 Dodge Durango SRT spied

Dodge is working diligently on revamping its lineup with new and refreshed models, including the high-performance Durango SRT due in 2017. Spy shooters captured a Durango with an aggressive front end that appears to fit the SRT bill, though it could just be a refreshed Durango. This Citadel-badged prototype is nearly identical to the current three-row SUV. The front fascia, which is being held in place by tape and has numerous rough edges, features a massive vent at the bottom and a distinct, three-holed air intake system just below the grille. The grille is also lacking the Durango's cross-like design. The front end appears to have gaping holes on both sides, with the right side being covered up by tin foil. The extra vents could be there for aerodynamic purposes, for cooling purposes, or just a pair of fog lights that Dodge doesn't want people to see. The high-performance SUV is expected to get a full makeover on the outside, which includes sportier wheels, a more aggressive hood, athletic body panels, and some aerodynamic components. The meat of the SUV, the engine, is still a mystery. While the Hellcat brothers feature a 707-horsepower, 6.2-liter supercharged V8, a previous report by Automotive News claims the upcoming Durango SRT will be powered by a 6.4-liter V8 engine. The 475-horsepower motor is currently in the Jeep Grand Cherokee SRT. Regardless of what type of engine the Durango will have, it looks like Dodge really is working on a high-performance SUV to enter the continually-growing segment. Related Video: This content is hosted by a third party. To view it, please update your privacy preferences. Manage Settings. Featured Gallery 2018 Dodge Durango SRT Spy Shots News Source: Automotive NewsImage Credit: Chris Doane Automotive Spy Photos Dodge SUV Future Vehicles Performance

Chrysler almost smothered the Hellcat before it lived

Chrysler's 6.2-liter supercharged Hellcat V8 was an absolute sensation from the very moment it was announced, and honestly, how could it not have been? Packing 707 horsepower and 650 pound-feet of torque, its numbers immediately put every other production muscle car (and many supercars) to shame. Plus, we soon learned that would be wrapped in a package retailing for around $60,000 - a pittance compared to other vehicles offering similar grunt. However, the Hellcat almost never got the chance to rumble under the hood of the Challenger and Charger.
The Hellcat was initially proposed back in 2011, back when Fiat was deciding its future strategy for Chrysler Group, according to Automotive News. At the time, the company was just emerging from its bankruptcy doldrums, and an ultra-high-performance V8 wasn't exactly a must-have item. The program didn't move forward. However, SRT engineers kept fighting, according to AN, and four months later, they received the green light to pull the project off the shelf and continue developing the Hellcat. The muscle car world is certainly better for that decision.
The work of those engineers focused on taking Chrysler's standard 6.2-liter V8 and making it reliably handle all of the extra power from the supercharger. "It came down to micron levels of changes in the crank to be able to withstand the pressures of the engine," said Chris Cowland, director of advanced and SRT powertrain, to Automotive News. The changes amounted to switching out about 91 percent of the parts to make the Hellcat, including some quite minuscule alterations. For example, the washer holding the supercharger pulley is embedded with industrial diamonds to keep it from slipping.

FCA seeks partner to keep building Dodge Dart, Chrysler 200

Mere weeks after FCA announced it was shutting down production of the Dodge Dart and Chrysler 200, new hope emerges to give the sedans a stay of execution. Speaking at the Geneva Motor Show last week, Sergio Marchionne said that the company was looking for a partner "who is better at it than we are and who has got capacity available" in order to continue building the models on its behalf. "There are discussions going on now," said Marchionne, according to Motor Trend. "I think we will find a solution. We continue to talk. It's both a technical solution and an economic one. We need to find a solution that works economically." Contracting vehicles to be manufactured offsite is more common practice among European automakers than it is with American ones. Chrysler's former patron Mercedes, for example, has the G-Class built for it by Magna Steyr in Austria, the A-Class by Valmet in Finland, and the R-Class by AM General in Indiana (even though it's no longer sold in the US). This arrangement would, on the surface at least, appear more similar to the deal that Toyota struck with Mazda to build the Scion iA, drawing on the contractor's expertise and capacity to build the small sedan on the client company's behalf. Only rather than basing a new model on one of the partner's existing ones, this deal would ostensibly continue building FCA models on FCA platforms using FCA components. We'll have to wait to find out with whom FCA strikes up the manufacturing deal, but we wouldn't be surprised to see Marchionne turn to a partner he already knows. The company is, after all, at the center of an intricate web of joint ventures and manufacturing contracts. The Fiat 124 Spider, for example, is built by Mazda. The Fiat Sedici that preceded the 500X was built by Suzuki. Models like the Dodge Stealth and Eagle Talon were built in Illinois at the Diamond-Star Motors joint venture before Mitsubishi took it over altogether. And Dodge continued selling the Mercedes-made Sprinter long after DaimlerChrysler split. The Ram ProMaster, though built by FCA in Mexico for the North American market, stems from a partnership in France with PSA Peugeot Citroen. And the ProMaster City is built in a joint-venture plant in Turkey, from which it's also sold by GM as an Opel in Europe and a Vauxhall in the UK. With all those deals coming and going, after all, what would one more add to the complexity?