2012 Dodge Challenger R/t on 2040-cars

Auto blog

Race Recap: Rolex 24 at Daytona was fast and feisty

Let the record show that victory at the 2015 Rolex 24 at Daytona went to the No. 02 Chip Ganassi Racing with Felix Sabates Target/Ford EcoBoost Riley DP driven by Verizon IndyCar drivers Scott Dixon and Tony Kanaan and NASCAR drivers Jamie McMurray and Kyle Larson. The winner did 740 laps to cover 2,634.3 miles in 24 hours and 57.667 seconds. That's a statement to this year's pace in spite of 18 cautions, two more than last year: the Michael Shank Racing Ligier got pole with a time of 1:39.194, slower than last year's pole time of 1:38.270; however, the winning car last year only did 695 laps. The fight for top honors was shaved to a four-car battle over the first third of the event. The No. 02 Ganassi car took the lead on the first lap, swapping it well into the night with the No. 01 Ganassi car, the No. 10 Wayne Taylor Racing Corvette DP, and the defending champion No. 5 Action Express Corvette DP, all of them staying within about 20 seconds of one another. The Action Express car had a fuel connector come loose and lost three laps getting towed back to the pits to have it reattached, but was back in the lead 18 hours in. The No. 01 Ganassi car dropped out with recurring clutch problems 22 hours in, retiring not long after. A race-within-the-race is where the concluding action happened, a seven minute, 30-second dash from the end of the last caution to the checkered flag. During the penultimate pit stops with an hour to go, Dixon was in second place followed Jordan Taylor in the Wayne Taylor Racing DP into the pits but beat him out, taking the lead. The Action Express car was in third. In the last pit stops of the race, Dixon gained even more time, getting a four-second advantage over Taylor. Then a full-course caution came out twenty minutes before the finish when a Prototype Challenge car hit the wall and caught fire, bunching up the field. That closed the pits, but the Wayne Taylor Racing car had to pit during that yellow because of a miscalculation of driver time. No driver can be behind the wheel for more than four hours in a six-hour period but Jordan Taylor was going to go over, so he came in to swap out for brother Ricky. That cost the team any chance of second place, since they took an additional drive-through penalty for entering closed pits. When the track went green again, Sebastien Bourdais in the Action Express car stayed all over Dixon for the final five laps but couldn't get around him.

Barracuda's Dodge branding no biggie, but what about engines?

Rumors about a revival of the Barracuda nameplate have been circulating for years now, though which brand it might fall under has been a bit of a mystery. Initial speculation had the car labeled an SRT product, but that acronym has since returned to its former role as a sub-brand for top-performance Mopars. Thanks to leaks from a recent FCA dealership event, we know the Barracuda is back on the table but will be sold under the Dodge umbrella, a move that has been generating a bit of ire from Pentastar fanatics, as the car was originally part of the defunct Plymouth brand. Given what's known about the new model, however, the badge is the least of my concerns about the new car. Let's start with the re-branding itself. This isn't the first time Chrysler has shuffled models around to different brands. The current-generation Viper spent two years as the flagship model under the SRT banner, only to return to Dodge for 2015 when SRT resumed its former role as a sub-brand. Years ago, the Neon was sold as a Plymouth, a Dodge, and a Chrysler model, depending on where you shopped for one. When Plymouth ceased to exist, the last few years of Prowler production got Chrysler badges instead. Then there's the new Jeep Renegade, a model whose name was born out of a trim level. The Barracuda might not turn out to be a muscle car in the way we currently define them. Further examples of naming liberties taken throughout automotive history could fill a book, but suffice it to say that these days a model's name has very little to do with the vehicle itself or any legacy it might have. The Barracuda name might be a particularly sacred cow with enthusiasts, but to me, a much bigger concern is the fact that the car might not turn out to be a muscle car in the way we currently define them. News from the Fiat Chrysler dealer briefing earlier this week indicates that when the next Charger debuts it will share its platform with the Barracuda, much the way the Charger and Challenger are twinned now. One difference is that the Barracuda is tipped to be offered as a convertible, while the modern Challenger is tintop-only. The Charger and Barracuda will use the rear-drive platform developed for Alfa Romeo's new Giulia, itself designed as a BMW M3 fighter both from a dimensional and dynamic standpoint; the Barracuda is expected to be slightly smaller than the current Challenger.

Dodge to resurrect Scat Pack?

Before social media ever existed, if automotive enthusiasts wanted to be noticed or recognize other fans, they joined a car club. For Dodge muscle car lovers from 1968 through 1971, that group was known as the Scat Pack. Just like the Charger, Challenger and Dart nameplates, it looks like the Scat Pack could be getting a resurrection by Chrysler.
Automotive News is reporting that Chrysler recently renewed its trademark on the Scat Pack name, and while this is in no way a guarantee that the name will return, AN talked to Tim Kuniskis, Dodge President and CEO, who stoked the fire a little more. In the article, Kuniskis said that the name is "a very important part of our history" and added that "we like the whole idea of having a Scat Pack of cars." Scat Pack models were identified by their bumblebee stripes and helmet-wearing bumblebee logo, and the idea of a modern Scat Pack doesn't seem all that outlandish in light of recent vehicles like the Charger SRT Super Bee and the Ram 1500 Rumble Bee Concept.
What do you think, is this a cool idea, or is it just an unwelcome bit of nostalgia? Have you say in Comments.