FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Yemenia Flight 626

30 Jun 2009 · Indian Ocean, near Comoros

Airbus A310-324 · Stalled on approach due to pilot error; impacted ocean

From Sanaa International Airport (SAH) to Prince Said Ibrahim International Airport (HAH)

Report a problem

Event

NTSB case
DCA09WA063
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Final · Commission d'enquête final report, 25 Jun 2013 
Event fatalities
152 · all aircraft and ground
Ground fatalities
0
Occupants
153
Survivors
1
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
1
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Not recorded

Airbus A310-324

Flight
IY626
Aircraft type
Airbus A310
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
7O-ADJ
Operator
Yemenia
Onboard fatalities
152
Route
From Sanaa International Airport (SAH)To Prince Said Ibrahim International Airport (HAH)
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Non-U.S., Commercial
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Not recorded
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Not recorded
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Personnel issues › Task performance
  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Experience/knowledge

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

Yemenia Flight 626 was a scheduled flight on an Airbus A310-324 twin-engine jet airliner operated by Yemenia that was flying a scheduled international service, from Sanaa in Yemen to Moroni in Comoros, when it crashed on 30 June 2009 at around 1:50 am local time (10:50 pm on 29 June UTC) while on approach to Prince Said Ibrahim International Airport, killing all but one of the 153 passengers and crew on board. The sole survivor, 12-year-old girl Bahia Bakari, was found clinging to wreckage after floating in the ocean. Bakari was discharged from the hospital on 23 July 2009.

With 152 deaths, it was the deadliest aviation disaster in the Comoros and one of the deadliest modern disasters in the nation.

The final report on the incident concluded that the crew's inappropriate flight control inputs led to an aerodynamic stall. Failing to stabilize the approach, the crew decided to abandon it and made a go-around. While conducting the climb, they were unaware that their inputs caused the automation system to set the thrust to idle, decreasing the airspeed and causing the aircraft to stall. Saturated by their workload and lack of training, the crew failed to properly get out of the stall as they kept making a nose up input. The aircraft eventually impacted the Indian Ocean. The report also noted that the crew did not react to the warnings being issued by the aircraft.

Flight history

Flight 626 was a scheduled international passenger flight from the Yemeni capital of Sana'a to Moroni, the capital of the Comoros. At the time, it was one of the primary flights to the Comoros archipelago. The flight was frequented by Comorian diaspora to come home to their homeland, particularly due to its significantly cheaper prices than the other airliners. Passengers from the flight usually came from multiple countries, with the majority coming from France after working overseas.

On 29 June, Flight 626 began its boarding process. Many of the passengers had been in transit from a previous Yemenia flight from Paris to Sana'a with a stopover in Marseille, which was using an Airbus A330-200. Of the 111 passengers, a total of 52 had boarded in Paris and another 59 boarded in Marseille. Comorians diaspora in the Middle East had gathered in the Yemeni capital and eventually boarded the plane, bringing the total number of occupants to 153 people. Majority of the passengers were families who were travelling back to the Comoros for vacation, as it was summer holiday in France. It also coincided with the "wedding season" in the Comoros, known locally as Ada N'amdra. Accordingly, many on the flight were attendees of the weddings.

On the flight was Captain Hajeb, who would be the commander of the flight and pilot flying, and First Officer Atef, who would be the pilot non-flying. The flight took off at 21:54 local time, approximately 24 minutes late due to issues with the APU, and was due to arrive at Prince Said Ibrahim International Airport in Moroni, Comoros, at 2:30 am local time on 30 June. The take-off and enroute phase were uneventful, and the flight proceeded normally.

Crash

The aircraft continued flying towards the northwest with a decreasing altitude. During the descend, the autopilot was disengaged. The aircraft was flying too low and descending with an alarming rate, prompting the aircraft's warning system to blare on the flight's dangerous altitude. The pilots then pulled the nose up, causing the aircraft to momentarily level off.

The aircraft continued its right turn but soon resumed descending at a vertical speed of approximately 1,000 ft/min. At one point, it descended to an altitude of about 160 ft above the surface of the Indian Ocean. The Ground Proximity Warning System (GPWS) again issued repeated "Too low, terrain" warnings. During this time, the crew informed Moroni air traffic control that they would call back later and proceeded to extend the landing gear.

Engine thrust was then increased, and the aircraft's nose began to rise. Shortly afterward, a repetitive chime sounded briefly before stopping, and the aircraft's airspeed continued to decrease. As the speed decayed further, the aircraft began to experience aerodynamic buffeting. The pilots, realizing how low they were flying above the sea, immediately pulled up the yoke. The pitch went up as high as 28 degrees, and the aircraft banked heavily to the right while their altitude fluctuated.

The aircraft began to bank to the left and right in quick succession. The low airspeed caused the aircraft to shake more, which caused the pilots to panic. As the aircraft lost its lift, it began to lose altitude as it had entered a stall. The aircraft began to shake violently to the left and right due to lack of lifting forces on the wings. The pilots tried to control the aircraft by pressing the rudder pedals.

