Jump to content

Apple gets dragged into court by relatives in a plane crash, blaming an exploding iPhone

ItsMitch
12 hours ago, Not_Sean said:

I'm no apple fanboy, but when apple wins I hope they sue the living crap out of TMZ for slander and all that other crap, The less of these "Publications" in the world the better. 

im no fake news supporter, but what else than reporting on the case did the publication do? 

Link to comment
Share on other sites

Link to post
Share on other sites

16 minutes ago, GoldenLag said:

im no fake news supporter, but what else than reporting on the case did the publication do? 

 

69FBD76B-089A-42DF-A54E-22E4671151A5.png

Link to comment
Share on other sites

Link to post
Share on other sites

32 minutes ago, Wolther said:

-snip-

looks like avarage over clickbaity article if you ask me

Link to comment
Share on other sites

Link to post
Share on other sites

12 minutes ago, GoldenLag said:

looks like avarage over clickbaity article if you ask me

Not when 66 people die. You’d think that whole part would be more important than a possible cause. It’s clear what the intent of the article is, to get readers, not to report on information. Not to mention disrespect to families, that exclamation mark indicating excitement that it happened 

 

The entire article is built around apple.

Edited by Wolther
Link to comment
Share on other sites

Link to post
Share on other sites

I wonder what the effects of the continued radiation exposure from regular high altitude flights are on Lithium Batteries? I'm not saying I think this lawsuit has any merit but its an interesting thought.

Link to comment
Share on other sites

Link to post
Share on other sites

7 hours ago, Oh Schmitt said:

I wonder what the effects of the continued radiation exposure from regular high altitude flights are on Lithium Batteries? I'm not saying I think this lawsuit has any merit but its an interesting thought.

The, I believe, 5% higher cancer risk is probably more of a concern.

PSU Tier List | CoC

Gaming Build | FreeNAS Server

Spoiler

i5-4690k || Seidon 240m || GTX780 ACX || MSI Z97s SLI Plus || 8GB 2400mhz || 250GB 840 Evo || 1TB WD Blue || H440 (Black/Blue) || Windows 10 Pro || Dell P2414H & BenQ XL2411Z || Ducky Shine Mini || Logitech G502 Proteus Core

Spoiler

FreeNAS 9.3 - Stable || Xeon E3 1230v2 || Supermicro X9SCM-F || 32GB Crucial ECC DDR3 || 3x4TB WD Red (JBOD) || SYBA SI-PEX40064 sata controller || Corsair CX500m || NZXT Source 210.

Link to comment
Share on other sites

Link to post
Share on other sites

20 hours ago, Cheezdoodlez said:

Using Chinese cheapo chargers and cables and dropping your phone are two things. Fast charging and wireless charging also heats up the battery more than regular chargers. 

I see, thank you. I have some cheap Chinese unbranded chargers, but I usually use them for little USB gadgets like lights or fans or such. Not charging a phone. Although I do drop my phone a lot. I didn't know that could lead to battery failure.

Yes, it's 2871 as in the year 2871. I traveled all this way, back in time, just to help you. And you thought your mama lied when she said you were special-_-

Link to comment
Share on other sites

Link to post
Share on other sites

On ‎14‎/‎05‎/‎2018 at 10:00 PM, Christophe Corazza said:

 

Now, if the pilot had a Samsung phone... ;)

He wouldn't be a pilot, That's one of their safety checks, You carrying an Samsung Note ?

yes....?

Sorry you're not allowed to be a pilot 

Some people prefer a challenge, I just band my head against a wall until my method works...

Link to comment
Share on other sites

Link to post
Share on other sites

9 hours ago, valdyrgramr said:

To be fair, she wasn't suing them over the crash itself.  She was suing them because they found a defect with the seatbelt.  Had that defect not been there Paul could have gotten out, but yes his friend was an idiot for drifting/reckless driving.

After crashing into a tree at 200 km/h+ i doubt anyone was concious in that car if they were still alive after that crash.

Computer users fall into two groups:
those that do backups
those that have never had a hard drive fail.

Link to comment
Share on other sites

Link to post
Share on other sites

9 minutes ago, mate_mate91 said:

After crashing into a tree at 200 km/h+ i doubt anyone was concious in that car if they were still alive after that crash.

