Air France Flight 296 (1996): conspiracy?

The thread about what happened in the cockpit of Air France 447 got me curious about another Air France crash: Flight 296, which happened back in 1988. This was a demonstration flight at an airshow of a brand new Airbus A320. The aircraft flew too low and too slow on the flyby, and when the pilot wanted to climb, the engines developed power too late; the plane flew past the end of the airfield, descended gently into the trees before bursting into flames. video of the crash is here.

The Captain, First Officer, a couple of Air France officials and the president of the club that put on the airshow were all found guilty of manslaughter.

There are claims that a conspiracy existed to protect Airbus and the government of France by scapegoating these folks, the motive being that any fault that could be publicly attributable to this fancy new fly-by-wire plane could be financially devastating to Airbus and its shareholders. The details of that alleged conspiracy are described here; among other things they allege that the FDR and CVR presented at the trial were out of police custody for over a week after the accident and had been tampered with.

Question: how credible are these conspiracy theories?

How credible are ANY conspiracy theories? Especially ones that emerge decades later?

Any time there’s any aircraft accident there’s a certain rush to blame anybody but the manufacturers or operating companies. As long as we can label it pilot or maintainer or controller error, then everybody is spared the expense of actually discovering & remediating the problem, plus it reduces the liability tail a bit.

Overall aviation is very clean-hands & honest about assessing & fixing problems. Certainly moreso than any other industry I’m familiar with. But it isn’t perfect.

IIRC at the time it occurred there wasn’t much doubt what happened. A combination of the odd handling qualities plus a simple pilot goof put them in a crack which the pilot noticed just a bit too late to recover from. So they didn’t.

No kidding high level conspiracy? Heck no. The general desire of the manufacturer’s engineering organization to defend their invention, sure.

Airbus remains dedicated even today to their ideas about how to design an airliner. Despite a notably higher rate of accidents caused by, or exacerbated by, the airplane being, IMO, just a little too smart, which turns into being just a little too dumb when the chips are down.

Well the conspiracy theory has been around since the accident, it’s not a recent thing. And there have been other attempts by manufacturers and airlines to cover things up. Air New Zealand acted poorly in the aftermath of the Erebus crash and McDonell Douglas had some bad moments with the DC10.

Not long after the Airbus crash there was an episode of NOVA about this new fly-by-wire technology and they specifically and very matter-of-factually said that the crash was caused by it. That the plane was essentially in ‘landing mode’ and therefore refused to respond to the pilot’s commands to climb (being a commercial airliner it didn’t have an ‘acrobatic’ mode). They also said that AirFrance publicly denied this and just said it was pilot error.

Thing is both could be, and I think are, true. It was the pilot’s error in not recognizing the potential conflict doing a low, non-landing pass in a high-tech plane like that would cause. So I think it’s almost certain that Airbus did cover things up and unjustly used the flight crew as scapegoats.

It wasn’t exactly a *grand *conspiracy, but I think it was a govt/corporate conspiracy nonetheless! France certainly has done that sort of thing before (building an SST nobody wanted, blowing up Greenpeace cause it annoyed them…)

I recall hearing the same thing back then, but the Wikipedia page says the plane’s software refused to allow a pitch-up because a stall was already imminent. This can be seen in the video, as the tail of the plane is actually lower than the main landing gear despite a level (or slightly descending) flight path. Regardless of whether a “landing” mode exists or whether he was in it, it’s clear from the video that he was flying too slow. This reminds me of the mention (in the AF447 thread) about Airbus fly-by-wire planes operating in “normal law” mode, in which the software will not permit the plane to be stalled.

At that speed and power setting, if he had been flying a low-tech airliner that permitted the nose to pitch up when he commanded it, they would have stalled and crashed anyway.

Going by long-ago recollections, but I remember hearing that the plane’s software was preventing the engines from spooling up as fast as the pilot wanted them to. He pushed the thrust levers forward, expecting full power to allow him to climb, and the software (either to save fuel or wear-and-tear on the engines) decided to apply the power more gently.

If such a thing were true, the findings of the accident investigation don’t necessarily imply a conspiracy. Was the plane at fault for overriding the pilot’s command, or was the pilot at fault for putting the plane into a situation it wouldn’t be able to get out of? In normal operations, the A320 does what it was designed to do. The design of very complex machines to always do what they “should” is not a straightforward task.

All this gets deep quickly, and it’s real easy to find oneself throwing out sound bites which, while mostly accurate, add up to a pitifully poor caricature of reality. Discovery, NOVA, and all the rest are notorious for this.

Speaking just to engines as an example …

  1. All jet engines take several seconds to go from idle to useful thrust. The Airbus is not unique in that regard. It’s simply a mattter of the physics of how they’re designed. Some are slower than others, some are quicker. Any given model is quite consistent though.
  2. Starting about 20 years ago jet engines began to have computerized fuel controls. Much as cars went from mechanical carburetors to modern computerized fuel injection. Jet engines are now available with several different versions of the fuel control program but otherwise identical hardware. An airline can decide to buy the lower-power engines or the higher-power engines. Same hardware, just a different rev limiter inside the software. The software can also be tuned for faster or slower engine acceleration. faster acceleration dumps more fuel in faster resulting in higher internal temps, which in turn directly cause greater wear, short life, etc.

