Air France Flight 296

Air France Flight 296

An Air France Airbus A320 similar to the aircraft involved in the accident.
Accident summary
Date 26 June 1988 (1988-06-26)
Summary Pilot Error disputed with error with fly-by-wire system
Site Mulhouse–Habsheim Airport, Mulhouse, France
47°44′58″N 7°25′34″E / 47.74944°N 7.42611°E / 47.74944; 7.42611Coordinates: 47°44′58″N 7°25′34″E / 47.74944°N 7.42611°E / 47.74944; 7.42611
Passengers 130
Crew 6
Fatalities 3
Injuries (non-fatal) 50
Survivors 133
Aircraft type Airbus A320-111
Operator Air France
Registration F-GFKC

Air France Flight 296 was a chartered flight of a new fly-by-wire Airbus A320-111 operated by Air France. On 26 June 1988, it crashed in front of a crowd of several thousand while flying over Mulhouse–Habsheim Airport (ICAO code LFGB) as part of the Habsheim air show, which resulted in it being one of the very few crashes of a commercial airplane caught in its entirety on video. This particular flight was not only the A320's very first passenger flight (most of whom were journalists and raffle winners), but it was also the very first public demonstration of any civilian fly-by-wire aircraft. The cause of the crash has been the source of major controversy. The low-speed flyover, with landing gear down, was supposed to take place at an altitude of 100 feet (33 metres); instead, the plane performed the flyover at 30 feet, skimmed the treetops of the forest at the end of the runway, and crashed to the ground. All the passengers survived the initial impact, though a woman and two children died from smoke inhalation before they were able to escape.

Official reports concluded that the pilots failed to see the forest and accidentally flew into it. This was the first crash of an A320 aircraft.

Flight deck crew

Captain Michel Asseline, 44, had been an airline pilot with Air France for almost 20 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 to his credit.[1] A training captain since 1979, he 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. He had total confidence in the aircraft's computer systems.[2]

First Officer Pierre Mazières, 45, had been flying with the company since 1969 and had been a training captain for six years. He was endorsed on Caravelle, Boeing 707 and 737, and had qualified as an A320 captain three months before the accident.[2] He had 10,853 hours of flight time under his belt.[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.[2]

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 Habsheim aerodrome. 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.[2]

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.[2]

Flyover

The flight plan was that as they approached the airfield, they would extend third-stage flap, lower the landing gear, and line up for level flight at 100 feet. 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 increase engine thrust when the angle of attack reached 15°) 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 TOGA (takeoff, go-around) power and climb steeply before turning back for the second pass. "I've done it twenty times!" the captain assured his first officer.[2]

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.[2]

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 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.[2]

Additionally, the captain was expecting from the flight plan to do the pass over runway 02 (3,281 feet 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 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.[2]

From higher up, the forest at the end of 34R had looked like a different type of grass. But now that the aircraft was performing its flyover at only 30 feet, the crew noticed the aircraft was lower than the now-identified hazard that they were fast approaching.[2]

First officer: "TOGA power! Go-around track!"[2]

The crew applied full power and the pilot attempted to climb. However, the elevators did not respond to the pilot's commands, because the A320 computer system engaged its "alpha protection" mode (meant to prevent the aircraft 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 up and the engines failed. The aircraft fell to the ground.[2]

Traditionally, pilots respect the inherent dangers of flying at low speeds at low altitude, 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). But in this instance, the pilots involved did not hesitate to fly the aircraft below its normal minimum flying speed because the whole purpose of the flyover was to demonstrate that the aircraft's computer systems would ensure lift would always be available regardless of how the pilots handle the controls. The captain's previous experience flying the aircraft type at the edge of its limits may have led to overconfidence and complacency.[2]

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.[2]

In the aircraft, many of the 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 (it 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.[2]

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.[2]

The panicking passengers now began pushing toward the front of the cabin. A flight attendant standing in the center 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.[2]

The medical team from the airshow 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.[2]

Of 136 people on board, three did not escape. One was a handicapped boy in seat 4F who was unable to move. Another was a girl in seat 8C, who was unable to remove her seatbelt (her younger 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 hospitalization for injuries and burns. Both pilots received minor head injuries and also suffered from smoke inhalation and shock.[2]

Accident investigation

The official investigation was carried out by the Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation Civile (BEA), the French air accident investigation bureau, in conjunction with the airline and the aircraft manufacturer.[2]

Flight recorders

The 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.[2]

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.[2]

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

Aircraft and engines

The investigators found the aircraft to have been airworthy, that its weight and center-of-gravity had been within limits, and that there was no evidence of mechanical or electronic systems failure.[2]

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 TOGA 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.[2]

Official report

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

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.[3][4]

Prosecutions

Captain Asseline, First Officer Mazière, two Air France officials and the president of the flying club sponsoring the air show were all charged with involuntary manslaughter. All five were found guilty. Asseline was initially sentenced to six months in prison along with 12 months of probation. The others were sentenced to probation. During the appeal process, Asseline's sentence was increased to 10 months of imprisonment along with 10 months of probation. Asseline walked free from the court and said he would appeal to France's Supreme Court, the 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 Supreme Court.

Alternative explanation

The TV documentary series Mayday also reports claims in Season 9 Episode 3 that the 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. The pilot 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. The pilot claims that this indicated a problem with the aeroplane's fly-by-wire system rather than pilot error. After some seconds he got worried and thought there was something like a short-circuit in the completely computerized throttle control. So he pulled the throttle back all the way and forth again. By that time the aircraft had touched the trees.[5]

It is also claimed that the flight data recorders have been switched and were not the original ones in the aeroplane.[5][6] Airbus made a detailed rebuttal of these claims in a document published in 1991.[7] Airbus contends 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.

Dramatization

On 8 March 2010, Season 9 Episode 3 of the Mayday (Air Crash Investigation, Air Emergency,'Air Disasters) TV series featuring this accident was broadcast. The episode is entitled "Pilot vs. Plane". The episode "Blaming the Pilot" of Survival in the Sky featured the accident.

See also

Notes

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

Footnotes

  1. 1 2 "Commission D'Enquête" (PDF). 24 April 1990. Archived from the original (PDF) on 2 January 2014.(French)
  2. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 Job, Macarthur (1998). Air Disaster Volume 3. Australia: Aerospace Publications. p. 155. ISBN 1 875671 34 X.
  3. ↑ Accident description at the Aviation Safety Network. Retrieved on 3 February 2007.
  4. ↑ 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 (PDF). 1990. (Archive)
  5. 1 2 "AirDisaster.Com: Investigations: Air France 296". airdisaster.com.
  6. ↑ Roger, Christian (26 June 1998). "The Airbus A320 crash at Habsheim, France 26 June 1988" (PDF). crashdehabsheim.net.
  7. ↑ "The A320 Habsheim accident" (PDF). March 1991.

External links

This article is issued from Wikipedia - version of the 11/23/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.