The crash happened around 140km/h, whether or not he was conscious is something else (you certainly could still be conscious, and maybe there was evidence that he was awake?). 

 

@valdyrgramr his friend was reckless for taking the corner too fast; he was an idiot for not replacing the tires. The driver was experienced and the car is more than capable of making the turn. The problem was the tires had deteriorated to garbage.

PSU Tier List | CoC

Gaming Build | FreeNAS Server

Spoiler

i5-4690k || Seidon 240m || GTX780 ACX || MSI Z97s SLI Plus || 8GB 2400mhz || 250GB 840 Evo || 1TB WD Blue || H440 (Black/Blue) || Windows 10 Pro || Dell P2414H & BenQ XL2411Z || Ducky Shine Mini || Logitech G502 Proteus Core

Spoiler

FreeNAS 9.3 - Stable || Xeon E3 1230v2 || Supermicro X9SCM-F || 32GB Crucial ECC DDR3 || 3x4TB WD Red (JBOD) || SYBA SI-PEX40064 sata controller || Corsair CX500m || NZXT Source 210.

Link to comment
Share on other sites

Link to post
Share on other sites

I really, HIGHLY doubt an iPhone that caught fire could have taken down an entire Airbus A320

 

Because think about it, don’t cockpits have a fire extinguisher somewhere? I’ve seen many in the cabin, so it’s fair to assume that the cockpit has one too. If the iPhone had caught fire, the pilots would have extinguished it in some way. Furthermore, it was right next to him. So if anything happened, you’d know they’d have dealt with it pronto.

 

If you look at past air crashes involving in-flight fires, many of them have fires that started in areas that aren’t visible at all. Some include;

  • Swissair Flight 111: McDonnell Douglas MD-11 that crashed due to an in-flight fire which was caused by an arc from the IFE’s wiring, igniting flammable metallized-mylar insulation and causing a catastrophic fire behind the pilots which rendered electrical systems in the cockpit inoperable. 
  • ValuJet Flight 592: McDonnell Douglas DC-9 that crashed into the Everglades shortly after takeoff due to a fire in the cargo hold caused by improperly packed oxygen generators that quickly grew uncontrollable.
  • Air Canada 797: McDonnell Douglas DC-9 that suffered an in-flight fire caused by an electrical arc underneath the washroom. Although the hidden fire made the plane difficult to fly and difficult to breathe, the plane did make an emergency landing but while evacuation was underway, a flashover occurred, killing 23 who have yet to evacuate.
  • Nigeria Airways Flight 2120: Douglas DC-8 wet-leased from NationAir that suffered an inflight-fire caused by landing gear tires that caught fire due to underinflation and subsequently led to the failure of critical systems and a ruptured fuel tank when the gear was retracted. Despite managing to fly the crippled jet to align with the runway, the plane sadly crashed short of it.
  • Saudia Flight 163: Lockheed L-1011 which suffered an inflight-fire on its aft cargo bay. Despite managing to make an emergency landing, the delayed evacuation caused the fire to eventually consume the plane and many passengers had started to be incapacitated from the smoke.

However, there were some exceptions

  • South African Airways Flight 295: Boeing 747-200M Combi which suffered an in-flight fire on its rearmost cargobay on the passenger deck. Despite attempts to extinguish it by attendants with hand extinguishers, the plane crashed, with no conclusive reason.
  • UPS Flight 6: Boeing 747-400F which suffered an inflight-fire in its cargo hold caused by lithium batteries. Despite the pilots’ attempts, the plane crashed past the airport, with neither pilot surviving.

I feel that a fire in the avionics bay would have been more likely because a combusting iPhone wouldn’t have had the ability to take down an entire jetliner unless it was ignored for far too long.

The Workhorse (AMD-powered custom desktop)

CPU: AMD Ryzen 7 3700X | GPU: MSI X Trio GeForce RTX 2070S | RAM: XPG Spectrix D60G 32GB DDR4-3200 | Storage: 512GB XPG SX8200P + 2TB 7200RPM Seagate Barracuda Compute | OS: Microsoft Windows 10 Pro

 

