Crash of an Airbus A300B4-203 in Istanbul

Date & Time: Mar 23, 2007 at 1349 LT
Type of aircraft:
Operator:
Registration:
YA-BAD
Survivors:
Yes
Schedule:
Ankara - Istanbul
MSN:
177
YOM:
1982
Flight number:
FG719
Country:
Region:
Crew on board:
20
Crew fatalities:
Pax on board:
30
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 24 at Istanbul-Atatürk Airport, the aircraft was unable to stop on a wet runway, overran and came to rest 30 metres further. All 50 occupants evacuated safely while the aircraft was later declared as damaged beyond repair. At the time of the accident, the runway surface was wet due to rain falls.

Crash of a Tupolev TU-134A in Samara: 6 killed

Date & Time: Mar 17, 2007 at 1140 LT
Type of aircraft:
Operator:
Registration:
RA-65021
Survivors:
Yes
Schedule:
Surgut - Samara - Belgorod
MSN:
48390
YOM:
1976
Flight number:
UT471
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
50
Pax fatalities:
Other fatalities:
Total fatalities:
6
Aircraft flight hours:
35154
Aircraft flight cycles:
22611
Circumstances:
The aircraft departed Surgut on a flight to Belgorod with an intermediate stop in Samara, carrying 50 passengers and 7 crew members. While descending to Samara-Kurumoch Airport, weather conditions worsened and the visibility was below minimums. After the approach checklist was completed, the crew lowered the landing gear, selected flaps down at 30° and continued the approach. In poor visibility, the aircraft descended below the MDA until it struck the ground at a speed of 320 km/h and crashed 304 metres from the runway threshold and 95 metres to the left of its extended centerline. The aircraft came to rest upside down and partially burned. Six passengers were killed, 21 other occupants were injured and 30 people escaped uninjured. At the time of the accident, the visibility was estimated to be 150 metres with an RVR of 200 metres for runway 23 and a vertical visibility of 300 feet in freezing fog.
Probable cause:
The decision of the crew to continue the descent below MDA in below minimums weather conditions until the aircraft impacted ground and crashed.
The following contributing factors were identified:
- Organizational, technical and procedural deficiencies in the work and interactions between the met office and ATC services as well as from the crew,
- Deficiencies in the standards and technical documentation of the Samara Airport that made it impossible for ATC to inform the crew on a timely manner about the readings from the KRAMS-4 weather station that indicated a deterioration of the weather conditions below airport minimums,
- At decision height, in the absence of reliable visual contact with the approach lights and airport environment, the flight crew failed to initiate a go-around procedure,
- ATC failure to use the full capability of the radar equipment because of contradictions in the relevant standards and procedures documents,
- Poor crew coordination and their delay in executing a missed approach procedure,
- Lack of unified federal regulations covering flight operations, ATC, met and other services, taking into account both domestic and international experience in flight safety.

Crash of a McDonnell Douglas MD-82 in Kish Island

Date & Time: Mar 16, 2007
Type of aircraft:
Operator:
Registration:
LZ-LDD
Survivors:
Yes
Schedule:
Dubai - Kish Island
MSN:
49218/1274
YOM:
1986
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
154
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
For unknown reasons, the aircraft landed hard at Kish Island Airport and was considered as damaged beyond repair. All 158 occupants escaped uninjured.

Crash of an Ilyushin II-76TD in Mogadishu

Date & Time: Mar 9, 2007 at 0835 LT
Type of aircraft:
Operator:
Registration:
EW-78826
Flight Type:
Survivors:
Yes
Schedule:
Entebbe - Mogadiscio
MSN:
10034 99991
YOM:
1990
Country:
Region:
Crew on board:
9
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On final approach, while flying at an altitude of 120 metres at 3 kilometres from the runway threshold, the aircraft was hit by an RPG, probably fired by rebels from a boat. The projectile hit the left main gear and a fire erupted. The aircraft landed safely and all 15 occupants escaped uninjured. It took about one hour for the only fire-fighting truck available at the airport to reach the plane as it had no fuel. Eventually, the aircraft was damaged beyond repair and cannibalized. One week later, some technicians of the Belarus operator returned to Mogadishu to recover pieces and material from the aircraft. On departure, another II-76 from the same operator was hit by a missile and destroyed.
Probable cause:
Damaged beyond repair after being shot down.

Crash of a Boeing 737-497 in Yogyakarta: 21 killed