Lower power and/or slower acceleration saves fuel in operation and costs less per hour in lifecycle maintenance. So often airlines opt for that. Other carriers, who may operate from shorter or higher-altitude airports or often operate the aircraft near max range = max weight may choose the higher/faster engine option because net net the extra performance pays for itself.

But whatever the program is, that’s what it is. It’s factually accurate but logically invalid to say something like “the engine accelerated slowly to save money/fuel.” The pilots at that carrier will be trained on, and come to know, the characteristics of their engines. From their POV, characteristics are what they are.
2.a Having said that, it’s not uncommon for engines to have different idle modes. Flight, ground, approach, and landing could each have a different idle setting & therefore different acceleration time curves. Approach is the critical one and would tend to be hghest idle = quickest acceleration. These various modes are automatically selected by the aircraft logic and are subliminal to the pilot.
3. Pilots critically need to have an accurate visceral “feel” for how long engine acceleration takes to safely operate near the corners of the envelope. As well as a solid & accurate awareness of altitude & altitude trend and most of all speed & speed trend.

It *is *fairly easy to get into a crack where you figure out too late that you’re in a crack. And then instantly moving the throttles to full power is too late to save you. This is a risk every day on every flight during the approach & landing. The answer is to know the trap is there and stay far enough away from the edge that you don’t get suckered.

In day-to-day airline ops it’s easy to stay far enough from the trap that we don’t fall in. Although I’d wager that every day someplace around the world some airliner has a closer-than-desired call with falling out of the approach & landing short due to pressing too close to the edge.

The airshow flyby we’re all taking about was emphatically *not *day-to-day airline ops. The show profile they planned was truly maximum performance. Which is another way of saying zero margin for error. Through some combination of poor planning, poor execution, or poor understanding of the nooks & crannys of operating the airplane on the edge (which really falls under poor planning), they drove into a crack the couldn’t drive out of.

If the pilot was expecting approach idle but the airplane was actually running in landing idle mode (for legit or malfunction reasons) , that could be the straw which broke the camel & “caused” the mishap.

All the above only scratches the surface of just engine acceleration issues. There’s another half-dozen engineering factors which NOVA, Discovery et al talked about which could also be de/re-constructed to provide teh rest of teh nuance points to a lay audience. And probably a half-dozen human factors as well. This stuff is not simple. These are among the most highly engineered things mankind knows how to build.
4. I’m not trying to hang the pilot. This show maneuver should have been fully vetted by management & engineering & flown in the sim umpteen times. My bet, knowing a little of Airbus culture, is that both the engineers & the pilots hubristically assumed everything would work 100% as expected. Management gave a wink & nod & said “Let 'er rip!”, and the engineers & piltos gave it a quick once over in the sim.

At the moment of truth, I can’t say whether the pilot just goofed, or the instruments told a factually accurate but holistically misleading picture, or there was a software glitch / unexpected “feature” which threw a joker on the pile at the last moment.

But at the end of the day a very skilled aviator, much more skilled than I, ran a perfectly good airplane into trees by trying to do something the machine couldn’t do. Not wouldn’t. Couldn’t.
5. A very legit quetion about aircraft design philosophy is whether it’s a good thing to have airplanes with lots of “intelligence” in the very basics of power & attitude control. Smarts sound nice. But if they actually produce unpredictable or unexpected behavior in real time in extremis, we’d be better off with less smarts.

When it’s down to the nut cuttin’ & fractions of seconds matter, pilots are not going to deeply grok that Control Mode 12.a.4.c has activated and now this, that, and the *other thing *all now work dfferently. That’s now *couldn’t *shades into *wouldn’t *as seen from the cockpit.

My overall gut feel is Airbus has this problem but can’t / won’t admit their engineers have gone too far. But that’s gut. And as I said in another recent post in another thread, I’ve never flown Airbuses (yet), so my opinion should be taken as an interested & skilled observer, not an experienced participant.

One of the most informative posts I’ve ever read here. I feel proud that it was my ignorance which inspired it.

However…

Do we really need all this “intelligence”, the engine software acceleration curves and all the rest, when there’s already a well-programmed and highly-adaptable computer sitting in the pilot’s seat? Tell him to apply the throttles slowly to save fuel and maintenance costs, but that one time in a million that he needs power right now, that situation that nobody thought of in advance, it should be there.

I am awed by the state of aviation safety and the herculean efforts to investigate accidents. But it almost seems like aircraft designers are starting to take that for granted. They know what a plane goes through in normal service, so they design the next new airplane to do just that and nothing more. They’ll put in a particular fuel-mapping strategy for the engines because none of that airline’s routes use an airport above a certain altitude; doesn’t that seem like we’re cutting awfully close to the bone? (Yes, a .01% fuel savings probably means a few million dollars per year to the airline.)

My dad was a career pilot and I’ve done a little flying. I work with computers, and there are times when I want the software to get out of my way. Stop trying to help me, I know what I’m doing.

