F-GZCP, the aircraft involved in the accident |
|
Accident summary | |
---|---|
Date | 1 June 2009 |
Type | Under investigation |
Site | Near waypoint TASIL, Atlantic Ocean[1] |
Passengers | 216 [2] |
Crew | 12 [2] |
Fatalities | 228 [1] (all) |
Survivors | 0 |
Aircraft type | Airbus A330-203 |
Operator | Air France |
Tail number | F-GZCP [2] |
Flight origin | Rio de Janeiro-Galeão International Airport |
Destination | Paris-Charles de Gaulle Airport |
Air France Flight 447 was a scheduled commercial flight from Rio de Janeiro-Galeão (GIG) to Paris-Roissy (CDG) involving an Airbus A330-200 aircraft that crashed into the Atlantic Ocean on 1 June 2009, killing all 216 passengers and 12 aircrew. The accident was the deadliest in the history of Air France,[3][4] and has also been described as the worst accident in French aviation history.[5] It was the deadliest commercial airliner accident to occur since the crash of American Airlines Flight 587 in New York City in 2001.[6] It was the first fatal accident to an Airbus A330 airliner while in passenger service.
While the investigation is still awaiting formal conclusion, preliminary reports of the BEA stated that the aircraft crashed following an aerodynamic stall caused by inconsistent airspeed sensor readings, the disengagement of the autopilot, and the pilot pulling the nose of the plane back despite stall warnings, causing a fatal loss of airspeed and a sharp descent. Additionally, reports indicated that the pilots had not received specific training in "manual airplane handling of approach to stall and stall recovery at high altitude", and that this was not a standard training requirement at the time of the accident.[7][8]
The reason for the faulty readings is unknown, but it is assumed by the accident investigators to have been caused by the formation of ice inside the pitot tubes, depriving the airspeed sensors of forward-facing air pressure.[9][10][11] Pitot tube blockage is suspected of having contributed to airliner crashes in the past — such as Birgenair Flight 301 in 1996.[12]
The investigation into the accident was initially hampered by the lack of eyewitness evidence and radar tracks, as well as by difficulty finding the aircraft's black boxes, which were located and recovered from the ocean floor two years following the incident in May 2011.[1][13]
Contents |
The aircraft involved in the accident was an Airbus A330-203, with manufacturer serial number 660, registered as "F-GZCP". This airliner first flew on 25 February 2005.[14][15] The aircraft was powered by two General Electric CF6-80E1 engines with a maximum thrust of 72,000 lb giving it a cruise speed range of Mach 0.82–0.86 (871–913 km/h, 470−493 KTAS, 540 – 566 mph), at 35,000 ft (10.7 km altitude) and a range of 12,500 km (6750 nmi).[14] The aircraft underwent a major overhaul on 16 April 2009,[16] and at the time of the accident had accumulated 18,870 flying hours.[14] On 17 August 2006, the A330 was involved in a ground collision with Airbus A321-211 F-GTAM, at Charles de Gaulle Airport, Paris. F-GTAM was substantially damaged while F-GZCP suffered only minor damage.[17] The plane made 24 flights from Paris, to and from 13 different destinations worldwide, between 5 May and 31 May 2009.[16]
The aircraft departed from Rio de Janeiro-Galeão International Airport on 31 May 2009 at 19:03 local time (22:03 UTC), with a scheduled arrival at Paris-Charles de Gaulle Airport approximately 11 hours later.[1] The last verbal contact with the aircraft was at 01:33 UTC, when it was near waypoint INTOL (), located 565 km (351 mi) off Natal, on Brazil's north-eastern coast. The crew reported that they expected to use airway UN873 and enter Senegalese-controlled airspace at waypoint TASIL () within 50 minutes, and that the aircraft was flying normally at flight level 350 (a nominal altitude of 35,000 ft/11,000 m) and at a speed of 467 knots (865 km/h; 537 mph).[1] The aircraft left Brazil Atlantic radar surveillance at 01:48 UTC.
An Air France spokesperson stated on 3 June that “the aircraft sent a series of electronic messages over a three-minute period, which represented about a minute of information. Exactly what that data means hasn't been sorted out, yet.”[18][19][Note 1] These messages, sent from an onboard monitoring system via the Aircraft Communication Addressing and Reporting System (ACARS), were made public on 4 June 2009.[20] The transcripts indicate that between 02:10 UTC and 02:14 UTC, 6 failure reports (FLR) and 19 warnings (WRN) were transmitted.[21] The messages resulted from equipment failure data, captured by a built-in system for testing and reporting, and cockpit warnings also posted to ACARS.[22] The failures and warnings in the 4 minutes of transmission concerned navigation, auto-flight, flight controls and cabin air-conditioning (codes beginning with 34, 22, 27 and 21, respectively).[23]
Among the ACARS transmissions in the first minute is one message that indicates a fault in the pitot-static system (code 34111506).[20][23] Bruno Sinatti, president of Alter, Air France’s third-biggest pilots’ union, stated that “the first automated system-failure message in a string of radio alerts from the incident aircraft explicitly indicated that the airspeed sensors were faulty”.[24] The twelve warning messages with the same time code indicate that the autopilot and auto-thrust system had disengaged, that the TCAS was in fault mode, and flight mode went from 'normal law' to 'alternate law'.[25][26] The 02:10 transmission contained a set of coordinates which indicated that the aircraft was at .[Note 2]
The remainder of the messages occurred from 02:11 UTC to 02:14 UTC, containing a fault message for an Air Data Inertial Reference Unit (ADIRU) and the Integrated Standby Instrument System (ISIS).[26][27] At 02:12 UTC, a warning message NAV ADR DISAGREE indicated that there was a disagreement between the three independent air data systems.[Note 3] At 02:13 UTC, a fault message for the flight management guidance and envelope computer was sent.[28] One of the two final messages transmitted at 02:14 UTC was a warning referring to the air data reference system, the other ADVISORY (Code 213100206) was a "cabin vertical speed warning", indicating that the plane was descending at a high rate.[29][30][31]
A meteorological analysis of the area surrounding the flight path showed a mesoscale convective system extending to an altitude of around 50,000 feet (15 km; 9.5 mi) above the Atlantic Ocean before Flight 447 disappeared.[32] From satellite images taken near the time of the incident, it appeared that the aircraft encountered a thunderstorm, likely containing significant turbulence.[33]
Detailed analysis of the weather conditions for the flight shows it is possible that the aircraft's final 12 minutes could have been spent "flying through significant turbulence and thunderstorm activity for about 75 mi (121 km)", and may have been subjected to rime icing, and possibly clear ice or graupel.[32] Satellite imagery loops from the CIMSS clarify that the flight was coping with a series of storms, not just one.[34]
Commercial air transport crews routinely encounter this type of storm in this area. Generally, when storms of this type are encountered at night, pilots use onboard radar to navigate around them.[35]
In this instance, shortly after the last verbal contact was made with Air Traffic Control about 350 mi (560 km) north-east of Natal (station identifier SBNT), the aircraft likely traversed an area of intense deep convection which had formed within a broad band of thunderstorms along the Intertropical Convergence Zone (ITCZ).[36] Turbulence in the vicinity of these rapidly developing storms may have contributed to the accident.[32][34][37][38] According to news sources, 12 other flights shared more or less the same route that Flight 447 was using at the time of the accident.[39][40]
Wil S. Hylton of The New York Times said that the crash "was easy to bend into myth" because "no other passenger jet in modern history had disappeared so completely — without a Mayday call or a witness or even a trace on radar." Hylton explained that the A330 "was considered to be among the safest" of the passenger aircraft. Hylton added that when the aircraft disappeared, "Flight 447 seemed to disappear from the sky, it was tempting to deliver a tidy narrative about the hubris of building a self-flying airplane, Icarus falling from the sky. Or maybe Flight 447 was the Titanic, an uncrashable ship at the bottom of the sea."[41] Dr. Guy Gratton, an aviation expert from the Flight Safety Laboratory at Brunel University, said "This is an air accident the like of which we haven't seen before. Half the accident investigators in the Western world – and in Russia too – are waiting for these results. This has been the biggest investigation since Lockerbie. Put bluntly, big passenger planes do not just fall out of the sky."[42] Many people in Germany closely followed the Flight 447 case because 26 German passengers were on board the aircraft.[43]
On 1 June at 02:20 UTC, Brazilian air traffic controllers contacted air traffic control in Dakar after noticing that the plane had not made the required radio call signaling its crossing into Senegalese airspace.[44] The Brazilian Air Force then began a search and rescue operation from the Brazilian archipelago of Fernando de Noronha,[44] and at 19:00 UTC on 1 June, Spain sent a CASA 235 maritime patrol plane in search and rescue operations near Cape Verde.[45] French reconnaissance planes were also dispatched, including one Breguet Atlantic from Dakar,[46] and the French requested satellite equipment from the United States to help find the plane.[47] Brazilian Air Force spokesperson Colonel Henry Munhoz told Brazilian TV that radar on Cape Verde failed to pick up the aircraft over the Atlantic Ocean.[44]
Later on 1 June, officials with Air France and the French government had already presumed that the plane had been lost with no survivors. An Air France spokesperson told L'Express that there was "no hope for survivors,"[48][49][50] and French President Nicolas Sarkozy told relatives of the passengers that there was only a minimal chance that anyone survived.[47]
Also late on 1 June, the deputy chief of the Brazilian Aeronautical Communications Center, Jorge Amaral, confirmed that 30 minutes after the Air France Airbus had transmitted the automatic report, a commercial pilot had reported the sighting of "orange dots" in the middle of the Atlantic, which could indicate the glow of wreckage on fire.[51][52] This sighting was reported by a TAM Airlines crew flying from Europe to Brazil, at approximately 1,300 km (810 mi) from Fernando de Noronha.[51][52] Another similar sighting of "something flashing brightly over the ocean then taking a descending vertical trajectory" was reported by the Spanish pilot of Air Comet Flight 974[53] flying from Lima to Madrid. The Brazilian newspaper O Globo reported that wreckage debris was discovered off the Senegalese coast, but that its origin was still uncertain.[54] EarthTimes and news.com.au reported that the crew of the French freighter Douce France spotted debris floating on the ocean in the area earlier indicated by the TAM crew.[55][56]
On 2 June at 15:20 (UTC), the Brazilian Air Force, using an Embraer R-99A fitted with Erieye radar, found wreckage and signs of oil, possibly jet fuel, strewn along a 5 km (3 mi) band 650 km (400 mi) north-east of Fernando de Noronha Island, near the Saint Peter and Saint Paul Archipelago. Spotted wreckage included a plane seat, an orange buoy, a barrel, and "white pieces and electrical conductors".[57] Later that day, after meeting with relatives of the Brazilians on the aircraft, Brazilian Defence Minister Nelson Jobim announced that the Air Force believed the wreckage was from Flight 447.[58][59] Brazilian vice-president José Alencar (acting as president since Luiz Inácio Lula da Silva was out of the country) declared three days of official mourning.[60][61]
Also on 2 June, two French Navy vessels, Foudre and Ventôse, were en route to the suspected crash site. Other ships sent to the site included the French research vessel Pourquoi Pas?, equipped with two mini-submarines able to descend to 6,000 m (20,000 ft),[62] since the area of the Atlantic in which the plane went down may be as deep as 4,700 m (15,400 ft).[63] A US Navy Lockheed Martin P-3 Orion anti-submarine warfare and maritime patrol aircraft was deployed in the search.[64]
On 3 June, the first Brazilian Navy ship, the patrol boat Grajaú, reached the area in which the first debris was spotted. The Brazilian Navy sent a total of five ships to the debris site; the frigate Constituição and the corvette Caboclo were scheduled to reach the area on 4 June, the frigate Bosísio on 6 June and the replenishment oiler Almirante Gastão Motta on 7 June.[65][66]
On 5 June, French defence minister Hervé Morin announced that the nuclear submarine Émeraude was being sent to the area, to assist in the search for the missing flight recorders or "black-boxes" which might be located at great depth.[67] The submarine would use its sonar to listen for the ultrasonic signal emitted by the black boxes' "pingers".[68] On 10 June, the Émeraude reached the crash zone of Air France Flight 447 with plans to troll 13 sq mi (34 km2) a day, listening for the pingers. The Émeraude was to work with the mini-sub Nautile, which can descend to the ocean floor. The French submarines would be aided by two U.S. underwater audio devices, capable of picking up signals at a depth of 20,000 ft (6,100 m).[69]
On 4 June, the Brazilian Air Force claimed they had recovered the first debris from the Air France crash site, 340 miles (550 km) northeast of the Fernando de Noronha archipelago,[70] but on 5 June, around 13:00 UTC, Brazilian officials announced that they had not yet recovered anything from Flight 447, as the oil slick and debris field found on 2 June could not have come from the plane.[71] Ramon Borges Cardoso, director of the Air Space Control Department, said that the fuel slicks were not caused by aviation fuel but were believed to have been from a passing ship.[72] Even so, a Brazilian Air Force official maintained that some of the material that had been spotted (but not picked up) was in fact from Flight 447. Poor visibility had prevented search teams from re-locating the material.[73]
On 6 June, five days after Flight 447 disappeared, it was reported that the Brazilian Air Force had located "bodies and debris" from the missing aircraft, after they had been spotted by a special search radar-equipped aircraft near the Saint Peter and Saint Paul Archipelago.[74] The bodies and objects were reportedly found at 08:14 Brazilian time (11:14 UTC), and experts on human remains were sent to investigate. Brazilian Air Force Colonel Jorge Amaral stated that "We confirm the recovery from the water of debris and bodies from the Air France plane. Air France boarding passes for Flight 447 were also found. We can't give more information without confirming what we have."[75] Two male bodies were later found along with a seat, a nylon backpack containing a computer and vaccination card and a leather briefcase containing a boarding pass for the Air France flight.[76][77][78]
Authorities also corrected the misunderstanding about the earlier debris findings: except for the wooden pallet, the debris did come from Flight 447, but rescue aircraft and ships had made the search for possible survivors and bodies a priority, delaying the verification of the origins of the other recovered debris.[79]
On 7 June, search crews recovered the Airbus's vertical stabilizer, the first major piece of wreckage to be discovered.[1][80]
By 17 June 2009, a total of 50 bodies had been recovered in two distinct groups more than 50 miles (80 km) apart,[81][82] and more than 400 pieces of debris from the plane had been recovered.[83] 49 of the 50 bodies had been transported to shore, first by the frigates Constituição and Bosísio to the islands of Fernando de Noronha and thereafter by plane to Recife for identification.[82][84][85][86][87] As of 23 June 2009, officials had identified 11 of the 50 bodies recovered from the crash site off the coast of Brazil, by using dental records and fingerprints. Of those identified, ten were Brazilian, although no names had been released.[88] On 25 June, Le Figaro reported that the bodies of the pilot, Marc Dubois, and a flight attendant had been retrieved and identified.[89] On 26 June, the Brazilian Military announced it had ended the search for bodies and debris, having recovered 51 bodies with the help of French vessels and French, Spanish and U.S. aircraft.
Following the end of the search for bodies, the search for the flight data recorder and the cockpit voice recorder, the "black boxes", continued with the French nuclear submarine and with two French-contracted ships (towing the U.S. Navy listening devices) trawling a search area with a radius of 80 kilometres (50 mi).[90] By mid July, recovery of the black boxes had still not been announced. French search teams denied an earlier report that a "very weak" signal had been picked up from the black box locator beacon.[91] The finite beacon battery life meant that, as the time since the crash elapsed, the likelihood of location diminished. In late July, the search for the black boxes entered its second phase, with a French research vessel resuming the search using a towed sonar array.[92] In July 2009, Airbus announced that they would fund an extended search for the aircraft's black boxes. This announcement came amidst their official backing to determine the root cause of the accident.[93] The second phase of the search ended on 20 August without finding wreckage within a 75 km radius of the last position, as reported at 02:10.[94]
On 13 December 2009, the BEA announced that a search for the recorders for three months more would be conducted using "robot submarines" beginning in February 2010.[95]
The BEA announced that they expected the search to resume in mid-March, depending on the weather. The third phase of the search was planned to take four weeks. Air France, Airbus, the US Navy, and the National Transportation Safety Board were to aid in the search.[96] The new search plan covered an area of 770 square miles (2,000 km2) and was to utilize four sonar devices and two underwater robots.[97] Oceanographers from France, Russia, Britain, and the United States each separately analysed the search area, to select a smaller area for closer survey.[98][99]
The search continued in the beginning of April 2010 and was planned to last for 30 days.[100][101][102] In May 2010 the French newspaper Le Figaro suggested that the plane had been heading back to Brazil when it had crashed.[103]
On 6 May 2010, the French Minister of Defense reported[104] that the cockpit voice recorders had been localized to a zone 5 km by 5 km, following analysis of the data recorded by the French submarine during the initial search conducted in mid-2009. On 12 May 2010, it was reported[105] that the search following the 6 May report of the possible location of the voice recorders had not led to any findings and that the search had resumed in a different area from the one identified by the French submarine. The third phase of the search ended on 24 May 2010 without any success, though the French Bureau d'Enquetes et d'Analyses (BEA) says that the search 'nearly' covered the whole area drawn up by investigators.
In November 2010, French officials announced that a fourth search would start in February 2011, using the most sophisticated technology available.[106]
On 3 April 2011, during Phase 4 of the search and recovery operation, a team led by the Woods Hole Oceanographic Institution operating full ocean depth autonomous underwater vehicles (AUVs) owned by the Waitt Institute discovered, by means of sidescan sonar, a large portion of debris field believed to be that of flight AF447. Further debris and bodies, still trapped in the partly intact remains of the aircraft's fuselage, were located in water depths of between 3,800 to 4,000 metres (2,100 to 2,200 fathoms; 12,000 to 13,000 ft). The debris was found to be lying in a relatively flat and silty area of the ocean floor (as opposed to the extremely mountainous topography that was originally believed to be AF447's final resting place). Other items found were engines, wing parts and the landing gear.[107]
The debris field was described as "quite compact", measuring some 200 by 600 metres (660 by 2,000 ft) and located a short distance to the north of where pieces of wreckage had been recovered previously, suggesting that the aircraft hit the water largely intact.[108] The French Ecology and Transportation Minister Nathalie Kosciusko-Morizet stated the bodies and wreckage would be brought to the surface and taken to France for examination and identification. It was not yet possible to determine how many bodies had been discovered.[109] The French government chartered three vessels – the René Descartes, the Île de Sein[110] and an American-based vessel, which are normally used by telecommunications companies for deep-ocean cable-laying and the Alucia, a deepwater expedition research vessel,[111][112] to retrieve debris and bodies. An American Remora 6000 remotely operated vehicle (ROV) and operations crew experienced in the recovery of aircraft for the United States Navy were on board the Île de Sein.[110][113][114]
The BEA announced that on 26 April, after a 12-hour dive by the Remora 6000, the flight data recorder chassis had been found, although without the crash-survivable memory unit,[115] which is the actual data storage medium.[116] On 1 May the memory unit was found and lifted on board the Île de Sein by the ROV.[117] According to the BEA's director Jean-Paul Troadec, the photos of the memory module showed that it had suffered little exterior corrosion, but it was not possible to say whether the memory chip remained readable. The plane's cockpit voice recorder was found at 2150 UTC (GMT) on 2 May 2011, and was raised and brought on board the Île de Sein the following day.[118]
On 7 May the flight recorders, under judicial seal, were taken aboard the French Navy patrol boat La Capricieuse for transfer to the port of Cayenne. From there they were transported by air to the BEA's office in Le Bourget near Paris for data download and analysis. One engine and the avionics bay, containing onboard computers, had also been raised.[119] On 5 May 2011, efforts to recover the bodies of passengers from the sea bed began. 51 bodies had been previously recovered from the sea.[41][120][121]
The BEA confirmed on 16 May that all the data from both the flight data recorder and the cockpit voice recorder had been successfully downloaded.[122] The data would be subjected to detailed in-depth analysis taking several weeks, after which another interim report would be released during the summer.[123] The download was completed in the presence of two Brazilian investigators of the Aeronautical Accidents Investigation and Prevention Center (CENIPA), two British investigators of the Air Accidents Investigation Branch (AAIB), two German investigators of the German Federal Bureau of Aircraft Accidents Investigation (BFU), one American investigator of the National Transportation Safety Board (NTSB), an officer of the French judicial police, and a court expert. The entire download was filmed and recorded.[123]
On 3 June, the last 27 bodies from the wreckage were recovered. With this, the number of bodies recovered from the wreckage reached 104 and the total number of recovered bodies was 154. The remaining 74 bodies from the flight have not been found.[124]
Investigators have not yet determined a cause of the accident, but preliminary investigation found that the crash could have been caused by erroneous airspeed indications, if the pitot tubes had iced over during the flight.[125] Although the full sequence of events is not yet clear, based on the timing of the events and the shape and distribution of debris, it appeared that the aircraft rapidly lost altitude (possibly going into a stall) and hit the ocean surface with its underside at a vertical speed of 150 km/h (90 mph) 4 minutes later, breaking up on impact.[126]
The French authorities opened two investigations:
A large quantity of more or less accurate information and attempts at explanations concerning the accident are currently being circulated. The BEA reminds those concerned that in such circumstances, it is advisable to avoid all hasty interpretations and speculation on the basis of partial or non-validated information. At this stage of the investigation, the only established facts are:
- the presence near the airplane’s planned route over the Atlantic of significant convective cells typical of the equatorial regions;
- based on the analysis of the automatic messages broadcast by the plane, there are inconsistencies between the various speeds measured.
By June 2009 the main task occupying the investigators was the recovery of aircraft parts, primarily the flight recorders. BEA chief Paul-Louis Arslanian said that he was not optimistic about finding them since they might be under as much as 3,000 m (9,800 ft) of water and the terrain under this portion of the ocean was very rugged.[134] Investigators were hoping to find the aircraft's lower aft section, since that was where the recorders were located.[135] Although France had never recovered a flight recorder from such depths,[134] there was precedent for such an operation: in 1988, an independent contractor was able to recover the cockpit voice recorder of South African Airways Flight 295 from a depth of 4,900 m (16,100 ft) in a search area of between 80 and 250 square nautical miles (270 and 860 km2).[136][137] The Air France flight recorders were fitted with water-activated acoustic underwater locator beacons or "pingers", which should have remained active for at least 30 days, giving searchers that much time to locate the origin of the signals.[138]
On 2 July 2009, the BEA released an intermediate report, which described all known facts, and a summary of the visual examination of the rudder and the other parts of the aircraft that had been recovered at that time.[1] According to the BEA, this examination showed that:
On 16 May 2011, Le Figaro reported that the BEA investigators had ruled out an aircraft malfunction as the cause of the crash, according to preliminary information extracted from the Flight Data Recorder.[141] The following day, the BEA issued a press release explicitly describing the Le Figaro report as a "sensationalist publication of non-validated information". They stated that no conclusions had yet been made, that investigations were continuing, and that no interim report was expected before the summer.[142] On 18 May the head of the investigation clarified this contradictory information, stating that no major malfunction of the aircraft had been found so far in the data from the flight data recorder, but that minor malfunctions had not yet been ruled out.[143]
On 27 May 2011, the BEA released a short factual report of the findings from the data recorders without any conclusions. A first analysis of the data was to be expected for the end of July.[11][144]
In the minutes before its disappearance, the aircraft's onboard systems had sent a number of messages, via ACARS, indicating disagreement in the indicated airspeed (IAS) readings. A spokesperson for the BEA claimed that "the air speed of the aircraft was unclear" to the pilots[67] and, on 4 June, Airbus issued an Accident Information Telex to operators of all its aircraft reminding pilots of the recommended Abnormal and Emergency Procedures to be taken in the case of unreliable airspeed indication.[145] French Transport Minister Dominique Bussreau said "Obviously the pilots [of Flight 447] did not have the [correct] speed showing, which can lead to two bad consequences for the life of the aircraft: under-speed, which can lead to a stall, and over-speed, which can lead to the aircraft breaking up because it is approaching the speed of sound and the structure of the plane is not made for resisting such speeds".[78]
Paul-Louis Arslanian, of France's air accident investigation agency, confirmed that there had been previous problems affecting the speed readings on other A330 aircraft stating, "We have seen a certain number of these types of faults on the A330 ... There is a programme of replacement, of improvement".[146] The problems primarily occurred on the Airbus A320, but, awaiting a recommendation from Airbus, Air France delayed installing new pitots on A330/A340, yet increased inspection frequencies.[147]
On 6 June 2009, Arslanian said that Air France had not replaced pitot probes as Airbus recommended on F-GZCP, saying that "it does not mean that without replacing the probes that the A330 was dangerous."[147] Air France issued a further clarification of the situation:
Malfunctions in the pitot probes on the A320 led the manufacturer to issue a recommendation in September 2007 to change the probes. This recommendation also applies to long-haul aircraft using the same probes and on which a very few incidents of a similar nature had occurred.
The recommendation from Airbus was that the Thales model AA pitot tubes which had been installed on the Air France fleet during manufacture should be replaced by Thales model BA pitot tubes, to address the problem of water ingress which had been observed. Since it was not an Airworthiness Directive (AD), the guidelines allow the operator to apply the recommendations at its discretion. Air France implemented the change on its A320 fleet where the incidents of water ingress were observed, and decided to do so in its A330/340 fleet only when failures occurred.[149]
Starting in May 2008 Air France experienced incidents involving a loss of airspeed data in flight (...) in cruise phase on A340s and A330s. These incidents were analysed with Airbus as resulting from pitot probe icing for a few minutes, after which the phenomenon disappeared.
After discussing these issues with the manufacturer, Air France sought a means of reducing these incidents, and Airbus indicated that the new pitot probe designed for the A320 was not designed to prevent cruise level ice-over. In 2009, tests suggested that the new probe could improve its reliability, prompting Air France to accelerate the replacement program,[150] but this work had not been carried out on F-GZCP.[16] By 17 June 2009, Air France had replaced all pitot probes on its A330 type aircraft.[149]
On 11 June 2009, a spokesman from the BEA reminded that there was no conclusive evidence at the moment linking pitot probe malfunction to the AF447 crash, and this was reiterated on 17 June 2009 by the BEA chief, Paul-Louis Arslanian.[83][151][152][153]
In July 2009, Airbus issued new advice to A330 and A340 operators to exchange Thales pitot tubes for tubes from Goodrich Sensors and Integrated Systems.[154][155][156]
On 12 August 2009, Airbus issued three Mandatory Service Bulletins, requiring that all A330 and A340 aircraft be fitted with two pitot tubes manufactured by Goodrich Sensors and one Thales model BA pitot (or alternatively three of the Goodrich pitots); Thales model AA pitot tubes were no longer to be used.[157] This requirement was incorporated into Airworthiness Directives issued by the European Aviation Safety Agency (EASA) on 31 August[157] and by the Federal Aviation Administration (FAA) on 3 September.[158] The replacement was to be completed by January 7, 2010. According to the FAA, in its Federal Register publication, use of the Thales model has resulted in "reports of airspeed indication discrepancies while flying at high altitudes in inclement weather conditions", that "could result in reduced control of the airplane." The FAA further stated that the Thales model probe "has not yet demonstrated the same level of robustness to withstand high-altitude ice crystals as Goodrich pitot probes P/N 0851HL,".
On 21 December 2010, Airbus issued a warning to roughly 100 operators of A330, A340-200 and A340-300 aircraft, regarding pitot tubes, advising pilots not to re-engage the autopilot following failure of the airspeed indicators.[159]
On 27 May 2011, the BEA released an update on its investigation[11] describing the history of the flight as recorded by the flight data recorder. At 3 hours 55 minutes absolute time (time from planned departure), the captain woke the second pilot and said: "[...] he's going to take my place". After having attended the briefing between the two co-pilots, the captain left the cockpit to rest at 4 hours 1 minute 46 seconds. At 4 hours 6 minutes absolute time, the pilot warned the cabin crew that they were about to enter an area of turbulence. Four minutes later, the pilots turned the plane slightly to the left and decreased its speed from Mach 0.82 to Mach 0.8 due to increased turbulence.
At 4 hours 10 minutes and 5 seconds absolute time the autopilot disengaged as did the engines' auto-thrust systems 3 seconds later. The pilot made a left nose-up input, as the plane began rolling to the right. The plane's stall warning sounded briefly twice due to the angle of attack tolerance being exceeded by short vertical accelerations due to turbulence. 10 seconds later, the plane's recorded airspeed dropped sharply from 275 knots to 60 knots. The plane's angle of attack increased, and the plane started to climb. The left-side instruments then recorded a sharp rise in airspeed to 215 knots. This change was not displayed by the Integrated Standby Instrument System (ISIS) until a minute later (the right-side instruments are not recorded by the recorder). The pilot continued making nose-up inputs. The trimmable horizontal stabilizer (THS) moved from 3 to 13 degrees nose-up in about 1 minute, and remained in that latter position until the end of the flight.
At around 4 hours 11 minutes into the flight, the plane had climbed to its maximum altitude of around 38,000 feet. There, its angle of attack was 16 degrees, and the thrust levers were in the TO/GA detent (fully forward), and at 4 hours 11 minutes 15 seconds the pitch attitude was slightly over 16 degrees and falling, but the angle of attack rapidly tracked towards 30 degrees. Lift was lost from the wing and the aircraft became stalled.[160] At 4 hours 11 minutes 40 seconds, the captain re-entered the cockpit. The angle of attack had then reached 40 degrees, and the plane had descended to 35,000 feet with the engines running at almost 100% N1 (the rotational speed of the front intake fan, which delivers most of a turbofan engine's thrust). The stall warnings stopped, as all airspeed indications were now considered invalid by the aircraft's computer due to the high angle of attack and/or the airspeed was less than 60 knots. In other words, the plane was oriented nose-up but descending steeply.
Roughly 20 seconds later, the pilot decreased the plane's pitch slightly, air speed indications became valid and the stall warning sounded again and sounded intermittently for the remaining duration of the flight, but stopped when the pilot increased the plane's nose-up pitch. From there until the end of the flight, the angle of attack never dropped below 35 degrees. During the last minutes, the thrust levers were in the "idle" detent position. The engines were always working, and responsive to commands.
The recordings stopped at 4 hours 14 minutes and 28 seconds absolute time (02:14:28 UTC), or 3 hours 45 minutes after takeoff. At that point, the plane's ground speed was 107 knots, and it was descending at 10,912 feet per minute, with the engines' N1's at 55%. Its pitch was 16.2 degrees (nose up), with a roll angle of 5.3 degrees left. During its descent, the plane had turned more than 180 degrees to the right to a compass heading of 270 degrees. The plane was stalled during its entire 3 minute 30 second descent from 38,000 feet.[11]
While the incorrect airspeed data was the apparent cause of the disengagement of the autopilot, the reason the pilots lost control of the aircraft remains something of a mystery, in particular because pilots would normally try to lower the nose in case of a stall.[161][162][163] Multiple sensors provide the pitch (attitude) information and there was no indication that any of them were malfunctioning.[164] One factor may be that since the A330 does not normally accept control inputs that would cause a stall, the pilots were unaware that a stall could happen when the aircraft switched to an alternate mode due to failure of the air speed indication.[165] Some reports have described this as a deep stall,[166] but this was a steady state conventional stall.[167] A deep stall is associated with an aircraft with a T-tail, but this aircraft does not have a T-tail.[168]
In October 2011, a transcript of the voice recorder was leaked and published in the book Erreurs de Pilotage (Pilot Error) by Jean Pierre Otelli,[165][169] According to the book, one of the co-pilots caused the accident by incorrectly pulling back on his stick when the aircraft went into a stall.[165] The BEA and Air France both condemned the release of this information however, calling it "sensationalized and unverifiable information" that "impairs the memory of the crew and passengers who lost their lives."[170]
Leaked transcript of cockpit voice recorder[165] | |||
---|---|---|---|
Time | Speaker | French | English translation |
02:02:00 | The captain leaves the flight deck to take a nap, leaving the considerably lesser experienced of the two co-pilots in command. | ||
02:03:44 | Bonin | La convergence inter tropicale… voilà, là on est dedans, entre 'Salpu' et 'Tasil.' Et puis, voilà, on est en plein dedans… | The inter-tropical convergence... look, we're in it, between 'Salpu' and 'Tasil'.[Note 6] And then, look, we're right in it... |
02:05:55 | Robert | Oui, on va les appeler derrière... pour leur dire quand même parce que... | Yes, let's call them in the back, to let them know... |
02:05:59 | Flight attendant | Oui? Marilyn. | Yes? Marilyn. |
02:06:04 | Bonin | Oui, Marilyn, c'est Pierre devant... Dis-moi, dans deux minutes, on devrait attaquer une zone où ça devrait bouger un peu plus que maintenant. Il faudrait vous méfier là. | Yes, Marilyn, it's Pierre up front... Listen, in 2 minutes, we're going to be getting into an area where things are going to be moving around a little bit more than now. You'll want to take care. |
02:06:13 | Flight attendant | D'accord, on s'assoit alors? | Okay, we should sit down then? |
02:06:15 | Bonin | Bon, je pense que ce serait pas mal… tu préviens les copains! | Well, I think that's not a bad idea. Give your friends a heads-up. |
02:06:18 | Flight attendant | Ouais, OK, j'appelle les autres derrière. Merci beaucoup. | Yeah, okay, I'll tell the others in the back. Thanks a lot. |
02:06:19 | Bonin | Mais je te rappelle dès qu'on est sorti de là. | I'll call you back as soon as we're out of it. |
02:06:20 | Flight attendant | OK | OK |
02:06:50 | Bonin | Va pour les anti-ice. C'est toujours ça de pris. | Let's go for the anti-icing system. It's better than nothing. |
02:07:00 | Bonin | On est apparemment à la limite de la couche, ça devrait aller. | We seem to be at the end of the cloud layer, it might be okay. |
02:08:03 | Robert | Tu peux éventuellement le tirer un peu à gauche. | You can possibly pull it a little to the left. |
02:08:05 | Bonin | Excuse-moi? | Sorry, what? |
02:08:07 | Robert | Tu peux éventuellement prendre un peu à gauche. On est d'accord qu'on est en manuel, hein? | You can possibly pull it a little to the left. We're agreed that we're in manual, yeah? |
A gong sounds indicating that the autopilot has disconnected (because the pitot tubes have iced over). | |||
02:10:06 | Bonin | J'ai les commandes. | I have the controls. |
02:10:07 | Robert | D'accord. | Okay. |
Bonin takes the aircraft into a steep climb; A chime alerts the crew that they are leaving their designated altitude. This is followed by a stall warning and a loud warning sound called a "cricket". | |||
02:10:07 | Robert | Qu'est-ce que c'est que ça? | What's this? |
02:10:15 | Bonin | On n'a pas une bonne… On n'a pas une bonne annonce de vitesse. | There's no good... there's no good speed indication. |
02:10:16 | Robert | On a perdu les, les, les vitesses alors? | We've lost the, the, the speeds, then? |
The aircraft is climbing at 7,000 ft per minute, slowing all the time until its speed is only 93 knots (172 km/h) | |||
02:10:27 | Robert | Faites attention à ta vitesse. Faites attention à ta vitesse. | Pay attention to your speed. Pay attention to your speed. |
02:10:28 | Bonin | OK, OK, je redescends. | Okay, okay, I'm descending. |
02:10:30 | Robert | Tu stabilises... | Stabilize… |
02:10:31 | Bonin | Ouais. | Yeah. |
02:10:31 | Robert | Tu redescends... On est en train de monter selon lui… Selon lui, tu montes, donc tu redescends. | Descend... It says we're going up... It says we're going up, so descend. |
02:10:35 | Bonin | D'accord. | Okay. |
As the de-icing system takes effect, one of the pitot tubes starts working again, and the cockpit displays again show correct speed information | |||
02:10:36 | Robert | Redescends! | Descend! |
02:10:37 | Bonin | C'est parti, on redescend. | Here we go, we're descending. |
02:10:38 | Robert | Doucement! | Gently! |
Bonin decreases his backward pressure on the stick, and stall warnings stop as the airspeed increases | |||
02:10:41 | Bonin | On est en… ouais, on est en "climb." | We're... yeah, we're in a climb. |
Bonin does not push the nose down. Robert presses a button to call the captain. | |||
02:10:49 | Robert | Putain, il est où... euh? | Damn it, where is he? |
02:10:55 | Robert | Putain! | Damn it! |
The other pitot tube starts working again; all aircraft systems are once again functional, and the pilots simply have to push the nose down to recover the aircraft from its stall. | |||
02:11:03 | Bonin | Je suis en TOGA, hein? | I'm in TOGA, huh? |
Benin is attempting to increase speed and climb as if taking off or aborting a landing, but he is at 37,500 ft where this maneuver is inappropriate. | |||
02:11:06 | Robert | Putain, il vient ou il vient pas? | Damn it, is he coming or not? |
The aircraft reaches its maximum altitude; with the nose up at 18 degrees, it begins to descend. | |||
02:11:21 | Robert | On a pourtant les moteurs! Qu'est-ce qui se passe bordel? Je ne comprends pas ce que se passe. | We still have the engines! What the hell is happening? I don't understand what's happening. |
Crew resource management fails as Robert is unaware that Bonin is still pulling back hard on his stick as the two pilots' controls are not physically linked so that they move together. Buffeting as the aircraft is falling makes it difficult to keep the wings level. | |||
02:11:32 | Bonin | Putain, j'ai plus le contrôle de l'avion, là! J'ai plus le contrôle de l'avion! | Damn it, I don't have control of the plane, I don't have control of the plane at all! |
02:11:37 | Robert | Commandes à gauche! | Left seat taking control! |
The more senior co-pilot briefly takes control, but is unaware that the aircraft has stalled. Bonin retakes control as the captain returns. | |||
02:11:43 | Captain | Eh… Qu'est-ce que vous foutez? | What the hell are you doing? |
02:11:45 | Bonin | On perd le contrôle de l'avion, là! | We've lost control of the plane! |
02:11:47 | Robert | On a totalement perdu le contrôle de l'avion... On comprend rien... On a tout tenté... | We've totally lost control of the plane. We don't understand at all... We've tried everything |
The aircraft is back at the correct altitude, but falling at 10,000 ft per minute with an angle of attack of 41 degrees. The pitot tubes are functional, but as the speed has fallen below 60 knots (110 km/h) and the angle of attack is too great, the data is considered invalid and the stall warnings stop. | |||
02:12:14 | Robert | Qu'est-ce que tu en penses? Qu'est-ce que tu en penses? Qu'est-ce qu'il faut faire? | What do you think? What do you think? What should we do? |
02:12:15 | Captain | Alors, là, je ne sais pas! | Well, I don't know! |
The captain urges Bonin to level the wings, which does not address the primary issue of the stall. The men discuss whether they are climbing or descending, before agreeing that they are indeed descending. As the plane approaches 10,000 feet, Robert tries to take back the controls, and pushes forward on the stick, however in "dual input" mode, the flight system averages his inputs with those of Bonin, who is still pulling back. The nose therefore remains up. | |||
02:13:40 | Robert | Remonte... remonte... remonte... remonte... | Climb... climb... climb... climb... |
02:13:40 | Bonin | Mais je suis à fond à cabrer depuis tout à l'heure! | But I've had the stick back the whole time! |
Bonin communicates for the first time that he has been pulling the stick back all the time. | |||
02:13:42 | Captain | Non, non, non... Ne remonte pas... non, non. | No, no, no... Don't climb... no, no. |
02:13:43 | Robert | Alors descends... Alors, donne-moi les commandes... À moi les commandes! | Descend, then... Give me the controls... Give me the controls! |
Bonin reliquishes control to Robert who for the first time is able to push the nose down to gather speed. A ground proximity warning sounds at 2,000 ft, and Bonin once again starts to pull back on the stick. | |||
02:14:23 | Robert | Putain, on va taper... C'est pas vrai! | Damn it, we're going to crash... This can't be happening! |
02:14:25 | Bonin | Mais qu'est-ce que se passe? | But what's happening? |
02:14:27 | Captain | 10 degrès d'assiette... | Ten degrees of pitch... |
End of recording |
Official analysis from the BEA of the transcript is yet to be published.
On 29 July 2011, the BEA released a third interim report on safety issues it found in the wake of the crash.[7] It was accompanied by two shorter documents summarizing the interim report[171] and addressing safety recommendations.[172]
The third interim report stated that some new facts had been established. In particular:
The BEA assembled a "human factors" working group to analyze the crew's actions and reactions during the final stages of the flight.[173]
A brief bulletin by Air France indicated that "the misleading stopping and starting of the stall warning alarm, contradicting the actual state of the aircraft, greatly contributed to the crew’s difficulty in analyzing the situation."[174][175]
Nationality | Passengers | Crew | Total |
---|---|---|---|
Argentina[176] | 2 | 0 | 2 |
Austria | 1 | 0 | 1 |
Belgium | 1 | 0 | 1 |
Brazil | 58 | 1 | 59 |
Canada | 1 | 0 | 1 |
China | 9 | 0 | 9 |
Croatia | 1 | 0 | 1 |
Denmark | 1 | 0 | 1 |
Estonia | 1 | 0 | 1 |
France | 61 | 11 | 72 |
Gabon | 1 | 0 | 1 |
Germany | 26 | 0 | 26 |
Hungary | 4 | 0 | 4 |
Iceland | 1 | 0 | 1 |
Ireland[177] | 3 | 0 | 3 |
Italy | 9 | 0 | 9 |
Lebanon | 3 | 0 | 3 |
Morocco | 3 | 0 | 3 |
Netherlands[178][179] | 1 | 0 | 1 |
Norway[180] | 3 | 0 | 3 |
Philippines | 1 | 0 | 1 |
Poland | 2 | 0 | 2 |
Romania | 1 | 0 | 1 |
Russia | 1 | 0 | 1 |
Slovakia | 3 | 0 | 3 |
South Africa | 1 | 0 | 1 |
South Korea | 1 | 0 | 1 |
Spain[181] | 1 | 0 | 1 |
Sweden[182] | 3 | 0 | 3 |
Switzerland | 6 | 0 | 6 |
Turkey[183] | 1 | 0 | 1 |
United Kingdom | 5 | 0 | 5 |
United States | 2 | 0 | 2 |
Total (33 nationalities) | 216 | 12 | 228 |
The aircraft was carrying 216 passengers and 12 aircrew in two cabins of service.[2][184][185] Among the 216 passengers were one infant, seven children, 82 women, and 126 men.[44] There were three pilots: 58-year-old flight captain Marc Dubois had joined Air France in 1988 and had approximately 11,000 flight hours, including 1,700 hours on the Airbus A330; the two first officers, 37-year-old David Robert and 32-year-old Pierre-Cedric Bonin, had over 9,000 flight hours between them. Of the 12 crew members, 11 were French and one Brazilian.[186]
According to an official list released by Air France on 1 June 2009,[187] the majority of passengers were French, Brazilian, or German citizens.[188][189] Attributing nationality was complicated by the holding of multiple citizenship by several passengers. The nationalities as released by Air France are shown in the table to the right.
Air France had gathered approximately 60–70 relatives and friends to pick up arriving passengers at Charles de Gaulle Airport. Many of the passengers on Flight 447 were connecting to other destinations worldwide, so other parties anticipating the arrival of passengers were at various connecting airports.[190]
On 20 June, Air France announced that each victim's family would be paid roughly €17,500 in initial compensation.[191] Wrongful death lawsuits maintaining that design and manufacturing defects supplied pilots with incorrect information, rendering them incapable of maintaining altitude and air speed, have been filed in US Courts.[192]
Shortly after the crash, Air France changed the number of the regular Rio de Janeiro-Paris flight from AF447 to AF445.[201]
Some six months later, on 30 November 2009, Air France Flight 445 (F-GZCK) made a mayday call due to severe turbulence around the same area and at a similar time to when Flight 447 had crashed. Because the pilots could not obtain immediate permission from air traffic controllers to descend to a less turbulent altitude, the mayday was to alert other aircraft in the vicinity that the flight had deviated from its normal flight level. This is standard contingency procedure when changing altitude without direct ATC authorization. After 30 minutes of moderate to severe turbulence the flight continued normally. The plane landed safely in Paris six hours and 40 minutes after the mayday call.[202][203]
On 6 September 2011, the French media reported that the BEA was investigating a similar incident on an Air France flight from Caracas to Paris. The aircraft in question was an Airbus A340.[204]
There have been several cases where inaccurate airspeed information led to flight incidents on the A330 and A340. Two of those incidents involved pitot probes.[Note 7] In the first incident, an Air France A340-300 (F-GLZL), en route from Tokyo, Japan, to Paris, France, experienced an event at 31,000 feet (9,400 m) in which the airspeed was incorrectly reported and the autopilot automatically disengaged. Bad weather, together with obstructed drainage holes in all three pitot probes, were subsequently found to be the cause.[205] In the second incident, an Air France A340-300 (F-GLZN), en route from Paris to New York, encountered turbulence followed by the autoflight systems going offline, warnings over the accuracy of the reported airspeed and two minutes of stall alerts.[205] Another incident on TAM Flight 8091, from Miami to Rio de Janeiro on 21 May 2009, involving an A330-200, showed a sudden drop of outside air temperature, then loss of air data, the ADIRS, autopilot and autothrust.[206] The aircraft fell 1,000 metres (3,300 ft) before being manually recovered using backup instruments. The NTSB also examined a similar 23 June 2009 incident on a Northwest Airlines flight from Hong Kong to Tokyo.[206][207]
External images | |
---|---|
Photos of F-GZCP at Airliners.net |
"Airline training guides, Aviation, Operations, Safety -Navigation A330". SmartCockpit. http://www.smartcockpit.com/pdf/plane/airbus/A330/systems/0019/. Retrieved 12 June 2009.
|
|