Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×

Airbus Plans to Expand Cockpit Automation 355

Carl Bialik from WSJ writes "Airbus plans computerized systems that could automatically maneuver jetliners to avoid midair collisions, without pilot input, the Wall Street Journal reports. From the article: 'For the first time, flight crews of Airbus planes will be instructed and trained to rely on autopilots in most cases to escape an impending crash with another airborne aircraft. Currently, all commercial pilots are required to instantly disconnect the autopilot when they get an alert of such an emergency, and manually put their plane into a climb or descent to avoid the other aircraft. The change, which hasn't been announced yet, comes after lengthy internal Airbus debates and despite skepticism from pilot groups and even some aircraft-equipment suppliers.'"
This discussion has been archived. No new comments can be posted.

Airbus Plans to Expand Cockpit Automation

Comments Filter:
  • by abigsmurf ( 919188 ) on Tuesday May 30, 2006 @12:45PM (#15429030)
    wasn't there a plane crash a few years back caused by both planes trying to avoid a mid air collision actually moving into each other? A system which ensures the planes do actually move apart seems a good idea
  • Poor pilots (Score:3, Insightful)

    by Rorian ( 88503 ) <`moc.liamg' `ta' `hsyf.semaj'> on Tuesday May 30, 2006 @12:47PM (#15429041) Homepage Journal
    Soon they'll have nothing left to do at all..

    I was always under the impression that pilots were trained pretty much entirely for these once-in-a-lifetime events, such as mid-air collision and having one jet fail. I guess they are only going to be useful for take-off and landing now?

    Maybe they're trying to phase out pilots all together? Sure would put an end to the whole pension-deficit issue that airlines are facing (well, once all the current pilots die of old age).
  • by happyrabit ( 942015 ) on Tuesday May 30, 2006 @12:52PM (#15429090)
    We will have too trust our lives more and more too machines, we already do it in hospitals...
    Machines and electronics are less subject to stress... pilots will have to share their responsabilities with electronics, it's inevitable.

    Still, we should first have a good quality check procedures on those programmers and engineers work, as a programmer myself I wouldn't trust my own code to keep me alive :)
  • by sheepoo ( 814409 ) on Tuesday May 30, 2006 @12:55PM (#15429123)
    there exists such a thing as 'Software Bugs'
  • by Conspiracy_Of_Doves ( 236787 ) on Tuesday May 30, 2006 @12:56PM (#15429130)
    "For the first time, flight crews of Airbus planes will be instructed and trained to rely on autopilots in most cases to escape an impending crash with another airborne aircraft or a building."

  • by vijayiyer ( 728590 ) on Tuesday May 30, 2006 @01:11PM (#15429250)
    Airbus's design philosophy is that the airplane knows best, and Boeing's is that the pilot knows best. I tend to agree with Boeing. For example, AFAIK, one cannot cross control a modern Airbus - the airplane automatically maintains coordinated flight under all conditions. Normally, this is a good thing. However, in the case of Air Canada flight 143, where a Boeing 767 was improperly fueled, the pilots intentionally slipped the aircraft to avoid disaster (http://www.wadenelson.com/gimli.html). In the case of American Airlines flight 587, where the tail of the Airbus broke off, the cause of crash was determined to be the pilot's rapid full extent rudder inputs. However, when one looks into _why_ the pilot put in those rudder inputs, you find out that Airbus uses a very high detent load (high load before initial travel) combined with very low load progression as the pedal is depressed - kind of like a keyboard key. Try to press a key on your keyboard 1/4 way - it's not easy. Bottom line - Airbus has some decent technology, but their aircraft are not always pilot friendly. To ignore what the end user - the pilots - have to say about design is just plain foolish.
  • by uniqueUser ( 879166 ) on Tuesday May 30, 2006 @01:12PM (#15429260)
    wasn't there a plane crash a few years back caused by...
    As we start to automate transportation (all forms) with computers, we will always remember when the computer got it wrong. Even if the computer is better most of the time. If a man makes one mistake out of a hundred, and a computer makes one mistake out of a million, the media will will always highlight the computers faults. We will always hear "...had a person been driving..."
  • by gaspyy ( 514539 ) on Tuesday May 30, 2006 @01:20PM (#15429325)
    I don't know whether or not we're thinking about the same crash, but the one I know of, it was traffic controller's fault.

    Two planes (one loaded with children going on vacation, going from aformer Soviet republic) were on a collion course somewhere near Switzerland. The traffic controller saw the problem very late; the autopilots on the planes reacted correctly, pointing one plane up and one down. However, the controller instructed the plane going up to go down instead. The pilot asked "are you sure?" and the controller repeated the instructions.

    More details on BBC [bbc.co.uk] (I may have got some facts wrong, I didn't re-read it now)
  • by kimvette ( 919543 ) on Tuesday May 30, 2006 @01:29PM (#15429410) Homepage Journal
    <Phillip J. Fry>I'm getting an idea. No, false alarm. No. Yes! No. Yep. Nope, waaiiit, no. Yes. Yes. No. YES!!!!</Phillip J. Fry>

    How about implementing international standards for collision avoidance similar to what exists in the marine world, e.g., if one aircraft is overtaking another, the one overtaking vectors starboard (that's right), the one being overtaken vectors port (that's left). If approaching head-on, both vector starboard, if approaching at right/oblique angles, the one to starboard descends (if altitude and terrain allows) and the one to port ascends. Seems simple to me.

    Of course, the ideal solution is to stick to your flight plan when flying IFR, keeping your eyes open when flying VFR and when flying VFR stay within VFR conditions, keeping your eyes open all the while, and fly conservatively. But no, that would be too sensible and would not earn lawyers (no legislation required) and avionics manufacturers enough money (no having to retrofit needless systems into aircraft and recertify them).
  • by Anonymous Coward on Tuesday May 30, 2006 @01:30PM (#15429418)
    The system to avoid mid-air collisions is already mostly automatic.
    It's called Traffic Collision Avoidance System (TCAS). It intercepts
    other aircrafts' transponder position signals, and, in case of
    intersecting traffic, actually communicates with the other aircraft's
    TCAS system, and they both agree on which of them will ascend or
    descend. This decision is then communicated to the pilots via audio.
    Therefore, if both aircraft have TCAS installed, they are guaranteed
    to receive opposite instruction (i.e., one to ascend, one to descend).

    In the mid-air collision over Germany a few years back, both aircraft
    had TCAS, and they both worked perfectly, and their instruction would
    have avoided the crash. However, at the same time that the TCAS alarm
    sounded, the traffic controller advised the one aircraft to sink,
    in disagreement of the TCAS instruction. Unfortunately, the pilot
    decided to ignore the TCAS, and followed the traffic controller's
    instruction, driving right into the path of the other aircraft,
    which was following TCAS advice to sink.

    Since then, pilots have been trained to always follow TCAS
    instruction. When pilots must follow TCAS instruction, it is
    logical to automate that decision. With the appropriate controls
    to override the autopilot, of course.
  • by badasscat ( 563442 ) <basscadet75@@@yahoo...com> on Tuesday May 30, 2006 @01:30PM (#15429423)
    Had both listened to the air control tower or the onboard warning systems everything would have worked.

    And this new system will not solve that problem, because it would require all aircraft to be equipped with it to work, not just Airbus.

    If the new system commands the airplane to dive, and the other pilot follows instructions from controllers on his manually-controlled plane to also dive, then you're still looking at an accident. This solves nothing, really.

    Relying on ATC in this situation is, in any case, about the worst thing you can do - and it's the reason why standard procedure in the west is not to. Only the pilots of the airplanes, by virtue of their accident avoidance systems, have the situational awareness required to take appropriate action in time to avoid an accident. And these accident avoidance systems will never give conflicting instructions - if the system in one plane says to pull up, the system in the other will say dive.

    Anyway, there are good reasons why airline pilots dislike having control taken away from them, especially in critical situations - because software in airliners, just like software in home computers, is prone to bugs. If you could see the software service advisories for the 747-400 flight management computer alone over the life of that airplane, you would probably never want to fly one again. Some of the lesser bugs have still never been patched; the manual simply contains workarounds for them. (These manuals are available to the public, despite the government's security concerns - you can buy one online, legally, if you'd like to see for yourself.) Obviously, anything safety-related would be patched as soon as it was found, but what if the first time a bug is discovered is after it causes an accident?

    No thanks. Flight management systems have evolved to the point where I feel comfortable enough flying in airplanes that I know are on auto-pilot in nominal flying conditions (as most are from shortly after takeoff to shortly before landing, or even right through landing), but in critical situations, I want somebody with both learned skill and judgement flying that plane. The key word being "somebody".
  • Good point... (Score:5, Insightful)

    by Graboid ( 975267 ) on Tuesday May 30, 2006 @01:44PM (#15429518)
    I had a good friend who once read a story about a guy who was thrown from a car accident and walked away because he wasn't wearing a seatbelt. He used that example for many years as justification for NEVER wearing a seatbelt (and, ironically, he suffered a concusion from a 15 mph fender bender).

    So, humans have an incredible capacity for ignoring the facts that don't support what they want to believe. In this case, even if the computer makes the RIGHT decision and a collision is avoided, passengers will get pissed for minor injuries in a severe turn, the computer will be blamed and a massive investigations will be launched.

    And, in some cases, very senior, experienced individuals will make better decisions, but these aren't the guys that will flying the planes most of the time. They're the guys that need to train the computer systems (like chess - you need really great chess players to 'teach' the computers and, at some point, the computer will outplay the master).
  • by Greased Monkey ( 920411 ) on Tuesday May 30, 2006 @01:49PM (#15429566) Homepage
    I work on the Avionics package of the F-16. These (among many other aircraft) are fly-by-wire meaning that all pilot inputs (stick, rudder pedals) are passed through a computer and electrically sent to the control surfaces. These aircraft fly in conditions that are *somewhat* more hazardous and complex than your average Airbus, and largely the pilot does what the little screens tell him to. A common AF joke is to refer to a pilot as a "stick actuator", as that is largely what he is. It is a relatively small step (relatively speaking) to automate this last bit of flight. Or, for that matter, the Predator is a remote-controlled plane that carries Hellfire missles- surely if that can work, this can work.
  • Re:Poor pilots (Score:5, Insightful)

    by Daniel Dvorkin ( 106857 ) * on Tuesday May 30, 2006 @01:58PM (#15429634) Homepage Journal
    A computer cares about what it's programmed to do, and that's all it cares about. A computer doesn't care about how tired it is, or the problems it's having with its marriage, or how it doesn't think it gets paid enough. A computer cares about one thing: executing code. And if that code tells it to fly the plane without crashing, then it cares about flying the plane without crashing more than any human possibly can.

    In other words, "caring" is great, but it doesn't fly planes. If you or I found myself at the controls of an airliner, we'd care a great deal about not crashing it, but odds are we'd still end up making a big smoking hole in the ground. The idea that a flight computer (or an android, for that matter) will do a worse job than a human because it "doesn't care as much" is ridiculous.
  • by FirienFirien ( 857374 ) on Tuesday May 30, 2006 @02:19PM (#15429891) Homepage
    In your earlier post, the one you just referenced as higher in the thread, you titled your post "Old school". Quoting that article fit there, because it was posted in 1989.

    While there are craft still in operation that were built pre-1989 (well, I assume so - those things were and still are expensive, and so built to last), seventeen years have passed since. Your 'major revisions' have come and gone and been replaced with new problems.

    I can understand tracking down a newsgroup(?) post made 17 years ago to point out that history repeats itself and problems will mutate and resurface. But implying that the aircraft manufacturer does nothing against problems over that timescale? That's laughable. They'll have had scores of people working on the problem as soon as it came up, because any disaster like that makes stunning headlines and puts big dents in those companies' prides. Far more recently, Concorde had problems and was pulled rapidly; the entire line no longer exists. Granted, there were more and varied other factors added in - but your post here is utterly misleading. Air crashes happen, and make big news. Car crashes happen daily, often, expensive by wasting entire tailbacks worth of peoples' time; boat crashes are thankfully lower-speed and better balanced and tend to cause fewer problems unless something vast has too much momentum. The air transport industry sees the greatest safety margin requirements by far among transport types.
  • by nsayer ( 86181 ) <`moc.ufk' `ta' `reyasn'> on Tuesday May 30, 2006 @02:24PM (#15429954) Homepage
    b. On 26 June 1988, a brand-new Air France A 320 that was participating in an air show crashed in a wooded area in the Alsatian town of Habsheim near Mulhouse while performing an extremely low altitude fly by.

    To be fair, a number of overrides, including the disabling of the GPWS, were done to the computers on this plane in order to make the fly-by possible. It was a combination of those overrides that resulted in the engines being nearly powered down when they were needed to power the plane back up into the sky... with the result we know.

    In actual service, an A320 in such a situation would have already at least sounded a number of alarms and probably would not have allowed the airspeed to drop so low without the flaps and gear to be in landing configuration.

  • by shawn(at)fsu ( 447153 ) on Tuesday May 30, 2006 @03:21PM (#15430482) Homepage
    As far as B goes. How is this the fault of the onboard computer? It seems as though the pilot should not have waited so long to increase the thrust. It seems to me that the pilot put the plane in a no win situation. If the computer would have acted as the pilot had requested the plane would hve went in to a stall and still would have crashed in to the woods.
  • Re:Poor pilots (Score:3, Insightful)

    by Linker3000 ( 626634 ) on Tuesday May 30, 2006 @04:24PM (#15430931) Journal
    Your argument would hold more water if the only code being executed was:

    FPSAT ;Fly Plane Safely All the Time

    AND FPSAT was a microcode instruction AND the CPU contained the AI of a perfect pilot AND it had no bugs AND it was not likely to be affected by power glitches or other external influences.

  • by Anonymous Coward on Tuesday May 30, 2006 @04:40PM (#15431019)
    IMHO, Airbus suffers from a poor user interface between the pilot and the airplane. In several crashes, the pilot's last words were some version of "Why is it doing that?". Airbus is usually able to point to the manual and right there, in black and white, on page 599, it says that if you use the rudder pedals while the windshield wipers are on, on a Tuesday, the tail will fall off. So the crash is "pilot error". The aircraft and its controls behave differently in different modes and sub-modes. So, a pilot needs to know if the plane is in "approach mode", "cruise mode", etc., before he can understand how the plane will react. The interface is complex enough that several perfectly good airplanes have crashed while the pilot was completely bewildered by what was going on. The plane and at least one pilot ought to be in "flying an airplane" mode the entire time the plane is in the air. KISS - Keep it Simple Stupid applies.
  • Re:Not true... (Score:3, Insightful)

    by John Courtland ( 585609 ) on Tuesday May 30, 2006 @04:57PM (#15431111)
    A computer might be deterministic for a given set of inputs, but what happens when the sensors throw bad data?
  • by blitz487 ( 606553 ) on Tuesday May 30, 2006 @05:05PM (#15431159)
    ... that all possible emergencies are anticipated by the programmers. They aren't, and probably even most aren't. Emergencies, by their very nature, are unique, unforeseen, and unintended. You need a pilot with judgement to get out of it. For a recent example, remember the Sioux City crash? The engine failure took out the hydraulic systems and the flight controls. The pilot, though, was able to regain control by manipulating engine thrusts.

    If a computer had been in charge, computers have no intelligence, no judgement, and no creativity. All dead is the inevitable result.

  • by TrekkieGod ( 627867 ) on Tuesday May 30, 2006 @05:20PM (#15431246) Homepage Journal
    So it seems the pilot failed to accelerate in time, isn't it? What should the software do, switch to warpdrive?

    I think what he's saying is that the computer looked at the current speed without taking into account that the speed was increasing and thus the plane would not have stalled, because by the time the nose was up, the speed would have been higher

    Autopilots these days are good. They are really good. In a commercial flight, they do 99.999% of the flying. The problem really only occurs in situations which don't normally happen, as the ones being described by the grandparent. To deal with the tedious and well understood, computers generally do a better job than humans. To deal with the unexpected, a well trained human will always be better than computer programs (until the programs become sentient, at least). A collision situation would be "unexpected" except that how to avoid them really is pretty well understood these days. I didn't read the article (sue me), but the article description says that the pilots "will be instructed and trained to rely on autopilots in most cases." Sounds to me like if the pilot decides to override the system, he can still do it.

    When an autopilot gets to override a pilot's best judgement, I think that's unsafe. If the autopilot takes action first but allows the pilot to assess the situation and take control if necessary, then that's saving valuable seconds in most cases, at the expense of wasting some time in the more rare cases. That's probably a fair trade-off.

  • Likley vs. Certain (Score:3, Insightful)

    by SuperKendall ( 25149 ) on Tuesday May 30, 2006 @05:26PM (#15431284)
    To be fair, these engines are kept below full reverse to avoid catostrophic engine failure that could likely result in explosion and loss of the entire wing.

    Well if you are certain you are about to go off the edge of a runway into a body of water, or into a woods at high speed then I'd take a "Likley" loss of a wing any day.

    The problem is that pilots should have the ability to make that choice as needed, and not have an option removed because it offers some risk. Perhaps it takes some manual saftey overrides but it should at least be possible.
  • by fonetik ( 181656 ) <fonetik@NOspam.onebox.com> on Tuesday May 30, 2006 @06:27PM (#15431618)
    You can just have couple of pilots remotely take control of the plane in very extreme situations.

    Wouldn't that conceivably allow someone to hijack a plane without even boarding it? Just how do you secure that?

    Planes could have flown themselves for years now, the main reason the overpaid passengers are there is to make the rest of the passengers feel warm and cozy.

    My understanding is that these planes get their inputs from Satellite and ground based stations. Just to imagine one nightmare scenario, a solar flare knocks out the GPS satellites, and knocks out the power on the ground. Better shielding protects the aircraft from the flare. By some estimates, you have 60,000 people in the air at any time. I'd personally rather have the "Overpaid passenger" there than a computer attendant. Not saying the current solution is perfect by any means, but I don't share your enthusiasm to remove humans from the equation. Especially to save 10% on the cost of a ticket.

  • by wired_parrot ( 768394 ) on Tuesday May 30, 2006 @08:52PM (#15432334)
    The statistical data flat out contradicts your conclusion, despite your anecdotal evidence. Take a look at the NTSB accident reports at www.ntsb.gov. Human error is attributable as the cause of accident in close to 80% of cases (see http://www.ntsb.gov/publictn/2004/ARC0401.pdf [ntsb.gov] and http://www.ntsb.gov/publictn/2004/ARG0401.pdf [ntsb.gov] for an annual summary of accident data for 2000 as an example). Aircraft related causes were a factor in less than one third of cases. One can always find anecdotal evidence supporting your point of view, but skim across a listing of recent accident reports and one quickly finds that human error is the overwhelming majority cause in most accidents. Automating the cockpit and reducing the human element therefore is the best way to reduce the number of accidents in the sky.

Remember, UNIX spelled backwards is XINU. -- Mt.

Working...