Skip navigation
21180 Visits Today

Mazda recalls 3500 BT-50 utes

  • image

    Mazda BT-50 Dual Cab.

A defect recall on the Ford Ranger has also hit its shared-platform relative, the Mazda BT-50.

The two utes are twins under the skin – and in parts of the cabin, including the faulty rear seatback latch that saw a mid-October recall on 4258 Ford PX Rangers and has now been cited on the dual-cab BT-50.

“There are about 3500 Mazda BT-50s across Australia that are affected by the recall,” Mazda Australia spokesman Tony Mee says.

The defect is on BT-50s sold between late May 2011 and mid-February 2012, with the VIN numbers from MM0UP0YF100100501 to MM0UP0YF100108651. The recall notice says the rear seatback latch fitted to affected vehicles may not engage correctly, resulting in the rear seatback latch not being secured to the body striker and causing the rear seatback to fall forward.

The defect poses a safety hazard to passengers, and owners are warned not to use a rearward-facing child seat in the vehicle until the defect is fixed. However Mee says there have been no reports of incidents or injuries related to the defect.

“Not one report,” he says, adding that the fix is a relatively swift one. “Owners have been contacted by mail asking them to speak to their local dealer to arrange a convenient time to repair the car. The repair itself takes less than an hour,” Mee says.

The dealer will replace the link between the rear seatback release strap and the rear seatback locking mechanism with a revised component.

The Ford recall was the second on the Ranger within months, with an August notice issued on 16,287 Rangers built in Thailand from September 2006 to June 2011 for a defect that risked fracturing of the towbar welding.
 

Add your comment on this story

Indicates required

We welcome your comments on this story. Comments are submitted for possible publication on the condition that they may be edited. Please provide your full name. We also require a working email address - not for publication, but for verification. The location field is optional.