GM Recalls 218K Chevrolet Aveos for Fire Risk
Chevrolet announced today that it will call back 218,000 Chevrolet Aveos because of a potential fire risk.
Affected models range from the 2004 to 2008 model years and are equipped with daytime running lights. The DRL module located in the center console in the instrument panel might generate enough heat to melt itself and that can cause a fire.
According to NHTSA documents, General Motors doesn’t know how to fix the issue yet and hasn’t announced a timeline for the recall campaign. The automaker is still developing a way to fix the problem.
Today’s recall announcement comes after the company said yesterday that it will recall 2.42 million vehicles in a campaign spanning several nameplates for a variety of issues. The latest announcement is the 30th recall campaign for the Detroit automaker so far this year and marks it creeping close to having called back 14 million units since January. Currently, the total sits at over 13.8 million.
General Motors said yesterday that it expects to spend $400 million on recall related costs in the second quarter, but that figure doesn’t include today’s announcement. In the first quarter, GM saw its net profit all but wiped out by costs associated with its controversial ignition switch recall.
Discuss this story at our GM forum
Luke is an energetic automotive journalist who spends his time covering industry news and crawling the internet for the latest breaking story. When he isn't in the office, Luke can be found obsessively browsing used car listings, drinking scotch at his favorite bar and dreaming of what to drive next, though the list grows a lot faster than his bank account. He's always on <A title="@lukevandezande on Twitter" href="http://twitter.com/lukevandezande">Twitter</A> looking for a good car conversation. Find Luke on <A title="@lukevandezande on Twitter" href="http://twitter.com/lukevandezande">Twitter</A> and <A title="Luke on Google+" href="http://plus.google.com/112531385961538774338?rel=author">Google+</A>.
More by Luke Vandezande
Comments
Join the conversation