Actually, I thought you put your finger directly on the core issue. That was insightful, not ignorant.

Again you’ve insightfully put your finger exactly on the nub of the problem. There absolutely *are *cases where the uber-smart machines are getting in the way. But there are also cases where the smarter machines are preventing accidents / incidents we never read about. I’m not qualified to assess the net effect. But I’m gonna bet that since there’s no headline grabbing studies one way or the other (yet) the differences are subtle.

I’ve been flying for fun or for pay for 40 years now. I tend to lean back to the old ways. I do agree there is some sense in which modern state-of-the-art aviation is taking for granted things which got that way only through great effort & will stay that way only with ongoing great effort. And we’re seeing skimping in the ongoing part.

When I started with the airlines it took near continuous mental effort in cruise to maintain a complete mental model of our navigation situation, and it took a control input every couple of *minutes *to keep everything operating right on parameters. Now the complete nav model is on the screen & we can go multiple *hours *without touching anything but the comm radios to periodically change frequency. And even that’s slated to be supplemented by, and later replaced by, a fully automatic data link system.

It’s damn hard to attentively watch paint dry for hours on end. It’s even harder to be able to transition from paint watcher to Chuck Yeager on a moment’s notice.

I think what this is leading to is more brittle failure modes for the whole man / machine system. There will be fewer failures & fewer accidents. But a bigger proportion of those fewer accidents will be like AF 447: everything normal, something relatively minor fails, and the combo of man / machine becomes unrecoverable quickly followed not long after by a fiery mess.

IMO & all that, despite this being GQ.

I’ve been out of it for too long & did not know that the automation had gotten that far.

Most informative. Thanks you.

::: mass, never forget your mass :::

I have a BIL who was Coast Guard and he said that when your mass gets to a certain level, you no longer drive, you position in advance. The larger the mass or the greater the speed the smaller the amount of ‘out of position’ you can get away with.

Climb and descent is still pretty hands-on, even if it’s just button-pushing on the FMC & autopilot panels, not the yoke & throttles. All takeoffs & most approach & landings are pure yoke & throttles.

But from near top of climb to top of descent can be 100% hands off everything if we’re in a low-traffic all-goes-according-to-plan scenario. With the advent of high altitude GPS-based routes, we now flight plan very close to a straight line from SID end to STAR pickup, so far fewer “proceed direct” enroute clearance changes are needed or requested.

HAL knows where he’s going & how to get there. We & ATC just watch. And wait.

And if you get into trouble, you’ll wish you hadn’t skipped that last Mass… :slight_smile:

Well, the comment about my ignorance was meant somewhat tongue in cheek.

That’s where the science and art of airline safety really gets interesting. It does not stop with just the mechanical aspects. I’m sure someone (probably multiple someones) is studying exactly how much workload during flights will keep pilots at their optimal readiness to recognize and respond to an emergency.

I’m sure you’ve heard the joke about the flight crew of the future being one pilot and one dog.

From what I’ve heard (and perhaps I know just enough to ask the right questions), that really gets to the heart of the different design philosophies between Airbus and Boeing. Boeing puts the pilot as the ultimate authority, Airbus planes give that role to the computer. On a routine basis, obviously both approaches work.

I remember reading the incomparable (in my layman’s opinion, though I’d be interested in any disagreement) William Langewiesche’s assessment of the disaster. He put the whole thing (as I recall) squarely on Asseline’s head. He described him as a particularly arrogant pilot who went further during the actual show than had been planned beforehand, and the cockpit voice recorder seemed to show him ignoring warnings of the copilot. Anyhoo, sorry I can’t find the actual quotes from the book I read, but thought I’d throw that out there.

'Zactly.

Ya know the best example of this was Aeroflot Flight 593. Even though this was a blatant example of, not merely pilot error but of left-over communist bureaucratic corrupt entitlement, again the Airbus plane had too much control. Too much control and, more importantly, assumed that the flight crew was trained to know it, not them, would be in control:
*
“Despite the struggles of both pilots to save the aircraft, it was later concluded that if they had simply let go of the control column, the autopilot would have automatically taken action to prevent stalling, thus avoiding the accident.”*

Also makes me mad that this idiot pilot’s hometown considers him a hero. Like I said this was a case of culture trumping common sense. Sterile cockpit? Nope, that cockpit was his personal Red Sea dacha and damn if he wasn’t gonna impress his kids & their mother & the flight crew with it!

I found the book: Fly by wire, the relevant description starting around p140. Here is google books link.

Interesting excerpt. The captain’s, and his supporters’, almost-immediate allegation of a conspiracy is mentioned at pp. 150-151.

Is there any provision with these sophisticated fly-by-wire systems for a “manual override” button that the captain can push and then do just what he or she wants immediately, rather than wait for the computer to interpret and decide what’s best under the circumstances? (I understand that that might have resulted in even greater loss of life aboard AF296).

And would it have made any difference if the pilot had retracted the landing gear?

The A310 is not a fly-by-wire aircraft. I don’t see how you can blame this accident on supposed excessive automation in Airbus’s design philosophy.