Date & Time: Mar 7, 2007 at 0758 LT
Type of aircraft:
Operator:
Registration:
PK-GZC
Survivors:
Yes
Schedule:
Jakarta - Yogyakarta
MSN:
25664
YOM:
1992
Flight number:
GIA200
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
21
Captain / Total flying hours:
13421
Captain / Total hours on type:
3703.00
Copilot / Total flying hours:
1528
Copilot / Total hours on type:
1353
Aircraft flight hours:
35207
Aircraft flight cycles:
37360
Circumstances:
On 7 March 2007, a Boeing Company 737-497 aircraft, registered PK-GZC, was being operated by Garuda Indonesia on an instrument flight rules (IFR), scheduled passenger service, as flight number GA200 from Soekarno-Hatta Airport, Jakarta to Adisutjipto Airport, Yogyakarta. There were two pilots, five flight attendants, and 133 passengers on board. The pilot in command (PIC) and copilot commenced duty in Jakarta at about 21:30 Coordinated Universal Time (UTC), or 04:30 local time, for the flight to Yogyakarta. Prior to departing Jakarta, during the push back, the PIC contacted the ground engineers and informed them that the number-1 (left) engine thrust reverser fault light on the cockpit instruments had illuminated. The engineers reset the thrust reverser in the engine accessories unit and the fault light extinguished. The scheduled departure time was 23:00. The aircraft took off from Jakarta at 23:17, and the PIC was the pilot flying for the sector to Yogyakarta. The copilot was the monitoring/support pilot. During the cruise, just before top of descent, the crew was instructed by Jakarta Control to ‘maintain level 270 and contact Yogya Approach 123.4’. The copilot acknowledged; ‘contact Yogya 123.4, Indonesia 200’. The PIC started to give a crew briefing at 23:43 stating: ‘in case of holding, heading of 096’. The briefing was interrupted by a radio transmission from Yogya Approach, giving GA200 a clearance to Yogyakarta via airway W 17 for runway 09, and a requirement to report when leaving flight level 270. When radio communication was completed, the PIC continued with the crew briefing for an ILS approach, stating:
When clear approach ILS runway 09, course 088. (C) Frequency 1091, aerodrome elevation three hundred fifty, (C) leaving two thousand five hundred by 6 point 6 DME ILS, (C) to check four DME one thousand six hundred seventy, (C) crossing two DME one thousand thirty seven. Decision Altitude ILS Cat I, five eight seven, two three seven both set, approach flap forty, auto brake two. Speed one three six, one five one, two twenty. Timing from final approach-fix to VOR 6 DME. (C) With airspeed approximately one four one, two minutes thirty six. (C) In case localizer, MDA seven hundred, localizer, miss approach, at point six. (C) DME ILS India Juliet oscar golf. (C) On landing, to the left standby parking stand. Go-around missed approach climb one thousand five hundred turn left. To holding fix via Yogya VOR, continue climb four thousand feet, to cross Yogya at or above two thousand five hundred DME eight. (C).
Twelve minutes and 17 seconds later, Yogya Approach cleared GA200 ‘for visual approach runway zero nine, proceed to long final, report runway in sight’. The copilot acknowledged the clearance and asked for confirmation that they were cleared to descend to circuit altitude, Yogya Approach replied ‘descend to two thousand five hundred initially’. The crew informed the investigation that they were conducting an Instrument Landing System (ILS) approach to runway 09, in visual meteorological conditions (VMC). However they did not inform Yogya Approach or Yogyakarta Tower that they were flying the 09 ILS approach. At 23:58:10, the aircraft overran the departure end of runway 09 at Yogyakarta Airport. The PIC reported that as the aircraft was about to leave the runway, he shut down both engines. The aircraft crossed a road, and impacted an embankment before stopping in a rice paddy field 252 meters from the threshold of runway 27 (departure end of runway 09). The aircraft was destroyed by the impact forces and an intense, fuel-fed, post impact fire. There were 119 survivors. One flight attendant and 20 passengers were fatally injured. One flight attendant and 11 passengers were seriously injured.
Probable cause:
Causes:
1) Flight crew communication and coordination was less than effective after the aircraft passed 2,336 feet on descent after flap 1 was selected. Therefore the safety of the flight was compromised.
2) The PIC flew the aircraft at an excessively high airspeed and steep descent during the approach. The crew did not abort the approach when stabilized approach criteria were not met.
3) The pilot in command did not act on the 15 GPWS alerts and warnings, and the two calls from the copilot to go around.
4) The copilot did not follow company instructions and take control of the aircraft from the pilot in command when he saw that the pilot in command repeatedly ignored warnings to go around.
5) Garuda did not provide simulator training for its Boeing 737 flight crews covering vital actions and required responses to GPWS and EGPWS alerts and warnings such as ‘TOO LOW TERRAIN’ and ‘WHOOP, WHOOP PULL UP’.
Other Factors:
1) The airport did not meet the ICAO Standard with respect to runway end safety areas.
2) The airport did not meet the ICAO Standard with respect to rescue and fire fighting equipment and services for operation outside the airport perimeter and in swampy terrain.
Final Report:

