PPRuNe Forums

PPRuNe Forums (https://www.pprune.org/)
-   The Pacific: General Aviation & Questions (https://www.pprune.org/pacific-general-aviation-questions-91/)
-   -   Computers in Aircraft (https://www.pprune.org/pacific-general-aviation-questions/343753-computers-aircraft.html)

layman 15th Oct 2008 08:22

safety-critical systems
 
Just to expand on Mark1234 and others ...

I'm not sure of the computer / software fit in aircraft but I imagine it may somewhat similar to military requirements for safety-critical systems i.e. they aim to use processor chips with known capabilities / problems; and software with known capabilities / problems. This was one of the reasons Intel 386 chips (first delivered in 1986) were still being used extensively in the aerospace industry until the end of 2007 (Intel 80386 - Wikipedia, the free encyclopedia). Probably moved on to 486's by now !!

A chip might have 100 or more commands in it's instruction set, but only a “proven” (and well tested) sub-set are used in safety-critical systems. This substantially reduces the chance of errors being induced by the chip. There are still the “human” induced errors from software design and programming that need to be addressed.

With the (I'm guessing here) many thousands of permutations of control surface positions, combined with varying altitudes, speeds, headings, winds-aloft, navigation instrument inputs etc, etc , etc, it would be very difficult (and costly) to design and test a system that could handle every single permutation. So some serious risk versus cost calculations will be applied to hopefully cover the more important combinations.

And defining “more important” will always be an interesting discussion …

“Affordable safety” is a term that comes to mind here – if it is considered the travelling public might not be prepared to pay the (probably) high cost of being perfectly safe.

layman
(edited to correct human error)

flyhigh744 15th Oct 2008 09:09

Very enjoyable post indeed :ok:

ernie blackhander 15th Oct 2008 11:06

When it was time to prepare the Aircraft for departure, we fired up the APU and dozens and dozens of fault messages came up, most of which we had never even seen before. http://static.pprune.org/images/smilies/eek.gif

We completely depowered the Aircraft, waited a few minutes, then powered it all up again (as you would do with a computer) and NO problems.


Seems to happen more than once a fortnight some times. Last one took about 3 hours to get booted back up

Sunfish 15th Oct 2008 20:35

Guess what happened the first time an F18 tried to fire a Sidewinder at Woomera many, many years ago?

Yep, no one had ever tried that in the Southern Hemisphere had they?

- division by zero.

Same thing happened when the first Raptor Squadron were flying to Japan and crossed the International dateline.

Dogimed 15th Oct 2008 20:44

Ok, ...

Remove the ability to fail from the silicon brain, remove the posibility of human error into this.

Are we all still comfortable with a computer making the decisions for the safety of the aircraft?

Another example:

Airbus goes quiet, needs to go down and ditch, say you want to stall it in the flare to reduce foward movement. You pull back on the stick and the "computer says no" and pushed nose down to avoid the stall and spears nose first into the water. (computer logically was thinking it wanted to avoid the aircraft in an unsafe attitude at low altitude)

I fear computers and software are programmed to protect themselves and the aircraft first, without the benefit of true spatial awareness.

Dog

404 Titan 15th Oct 2008 21:12

Dogimed


Airbus goes quiet, needs to go down and ditch, say you want to stall it in the flare to reduce foward movement. You pull back on the stick and the "computer says no" and pushed nose down to avoid the stall and spears nose first into the water. (computer logically was thinking it wanted to avoid the aircraft in an unsafe attitude at low altitude)
You obviously have no idea of the Airbus flight control laws because this is not how they will work under the low speed protection laws.

4Greens 15th Oct 2008 22:01

My favourite:

ATSB spokesman (paraphrasing slightly) 'Its never happened before so it is unlikely to happen again!'

Dogimed 15th Oct 2008 23:47

404 Titan

Dammit you got me...

I have absolutely no idea how it works.(Edit: but after reading further )
A low speed stability function replaces the normal angle-of-attack protection
System introduces a progressive nose down command which attempts to prevent the speed from decaying further.
This command CAN be overridden by sidestick input.
The airplane CAN be stalled in Alternate Law.
An audio stall warning consisting of "crickets" and a "STALL" aural message is activated.
The Alpha Floor function is inoperative.

(but does the pilot or computer made the choice to go to Alternate Law?)



Actually, its not the point. (neither is Airbus the main issue either)

Dog

Mark1234 16th Oct 2008 00:20


Remove the ability to fail from the silicon brain, remove the posibility of human error into this.
Are we all still comfortable with a computer making the decisions for the safety of the aircraft?
Under those circumstances: Absolutely! With the caveat that it depends on how it's designed - any computer system is only as good as the design. The awareness of the system can be enhanced with sensors (airbus system includes Rad alt for instance). The design can be carefully thought through, codify the best of human practice, and doesn't get stressed by all hell breaking loose around it. Fantastic!

Biggest thing I've flown is a warrior, but according to the net, and *all in normal law* the airbus:
operates normally up to some value of AOA where it triggers alpha protection - from there the sidestick commands AOA directly, bank is limited, and spoilers are retracted (cancelled once the AOA reduces). At some higher AOA (alpha floor), the autothrottles go to TO/GA power.

Additionally, the system is linked to the rad alt, which causes it to enter flare mode below a given (100ft?) rad alt; That inhibits alpha floor. It's also in flare mode that the progressive nose down is introduced "to force the pilot to flare" (not sure I get that)

At no point does it pitch the nose down at the floor..

Allegedly the toulouse crash was caused by the show pilot attempting to demo alpha floor, but being so low it went into flare mode and inhibited. By the time they intervened the energy was too low and in it went.

Now consider all those boeings and other non fly-by-wire aircraft that are fitted with a stick pusher.. which is a very dumb, non-computerised device that boots the stick forward ahead of the stall......

Lookleft 16th Oct 2008 01:02

The A320 that went into the trees did not crash at Toulouse. The pilot was not demonstrating Alpha Floor but thought that it would look after him during the flypast, not realising that it was not active below 100' rad alt. If he had selected TO/GA at any point up to the impact he would have climbed away.

The reason stick pushers are installed is that the stall indications of a jet are not as obvious or benign as your Warrior. There is such a thing as a deep stall which T tails are more prone to and thats why the stick pusher is there. Far from being dumb, its a requirement to get the thing certified.

Mark1234 16th Oct 2008 01:32

Lookleft, you misunderstand me; I mean dumb as in 'not situationally aware', not as in that it is dumb they are fitted(!)

I'm also aware of swept wing stall characteristics - like tip stalling and adverse (up) pitch at the stall.. (I'm working on my ATPL theory) - I fully understand *why* you would require a stick pusher, was merely attempting to illustrate to Dogimed that his objection to FBW 'airframe' protection isn't entirely logical :)

I'll take the correction on 'airbus in trees'.. I did say allegedly!

Lookleft 16th Oct 2008 03:20

No worries, hope all goes well with the ATPL!

sprocket check 1st Nov 2008 10:26

I found this the other day:

What is chiefly needed is skill rather than machinery.

— Wilbur Wright, 1902.

And:

Man is not as good as a black box for certain specific things. however he is more flexible and reliable. He is easily maintained and can be manufactured by relatively unskilled labour.

— Wing Commander H. P. Ruffell Smith, RAF, 1949

Dogimed 1st Nov 2008 11:01

What a wonderfully simple and accurate approach to aviating.


What is chiefly needed is skill rather than machinery.

— Wilbur Wright, 1902.

ZEEBEE 2nd Nov 2008 13:17

Dogimed


What a wonderfully simple and accurate approach to aviating.
Unfortunately, it falls into the category of the quote,

"For every complex problem, there is often a simple solution and unfortunately it's almost always wrong'

No, like it or not, computers WILL rule our lives (some say they largely do already)

Pilotette 2nd Nov 2008 20:20

You've probably all seen this one before? YouTube - Air France Crash

:ugh:

404 Titan 2nd Nov 2008 20:58

Pilotette

Yes I have and it is a case of the pilot not understanding the aircraft he was flying. The aircraft performed exactly as it was designed. The pilot f*cked up.

And the video quote is misleading too. The A320 isn’t fully automated and at the time of this accident the pilot was hand flying the aircraft, not the auto pilot.

Dogimed 2nd Nov 2008 22:29


The aircraft p:cool:erformed exactly as it was designed.
404,

I doubt the aircraft was designed to fly into trees.

My point is that the computer that we trust with our lives cannot equal the ability of man (or woman) to adjust to the situation if required.

A computer cannot be programmed to understand the pilot hit the wrong button. The same laws designed to protect in this case caused fatalities.

404 Titan 2nd Nov 2008 23:43

Dogimed

No aircraft is designed to crash. The point here is that the aircraft crashed because the pilot didn’t understand how it worked. It’s just a shame that the investigation was clouded by misinformation and alleged corruption regarding the flight data recorder and cockpit voice recorder. The reality is that he was below 100 ft AGL and below the tree line, at a very low speed with idle power and at a very high AoA. If he was relying on α Floor to kick in at α Prot then he didn’t understand the system.

ZEEBEE 3rd Nov 2008 01:22


Dogimed

No aircraft is designed to crash. The point here is that the aircraft crashed because the pilot didn’t understand how it worked. It’s just a shame that the investigation was clouded by misinformation and alleged corruption regarding the flight data recorder and cockpit voice recorder. The reality is that he was below 100 ft AGL and below the tree line, at a very low speed with idle power and at a very high AoA. If he was relying on α Floor to kick in at α Prot then he didn’t understand the system.
Worse than that, the Captain had never been there before and the whole flyby was completely unplanned and adhoc. No safety brief prior to the pass.
The aircraft was "allowed" to descend below the safe height by innatention and poor oversight of the conditions and locality.
If a C150 got into those conditions it too would probably have come unstuck let alone a hundred and sixty tonne airliner with turbines that need spooling up.
Actually, it's a tribute to the aircraft that the casualty list was so low....but then most of the pax were journos and probably expendable:E


All times are GMT. The time now is 14:01.


Copyright © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.