Home / News / Mobile Phone News / Child ‘suffered burns’ after Galaxy Note 7 exploded in his hands – report

Child ‘suffered burns’ after Galaxy Note 7 exploded in his hands – report


samsung galaxy note 7

A 6-year-old boy has been burned by an exploding Samsung Galaxy Note 7, according to a new report.

A child in Brooklyn, New York has “suffered burns” after a Galaxy Note 7 he was using “burst into flames”, as reported by the New York Post. The Post says he was rushed to hospital at 20:00 on Sunday with burns to his body.

“The child was watching videos on the phone when the battery exploded. It set off alarms in my house,” Linda Lewis, the boy’s grandmother, told the Post. She added: “He is home now. He doesn’t want to see or go near any phones. He’s been crying to his mother."

According to the article, the boy’s family has been in contact with Samsung about the incident, but it’s not clear whether any resolution or settlement has been agreed.

Related: iPhone 8

The news comes around a week after Samsung initiated a global recall of the Galaxy Note 7, citing battery issues. An internal investigation discovered that some batteries were faulty, which created a tangible fire hazard. The investigation was launched after several users reported that their new phones had spontaneously combusted.

Since then, the FAA – America’s airline regulator – has warned Galaxy Note 7 owners against using or charging their phones in airplanes. After that statement was put out, Samsung’s market value plummeted by an incredible $10 billion. It’s believed that a number of airlines have already banned the phone from being used in-flight.

It’s sure to be a huge disappointment for Samsung as the Galaxy Note 7, which only launched last month, landed to extremely positive reviews from critics. The phone followed on from the equally well-received Galaxy S7, but now faces stiff competition from the iPhone 7 Plus, which will be probably be significantly less…fiery?

Related: Samsung Galaxy S8

Watch: iPhone 7 vs Galaxy S7

What would you like to see from the Galaxy Tab S3? Let us know in the comments.


September 12, 2016, 5:18 pm

Wow, who even knew that the Samsung Galaxy Note 7 was a fire hazard - why wouldn't you give it to your kids to play with?


September 13, 2016, 5:27 pm

It was a Galaxy Note Core, not a Note 7


September 13, 2016, 5:32 pm

Even now the rate that they have caught fire is below that of average phones and other large Lithium Ion Battery products. The failure rate is less than 0.01%. Unless I owned 200 of them I would be comfortable using them until they release the replacement. I might underclock the phone if I was using it often.

Luis R

September 14, 2016, 4:21 am

For that type of failure, it is too much. Enough to prompt authorities to ban its use in airplanes. Still, this particular case was not a Note 7. The news report is wrong in this regard. Neither I could find any report of one causing a fire in an airplane.


September 14, 2016, 6:20 am

The first Airline to ban them was Australian, and didn't do so because of the number of them that failed, but because a man lost his home to a fire caused by one and it made major news and they didn't know how bad the issue was yet, so to cover themselves, get good publicity and sating their customers concerns they stopped their use and controlled how you check them. Then people heard the news of this internationally and airlines very publicly banned them even though the consumer and safety departments only recomended and not ordered that they shouldn't be used because if they ordered them not allowed and forced recall conditions most of the markets LiIon products would be up for it too.

Should a Note 7 be allowed on a commercial flight? Until they determine and disclose the exact issue no. Otherwise it is more dangerous to cross the street in casual weekend traffic at night.

I think my problem is all the FUD and hysteria and misreporting on this when for once a Corperation did something good for both them and the customer and is being punished for it.

comments powered by Disqus