Crash of a Britten-Norman BN-2B-26 Islander in Ruhnu Island

Date & Time: Mar 3, 2007 at 1608 LT
Type of aircraft:
Operator:
Registration:
D-ILFB
Survivors:
Yes
Schedule:
Pärnu - Ruhnu Island
MSN:
2271
YOM:
1994
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
16079
Aircraft flight hours:
2811
Aircraft flight cycles:
27857
Circumstances:
Luftverkehr Friesland Brunzema und Partner KG, registered in Germany and holding the Air Operator Certificate issued by the Federal Republic of Germany in 1983, has been operating scheduled flights between Pärnu (EEPU) and Ruhnu (EERU) since 2006. The flight, initially planned for 26th February 2007, was postponed several times due to adverse meteorological conditions, causing problems with provision supply on the island. On Friday, 3rd March, pilot checked the weather at 13:00 and at 14:00. Based on the received information the pilot decided to depart for Ruhnu at 14:00. At 14:08, the aircraft took off from Pärnu airport to make a scheduled VFR flight to the island of Ruhnu. Flight was carried out in the uncontrolled airspace. Pilot, two passengers and 520 kg of cargo were on board the aircraft. According to the weather briefing received by the pilot via telephone from Kuressaare, at 14:00 the cloud height in Kuressaare (EEKE, 36 Nm northwest of Ruhnu) was 600 ft. and 180 m (approximately 540 ft.) in Ruhnu. During the uneventful flight on the altitude 1500 ft., the coast and the ice border were clearly visible. The aircraft stayed clear from the clouds and no signs of icing were noticed by persons on board. Approaching the island from the northeast it was intended by the pilot to use RWY 32 for landing. The pilot decided to fly low from east to west across the runway to check the windsock and runway condition. While approaching the island, the pilot descended at the rate of 150 ft/min with low power settings and flaps extended by 1 notch. During descent the horizontal and vertical visibility deteriorated and the flight was continued in IMC2 . The descent was continued in clouds; therefore the pilot had no visual contact with the ground and horizon. The aircraft broke off the clouds over the coast on a very low altitude (100-120 ft. by pilot’s statement). Trying to maintain safe altitude and speed pilot added power, at the same time stall warning signal activated and seconds later the lower part of aircraft’s fuselage touched the treetops and collided with the terrain at 14:36. The engines continued producing power until collision with trees which after those were set to the idle by pilot. The passengers and pilot escaped the aircraft without assistance and with no injuries. The accident site is situated 0.24 Nm northeast off the runway 32 threshold. Ground surface is uneven and forested with young pinewoods.
Probable cause:
The investigation established the following causes of the accident:
1. The pilot could not maintain safe flight altitude when approaching Ruhnu aerodrome.
2. The pilot continued the descent in spite of IMC.
Contributing factors to the accident:
The investigation established the following factors contributing to the accident:
1. High motivation to perform the flight.
2. Inadequate weather information from ground services of Ruhnu aerodrome.
3. Inadequate aeronautical oversight in the destination airport.
Final Report:

Crash of an Antonov AN-12BP in Geneina

Date & Time: Feb 24, 2007 at 0900 LT
Type of aircraft:
Registration:
ST-AQE
Flight Type:
Survivors:
Yes
Schedule:
Khartoum - Geneina
MSN:
1 4 001 06
YOM:
1961
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Owned by United Arabian Airlines, the four engine aircraft departed Khartoum on a cargo flight to Geneina on behalf of AZZA Air Transport. After touchdown, the aircraft was unable to stop within the remaining distance, overran and came to rest in a sandy area. There were no injuries but the aircraft was damaged beyond repair after the undercarriage were torn off and the left wing tip was sheared off. Witnesses interviewed by the Panel stated that the majority of the passengers were military personnel. In addition to the passengers there were two D-22 type 122 mm artillery howitzers and 40 to 50 wooden boxes painted olive drab, suspected to contain arms and ammunition. The cargo was offloaded during the days following the crash under the supervision of the Sudanese Armed Forces (SAF) who continued to guard the aircraft throughout the following week. In an official report published at the end of April 2007, UNO criticized the Sudanese authorities for not respecting the various points of resolution 1591 which stipulates that Sudan is not authorized to deliver military equipment to the Darfur region.

