Crash of a Cessna 550 Citation II in Manas: 3 killed

Date & Time: Mar 28, 2011 at 1945 LT
Type of aircraft:
Operator:
Registration:
B-7026
Flight Phase:
Survivors:
No
Site:
Schedule:
Korla - Korla
MSN:
550-0305
YOM:
1982
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
Owned by the Zhongfei General Aviation Company (CFGAC), the airplane was engaged in a survey flight over the north China province of Xinjiang. It departed Korla Airport at 1600LT with a crew of three. En route, it crashed in unknown circumstances in the Manas County, Hui autonomous prefecture of Changji. SAR did not find any trace of the aircraft nor the crew. Fatal index is presumed.

Crash of an Embraer ERJ-190-100LR in Yichun: 44 killed

Date & Time: Aug 24, 2010 at 2138 LT
Type of aircraft:
Operator:
Registration:
B-3130
Survivors:
Yes
Schedule:
Harbin - Yichun
MSN:
190-00223
YOM:
2008
Flight number:
VD8387
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
91
Pax fatalities:
Other fatalities:
Total fatalities:
44
Aircraft flight hours:
5109
Aircraft flight cycles:
4712
Circumstances:
The crew started the approach in poor weather conditions with a visibility reduced at 2,800 metres. On short final, the aircraft was too low and the crew did not establish visual contact with the runway. The aircraft impacted ground 1,110 metres short of runway 30, slid and came to rest in flames 690 meters short of runway. 44 passengers were killed while the aircraft was destroyed by a post crash fire. First fatal accident involving an Embraer 190 and first accident at Yuchin Airport since it was open to traffic in 2009.
Probable cause:
- In violation of the airline's flight operation manual the captain attempted the approach to Yichun below required visibility. The airport reported 2800 meters of visibility while the manual required 3600 meters of visibility to begin the approach
- In violation of regulations by the Civil Aviation Authority the crew descended below minimum descent altitude although the aircraft was operating in fog and visual contact with the runway had not been established
- Despite the aural height announcements and despite not seeing the runway the crew continued the landing in the blind without initiating a go-around resulting in impact with terrain
Contributing factors were:
- The airline's safety management is insufficient:
* part of the flight crew arbitrarily implement the company's operations manual as the company does not follow up outstanding problems. Records suggest frequent deviations from approach profiles, i.e. deviation above or below glide slopes, excessive rates of descents and unstable approaches
* crew rostering and crew cooperation: Each of the crew was flying into Yichun for the first time despite the known safety risks at the airport, the communication and cooperation within the crew was insufficient, the crew members did not monitor each other in order to reduce human errors
* the airline's emergency training did not meet requirements, in particular the cabin crew training did not provide for hands on training on E190 cabin doors and overwing exits. Alternate means by the airline did prove ineffective and did not provide the quality China's Civil Aviation Authority requires thus leaving cabin crew unprepared to meet required cabin crew emergency response capabilities
- Parent company's Shenzhen Airlines oversight insufficient
* Shenzhen Airlines, after having taken over Henan Airlines in 2006, did not provide sufficient funding and technical support affecting the stability and safety of staff and quality management
* Air China, holding stock into Shenzhen Airlines, installed a safety supervisor but failed to address the safety management issues with Shenzhen and Henan Airlines
- No supervision by China's Civil Aviation Authority
* the license to operate the flight from Harbin to Yichun was granted without route validation and without safety management in violation of regulations
* to solve the lack of cabin crew flight attendants were certified although not meeting the relevant requirements for air transport operations
* the regional office of the Civil Aviation Authority did not communicate to their superiors that they had approved the domestic operation of the route from Harbin to Yichun permitting non-standard procedures
- China's Civil Aviation Authority safety management loopholes.

Crash of a McDonnell Douglas MD-11F in Shanghai: 3 killed

