This is the aircraft involved in Flight 447, photographed during an earlier flight. It shows its external appearance before the accident; the pitot probes and cockpit indications discussed in the investigation cannot be assessed from this view.
Resized and JPEG recompressed; no content changes.
Geographic context
Rio de Janeiro Galeao
Atlantic Ocean, near TASIL
Paris Charles de Gaulle, intended
Schematic geography only. Airport and location markers are approximate; markers do not show a recorded flight track. Basemap: Natural Earth, public domain.Read supporting evidence
During cruise over the Atlantic, measured airspeeds became inconsistent, likely because ice crystals obstructed the Pitot probes. The autopilot disconnected and the flight controls changed to alternate law. Nose-up inputs led to a climb and then a sustained stall. The crew did not diagnose the stall and did not apply the inputs needed to recover. All 228 people on board died.
Read the full incident Follow what happened, from the flight to the investigation findings.
What investigators concluded
The BEA described a succession of technical and operational events, not one isolated cause. Its explanatory factors included gaps in operational feedback and training, weakened task-sharing under surprise, unclear presentation of airspeed inconsistencies, and difficulties recognising and responding to the stall warning. The report qualifies Pitot icing as likely.
1,540 words / about 7 minutes to read. Based on the investigation records cited below.
An overnight crossing of the Atlantic
Air France flight 447 left Rio de Janeiro for Paris on the evening of 31 May 2009. The Airbus A330-203, registered F-GZCP, carried 216 passengers and twelve crew members. Three of those crew members were pilots, allowing the captain to take a rest during the long overnight crossing. The departure and initial climb gave no indication of the accident that would follow. The aircraft settled into cruise at flight level 350, approximately 35,000 feet, with the autopilot and autothrust engaged.
The route crossed the equatorial Atlantic through the intertropical convergence zone, where large convective clouds are common. The crew had received information about a convective area ahead, and discussed weather radar returns, turbulence and the possibility of climbing. Temperature limited the altitude available to them at that stage. The BEA later found that the broad meteorological situation was not exceptional for June, although there were powerful cloud clusters along the route. The investigation did not describe an extraordinary storm overwhelming an otherwise functioning aircraft.
Shortly before 02:00 UTC, the relief copilot joined the cockpit. The two copilots discussed the conditions ahead while the captain attended their handover, then left to rest. One copilot remained the pilot flying in the right seat; the other monitored from the left. The aircraft was still at its assigned cruise altitude. Around 02:08, they turned approximately twelve degrees left, probably to avoid returns on the weather radar, and reduced the selected speed. They also turned on engine anti-icing. These were the last adjustments before the automatic systems disconnected.
At 02:10:05 UTC, the autopilot disconnected, followed by the autothrust. The aircraft began rolling right. The pilot flying took manual control and made left and nose-up inputs. The left primary flight display showed a sudden fall in airspeed from about 275 knots to about sixty knots, and the standby instrument subsequently showed a similar problem. Those numbers did not describe the aircraft actually slowing by that amount in a few seconds. They reflected an inconsistency in the measured airspeeds.
The BEA concluded that the temporary inconsistency was likely caused by ice crystals obstructing the Pitot probes. These probes measure the pressure used to calculate airspeed. The report retains the word likely because the exact obstruction could not be observed directly. The computers detected inconsistent measurements, disconnected the automatic systems and changed the flight controls from normal law to alternate law. In that mode, the aircraft no longer had the angle-of-attack protection available in normal law.
The monitoring copilot identified the loss of speed information and the change in control law. However, neither copilot called for the unreliable-airspeed procedure. Instead, their attention moved among instrument indications, warning messages and the aircraft's changing attitude. The flight director bars disappeared and later returned. The investigation found that no ECAM failure message clearly told the pilots that the computers had detected inconsistent airspeeds. The crew had to interpret several changes while also taking over manual flight at high altitude.
The control surfaces continued responding to the pilots' commands. There was no finding that the aircraft had become physically uncontrollable at the moment the autopilot disconnected. The immediate challenge was to maintain a stable attitude and flight path while identifying which indications could be trusted.
In the first seconds of manual flight, the pilot flying made rapid roll inputs and continued commanding nose-up movement. The pitch attitude increased to approximately eleven degrees in ten seconds. The aircraft began climbing above its original cruise altitude. The monitoring copilot noticed the climb and asked for a descent several times. Nose-down inputs then reduced the pitch and vertical speed, but the aircraft had already gained substantial height and lost actual airspeed.
At approximately 02:10:36, the left-side airspeed indication became valid again, showing 223 knots. It had been incorrect for twenty-nine seconds. The standby indication remained erroneous longer. The original upset did not require all airspeed information to remain unavailable throughout the event. By the time the measurements recovered, the aircraft's position within its flight envelope had changed.
Around 02:10:49, pitch was a little above six degrees, roll was controlled and the recorded angle of attack was slightly below five degrees. Two seconds later, the stall warning began sounding continuously. The pilot flying selected maximum takeoff or go-around thrust and made further nose-up inputs. The aircraft continued climbing, eventually reaching approximately 38,000 feet. Its angle of attack increased, and the horizontal stabilizer moved progressively into a strongly nose-up position.
The recovered airspeed indications were subsequently consistent, at about 185 knots, but nose-up commands continued. The aircraft was now leaving the range of conditions in which its wings could sustain the intended flight path. Increasing engine thrust did not resolve that condition. The BEA's chronology links the departure from the normal cruise path to the control inputs following the initial airspeed inconsistency.
The captain returned around 02:11:42, approximately a minute and a half after the autopilot disconnected. By then the aircraft was descending rapidly. Its angle of attack exceeded forty degrees, and its vertical speed was about 10,000 feet per minute downward. The nose was still above the horizon. A nose-up aircraft can descend steeply when its wings are stalled; aircraft attitude and flight direction are different measurements.
The stall warning had sounded continuously for fifty-four seconds before stopping as the recorded speeds became invalid. The warning logic treated angle-of-attack measurements as invalid when measured speeds fell below sixty knots. Consequently, the absence of the warning did not establish that the stall had ended. Later, when nose-down inputs reduced the angle of attack and the speeds became valid again, the warning resumed. Its return coincided with a change towards more valid information, rather than proving that the preceding silence had represented normal flight.
The BEA found that none of the pilots formally diagnosed the stall. They did not make explicit reference to the continuous stall warning or aerodynamic buffet. Control inputs and changes in engine thrust continued, but no sustained recovery manoeuvre followed. At times the two copilots exchanged control priority without a clear callout, and later simultaneous sidestick inputs were recorded. The captain had entered an already developed emergency and had to understand it from the indications and the copilots' descriptions.
The report describes a loss of comprehension under surprise and workload, complicated by warning behaviour, flight director indications and inadequate preparation for manual handling and unreliable airspeed at high altitude. Those conditions help explain the response; they do not alter the recorded finding that the stall remained unrecognised.
The aircraft remained in a stalled descent through the remainder of the flight. The engines operated normally and responded to the crew's commands, but the aircraft's angle of attack stayed very high. In the later recorded period, whenever that parameter was valid, it remained above thirty-five degrees. The flight crew's actions did not bring the aircraft back into a sustainable flight condition.
At 02:13:32, the pilot flying referred to the approaching altitude of 10,000 feet. Shortly afterwards, the recorder captured simultaneous sidestick inputs, followed by a transfer of control. The aircraft continued descending. From 02:14:17, the ground proximity warning system issued sink-rate and pull-up alerts. These warnings came during the last seconds of the recording, long after the original airspeed indications had first become inconsistent.
The recorders stopped at 02:14:28. The final recorded vertical speed was approximately 10,912 feet per minute downward. The aircraft's pitch attitude was 16.2 degrees nose-up, with a small left bank. All 228 people on board died when the aircraft struck the Atlantic. No emergency radio message was transmitted by the crew.
The sequence lasted approximately four minutes and twenty-three seconds from autopilot disconnection to the end of the recording. Within that short interval, a temporary loss of reliable measured airspeed had been followed by an uncontrolled climb, departure from the flight envelope and a sustained stall. Engine operation continued, while the crew never achieved the reduction in angle of attack necessary to recover the stalled wings.
The location and depth of the accident initially restricted what investigators could establish. Floating wreckage was found five days after the crash, but the principal wreckage remained on the seabed. The BEA records its discovery on 2 April 2011 at a depth of approximately 3,900 metres, near the last transmitted position. Recovery of the flight recorders allowed the investigation to move from the aircraft's transmitted messages and recovered material to a detailed account of cockpit activity and flight parameters.
The final report published in July 2012 identified a succession of events, beginning with the temporary inconsistency in airspeed measurements and continuing through inappropriate control inputs, failure to connect the recognised loss of speed indications with the appropriate procedure, late recognition of flight-path deviation and failure to identify and recover from the stall. The report also examined training, operational feedback, cockpit presentation and task sharing. It did not present the accident as the consequence of one isolated technical failure.
The BEA issued recommendations covering pilot training, certification, cockpit ergonomics, flight recorders, operational feedback and search-and-rescue arrangements. Those recommendations describe the investigation's proposed safety response at the time. They are not, by themselves, evidence that every proposed measure was subsequently implemented. The established account is more precise: the initial airspeed disturbance was temporary, the aircraft responded to control commands, and the developing aerodynamic stall was never correctly diagnosed.
Measured airspeeds fell and automatic systems disconnected. Alternate law followed. The appendix records autopilot disconnection at 02:10:05, law change at 02:10:06 and autothrust disconnection at 02:10:08.
No. The BEA describes an airspeed-measurement problem followed by automatic-system disconnection, inappropriate control inputs and an unidentified stall. Its causal account is a sequence, rather than an engine-failure explanation.
Did reliable speed indications return before impact?
The left-side speed indication became valid again after about 29 seconds. Restored measurement did not by itself resolve the developing loss of control.
The report describes the ice-crystal obstruction as likely. That wording is retained rather than presenting the precise obstruction mechanism as directly observed.
Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.
High-altitude manual handling: recommended
The BEA recommended that EASA require specific, regular training for approach to stall and stall recovery, including at high altitude. This is the recommendation recorded in the report, not a statement of its current implementation status.
The BEA recommended increasing recorder underwater-locator transmission time to 90 days and improving long-range wreckage localisation. These are report-era proposals; later compliance is not inferred.
Airspeed rejection disconnected automatic systems and changed the flight control law. This is a system response, not a claim that automation alone caused the accident.
These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.
Both investigations examine the relationship between automatic guidance, crew monitoring and the actual flight path. Flight 447 involved a stall at altitude; Flight 624 involved a displaced approach path near the runway.
Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.
Report from the working group convened in 2009 on recovering flight data and locating recorders after an ocean accident. It predates the recovery of the AF447 recorders and the final accident findings.
Sources and transparency
Checked against the BEA final report and recorder chronology through a source-based comparison. No independent expert review.
Source limitations
The linked recorder appendix is in French. The English final report is a BEA translation; its foreword says the French version is the reference. No cockpit transcript is republished.
Final Report: Accident on 1st June 2009 to the Airbus A330-203 registered F-GZCP operated by Air France flight AF 447
Bureau d'Enquetes et d'Analyses (BEA) English final report, 5 July 2012
Limited quotations for source-based commentary. Full report and illustrations are not republished. Wider reuse requires checking BEA terms. Source terms / provenance.
Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.
Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed
Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.
Revision history
: Checked report citations and source hashes. Added credited photographs, geographic context, sequence diagrams, reader answers, evidence limits, report-era safety follow-up, further records, sourced incident comparisons and this editorial record.
: Added a full chronological account with section-level report references and links from the short summary.