Fatal: Takata sued for $1.9b in Canada

Defective airbags reason behind class action lawsuit.


Afp March 28, 2015
The plaintiffs are seeking a total of $1.9 billion for personal injuries, car repairs and an expected loss in value of their vehicles included in a massive global safety recall, said Merchant Law Group LLP lead partner Tony Merchant. STOCK IMAGE

OTTAWA: Canadian drivers have launched three class action lawsuits against embattled Japanese auto supplier Takata over defective airbags linked to at least five fatalities worldwide, lawyers confirmed.

The plaintiffs are seeking a total of $1.9 billion for personal injuries, car repairs and an expected loss in value of their vehicles included in a massive global safety recall, said Merchant Law Group LLP lead partner Tony Merchant.

In addition to Merchant, two other Canadian law firms have launched suits, and a fourth is considering doing so.

If they are certified by a judge, they would likely be lumped into a single class action lawsuit in the coming months.

About 20 million vehicles produced by some of the world’s biggest automakers are being recalled due to the risk their Takata-made airbags could deploy with excessive explosive power, spraying potentially fatal shrapnel into the vehicle.

The problem has been linked to at least five deaths globally, with a sixth under investigation.

“They’re making products that are like grenades going off,” said Merchant. “These things are supposed to bring safety and instead they’re a danger.”

The Canadian litigation involves 400,000 vehicles equipped with Takata airbags. Potentially affected automakers include Acura, BMW, Chrysler, Dodge, Ford, Honda, Infiniti, Lexus, Mazda, Mitsubishi, Nissan, Pontiac, Subaru and Toyota.

Published in The Express Tribune, March 29th, 2015.

Like Business on Facebook, follow @TribuneBiz on Twitter to stay informed and join in the conversation.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