ASN Aircraft accident Boeing 737-219 EX-009 Bishkek-Manas International Airport (FRU)
ASN logo
Status:Accident investigation report completed and information captured
Date:Sunday 24 August 2008
Type:Silhouette image of generic B732 model; specific model in this crash may look slightly different
Boeing 737-219
Operator:Itek Air
On behalf of:Iran Aseman Airlines
Registration: EX-009
MSN: 22088/676
First flight: 1980-06-16 (28 years 3 months)
Total airframe hrs:60014
Engines: 2 Pratt & Whitney JT8D-15
Crew:Fatalities: 0 / Occupants: 5
Passengers:Fatalities: 65 / Occupants: 85
Total:Fatalities: 65 / Occupants: 90
Aircraft damage: Destroyed
Aircraft fate: Written off (damaged beyond repair)
Location:7,8 km (4.9 mls) WNW of Bishkek-Manas International Airport (FRU) (   Kyrgyzstan)
Phase: Approach (APR)
Nature:International Scheduled Passenger
Departure airport:Bishkek-Manas International Airport (FRU/UAFM), Kyrgyzstan
Destination airport:Tehran-Imam Khomeini International Airport (IKA/OIIE), Iran
Iran Aseman Airlines Flight 6895 from Bishkek (FRU), Kyrgyzstan to Tehran (IKA), Iran was carried out by Itek Air. The Kyrgyz airline operated one of their Boeing 737-200 aircraft on the flight.
In the afternoon of August 24, from 16:30 to 20:00 local time, a thunderstorm with associated rain passed over Bishkek. Over that period the wind shifted from 220 degrees to 100 degrees at 20:30. Wind was blowing at about 6 kts, with wind variable at 23 knots. The temperature had dropped from 31 to 27 degrees C.
The weather then improved and at the time of departure visibility was more than 10 km with 6/8 clouds at an altitude of 5000 m (ca 16400 ft).
The Boeing 737 was cleared to taxy to runway 08 for departure. Take off was commenced at 20:30. The flight was cleared for a DW-1 departure, which entailed a left turn after takeoff to a heading of 240 degrees towards the RENAT beacon. From there it was to continue to the Chaldovar NDB, which should be crossed at or above FL158.
At 20:36:40, the airplane was climbing through an altitude of 3000 m (almost 10.000 feet). At that moment the cabin altitude alert horn probably sounded, because the crew reported problems with the cabin pressure.
The crew decided to return to Bishkek and requested a visual approach to runway 08. This was approved and the airplane made a right hand turn, for a straight-in approach to runway 08. At 20:41:40 the crew reported the runway in sight. About 20:42:30 the flight was 12 km from the runway, flying at 400 m above airfield elevation at an airspeed of 460 km/h (250 kts). At a distance of 5 km from landing, the airplane had decelerated to 340 km/h (185 kts), but it was not properly configured for landing. The flight crew then obtained permission to carry out a left-hand orbit in order to configure the plane for landing. A left hand turn was flown with a 30-degree bank.
In the process of the turn the aircraft descended further with the airspeed decreasing to 290 km/h (155 kts).
The airplane struck terrain some 7.5 km from the runway. At the time of impact the landing gear was down and flaps were selected down at 15 degrees.

Probable Cause:

The cause of the Itek Air B737-200 EX-009 accident during the air-turn back due to the cabin not pressurizing (probably caused by the jamming of the left forward door seal) was that the crew allowed the aircraft to descend at night to a lower than the minimum descent altitude for visual approach which resulted in the crash with damage to the aircraft followed by the fire and fatalities.
The combination of the following factors contributed to the accident:
- Deviations from the Boeing 737-200 SOP and PF/PM task sharing principles;
- Non-adherence to visual approach rules, as the crew did not keep visual contact with the runway and/or ground references and did not follow the prescribed procedures after they lost visual contact;
- Loss of altitude control during the missed approach (which was performed because the PIC incorrectly evaluated the aircraft position in comparison with the required descent flight path when he decided to perform visual straight-in approach);
- Non-adherence to the prescribed procedures after the TAWS warning was triggered.

Accident investigation:

Investigating agency: MAK Russia
Status: Investigation completed
Duration: 259 days (9 months)
Accident number: -
Download report: Final report

Controlled Flight Into Terrain (CFIT) - Ground

» RIA Novosti

Follow-up / safety actions

MAK issued 21 Safety Recommendations

Show all...


photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-EX-009
photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-EX-009
accident date: 24-08-2008
type: Boeing 737-219
registration: EX-009
photo of Boeing-737-219-ZK-NAS
accident date: 24-08-2008
type: Boeing 737-219
registration: ZK-NAS

Aircraft history
date registration operator remarks
4 JUL 1980 ZK-NAS Air New Zealand delivered; 10th ANZ Boeing 737
21 JUL 1980 ZK-NAS Air New Zealand entered service named 'Piwakawaka'
25 AUG 1994 ZK-NAS Air New Zealand involved in airmiss with Cessna 152 ZK-EOJ, 5 nm NE of Dunedin
22 JUN 1995 N318CM COPA Panama delivered to COPA
JUL 1995 HP-1288CMP COPA Panama new registration
MAR 2003 EX-009 Phoenix Aviation sold to Phoenix Aviation
OCT 2005 EX-009 Phoenix rebranded to
23 APR 2006 EX-009 Itek Air

This map shows the airport of departure and the intended destination of the flight. The line between the airports does not display the exact flight path.
Distance from Bishkek-Manas International Airport to Tehran-Imam Khomeini International Airport as the crow flies is 2157 km (1348 miles).
Accident location: Exact; as reported in the official accident report.

This information is not presented as the Flight Safety Foundation or the Aviation Safety Network’s opinion as to the cause of the accident. It is preliminary and is based on the facts as they are known at this time.
languages: languages


Boeing 737-200

  • 1114 built
  • 113th loss
  • 55th fatal accident
  • 21st worst accident (at the time)
  • 23rd worst accident (currently)
» safety profile

  • The worst accident
» safety profile

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314