Crash of a Boeing 737-33A in Surabaya

Date & Time: Feb 21, 2007 at 1525 LT
Type of aircraft:
Operator:
Registration:
PK-KKV
Survivors:
Yes
Schedule:
Jakarta - Surabaya
MSN:
27284/2606
YOM:
1994
Flight number:
DHI172
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
148
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
37936
Aircraft flight cycles:
23824
Circumstances:
The aircraft was on a scheduled passenger flight from Soekarno-Hatta Airport, Jakarta to Juanda Airport, Surabaya, East Java. There were 155 persons on board, consist of 7 crew and 148 passengers. During the flight there was no abnormality declare by the flight crew. Weather condition at Surabaya was thunderstorm and rain, wind 240/7 knots with visibility 8,000 meters. The CVR revealed that there was conversation in the cockpit that was not related to the progress of the flight, the conversation was relating to the company fuel policy and training program until 2000 feet. The CVR did not reveal approach briefing and any checklist reading. On final approach of runway 28 passing 800 feet approach light insight and landing clearance was received. Prior to touchdown, control of the aircraft was transferred from co-pilot to PIC. The CVR recorded that the Ground Proximity Warning Systems (GPWS) warned “Sink Rate” and “Pull Up”. The right wheel track was found out of the runway for about 4 meter away and return to the runway. The aircraft stopped for about 100 meters from taxiway N3. After aircraft touched down, the fuselage aft of passenger seat row 16 was bended down. The passengers were panic. Flight attendants evacuated the passengers via all exits available and door slides were inflated. The two passengers were minor injured, and the aircraft suffered severe damage.
Probable cause:
From the findings, it is concluded that the aircraft experienced excessive sink rate upon the touch-down. The aircraft was in unstable approach even at below 200 feet. The high vertical acceleration caused severe damage to the aircraft structure. The flight crew did not comply to several procedures published by the Boeing company. The flight crew did not respond to the GPWS alert and warnings.
Final Report:

Crash of a Cessna 340A in Council Bluffs: 4 killed

Date & Time: Feb 16, 2007 at 2104 LT
Type of aircraft:
Operator:
Registration:
N111SC
Survivors:
No
Schedule:
Fayetteville – Council Bluffs
MSN:
340A-0335
YOM:
1977
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3275
Aircraft flight hours:
6417
Circumstances:
The flight was on a VHF Omni Range (VOR) instrument approach to the destination airport at the time of the accident. Radar track data indicated that the airplane passed the VOR at 2,800 feet. After passing the VOR, it turned right, becoming established on an approximate 017- degree magnetic course. The published final approach course was 341 degrees. The airplane subsequently entered a left turn, followed immediately by a right turn, until the final radar data point. Altitude returns indicated that the pilot initiated a descent from 2,800 feet upon passing the VOR. The airplane descended through 2,000 feet during the initial right turn, and reached a minimum altitude of 1,400 feet. The altitude associated with the final data point was 1,600 feet. The initial impact point was about 0.18 nautical miles from the final radar data point, at an approximate elevation of 1,235 feet. The minimum descent altitude for the approach procedure was 1,720 feet. Review of weather data indicated the potential for moderate turbulence and low-level wind shear in the vicinity of the accident site. In addition, icing potential data indicated that the pilot likely encountered severe icing conditions during descent and approach. The pilot obtained a preflight weather briefing, during which the briefer advised the pilot of current Airman's Meteorological Information advisories for moderate icing and moderate turbulence along the route of flight. The briefer also provided several pilot reports for icing and turbulence. A postaccident inspection of the airframe and engines did not reveal any anomalies associated with a preimpact failure or malfunction.
Probable cause:
The pilot's continued flight into adverse weather, and his failure to maintain altitude during the instrument approach. Contributing factors were the presence of severe icing, moderate turbulence, and low-level wind shear.
Final Report:

Crash of a Cessna 208B Grand Caravan in Walikale: 1 killed

Date & Time: Feb 15, 2007
Type of aircraft:
Operator:
Registration:
5Y-BNN
Flight Type:
Survivors:
No
Schedule:
Goma – Walikale
MSN:
208B-0683
YOM:
1998
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot was completing a cargo flight from Goma with a load of food on board. While approaching Walikale, weather conditions deteriorated. The pilot attempted three times to land but eventually initiated a go-around when the disappeared few minutes later. SAR operations were suspended after few days as no trace of the aircraft nor the pilot was found.