Maruti announces voluntary recall for 1,279 vehicles


25 Jul 2018

Maruti recalls 1,279 units of Swift, Dzire: Is yours affected?

On Wednesday, Maruti Suzuki India announced that it would recall 1,279 units of the new Swift and Dzire to probe a possible fault in their airbag controller units.

The company said that it would recall 566 new Swift units, and 713 new Dzire units manufactured between May 7 and July 5.

Owners of the affected vehicles will be contacted July 25 onwards.

Here's more.

Maruti Suzuki's statement on the recall

"Starting July 25, 2018, owners of the vehicles included in this recall campaign will be contacted by Maruti Suzuki dealers for inspection and replacement of the faulty part free of cost," said the company in a statement.


How to check if your vehicle is affected

How to check if your vehicle is affected

If you're concerned about whether your car falls among the affected vehicles, you can check the same on Maruti Suzuki's website.

All you need to do is file your chassis number - MBH for Swift, and MA3 for Dzire followed by the 14-digit alpha-numeric chassis number.

You can find your chassis number on the vehicle ID plate or in vehicle invoice/registration documents.

Love Business news?

Stay updated with the latest happenings.

Yes, notify Me

Earlier incident

Earlier, Maruti initiated a service campaign for 52,686 vehicles

Notably, this isn't the first time Maruti Suzuki vehicles have encountered problems this year.

In May, the company asked the owners of 52,686 new Swift and Baleno models to get their vehicles serviced to inspect a possible fault in the brake vacuum hoses of the cars.

Maruti, however, didn't opt for a recall of the cars as the fault posed no threat to safety.

Indian car manufacturers have to follow a voluntary recall policy

Automobile manufacturers in India are required to follow a voluntary recall policy to rectify manufacturing defects in their vehicles free of cost, under a policy adopted by the Society of Indian Automobile Manufacturers (SIAM) in July 2012.

Share this timeline

Share this timeline

Ask NewsBytes
User Image

Next Timeline