Posted on 04/29/2015 1:42:41 AM PDT by Mad Dawgg
Several American Airlines flights were delayed Tuesday night after a software glitch occurred in the Apple iPads provided to pilots, forcing authorities to return planes to the gates to fix the malfunction, the Verge reported. The affected flights reportedly included AA2413, AA2276, AA1654, AA235 and AA128.
Passengers were reportedly asked to exit the aircraft. American Airlines first confirmed the issue to a passenger, named Bill Jacaruso, who was traveling to Austin from Dallas/Fort Worth airport on flight AA1654.
“Some flights are experiencing an issue with a software application on pilot iPads,” Andrea Huguely, a spokeswoman for the American Airlines, told the Verge. “In some cases, the flight has had to return to the gate to access a Wi-Fi connection to fix the issue. We apologize for the inconvenience to our customers. We are working to have them on the way to their destination as soon as possible.”
Another representative for the airline said that the issue, which had affected "a few dozen flights," had been identified and that a fix was being worked on.
(Excerpt) Read more at ibtimes.com ...
The FAA approved the use of the iPads to replace the 35 pound flight bags -- 'way back in 2012.
Eliminating 75 lbs on every flight has saved beaucoup fuel since then.
So, American Airlines supplied bad data to their crews this one time. It was caught and corrected.
None of the above has ANYTHING to do with Apple, which you. evidently, love to trash...
I see. Except the App runs on an Apple which is built to have Apps update when the App manufacturer decides to do one without any approval or oversight from the FAA. So yeah Apple's design and App system grounded several dozen flights because of a glitch. Sorry but thems the facts AND it would be no different if it was anyone else's system besides Apple like a Surface for instance.
Its a Consumer good that has been approved for the role of flight manual in a Government controlled system OK yeah good show and all that BUT the APP can be updated AND/or the unit itself can be updated without FAA approval and as such the system can get FUBARed and ground planes because of FAA rules.
If it can happen once it can happen twice. And don't give me this "it isn't Apple" crap they have had system wide FUBARs before the most memorable was Apple Maps which was so bad they fired the guy in charge.
Now as I stated very far upthread the answer is very simple either new rules that stop the updates of apps and the OS on the Units used in plans until the FAA approves them or carry a backup of some sort so that planes don't get grounded from a single point of failure.
Anyone with an IQ in the double digits can see that as the system stands now many more planes can be grounded and disrupt flights en masse with how it is now.
Bottom line iPads glitched and planes were grounded and unless those planes were all empty then literally thousands of passengers were affected. The system needs changed to stop it from happening again.
After the entire American Airlines 737 fleet (according to the news sources) was affected by the glitch. A.K.A a single point of failure.
"None of the above has ANYTHING to do with Apple, which you. evidently, love to trash..."
Who designed the App system that allows updates to be performed that can glitch and shut down an entire fleet of planes? Yeah that was Apple.
BTW the same thing can happen with any other tablet approved for use as an E-flight manual. So the system needs changed so it won't happen again AND if you had read upthread I pointed out the solution but apparently its more important to try and cast blame on everyone BUT Apple. Which is always good for laugh.
It’s the same company that makes the same kind of software for laptops and other devices ... to take on planes.
When you have a laptop and the software company screws up the software, you don’t blame the laptop ... LOL ...
WELL ... maybe you do, but normal and intelligent people don’t ... :-) ...
They include everything that's in a normal flight kit.
You guys love to repeat lies. Have at it. . . but you've both been told the truth repeatedly. That makes you both liars.
And as I have pointed out that is how the Apple unit is designed. A single update can render the units inoperable or glitchy so as the system or the app will not work properly and apparently under the FAA rules if such happens the planes can't fly.
So the rules need changed or the system needs changed. At least some form of backup needs introduced so that a single point of failure can be dealt with.
Misrepresentation of what you were told is a lie. Try telling the truth instead of lying. None of what you posted is at all close to what was explained to you. Try telling the truth for a change instead of distorting what was said. Lies and propaganda makes you look like an idiot. . . or are you an idiot?
Take a look at Post #128. It’s explained there that it had nothing to do with the iPad or the iOS or the update. They identified it as a database problem in the software supplied by the company who does this for American Airlines.
All they did was issue some files to replace the one part of the database that was causing the problem, and installed the files outside of that App, and the problem was solved and they were on their way.
The software company will obviously fix their database so that it will not be a problem anymore, but that might take a few days to a week or so before it’s finished and tested.
In the meantime, it’s no problem to American Airlines and it wasn’t an iPad problem.
Ahh you are now trying to tell us that Apple software is to blame so not to blame Apple.
An iPad is only approved to run Apple OS and as such to make APPs for Apple products they must be approved by Apple to run on and be compatible with Apple OS AND the update system is APPLE's design. Which allows updates on the Apps that can glitch and that glitch can ground planes.
Apple's system, Apple's software, Apple's fault.
See Post #128 ... it wasn’t an iPad problem or an iOS update problem. And the problem did not affect all the flights, but very few of them, because it was only one file that caused the problem inside the app and very few of their fleet used that file.
And all they did was issue some files outside of that app to use separately, and avoid the one file inside the app. It was a simple work-around and they were on their way again ... :-) ...
You don’t seem very tech-literate if you can’t understand the problem as explained in Post #128 ... and it certainly isn’t my job to tutor you ... LOL ...
Ahh yeah it was and still is an iPad problem. An update can shut down the unit if it glitches and if the unit isn't working properly then by FAA rules the planes can't fly.
Or are you claiming that iPad's are glitch proof?
Uh, Apple does not do live updates on iPads, iPhones, or iPods. The user selects when to update iOS on those devices. Try to be accurate when BASHING Apple.
The fact is that it was not iOS, or Apple that screwed up. It was the APP provider that included two conflicting maps for JFK, when the APP could not resolve the conflict, it crashed. The problem was resolved by returning to the terminal downloading a new version of the data which solved the problem.
You Anti-Apple asshats have been joyfully bashing Apple when, as I pointed out, thousands of flights have flown since the update to iOS 8.3 without a single problem with the iPad's hardware or operating system. I suggested it had to be something external to those. I was correct.
Well done Sparky I knew you could hit ad hominem in under three replys
Quick question. Can an Apple iOS update glitch an iPad so that APPs won't work properly or the unit itself won't work properly?
I said I can’t tutor you since you are obviously tech-challenged here ... LOL ...
The iPad didn’t have a problem, an app had a problem. The iPad didn’t crash, the app crashed. The iOS on the iPad didn’t have a problem, the database inside the app had a problem.
American Airlines did a real simple workaround, they supplied the relevant files outside of the app, so that the app was not used for this file. It only affected a very few planes in the fleet, as only a few were headed to Reagan National (the problem file).
Now, since you are unable to understand what this means, I would advise you get some tech-savvy friend to help you out ... :-) ...
One of the specifications of the Interstate Highway system was that one mile out of each five was to be straight and free of overpasses, capable of landing jet aircraft. That should take care of that little problem. ;^)
The Data Base is modified daily. . . including weather data and whether runways are being modified or in use. That does not require FAA certification for each change, you idiot. The changes are normal business practice. The SAME DATA BASES load on to the Windows Surface computer used on a couple of other airlines and would have the same results. The Jeppson Software cannot handle two conflicting charts for the the same air port. It cannot resolve the conflict. It is NOT the fault of the computer handling the software. It was the DATA that was compromised and not the product of the operating system that you have been spending all your time bashing. THOSE ARE THE FACTS, not the ones you make up out of your delusional world.
You go on and on in this comment digging your hole deeper and deeper about something you know absolutely nothing about. . . because of a data glitch. . . that was easily correct. Would you have preferred these flights get to their destination Airport in Orange County and find they had BAD DATA??? I certainly would not.
There was nothing about an update to an APP or the OS that had anything to do with this. YOU are pulling problems out of your nether regions that do not exist, so that YOU can further bash Apple. That is deluded.
I have read the story. . . and it was only aircraft that were head toward Ronald Reagan International Airport in Orange County California that attempted to load those charts for that airport that crashed the FlightDeck App for American Airlines. The only affect it had on all of their 737 fleet was that every single plane in their fleet had that database in them, not that their FlightDeck apps crashed. . . but that it could have, had they attempted to load that doubled chart. Since the vast majority of American Airlines fleet does not land at Ronald Reagan international Airport, they were not affected by the glitch. You don't know what you are talking about.
The rest of the fleet merely had to download an updated version of the database which Jeppson had to correct which did not include the doubled chart for RRIA. Problem solved.
None of that was an update problem with the Apple iPad, the iOS 8.3 update, or even the FlightDeck software. It had to do with some worker somewhere who assembles the database putting in two version of the chart for RRIA. . . perhaps one with a minor change and one without.
You are building a mountain out of a molehill. . . and really, really wanting to blame Apple for it.
I used it because it was used on me. . . and you fellows really deserved it with the degree of nonsense you all were spewing all over the place. Nobody was using the brains God gave you in your rush to blame Apple for the glitch. Not one of you bothered to THINK. You emoted like asshat Liberals. . . so you deserved to be called on it.
I pointed out the flaws in all of your claims. . . the errors in your thinking. IF you had stopped and bothered to think for just a few moments before you rushed to bash, you might have wondered how it would effect just a few flights. . . and not every other plane in the sky that flies with the same software and the iPad. I did. I realized that it could not be a generalized hardware/software issue. It had to be something else. . . localized, to be affecting on a few flights. This is the kind of analysis and diagnoses I do for a living and the headline conclusion simply stunk.
Quick question. Can an Apple iOS update glitch an iPad so that APPs won't work properly or the unit itself won't work properly?
Could an Apple iOS update glitch an iPad (would that be a single iPad or all iPads?) so that APPS won't work properly? Frankly, it could, but it has not yet. iOS 8.3 came out in OCTOBER 2014. . . and airlines have been flying with FlightDeck on iOS 8.3 for some time. That is a time tested number of flights without a glitch. Jeppeson tested their software under iOS 8.3 Beta for some time prior to the release date because it is mission critical. I considered all this in making my opinion and call that it had to be external to the iPad and software.
In other words, Mad Dawgg, I used my BRAIN and THOUGHT it through. None of you characters bothered to do that except Star Traveler and a few other non-Apple bashers, the ones who provided answers. . . not bashing.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.