Date & Time: Nov 28, 2009 at 0814 LT
Type of aircraft:
Operator:
Registration:
Z-BAV
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Shanghai - Bishkek
MSN:
48408/457
YOM:
1990
Flight number:
SMJ324
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The three engine aircraft departed Shanghai-Pudong Airport on a cargo flight to Bishkek, carrying various goods and seven crew members. During the takeoff roll from runway 35L, the pilot-in-command initiated the rotation but the aircraft did not lift off properly with had a negative vario. It overran the runway and eventually crashed in an open field. Three crew were killed while four others were injured. The aircraft was totally destroyed.
Probable cause:
The crew did not properly operate the thrust levers so that the engines did not reach take off thrust. The aircraft had not reached Vr at the end of the runway and could not get airborne. According to the design criteria of the MD11 the crew needs to push at least two thrust levers to beyond 60 degrees, which will trigger autothrust to leave "CLAMP" mode and adjust the thrust to reach the target setting for takeoff, the servo motors would push the thrust levers forward in that case. During the accident departure the pilot in the left seat did not advance the thrust levers to more than 60 degrees, hence the server motors did not work although autothrust was engaged but remained in CLAMP mode and thus did not adjust the thrust to reach takeoff settings. The crew members perceived something was wrong. Audibly the engine sound was weak, visibibly the speed of the aircraft was low, tactically the pressure on the back of the seat was weaker than normal. Somebody within the crew, possibly on the observer seats, suggested the aircraft may be a bit heavy. The T/O THRUST page never appeared (it appears if autothrust is engaged and changes from CLAMP to Thrust Limit setting. Under normal circumstances with autothrust being engaged a click sound will occur as soon as the thrust levers reach the takeoff thrust position. A hand held on the thrust levers will feel the lever moving forward, however, the crew entirely lost situational awareness. None of the anomalies described in this paragraph prompted the crews members' attention. When the aircraft approached the end of the runway several options were available: reject takeoff and close the throttles, continue takeoff and push the throttle to the forward mechanical stop, continue takeoff and immediately rotate. The observer called "rotate", the captain rotated the aircraft. This shows the crew recognized the abnormal situation but did not identify the error (thrust levers not in takeoff position) in a hurry but reacted instinctively only. As the aircraft had not yet reached Vr, the aircraft could not get airborne when rotated. As verified in simulator verification the decision to rotate was the wrong decision. The simulator verification showed, that had the crew pushed the thrust levers into maximum thrust when they recognized the abnormal situation, they would have safely taken the aircraft airborne 670 meters before the end of the runway. The verification also proved, that had the crew rejected takeoff at that point, the aircraft would have stopped before the end of the runway. The crew did not follow standard operating procedures for managing thrust on takeoff. The crew operations manual stipulates that the left seat pilot advances the thrust levers to EPR 1.1 or 70% N1 (depending on engine type), informs the right seat pilot to connect autothrust. The pilot flying subsequently pushes the thrust levers forward and verifies they are moving forward on servos, the pilot monitoring verifies autothrust is working as expected and reaches takeoff thrust settings. In this case the left seat pilot not only did not continue to push the thrust levers forward, but also called out "thrust set" without reason as he did not verify the takeoff thrust setting had been achieved. It is not possible to subdivide the various violations of procedures and regulations. The crew had worked 16 hours during the previous sector. In addition, one crew member needed to travel for 11 hours from Europe to reach the point of departure of the previous sector (Nairobi Kenya), two crew members need to travel for 19 hours from America to the point of departure of the previous sector. These factors caused fatigue to all crew members. The co-pilot was 61 years of age, pathological examination showed he was suffering from hypertension and cardiovascular atherosclerosis. His physical strength and basic health may have affected the tolerance towards fatigue. All crew members underwent changes across multiple time zones in three days. Although being in the period of awakeness in their biological rhythm cycle, the cycle was already in a trough period causing increased fatigue. The captain had flown the Airbus A340 for 300 hours in the last 6 months, which has an entirely different autothrust handling, e.g. the thrust levers do not move with power changes in automatic thrust, which may have caused the captain to ignore the MD-11 thrust levers. The co-pilot in the right hand seat had been MD-11 captain for about 7 years but had not flown the MD-11 for a year. Both were operating their first flight for the occurrence company. The two pilots on the observer seats had both 0 flight hours in the last 6 months. The co-pilot (right hand seat) was pilot flying for the accident sector. The captain thus was responsible for the thrust management and thrust lever movement according to company manual. A surviving observer told the investigation in post accident interviews that the captain was filling out forms and failed to monitor the aircraft and first officer's actions during this critical phase of flight. There are significant design weaknesses in the MD-11 throttle, the self checks for errors as well as degree of automation is not high.
Source: Aviation Herald/Simon Hradecky

Crash of a Harbin Yunsunji Y-12-II near Chifeng: 3 killed

Date & Time: Jun 15, 2008
Type of aircraft:
Operator:
Registration:
B-3841
Flight Phase:
Survivors:
Yes
Site:
MSN:
0061
YOM:
1992
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The twin engine aircraft was engaged in an aluminium prospecting flight. In unknown circumstances, it collided with the slope of a mountain and was destroyed. A pilot survived while three other occupants were killed.

Crash of a Xian Yunsunji Y-7-100 near Hengshui: 2 killed

Date & Time: Oct 19, 2006 at 1400 LT
Type of aircraft:
Operator:
Flight Phase:
Flight Type:
Survivors:
Yes
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
While flying at low altitude, the crew made a sharp turn to avoid high tension cables. The aircraft went out of control and crash landed in a field located in the village of Lishan, near Hengshui. Four people were injured while both pilots were killed.

Crash of a Shaanxi Y-8 in Yao: 40 killed

Date & Time: Jun 3, 2006 at 1500 LT
Type of aircraft:
Operator:
Flight Phase:
Flight Type:
Survivors:
No
Location:
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
35
Pax fatalities:
Other fatalities:
Total fatalities:
40
Circumstances:
While cruising at an altitude of 8,000 metres, the crew encountered icing conditions. In unclear circumstances, the aircraft entered an uncontrolled descent, partially disintegrated in the air and eventually crashed in a bamboo forest located near Yao. The aircraft was totally destroyed and all 40 occupants were killed.

Crash of a Canadair RegionalJet CRJ-200LR in Baotou: 55 killed

Date & Time: Nov 21, 2004 at 0820 LT
Operator:
Registration:
B-3072
Flight Phase:
Survivors:
No
Schedule:
Baotou – Shanghai
MSN:
7697
YOM:
2002
Flight number:
CYH5210
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
55
Circumstances:
Shortly after takeoff from runway 13 at Baotou Airport, while in initial climb, the aircraft encountered difficulties to maintain a positive rate of climb. It stalled, collided with a small house and eventually crashed in the icy lake of the Nanhai Park. The wreckage was found about 2 km from the airport and all 53 occupants were killed as well as two people in the house.
Probable cause:
Loss of lift and subsequent stall after takeoff due to an excessive accumulation of ice and frost on wings, tail and fuselage. It was determined that the aircraft remained parked outside, on the ramp, all preceding night by negative temperature and that the crew failed to deice the airplane prior to takeoff.

Crash of an Ilyushin II-76TD in Ürümqi: 7 killed

Date & Time: May 18, 2004 at 1050 LT
Type of aircraft:
Registration:
4K-AZ27
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Taiyuan – Ürümqi – Baku – Riga
MSN:
00534 60827
YOM:
1985
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The aircraft was completing a cargo flight from Taiyuan to Riga with intermediate stops in Ürümqi and Baku, carrying seven crew members and a load of clothes. Two minutes after takeoff, while climbing, the aircraft stalled and crashed near a farm located 10 km from the airport. The aircraft was partially destroyed by impact forces and a post crash fire and all seven occupants were killed. Weather conditions were good at the time of the accident with a wind from 170 at 36 km/h.