The Portable Workstation (Apple MacBook Pro 16" 2021)

SoC: Apple M1 Max (8+2 core CPU w/ 32-core GPU) | RAM: 32GB unified LPDDR5 | Storage: 1TB PCIe Gen4 SSD | OS: macOS Monterey

 

The Communicator (Apple iPhone 13 Pro)

SoC: Apple A15 Bionic | RAM: 6GB LPDDR4X | Storage: 128GB internal w/ NVMe controller | Display: 6.1" 2532x1170 "Super Retina XDR" OLED with VRR at up to 120Hz | OS: iOS 15.1

Link to comment
Share on other sites

Link to post
Share on other sites

This case sounds suspicious for 2 reasons, as it is hinging on the cause of the crash being the iPhone. There are only two reasons that would be somewhat valid (if at all):

  • Radio/communications interference, caused by the device in question operating in a matter that violates FCC policy requirements
  • An immediate danger/dangerous situation caused by the device in question being (either) used improperly or with defect.

In the case of the first option, that is extremely unlikely - the testing that iPhones undergo should already cover testing for radio/signal interference. Thus, the only way this option could hold water is if the device was modified post-purchase (which is then on the user).

 

Now for the second option. If it was caused by a battery defect, the device would begin to expand/distort its regular shape first - which would be a very obvious warning sign (in addition to releasing nasty smells due to the chemical reaction in play). If you don't notice that, go see a doctor. Perhaps the device in question may have been used in a way that is outside of normal use cases, or modified (hardware only - not software) by the end-user? Even in that case, there still would have been warning. Most modern phones only explode because of one thing - the battery (can't say capacitors anymore - the ICs are too small to cause such). Once again, there would have been more than enough time to react before the event occurred. 

 

It is quite likely that something else transpired that occured, seeing that they did not radio in before being downed. Something would have to prevent:

  • The radio from operating in its normal capacity, or
  • the pilot/someone from being able to reach the radio

For this to occur. Thus, it is very unlikely that the iPhone caused the accident in question. It is most likely due to another factor that hasn't been mentioned yet...

Link to comment
Share on other sites

Link to post
Share on other sites

On 5/14/2018 at 10:50 AM, NMS said:

But in the end all those batteries are the same. It's the controller on them that distributes power is different. Hence why Samsung F'ed up so hard.

But in the case of samsung it was actually faulty batteries, they are not all the same

https://www.nytimes.com/2017/01/22/business/samsung-galaxy-note-7-battery-fires-report.html

https://www.recode.net/2017/1/22/14330404/samsung-note-7-problems-battery-investigation-explanation

Samsung_Note_7_infographic.jpg

Insanity is not the absence of sanity, but the willingness to ignore it for a purpose. Chaos is the result of this choice. I relish in both.

Link to comment
Share on other sites

Link to post
Share on other sites

3 hours ago, valdyrgramr said:

 

Even then that's not why the maker was being sued.  According to the case she was simply suing them over a known seatbelt defect with that exact model, and had that defect not been there Paul could have gotten out.  I'm not saying the whole seatbelt defect is true, but that's why she was suing.  Not because the driver crashed the car, and not because of the tires either.

I understand why she sued, I was just pointing out that the cause wasn't the speed. The cause was the tires, which was only a serious problem because of the speed, but the tires were still the reason the car lost control. 

 

And Porsche isn't to blame for the tires, so again I understand that wasn't the reason for that particular lawsuit. Tires don't age well as the rubber compound deteriorates significantly (I believe Porsche themselves advise replacing the tires within five years), and that's even more of an issue with high performance tires (which are stupidly dangerous to drive on in just in bad conditions even when new -- e.g. High performance tires of a small window of road worthiness).

PSU Tier List | CoC

Gaming Build | FreeNAS Server

Spoiler

i5-4690k || Seidon 240m || GTX780 ACX || MSI Z97s SLI Plus || 8GB 2400mhz || 250GB 840 Evo || 1TB WD Blue || H440 (Black/Blue) || Windows 10 Pro || Dell P2414H & BenQ XL2411Z || Ducky Shine Mini || Logitech G502 Proteus Core

Spoiler

FreeNAS 9.3 - Stable || Xeon E3 1230v2 || Supermicro X9SCM-F || 32GB Crucial ECC DDR3 || 3x4TB WD Red (JBOD) || SYBA SI-PEX40064 sata controller || Corsair CX500m || NZXT Source 210.

