Air France Flight 296Q

Air France Flight 296Q was a chartered flight of a new Airbus A320-111 operated by Air France for Air Charter International.[1] On 26 June 1988, the plane crashed while making a low pass over Mulhouse–Habsheim Airfield (ICAO airport code LFGB) as part of the Habsheim Air Show. Most of the crash sequence, which occurred in front of several thousand spectators, was caught on video.

Air France Flight 296Q
F-GFKC, the Airbus A320 involved in the accident
Accident
Date26 June 1988 (1988-06-26)
SummaryControlled flight into terrain during flying display
SiteMulhouse–Habsheim Airport, Mulhouse, France
47°44′58″N 7°25′34″E
Aircraft
Aircraft typeAirbus A320 family
Aircraft nameVille d'Amsterdam
OperatorAir Charter International for Air France
IATA flight No.SF296Q
ICAO flight No.ACF296Q
Call signAIR CHARTER 296 QUEBEC
RegistrationF-GFKC
Flight originCharles de Gaulle Airport
StopoverIndira Gandhi International Airport
DestinationBasel–Mulhouse Airport
Occupants136
Passengers130
Crew6
Fatalities3
Injuries50
Survivors133

This particular flight was the A320's first passenger flight and most of those on board were journalists and raffle competition winners, having won tickets as part of a promotional event by local businesses. Many, including several unaccompanied children, had never previously been on an airplane.[2] The low-speed flyover, with landing gear down, was supposed to take place at an altitude of 100 feet (30 m); instead, the plane performed the flyover at 30 ft (9 m), skimmed the treetops of the forest at the end of the runway (which had not been shown on the airport map given to the pilots) and crashed. All 136 passengers survived the initial impact, but 3 then died of smoke inhalation from the subsequent fire; a quadriplegic boy in seat 4F, a 7 year old in seat 8C, trapped by her seat being pushed forward and struggling to open the seatbelt, and an adult who, according to her partner, had reached the exit with him but then turned back to try help the 7 year old. (The child had been travelling with her older brother but seated apart, he was swept out by a flow of escapees as he tried to find his sister).[3][4]

Official reports concluded that the pilots flew too low, too slow, failed to see the forest and accidentally flew into it. The captain, Michel Asseline, disputed the report and claimed an error in the fly-by-wire computer prevented him from applying thrust and pulling up. Five individuals, including the captain and first officer, were later found guilty of involuntary manslaughter. Captain Asseline, who maintained his innocence, went on to serve ten months in prison and a further ten months probation.[5]

This was the first fatal crash of an Airbus A320.

Aircraft

The accident aircraft, an Airbus A320-111, registration F-GFKC, serial number 9, first flew on 6 January 1988 and was delivered to Air France on 23 June, three days prior to its destruction. It was the third A320 delivered to Air France, the launch customer.[6]

Flight deck crew

Captain Michel Asseline, 44, had been a pilot with Air France for almost twenty years and had the following endorsements: Caravelle; Boeing 707, 727, and 737; and Airbus A300 and A310. He was a highly distinguished pilot with 10,463 flight hours.[1] A training captain since 1979, Asseline was appointed to head the company's A320 training subdivision at the end of 1987. As Air France's technical pilot, he had been heavily involved in test flying the A320 type and had carried out maneuvers beyond normal operational limitations. Asseline had total confidence in the aircraft's computer systems.[4]

First Officer Pierre Mazières7, and had qualified as an A320 captain three months before the accident.[4] Mazières had 10,853 hours of flight time.[1]

Flight plan

At the time of the incident, only three of the new aircraft type had been delivered to Air France, and the newest one (in service for two days) had been chosen for the flyover.[4]

The aircraft was to fly from Charles de Gaulle Airport to Basel–Mulhouse Airport for a press conference. Then, sightseeing charter passengers would board and the aircraft would fly the short distance to the small Mulhouse–Habsheim Airfield. The captain would make a low-level fly-pass over Runway 02, climb up and turn back, and repeat the fly-pass over the same runway in the reciprocal direction (Runway 20). This would be followed by a sightseeing trip south to Mont Blanc before the passengers would be returned to Basel–Mulhouse Airport. Finally, the aircraft would return to Paris.[4]

The pilots had each had a busy weekend and did not receive the flight plan until the morning of the flight. They received no verbal details about the flyover or the aerodrome itself.[4]

Flyover
F-GFKC taking off on its way to the Habsheim Airfield

