It looks like you're using an Ad Blocker.

Please white-list or disable AboveTopSecret.com in your ad-blocking tool.

Thank you.

 

Some features of ATS will be disabled while you continue to use an ad-blocker.

 

Help ATS via PayPal:
learn more

US aviation authority: Boeing 787 bug could cause 'loss of control'

page: 1
2

log in

join
share:

posted on May, 1 2015 @ 09:47 PM
link   
Link


“We are issuing this AD [airworthiness directive] to prevent loss of all AC electrical power, which could result in loss of control of the aeroplane,” said the Federal Aviation Administration directive. “If the four main generator control units (associated with the engine-mounted generators) were powered up at the same time, after 248 days of continuous power, all four GCUs will go into failsafe mode at the same time, resulting in a loss of all AC electrical power regardless of flight phase.”


I honestly think this is a non-issue but because its 787 related it makes the news. The fault was found in Lab tests and has not affected the airframe in the field. I cant imagine a plane being left on for 248 days without some kind of power down.

AD link for those intrested
AD




posted on May, 1 2015 @ 10:02 PM
link   
It wouldn't cause a loss of control, even on takeoff or landing. By the time there was a chance of that happening, the RAT would have deployed, and they'd have emergency power to the flight controls. Never miss a chance for fear mongering though.

No commercial aircraft is ever going to me powered up 24/7 for 8 months. But since it happened in the lab, this gets notice out to be sure.
edit on 5/1/2015 by Zaphod58 because: (no reason given)



posted on May, 2 2015 @ 05:32 AM
link   
a reply to: Zaphod58

I found a similar bug in Cadence once. It required me to have some unlikely magic combination of factors, sort of like this one. Instead of 8 short of 256 like this, I had to hit a particular even binary boundary of nets and nodes. They thought it couldn't happen.

They don't know me very well. It was something creepy like 8192 nets and 32,768 vertices at the same time (not the actual #). I, of course, did it by accident.



posted on May, 2 2015 @ 07:55 AM
link   
The ultimate question. Is this the only way for the problem to surface? Many times bugs have multiple ways to to be found. After you find the first one it pays to keep searching for other ways for the issue to occur. That's the scary part about troubleshooting problems. The more you find the more you have to look and other things come to light.



posted on May, 2 2015 @ 08:16 AM
link   
a reply to: datasdream

They've been checking systems for several years and this is currently the only way that they have seen it occur to date. There may be others, but none have cropped up yet.




top topics
 
2

log in

join