Link to comment
Share on other sites

Link to post
Share on other sites

7 hours ago, djdwosk97 said:

I understand why she sued, I was just pointing out that the cause wasn't the speed. The cause was the tires, which was only a serious problem because of the speed, but the tires were still the reason the car lost control. 

 

And Porsche isn't to blame for the tires, so again I understand that wasn't the reason for that particular lawsuit. Tires don't age well as the rubber compound deteriorates significantly (I believe Porsche themselves advise replacing the tires within five years), and that's even more of an issue with high performance tires (which are stupidly dangerous to drive on in just in bad conditions even when new -- e.g. High performance tires of a small window of road worthiness).

Not to mention that car was a Carrera GT, which is one of those cars that require immense skill to control even on the world's best tires. 

The Workhorse (AMD-powered custom desktop)

CPU: AMD Ryzen 7 3700X | GPU: MSI X Trio GeForce RTX 2070S | RAM: XPG Spectrix D60G 32GB DDR4-3200 | Storage: 512GB XPG SX8200P + 2TB 7200RPM Seagate Barracuda Compute | OS: Microsoft Windows 10 Pro

 

The Portable Workstation (Apple MacBook Pro 16" 2021)

SoC: Apple M1 Max (8+2 core CPU w/ 32-core GPU) | RAM: 32GB unified LPDDR5 | Storage: 1TB PCIe Gen4 SSD | OS: macOS Monterey

 

The Communicator (Apple iPhone 13 Pro)

SoC: Apple A15 Bionic | RAM: 6GB LPDDR4X | Storage: 128GB internal w/ NVMe controller | Display: 6.1" 2532x1170 "Super Retina XDR" OLED with VRR at up to 120Hz | OS: iOS 15.1

Link to comment
Share on other sites

Link to post
Share on other sites

19 hours ago, valdyrgramr said:

Weren't the ones that had issues only from one factory?

Actually no. From what I gathered, the first set had a defect in the corners of the batteries as shown, so they immediately started recalls and switched to a second provider and started pumping out replacements, but as it turns out, that company had a completely different defect as shown with welding burrs

It was 2 different companies with 2 different defects. People were quick to blame samsung for this, but as I see it, they had some really bad luck. 

Insanity is not the absence of sanity, but the willingness to ignore it for a purpose. Chaos is the result of this choice. I relish in both.

Link to comment
Share on other sites

Link to post
Share on other sites

11 minutes ago, Jtalk4456 said:

Actually no. From what I gathered, the first set had a defect in the corners of the batteries as shown, so they immediately started recalls and switched to a second provider and started pumping out replacements, but as it turns out, that company had a completely different defect as shown with welding burrs

It was 2 different companies with 2 different defects. People were quick to blame samsung for this, but as I see it, they had some really bad luck. 

Well, in fairness, one of the two companies that produced the batteries was technically Samsung.

PSU Tier List | CoC

Gaming Build | FreeNAS Server

Spoiler

i5-4690k || Seidon 240m || GTX780 ACX || MSI Z97s SLI Plus || 8GB 2400mhz || 250GB 840 Evo || 1TB WD Blue || H440 (Black/Blue) || Windows 10 Pro || Dell P2414H & BenQ XL2411Z || Ducky Shine Mini || Logitech G502 Proteus Core

Spoiler

FreeNAS 9.3 - Stable || Xeon E3 1230v2 || Supermicro X9SCM-F || 32GB Crucial ECC DDR3 || 3x4TB WD Red (JBOD) || SYBA SI-PEX40064 sata controller || Corsair CX500m || NZXT Source 210.

Link to comment
Share on other sites

Link to post
Share on other sites

@djdwosk97 Fair enough, though that is one mistake, and their response was quick, so i'm still not going to BLAME them, mistakes happen and they learned from it. That's part of the reason i now use an S8. The way I see it, if samsung has another recall fiasco, they might not make it. Consequently their butt was really on the line with the S8, so I trusted they would do a good job on it. And besides the newest gorilla glass being crap (not samsung's fault) I have not been disappointed

Insanity is not the absence of sanity, but the willingness to ignore it for a purpose. Chaos is the result of this choice. I relish in both.

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×