The flight plan was that as the flight approached the airfield, the pilot would extend the third-stage flap, lower the landing gear, and line up for a level flight at 100 feet (30 m). The captain would slow the aircraft to its minimum flying speed with maximum angle of attack, disable the "alpha floor" (the function that would otherwise automatically advance engine thrust to TO/GA when the IAS reaches αMax), and rely on the first officer to adjust the engine thrust manually to maintain 100 feet. After the first pass, the first officer would then apply TO/GA power and climb steeply before turning back for the second pass. "I've done it twenty times!" Asseline assured his first officer.[4] The flyover had been approved by Air France's Air Operations Directorate and Flight Safety Department, and air traffic control and Basel tower had been informed.[4]

Habsheim Aerodrome was too small to be listed in the aircraft's flight computer, thereby requiring a visual approach; both pilots were also unfamiliar with the airfield when they began their descent from 2,000 feet (610 m) only 6 nautical miles (11 km) from the field. This distance was too short for them to stabilize the aircraft's altitude and speed for the flyover.[4] Additionally, the captain was expecting from the flight plan to do the pass over runway 02 (3,281 feet (1,000 m) long, paved) and was preparing for that alignment. But as the aircraft approached the field, the flight deck crew noticed that the spectators were gathered beside runway 34R (2,100 feet (640 m) long, grass). This last-minute deviation in the approach further distracted the crew from stabilizing the aircraft's altitude and they quickly dropped to 40 feet (12 m).[4]

From higher up, the forest at the end of 34R had merely looked like a different type of grass rather than what it was: a forest with trees. But now that the aircraft was performing its flyover at only thirty feet, the crew noticed the aircraft was lower than the now-identified hazard that they were fast approaching.[4] The cockpit voice recorder recorded the first officer's call:

First officer: "TO/GA power! Go-around track!"[4]

Followed by:

Cockpit area microphone (CAM): (increase in engine speed)
CAM: (noises of impact with treetops)
Captain: "Oh sh*t!"
END OF TAPE

The crew applied full power and Asseline attempted to climb. However, the elevators did not respond to the pilot's commands because the A320's computer system engaged its "alpha protection" mode (meant to prevent the aircraft from entering a stall). Less than five seconds later, the turbines began ingesting leaves and branches as the aircraft skimmed the tops of the trees. The combustion chambers clogged and the engines failed. The aircraft fell to the ground.[4]

Traditionally, pilots respect the inherent dangers of flying at low speeds at low altitudes, and normally, a pilot would not attempt to fly an aircraft so close to stalling with the engines at flight idle (minimum thrust setting in flight). In this instance, however, the pilots involved did not hesitate to fly the aircraft below its normal minimum flying speed because the purpose of the flyover was to demonstrate that the aircraft's computer systems would ensure that lift would always be available regardless of how the pilots handled the controls. Asseline's experience of flying the aircraft type at the outer limits of its flight performance envelope may have led to overconfidence and complacency.[4]

Crash and evacuation

During the impact, the right wing was torn off, and the spilling fuel ignited immediately. Two fire trucks at the airshow set off and an ambulance followed. Local emergency services were informed by radio communication.[4]

Inside the aircraft, all the lights had gone out before it came to a final rest, there was no emergency lighting apart from the exit signs.[3] Many passengers were dazed from hitting their heads on the backs of the seats in front of them. Some passengers had difficulty unfastening their seatbelts because they were unfamiliar with the mechanism (which differs from the type used in car seatbelts). The purser went to announce instructions to the passengers but the public address system handset had been torn off. He then tried to open the left-side forward door, which was blocked by trees. The door opened partway, and the emergency escape slide began inflating while it was stuck partly inside the fuselage. The purser, a passenger, and a flight attendant (a guest from another airline) managed to push the door fully open. In the process, the purser and the passenger were thrown out of the fuselage with the slide landing on top of them. The flight attendant then began evacuating the passengers but they soon began to pile up at the bottom of the slide as their route was blocked by trees and branches. The egress of the passengers was temporarily halted while the purser and another flight attendant began clearing the branches. When the evacuation continued, the flight attendant stayed at the door, helping passengers, until she began suffering from smoke inhalation.[4]

By this time, the fire had entered the right side of the fuselage through the damaged floor section between seat rows 10 and 15. A passenger tried to open the left-side overwing exit. It would not open, which was fortunate as there was by that time a fire on the left wing.[4]

The panicking passengers now began pushing toward the front of the cabin. A flight attendant standing in the centre of the cabin at seat 12D was pushed into the aisle by a severely burnt passenger from 12F. Then, as she was helping another passenger whose clothes were on fire, she was carried forward by the surge of people rushing to escape. After the rush of people had left and the interior was fast becoming toxic, she stood at the front door and called back into the cabin. There was no reply and the thick black smoke made a visual check impossible, so she exited the fuselage. The evacuation from the rear door had been fast and smooth thanks to the instructions from the flight attendants at the rear of the aircraft.[4]