After a series of heavy banks and rapidly decreasing airspeed, the aircraft finally had lost all lift forces on the left wing. The left wing stalled completely, causing the stall alarm to blare. Moments later, the aircraft rolled sharply to the left, reaching a bank angle of approximately 74 degrees. The pilots pulled the yoke hard to the right as they tried to save the aircraft by leveling the wings.

The pilots managed to level the wings, but the aircraft kept stalling. Moments later, it impacted the Indian Ocean in the north coast of Grande Comore, approximately 6 km off the coast of Mitsamiouli. Moroni Tower immediately lost all contact with Flight 626. They tried to call the crew four times, but they received no response. The emergency team was quickly informed about the disappearance of the flight. The controller later relayed the information to other controllers in Antananarivo, Dar es Salaam, Sana'a and Réunion about Flight 626. An unnamed United Nations official at the airport said that the control tower had received a notification that the plane was approaching to land before losing contact. An unseasonably strong cold front had moved through the Comoros Islands, bringing winds gusting to 64 km/h and conditions favorable for light to moderate turbulence. Yemeni civil aviation deputy chief Mohammed Abdul Qader said the wind speed was 61 km/h at the time the aircraft was landing.

Investigation and cause

Investigation

The National Civil Aviation and Meteorological Agency (ANACM) of the Comoros was in charge of the investigation. The French Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) sent an investigative team, accompanied by Airbus specialists, to assist in the investigation of the causes. Yemen also sent a technical team to Moroni, while a committee, headed by the Yemeni Minister of Transport, was formed. The BEA noted that due to corrosion damage on the memory cards, not all of the data from the CVR could be recovered.

In 2011, the BEA criticized the Comorian authorities, saying that they are not releasing the report in a timely enough manner. A preliminary report was eventually published in 2011. The report only stated an already known and established facts from the crash, though several findings of the investigation pointed to pilot error as the cause of the accident, bringing objections from the Yemeni authorities. In one of its commentaries regarding the draft report, Yemeni authorities argued that the investigation commission should "carefully consider" the possibility of external forces causing the plane to be brought down, stating that they should've recovered the rudder of the aircraft first before making conclusions.

In 2013, the Yemeni government decided to reopen the investigation, as previous attempts were hindered by the political crisis in the country. A group consisted of high-ranking officials was established and a visit to the Comoros for collaboration with Comorian investigators was planned. Yemeni Minister of Transport Wa'ed Abdullah Badhib stated that the result of the investigation would be published to the public in a clear and transparent manner.

Conclusion

The investigation determined that the accident was caused by the inappropriate actions of the crew that led to a stall from which the aircraft did not recover. The approach was unstabilized, triggering various alarms for ground proximity, aircraft configuration and approach to stall. The crew was focused on navigating, were stressed, and did not respond adequately to the different alarms. Contributing to the accident were the windy weather conditions, a lack of training, the lack of a crew briefing before the flight, and a failure to correctly respond to the pull up alarm.

A group of victims' family members called for a demonstration in Paris on 28 June 2013 to protest the final report.

Text from the Wikipedia article “Yemenia Flight 626” (revision 1375547332, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

On June 29, 2009, about 2251 UTC, an Airbus A310-300, 7O-ADJ, operated as Yemenia flight 626, collided with the waters of the Indian Ocean, during an approach to land at Moroni, Comoros. Of the 153 aboard, one passenger was the sole survivor and the aircraft was destroyed. The weather was reported as windy. The last departure point was Sana'a, Yemen.

The investigation is under the responsibility of the Comoros Ministry of Transport. The US NTSB has designated an Accredited Representative to support the investigation under the provisions of ICAO Annex 13.

All inquiries on this accident should be directed to:

Direction Générale de l’Aviation Civile et de la Météorologie B.P. 72 Moroni Comores

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: Yemenia Flight 626
Article
Yemenia Flight 626
Revision
1375547332 · 2026-09-18 · retrieved 2026-09-18
Wikidata
Q904715
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA09WA063
Event ID
20090628X32005
Case number
DCA09WA063
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "Yemenia Flight 626" (page 23439581, revision 1375547332); merged with NTSB case DCA09WA063 (events / aircraft)
Date
Wikipedia infobox: date; matches the Commission d'enquête, Union des Comores (Ministère des Postes et Télécommunications ... chargé des Transports et du Tourisme) final report
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA09WA063
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities; matches the Commission d'enquête, Union des Comores (Ministère des Postes et Télécommunications ... chargé des Transports et du Tourisme) final report
Ground fatalities
Commission d'enquête, Union des Comores (Ministère des Postes et Télécommunications ... chargé des Transports et du Tourisme) final report
Summary
Wikipedia infobox: summary
Source notes (4)
  • One occurrence in two sources, merged: the Wikipedia article "Yemenia Flight 626" and NTSB case DCA09WA063, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • The NTSB record dates it 2009-06-29 and the Wikipedia article 2009-06-30; Wikipedia's date is used.
  • No bulk values were replaced by the NTSB case API.
  • Checked against the Commission d'enquête, Union des Comores (Ministère des Postes et Télécommunications ... chargé des Transports et du Tourisme) final report (2013-06-25) on 2026-09-18. The report states the same date, flight number, fatalities, registration, operator, departure, destination and damage. Taken from the report: ground fatalities. Not checked: place, crash-site coordinates, aircraft type and type of operation.