Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/virtualw/public_html/Archive/IndividualNews.php on line 12
VWN News: GoPro recalls drone after power failure
Untitled Document
Not a member yet? Register for full benefits!

Username
Password
 GoPro recalls drone after power failure

This story is from the category Business
Printer Friendly Version
Email to a Friend (currently Down)

 

 

Date posted: 09/11/2016

Action camera firm GoPro has recalled its new drone after reports of power failures.

The company said there had been a “small number of cases” of the drone malfunctioning during flight.

GoPro said it would rectify the problem and put the Karma drone back on sale once the issue was resolved. Anyone who has bought the $799 (£646) drone can get a full refund, it said.

GoPro launched the Karma in September along with two new cameras.

The cameras are not affected by the recall, the company said on Tuesday.

GoPro issued the recall notice just as polls began to close in the US presidential election - giving rise to accusations the company was seeking to bury the news.

Instructions for people who bought the drone have been posted on the GoPro website.

See the full Story via external site: www.bbc.co.uk



Most recent stories in this category (Business):

14/12/2016: UK: Amazon makes first drone delivery

09/11/2016: GoPro recalls drone after power failure

16/09/2014: Airwares operating system makes drones simple to build and modify for multiple applications

10/09/2014: Barclays taps vein biometrics in bank fraud fight

28/08/2014: Bitcoin shows staying power as online merchants chase digital sparkle

02/10/2013: Telecommuting can be beneficial for a work/life balance

07/09/2013: Nintendo faces 'path to irrelevance', says Atari founder

14/06/2013: Smart technology makes its way into lighting



Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0