The medical team from the air-show arrived and began examining the passengers. Ten minutes after the crash, the first of the fire trucks arrived. But because of the forest, only the smaller vehicles were able to reach the wreckage. Apart from the tail section, the aircraft was consumed by fire.[4]

Of 136 people on board, three did not escape. One was a disabled boy in seat 4F who was unable to move. Another was a girl in seat 8C, who was unable to remove her seatbelt (her older brother had removed his own seatbelt but was carried away by the rush of people before he could help his sister). The third was a woman who had reached the front door and then returned to help the girl. Thirty-four passengers required hospitalisation for injuries and burns. Both pilots received minor head injuries and also suffered from smoke inhalation and shock.[4]

Accident investigation

The official investigation was carried out by the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), the French air accident investigation bureau, in conjunction with Air France and Airbus.[4] Although the official investigation was written in French, the BEA released an English version on 29 November 1989. The translated version of the report can be found on the Aviation Accidents Database and at the Aviation Safety Network.[7][3]

Flight recorders

The plane's flight recorders were found still attached in the unburnt tail section. The Cockpit Voice Recorder (CVR) continued to operate for about 1.5 seconds after the initial impact. The Digital Flight Data Recorder (DFDR) continued to operate for about one second, then recorded nonsensical data for another two seconds. Interruption of the power occurred forward of the tail section—most probably in the wheel-well area, which was heavily damaged.[4]

The CVR was read during the night of 26 June at the BEA. The transcription was later clarified with the assistance of the pilots involved. The tape speed was set using the 400 Hz frequency of the aircraft's electrical supply and then synchronised with the air traffic control recordings, which included a time track.[4]

The DFDR was read the same night by the Brétigny sur Orge Flight Test Centre:

  • 12:43:44 - the aircraft begins its descent from 2,000 feet (610 m), initially at a rate of 300 feet (91 m) per minute with 'Flaps 1'.
  • 12:44:14 - the engine power is reduced to flight idle. Three seconds later, the undercarriage is extended. A further ten seconds later, 'Flaps 2' is selected.
  • 12:44:45 - 'Flaps 3' is selected as the aircraft descends through 500 feet (150 m) at an airspeed of 177 knots.
  • 12:45:06 - the aircraft descends through 200 feet (61 m) at an airspeed of 155 knots.
  • 12:45:15 - the aircraft, now at 90 feet (27 m), begins a deviation to the right (maximum bank angle: 30°) to line up with the grass strip 34R.
  • 12:45:23 - the aircraft completes the deviation at a height of 46 feet (14 m) and an airspeed of 141 knots. During this manoeuvre, a fluctuation in the radio altimeter height corresponds to the aircraft passing over a patch of trees (whereas before and after this fluctuation, the readings of the radio altimeter and those of the barometric altimeter match perfectly). Three seconds later, the aircraft descends through 40 feet (12 m) at an airspeed of 132 knots. The Captain begins to flare the aircraft (he lifts the nose 4°) to level its flight. The aircraft levels off at 30 feet (9.1 m).
  • 12:45:30 - nose-up attitude increases to 7°.
  • 12:45:35 - nose-up attitude is now 15° and speed is 122 knots. TO/GA power is applied. Four seconds later, the aircraft begins striking the treetops.[4]

Aircraft and engines

Investigators found that the aircraft had been airworthy, that its weight and centre-of-gravity had been within limits, and that there was no evidence of mechanical or electronic systems failure.[4]

The flight deck crew believed that the engines had failed to respond to the application of full power. With the CFM56-5 engines, four seconds are required to go from 29% N1[lower-alpha 1] (flight idle) to 67%. It then takes one second more to go from 67 to 83% N1. From the engine parameters recorded on the DFDR and spectral analysis of the engine sounds on the CVR, it was determined that five seconds after TO/GA power was applied, the N1 speed of Nº1 engine was 83% while that of Nº2 engine was 84%. Spectral analysis of the engine sounds indicated that 0.6 seconds later, both engines had reached 91% (by this stage, they were starting to ingest vegetation). This response of the engines complied with their certification data.[4]

Official report

The official report from BEA concluded that the probable cause of the accident was a combination of the following:

  • Very low flyover height, lower than surrounding obstacles;
  • Speed very slow and reducing to reach maximum possible angle of attack;
  • Engines speed at flight idle; and
  • Late application of go-around power.[4]

Furthermore, the bureau concluded that if the descent below 100 feet was not deliberate, it may have resulted from a failure by the crew to take proper account of the visual and aural information available to them regarding the elevation "above ground level" (AGL) of the aircraft.[1][6]

