FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Armavia Flight 967

3 May 2006 · Black Sea, near Adler-Sochi International Airport, Sochi, Russia

Airbus A320-211 · Controlled flight into water due to pilot error and ATC error aggravated by psycho-emotional stress

From Zvartnots International Airport (EVN) to Sochi International Airport (AER)

Report a problem

Event

NTSB case
ENG07WA003
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
Unknown · led by another country; figures from NTSB notifications
Event fatalities
113 · all aircraft and ground
Ground fatalities
Unknown
Occupants
113
Survivors
0
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
0 serious · 0 minor (NTSB)
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
Instrument Meteorological Cond

Airbus A320-211

Flight
U8967
Aircraft type
Airbus A320
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
EK-32009
Operator
Armavia
Onboard fatalities
113
Route
From Zvartnots International Airport (EVN)To Sochi International Airport (AER)
Aircraft age
About 11 years (built 1995)
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
Approach · IFR missed approach
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
Controlled flight into terrain/object (CFIT)
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

No findings designated as a cause are recorded in the NTSB data yet.

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

From the Wikipedia article

Armavia Flight 967 was a scheduled international passenger flight operated by Armavia from Zvartnots International Airport, Zvartnots in Armenia to Sochi, a Black Sea coastal resort city in Russia. On 3 May 2006, the aircraft operating the route, an Airbus A320, crashed into the sea while attempting a go-around following its first approach to Sochi airport; all 113 aboard were killed. The accident was the first major commercial airline crash in 2006. It was Armavia's only fatal accident during the airline's existence.

Flight

The aircraft took off from Zvartnots International Airport (EVN) at a scheduled departure time at 01:45 Armenian Daylight Time (20:45 UTC, May 2), with a scheduled arrival time at Sochi International Airport (AER) of 02:00 Moscow Daylight Time (22:00 UTC, May 2).

To make their decision for departure, the crew obtained the observed weather data and the weather forecast for the takeoff, landing, and alternate aerodromes, all of which met the requirements for IFR flights. All the crew were correctly licensed and adequately rested to operate the flight.

The airplane took off from Zvartnots airport at 20:47 with 113 occupants on board: 105 passengers (including five children and one infant), two pilots, one aircraft engineer, and five flight attendants. Takeoff, climb, and cruise were uneventful.

The first communication between Sochi approach controller and the crew took place at 21:10. At that moment, the airplane was beyond the coverage area of the Sochi radar. Until 21:17, the approach controller and the crew discussed the observed and forecast weather, and as a result, the crew decided to return to Yerevan. At 21:26, after the decision had already been made, the crew asked the controller about the latest observed weather. At 21:30, the controller informed the crew that visibility was 3600 m and the cloud ceiling was 170 m. At 21:31, the crew decided to continue the flight to Sochi airport.

The next communication with the approach controller was at 22:00. The aircraft then was descending to an altitude of 3600 m and was being tracked by the Sochi radar. The approach controller cleared the flight for a descent to 1800 m and reported the observed weather at Sochi, as at 22:00, for runway 06, which was above the minima.

The crew was then handed over to the holding and tower controllers, and was cleared for descent to 600 m, before entering the turn to the final approach. Whilst performing the turn, the runway extended centreline was overshot. After eliminating the deviation, the crew started descending the aircraft along the glide slope, following the approach pattern. At 22:10, the crew reported that the gear was down and that they were ready for landing. In response, they were advised that they were 10 km from the airport and that the weather was now 4000 m visibility and 190 m cloud ceiling, and were cleared to land. About 30 seconds later, the controller advised the crew of the observed cloud ceiling at 100 m and instructed them to cease their descent, abandon the landing attempt, and carry out a right turn and climb to 600 m and also to contact the holding controller, who would give instructions for entering the airport's holding pattern. The last communication with the crew was at 22:12. After that, the crew did not respond to any of the controller's calls. At 22:13, the aircraft struck the water, and broke up on impact.

Text from the Wikipedia article “Armavia Flight 967” (revision 1372768180, 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

Sources

Wikipedia article: Armavia Flight 967
Article
Armavia Flight 967
Revision
1372768180 · 2026-09-02 · retrieved 2026-09-18
Wikidata
Q2422973
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record ENG07WA003
Event ID
20081219X65319
Case number
ENG07WA003
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
Record
Wikipedia article "Armavia Flight 967" (page 5003758, revision 1372768180); merged with NTSB case ENG07WA003 (events / aircraft)
Date
Wikipedia infobox: date
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 ENG07WA003
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (2)
  • One occurrence in two sources, merged: the Wikipedia article "Armavia Flight 967" and NTSB case ENG07WA003, 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.
  • No bulk values were replaced by the NTSB case API.