Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Air France Flight Missing

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
There are multiple accidents where the use [misuse?] of Airbus automation has been a factor. Such Boeing events (like the Turks in Amsterdam) are less frequent. I am not a Boeing grandstander by any means but I think the data supports my statement.
 
"..the crew didn't realize what "mode" the computer was in. "

Therefore, Pilot error.

However, were there no FBW ( direct mechanical control ) and no "modes" to deal with there would have been no crash.

Hmmm. A conundrum.

Next: Which came first? The Chicken? Or, the Egg?


MKR

Yeah, when the first airline pilot uttered the words "what's it doing now?" we had a whole new slew of problems to deal with.

Had this same AF scenario happened exactly as it did...only in 1968 and the aircraft had been a DC-8, I'd be willing to lay money down we wouldn't be having a discussion about an accident...
 
Try the Paris Air Show years ago when the flight computer landed the jet in the forest. Trying to do a low pass the crew didn't realize what "mode" the computer was in. It was landing. Crews advanced throttles and rotated the aircraft, both actions were overridden by the computer logic. Am I wrong here? It was a long time ago.
Yup you are wrong and it wasn't the Paris Air Show...
 
2 bodies found, and a suitcase now too from that flight
 
On a Boeing, if I override the autothrottles (just by moving them) or kick the autopilot off, I have control of the airplane. Period. The end.

What about the 777? Do you have control of the airplane? Period. The end. That's a Boeing too, right?:confused:
 
Try the Paris Air Show years ago when the flight computer landed the jet in the forest. Trying to do a low pass the crew didn't realize what "mode" the computer was in. It was landing. Crews advanced throttles and rotated the aircraft, both actions were overridden by the computer logic. Am I wrong here? It was a long time ago.

It wasn't the Paris Air Show but never mind. The crew dipped way below their planned fly-by altitude and then expected the airplane to apply corrective thrust. The airplane doesn't behave the same that close to the ground as at higher altitude and refused to override the pilot. The crew was too late applying corrective thrust and they crashed. The crew sat on their hands waiting on a feature demo that wasn't armed. The plane never overrode the crew's commands. The crew simply didn't act until it was too late to matter.
 
Last edited:
Yup you are wrong and it wasn't the Paris Air Show...
Thanks Filejw for the good catch! Unfortunately, my memory is the second shortest thing I own anymore.
I dug up some info on that one and it seemed that pilot error was a primary factor.
I hope that they find the acft and figure this one out so it might be prevented in the future. Condolences to all those effected by this sad event.
Date: June 26, 1988
Time: 14:45
Location: Habsheim, France
Operator: Air France
Flight number: 296Q
Route: Basel - Basel
AC type: Airbus A320-111
Aboard: 136 (passengers: 130, crew:6)
Fatalities: 3 (passengers: 3, crew:0)

Summary: The plane was scheduled to perform a series of fly-bys at an air show. The plane was to descend to 100 ft. altitude with landing gear and flaps extended. The automatic go-around protection was inhibited for the maneuver. During the maneuver, the plane descended thru 100 ft. to an altitude of 30 feet and hit trees at the end of the runway. The aircraft was totally destroyed by the successive impacts and violent fire which followed. The pilot allowed the aircraft to descend through 100 ft. at slow speed and maximum angle of attack and was late in applying go-around power. Unfamiliarity of the crew with the landing field and lack of planning for the flyby.

http://www.youtube.com/watch?v=_EM0hDchVlY&feature=related
 
Try the Paris Air Show years ago when the flight computer landed the jet in the forest. Trying to do a low pass the crew didn't realize what "mode" the computer was in. It was landing. Crews advanced throttles and rotated the aircraft, both actions were overridden by the computer logic. Am I wrong here? It was a long time ago.

Yes you are wrong, the crew did not advance the thrust levers to TOGA in initiate a go-around. So the airplane thought it was still landing, not the smartest thing in the world...but like they say garbage-in, garbage-out.

"..the crew didn't realize what "mode" the computer was in. "

Therefore, Pilot error.

However, were there no FBW ( direct mechanical control ) and no "modes" to deal with there would have been no crash.

Hmmm. A conundrum.

Sorta...how many go-around's are performed in A320's during a year? How many have had a similar result?

I don't disagree, manual inputs provide a better "feel" but you can't argue with statistics.
 

Latest posts

Latest resources

Back
Top