The report further recommended that:

  • Passengers should be banned from all demonstration flights
  • Flight crews should be provided with – and ensure – proper reconnaissance of airfields
  • Airline company procedures should be reviewed to ensure they comply with official regulations concerning altitude

Prosecutions

In 1996, Captain Asseline, First Officer Mazières, two Air France officials and the president of the flying club sponsoring the air show were all charged with involuntary manslaughter. In 1997, all five were found guilty. Asseline was initially sentenced to six months in prison along with twelve months of probation. Mazières was given a twelve month suspended sentence. The others were sentenced to probation.[8] Asseline walked free from the court and said he would appeal to France's highest court, the Court of Cassation (French: Cour de Cassation). According to French law, Asseline was required to submit himself to the prison system before his case could be taken up by the Court of Cassation. In 1998, Asseline's appeal was rejected and his sentence was increased to ten months of imprisonment along with ten months of probation.[5]

Alternative explanation

The television documentary series Mayday also reports claims in Season 9 Episode 3 that the plane's flight recorder might have been tampered with and indicated that four seconds had been cut from the tape; this was shown by playing back a control tower tape and comparing it to the remaining tape. Asseline argues that he attempted to apply thrust earlier than indicated in the flight recorder data. When he increased throttle to level off at 100 ft, the engines did not respond. Asseline claims that this indicated a problem with the aeroplane's fly-by-wire system rather than pilot error. After a few seconds, Asseline claims, he became worried that the plane's completely computerised throttle control had malfunctioned and responded by pulling the throttle all the way back then forward again. By that time the aircraft had touched the trees. Mayday also looks at the theory that it was the computer at fault, not the pilots. Because the aircraft's altitude had fallen below 100 ft, the plane's computer may have been programmed to believe it was landing and therefore prevent any drastic manoeuvres from either pilot. When the crew suddenly asked the plane for more power and lift, it may have simply ignored them.[5]

It was also claimed by the Institute of Police Forensic Evidence and Criminology, based in Switzerland, that the flight data recorders may have been switched and were not the original ones in the airplane.[5][9] Airbus made a detailed rebuttal of these claims in a document published in 1991, contending that the independent investigator employed by the filmmakers made an error when synchronising the recordings based on a misunderstanding of how the "Radio Transmit" parameter on the flight data recorder functioned.[10]

Depictions in media

The episode "Blaming the Pilot" of the TV series Survival in the Sky featured the accident.

The Discovery Channel Canada / National Geographic TV series Mayday featured the accident and subsequent investigation in a season 9 episode titled "Pilot vs. Plane" and included an interview with Captain Michel Asseline, survivors, and accident investigators.[11]

The episode "Disastrous Descents" of the TV series Aircrash Confidential produced by WMR Productions and IMG Entertainment, featured the accident and included an interview with Captain Michel Asseline.

See also

Notes
  1. The speed of the Stage 1 fan of a turbofan engine, expressed as a percentage of normal maximum

Footnotes
  1. "Commission d'Enquête sur l'accident survenu le 26 de juin de 1988 à Mulhouse-Habsheim (68) à l'Airbus A 320, immatriculé F-GFKC – Rapport Final" [Commission of Inquiry into the accident on June 26, 1988 in Mulhouse-Habsheim (68) on the Airbus A 320, registered F-GFKC - Final Report] (PDF) (in French). 24 April 1990. Archived from the original (PDF) on 12 November 2013.
  2. Cloudberg, Admiral (10 November 2022). "Fly By Wire: The crash of Air France flight 296". Medium. Retrieved 9 October 2023.
  3. "Air France flight AF296Q English official report" (PDF). 29 November 1989.
  4. Job, Macarthur (1998). Air Disaster Volume 3. Australia: Aerospace Publications. p. 155. ISBN 1-875671-34-X.
  5. Kilroy, Chris. "Investigations: Air France 296". AirDisaster.Com. Archived from the original on 5 August 2005.
  6. "ASN Aircraft accident Airbus A320-111 F-GFKC Mulhouse-Habsheim Airport". aviation-safety.net. Aviation Safety Network. Retrieved 3 February 2007.
  7. "Air France – Airbus A320-111 (F-GFKC) flight AF296Q". 26 April 2020.
  8. "Pilot who crashed jet in air show gets jail time". AP NEWS. 14 March 1997. Retrieved 10 February 2021.
  9. Roger, Christian (26 June 1998). "The Airbus A320 crash at Habsheim, France 26 June 1988" (PDF). crashdehabsheim.net.
  10. "The A320 Habsheim accident: An Airbus Industrie response to allegation made in television programmes and other media" (PDF). Airbus. March 1991.
  11. "Pilot vs. Plane". Mayday. Season 9. 2010. Discovery Channel Canada / National Geographic Channel.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.