On 26 June 1988, an Airbus A320 registered F-GFKC, operated by Air France as Flight 296, crashed during a demonstration at an air show near the Mulhouse-Habsheim aerodrome in eastern France. The aircraft was nearly new - the A320 had entered service only weeks earlier - and it was the first commercial airliner with full digital fly-by-wire controls, in which computers, not direct mechanical linkages, translated the pilots’ inputs into movements of the flight surfaces. The accident was the first fatal crash of an A320 and one of the most scrutinized in aviation history.
The plan was a slow, low pass over the airfield’s runway with the landing gear down. As the BEA’s record of the event describes, “on 26 June 1988, the A320 F-GFKC of the national airline Air France was to perform a series of passenger flights” in connection with the local aero club’s show. During the flyover the aircraft descended lower than intended, flew very slowly at a high angle of attack, and, when the crew finally applied go-around power, the engines could not spool up in time. The A320 settled into the trees beyond the runway and caught fire. Three of the people on board died.
The BEA, France’s civil aviation accident investigation bureau, conducted the official inquiry and published its final report. It identified a combination of causes centered on the way the flyover was flown: an overflight height far lower than the surrounding obstacles, a very low airspeed, engines at flight idle, and the late application of go-around thrust. In the BEA’s account, the immediate chain of events was rooted in how low and slow the aircraft was brought, not in a failure of the engines or structure.
That conclusion was fiercely contested and became the heart of a long-running controversy. The captain and others argued that the fly-by-wire flight computers had not responded as the crew expected, and questions were raised about the handling and integrity of the flight-data and cockpit-voice recorders used in the investigation. Whether the airplane’s computers behaved correctly, and whether the recorders accurately captured what happened, were debated for years in the press and the courts. For the first fly-by-wire airliner to crash at a public demonstration, the dispute could hardly have been more pointed.
Habsheim entered history as an early, vivid case of the central tension introduced by putting computers in command of flight: when an aircraft is lost, did the machine do what the pilots intended, did the pilots understand what the machine was doing, and can investigators reconstruct the truth from the system’s own records? Those same questions would return, with far greater loss of life, in later computerized-flight disasters - making this 1988 air-show crash a foundational reference point for the field of software in safety-critical systems.