Armavia Flight 967
| Industry | Airline |
|---|---|
| Founded | 1996 |
| Defunct | 2013 |
| Headquarters | Yerevan , Armenia |
Area served | International |
Armavia Flight 967 was a planned international passenger service operated by Armavia from Zvartnots International Airport in Armenia to Sochi, Russia. On 3 May 2006, the Airbus A320-200 assigned to this flight crashed into the Black Sea during a go-around maneuver following an initial approach to Sochi airport; all 113 individuals onboard perished. This incident marked Armavia's sole fatal crash and was the first significant commercial airline disaster of 2006.
Flight
The aircraft departed from Zvartnots International Airport at 01:45 Armenian Daylight Time (20:45 UTC on May 2), with an expected arrival at Sochi International Airport at 02:00 Moscow Daylight Time (22:00 UTC on May 2). The flight crew reviewed weather conditions and forecasts for departure, destination, and alternate airports, all of which complied with IFR standards. Each crew member held valid licenses and was adequately rested.
Takeoff occurred at 20:47 with a total of 113 people onboard: 105 passengers (including five children and one infant), two pilots, one aircraft engineer, and five cabin crew members. The phases of takeoff, ascent, and cruising proceeded without incident.
Initial contact with Sochi approach control happened at 21:10 when the aircraft was outside radar coverage. After discussing the weather, the crew first planned to return to Yerevan. However, at 21:30, updated weather reports showed visibility of and a cloud base at , prompting the decision to continue toward Sochi.
At 22:00, while descending to , Sochi radar began tracking the flight. Air traffic control cleared the descent to , confirming weather conditions above minimums for runway 06.
Control was transferred between holding and tower controllers, who authorized descent to before initiating final approach. During the turn to final, the aircraft initially deviated beyond the runway centerline but corrected its path and commenced descent along the glide slope. At 22:10, the crew reported landing gear down and readiness for landing; clearance was granted with visibility at and cloud ceiling at .
Approximately thirty seconds later, the controller notified that the cloud ceiling had lowered to , instructed a go-around with climb to , a right turn, and contact with holding controller for further instructions. The last transmission from the crew was at 22:12; no subsequent response was received. At 22:13, the aircraft struck the water surface and disintegrated on impact.
Aircraft
The aircraft involved was an A320 manufactured in France, first flown in June 1995 bearing manufacturer serial number 547 and test registration F-WWIU. Initially delivered in 1995 to Ansett Australia as VH-HYO, it was acquired by Armavia in 2004, registered as EK-32009, and named Mesrop Mashtots. Armavia applied a new livery on 31 October 2004. Prior to the accident, the airplane had accumulated over 10,000 flight hours.
Passengers and crew
The majority of passengers were Armenian nationals, comprising 85 Armenians alongside 26 Russians, one Georgian, and one Ukrainian onboard.
- Nationality breakdown of passengers and crew
| Nationality | Passengers | Crew | Total | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Armenia | 77 | 8 | 85 | Russia | 26 | 0 | 26 | Georgia | 1 | 0 | 1 | Ukraine | 1 | 0 | 1 | Total | 105 | 8 | 113 |
The captain was Grigor Grigoryan, aged 40, who trained at Krasnokutsk Civil Flight School and Moscow Institute of Civil Aviation Engineers. He began his career as co-pilot with Balaklavsky United in 1986, attained captaincy at Ararat Airlines in 1997, joined Armavia as co-pilot in 2004, and was promoted to captain in 2005. He completed Airbus A320 captain training at SAS Flight Academy in Stockholm and had accumulated a total of 5,458 flight hours, including 1,436 hours on the A320.
First officer Arman Davtyan was aged 29; he graduated from Ulyanovsk Civil Flying School in 1999. He worked for Chernomor-Avia from 2001 before joining Armavia in 2002. Davtyan successfully completed Airbus A320 training at SAS Flight Academy and had logged a total of 2,185 flight hours, including 1,022 on this aircraft type.
Recovery operations
Flight 967 vanished from Sochi’s radar screens at 02:13 local time. N.G. Savelyev, the Chief of Flight Operations, immediately alerted all relevant search-and-rescue units and dispatched an Mi-8 helicopter to assist. By 02:19, the Minister of Emergencies in Russia was notified of the situation. Although a search helicopter was prepared for deployment, deteriorating weather conditions forced a temporary halt to the mission. At 04:08, the Ministry’s vessel Valery Zamarayez identified the likely crash site, prompting rescue teams to proceed there. Between 07:30 and 12:30, nine human remains were recovered.
The recovery team collected vital Airbus components such as the nose section, landing gear, vertical stabilizer, elevator parts, wiring harnesses, and electronic modules. Overall, 52 body fragments were retrieved. According to the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), the landing gear was extended upon impact. The lower portion of the rudder and several elevator elements exhibited severe damage and significant deformation.[1]
Pilot-Autopilot Interaction
The pilot voiced concerns regarding the late hour of the flight and autopilot operations, opting to manually intervene in ways that appeared intended to override automated controls. This behavior, combined with limited communication, likely heightened pressure on the first officer. After receiving instructions to abort the landing and execute a turn, the crew deviated from standard operating procedures multiple times. These factors, along with inadequate control inputs, led to suboptimal aircraft performance and triggered several warning alerts.
Meteorological Conditions
Initial weather assessments indicated favorable conditions near Sochi, with low atmospheric pressure and a cold front developing in the Caucasian Edge east of Turkey. Rainfall occurred in Adler (Sochi), while typical springtime low clouds may have restricted pilot visibility—a critical element in many controlled flight into terrain (CFIT) accidents.[1][2]
Prior to departing Yerevan, the crew received a weather update indicating good conditions at Sochi. Following takeoff, a second briefing confirmed continued favorable weather featuring clouds, mist, and light rain—conditions unlikely to produce phenomena such as vortices or downdrafts. However, by the time Flight 967 approached Sochi, weather had worsened due to an advancing cold front that generated a cumulonimbus formation accompanied by heavy rain and visibility reduced to approximately 1,500 m. Air traffic controllers instructed an immediate go-around owing to low cloud cover at Sochi International Airport just before Flight 967 disappeared from radar.[1]
Flight Recorder Examination
Shortly after the crash of Flight 967, emergency locator transmitter signals were activated. The French BEA successfully retrieved both the cockpit voice recorder (CVR) and flight data recorder (FDR) from their submerged locations in the Black Sea; both devices sustained only minor damage. Subsequent analysis of these recorders was conducted by BEA.
Examination
The flight proceeded without incident until the approach phase. Throughout the cruise, First Officer Davtyan voiced dissatisfaction regarding operational circumstances and insufficient rest. The BEA report highlighted that neither pilot possessed a comprehensive understanding of the Airbus A320 autopilot functionality. Captain Grigoryan expressed dissatisfaction with the descent rate managed by the DESCENT mode, which automatically determines descent based on aircraft parameters.
Flight 967 passed the designated waypoints GUKIN and TABAN as directed by Sochi tower. As the final approach unfolded, worsening weather conditions led Sochi to command an aborted descent. The crew responded with profanity and engaged in a three-minute discussion while working through checklist procedures.
The aircraft ascended with flaps set at 18°, during which Captain Grigoryan showed frustration toward air traffic control. The crew activated glide-slope capture descent mode with autopilots and autothrust operational, maintaining a stabilized speed of 137 knots in landing configuration while preparing for touchdown.
Due to low cloud cover, Sochi tower instructed a go-around. Although thrust levers were advanced for climb, flaps, slats, and landing gear remained fully extended—actions inconsistent with standard go-around protocols—indicating potential crew impairment. At 1,150 feet, a low energy warning was triggered; subsequently, the crew engaged the TO/GA mode.
The autopilot was disconnected amid concerns about its dependability. Captain Grigoryan initiated a right bank as both pilots displayed increasing emotional tension. The aircraft’s pitch angle decreased during the right turn; unnecessary rudder inputs were observed, possibly linked to psychological stress.
The BEA suggested that the crew might have suffered from somatogravic illusion—a sensory misperception causing false pitch awareness—compounded by night conditions and absence of visual cues. Additionally, possible misreading of Airbus A320 speed indicators may have provoked instinctive side stick movements under stress; however, conclusive evidence is lacking.
Flight 967’s final transmission was incomplete before Captain Grigoryan commanded full flap deployment. Shortly thereafter, a master warning activated due to excessive speed threatening flap structural integrity. The aircraft banked sharply to the right, adopted a nose-down attitude, and flaps retracted to 18°. The captain’s control inputs intensified both the descent rate and severe right bank (39° roll).
The ground proximity warning system (GPWS) sounded as First Officer Davtyan attempted to level the aircraft and counteract the bank with left stick input while simultaneously pitching down—both pilots applied controls simultaneously without coordination or transfer of control authority, causing prohibited dual inputs. The dual-input alert did not activate because it is lower priority than GPWS warnings.
Crew distraction escalated when air traffic control transmitted an extended message during descent. Thrust levers were abruptly manipulated, disengaging autothrottle. Despite recovery attempts, Flight 967 impacted water at 285 knots, resulting in total fatality.
Primary conclusions of the final accident report
Armavia Flight 967 crashed due to controlled flight into terrain (water) during a climbing maneuver following an aborted approach to Sochi airport at night under weather conditions below minimums for runway 06.
With autopilot disengaged, the captain—affected by psychoemotional stress—made nose-down control inputs resulting from loss of situational awareness regarding pitch and roll attitudes, initiating the abnormal flight condition. Inadequate pitch control prevented recovery and caused the accident.
Contributory elements included insufficient monitoring of pitch attitude, altitude, and vertical speed by the first officer and improper crew reaction to GPWS alerts.
Contributing elements and deficiencies
Source:
| Time | Element or deficiency | Relevant regulation |
|---|---|---|
| Crew members engaged in unrelated discussions during the descent and approach phases. | ||
| The Armenia Civil Aviation Administration-approved A320 Flight Crew Techniques Manual did not include a compulsory captain upgrade training program; the captain had not undergone this training, which was introduced in subsequent updates. | A320 Flight Crew Techniques Manual | |
| Armavia's flight operations failed to perform required analyses of flight data recorder (FDR) and cockpit voice recorder (CVR) information for aircraft exceeding 27,000 kg maximum takeoff weight, limiting evaluation of crew performance. | ROLRGA RA Section 11.2 and ICAO Annex 6 Part 1 Chapter 3 | |
| The airline lacked documentation of captains’ approaches and landings conducted under adverse weather conditions. | ROLRGA RA-2000 Sections 4.5.33 and 6.1.5 | |
| 21:16 | Sochi approach control inaccurately conveyed weather conditions, reporting steady visibility at 1500 m and cloud base at 150 m without qualifiers such as "at times"; this influenced the crew’s initial plan to return to Zvartnots but was not a direct cause. | |
| 22:01 | The approach controller incorrectly described the cloud ceiling as "considerable" at 1800 m instead of the actual 180 m; this did not impact the captain’s decisions. | |
| 22:03 | The crew neglected to report the selected instrument approach system/mode; meanwhile, the holding controller did not request this information. | Holding Controller's Operation Manual, Section 4.2.1 |
| 22:11 | The final controller received a weather update indicating a cloud ceiling at 100 m—below minimum requirements—and directed an aborted descent with a climb to 600 m; although these instructions did not fully comply with regulations, the controller was authorized to command a go-around. | Civil Flight Operations Guidance 85 Section 6.5.16; Final Controller's Operation Manual |
| Controller held authority to order a go-around maneuver. | The AIP of Russia | |
| Sochi weather forecasts from 18:00 to 03:00 were not verified for intermittent visibility fluctuations. | ||
| 22:11 | The weather observer failed to issue a mandatory special weather report when the cloud ceiling dropped to 100 m. | Guidance for Meteorological Support in Civil Aviation 95; Sochi Meteorological Instructions; Special Weather Report Criteria |
| ATIS broadcast recommendations were only partially implemented. | Federal Air Transport Administration and Hydrometeorology Service Joint Order No. 62/41 (2000) | |
| Inconsistencies were identified in documentation outlining FDR binary signal logic during data examination. | ||
| Airbus classifies low-energy warnings during landing configuration adjustments with autopilot/autothrust active as abnormal events. |
Safety recommendations
The comprehensive accident investigation report issued a total of 22 safety recommendations aimed at remedying the detected deficiencies:
| Number of Recommendations |
Recipient |
|---|---|
| 5 | Aviation regulatory authorities within Commonwealth of Independent States (CIS) nations |
| 1 | Aviation regulatory bodies of CIS countries in collaboration with industrial and scientific research institutions |
| 6 | Civil Aviation Administration of Armenia alongside Armavia airline management |
| 2 | Federal Air Navigation Service of the Russian Federation |
| 2 | Federal Service for Hydrometeorology and Environmental Monitoring |
| 2 | Federal State Unitary Enterprise “State Corporation for Air Traffic Management" |
| 4 | Airbus Industrie |
See also
- List of accidents and incidents involving commercial aircraft
- Ethiopian Airlines Flight 409
- Flydubai Flight 981, an accident resulting from diminished situational awareness during the approach at Rostov Airport, causing a fatal nose dive with the loss of all 62 passengers and crew.
- Air China Flight 129
- Afriqiyah Airways Flight 771
- Gulf Air Flight 072, a comparable incident involving an Airbus A320 that crashed into the sea during a nighttime go-around maneuver.
- Northwest Airlink Flight 5719
- Kenya Airways Flight 507
- 2016 Russian Defence Ministry Tupolev Tu-154 crash, which occurred close to the location of Flight 967.
External links
- Interstate Aviation Committee
- Final accident report – English version provided by the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), featuring BEA remarks and responses from the IAC.
- Investigation and Report – Official Russian documentation.
- Bureau of Enquiry and Analysis for Civil Aviation Safety
- Armeniapedia.org article
- Airbus
- Articles with short description
- Airliner accidents and incidents caused by pilot error
- Aviation accidents and incidents in Russia in 2006
- Airliner accidents and incidents involving controlled flight into terrain
- Accidents and incidents involving the Airbus A320
- May 2006 in Asia
- Armenia–Russia relations
- May 2006 in Russia
- Pages with reference errors
- Pages with script errors