Crash of an ATR42-320 in Puerto Ordaz: 17 killed

Date & Time: Sep 13, 2010 at 1023 LT
Type of aircraft:
Operator:
Registration:
YV1010
Survivors:
Yes
Schedule:
Porlamar - Puerto Ordaz
MSN:
371
YOM:
1994
Flight number:
VCV2350
Country:
Crew on board:
4
Crew fatalities:
Pax on board:
47
Pax fatalities:
Other fatalities:
Total fatalities:
17
Captain / Total hours on type:
1574.00
Copilot / Total flying hours:
1083
Copilot / Total hours on type:
483
Aircraft flight hours:
27085
Aircraft flight cycles:
29603
Circumstances:
Following two uneventful flights to Santiago Mariño and Maturín, the aircraft departed Porlamar on a flight to Puerto Ordaz with 47 passengers and a crew of four on board. While descending to Puerto Ordaz, at an altitude of 13,500 feet and at a distance of 79 km from the destination, the crew reported control difficulties. After being prioritized, the crew was instructed for an approach and landing on runway 07. At 1021LT, the crew reported his position at 3,000 feet and 28 km from the destination Airport. Two minutes later, the message 'mayday mayday mayday' was heard on the frequency. The aircraft went out of control and crashed in an industrial area located about 9 km short of runway, bursting into flames. Three crew members and 14 passengers were killed while 34 other occupants were injured, 10 seriously.
Probable cause:
The most probable cause for the occurrence of the accident was the malfunction of the centralized crew warning system (CCAS/CAC) with erroneous activation of the flight loss of lift warning system.
The following contributing factors were identified:
- Poor crew resources management,
- Loss of situational awareness,
- Inadequate coordination during the decision-making process to deal with abnormal situations in flight,
- Ignorance of the loss of lift warning system.
- Inadequate handling of flight controls.
Final Report:

Crash of a Fokker 100 in Tabriz

Date & Time: Aug 26, 2010 at 2245 LT
Type of aircraft:
Operator:
Registration:
EP-ASL
Survivors:
Yes
Schedule:
Tehran - Tabriz
MSN:
11432
YOM:
1992
Flight number:
EP773
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
103
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Tehran, the crew started the descent to Tabriz and was informed by ATC that visibility was low due to heavy rain falls. After landing on runway 30R (3,556 metres long), the aircraft was unable to stop within the remaining distance. It overran and rolled for about 500 metres before coming to rest in a ditch. All 110 occupants were rescued, among them two passengers were slightly injured. The aircraft was damaged beyond repair as the nose was destroyed and the bulkhead severely damaged.

Crash of an Embraer ERJ-145LU in Vitoria da Conquista

Date & Time: Aug 25, 2010 at 1440 LT
Type of aircraft:
Operator:
Registration:
PR-PSJ
Survivors:
Yes
Schedule:
São Paulo – Vitoria da Conquista
MSN:
145-351
YOM:
2000
Flight number:
PTB2231
Country:
Crew on board:
3
Crew fatalities:
Pax on board:
35
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4400
Captain / Total hours on type:
3100.00
Copilot / Total flying hours:
1373
Copilot / Total hours on type:
813
Circumstances:
While approaching Vitoria da Conquista Airport runway 15, the crew failed to realize his altitude was too low. On short final, the aircraft impacted a small mound located few metres short of runway threshold. On impact, both main landing gears were torn off. The aircraft slid on runway for about 300 metres then veered off runway to the left and came to rest in a grassy area some 35 metres left of the runway with the right engine on fire. All 38 occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The following factors were identified:
- During the approach, the flight crew's attention was focused on the characteristics of the geographical relief and presence of birds, reducing their awareness as to the maintenance of the approach slope.
- The group culture of maintaining a low angle of approach led the crew to choose the runway aspect instead of the VASIS as a reference for the approach, making them susceptible to various types of spatial illusion.
- Taking into account copilot's report that he was not succeeding in correcting the aircraft glide path relative to the runway, one may suppose that he was not applying the appropriate amplitude for such correction.
- The physical characteristics of the runway 15 (the active one) contributed to a wrong perception of the ideal glide path. The pronounced acclivity of the runway, its width (narrower than the runways on which the crew was accustomed to operate), and the low terrain near the threshold, caused in the pilots a perception that they were above the ideal approach slope, leading them to seek correction, which resulted in an angle of approach below the ideal one.
- For the flight in question, the company chose two pilots who had never operated in SBQV. A crewmember with previous experience in the locality would have a higher level of awareness in relation to the specific characteristics of the aerodrome.
- No company publications were found that could provide the pilots with guidance on the specifics of SBQV, capable of helping with the management of the risks associated with the operation in that aerodrome.
Final Report:

Crash of a Let L-410UVP-E20C in Bandundu: 20 killed

Date & Time: Aug 25, 2010 at 1400 LT
Type of aircraft:
Operator:
Registration:
9Q-CCN
Survivors:
Yes
Schedule:
Kinshasa - Kiri - Bokoro - Semendwa - Bandundu - Kinshasa
MSN:
91 26 08
YOM:
1991
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
18
Pax fatalities:
Other fatalities:
Total fatalities:
20
Circumstances:
On final approach to Bandundu Airport, the twin engine aircraft nosed down and crashed onto an earth made house. The aircraft was destroyed by impact forces and all occupants, except one passenger, were killed. According to the survivor, a passenger embarked illegally a crocodile he would sell to local market at Bandundu as 'bush meat'. On final approach, the animal went out of his bag and walked in the cabin. Panicked, the stewardess and several passengers departed their seats and rushed to the front of the cabin near the cockpit. After the CofG moved too far forward, the crew lost control of the aircraft that nosed down and crashed. The crocodile was later found unhurt but eventually killed by locals.
Probable cause:
Loss of control on final approach due to the movement of several passengers in the cabin, panicked by the presence of a crocodile.

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 Dornier DO228-101 near Kathmandu: 14 killed

Date & Time: Aug 24, 2010 at 0725 LT
Type of aircraft:
Operator:
Registration:
9N-AHE
Survivors:
No
Schedule:
Kathmandu - Lukla
MSN:
7032
YOM:
1985
Flight number:
AG101
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
14
Circumstances:
On approach to Lukla, the crew encountered poor weather conditions. Unable to locate the runway, he decided to divert to Simara Airport. Unfortunately, the visibility at Simara Airport was insufficient and the crew eventually decided to return to Kathmandu. While descending to runway 02, a generator failed. The crew did not declare an emergency, contacted his maintenance base and was unable to switch to the backup generator. Shortly after the crew elected to reset the battery system, the aircraft entered an uncontrolled descent and crashed in a rice paddy field. The aircraft disintegrated on impact and all 14 occupants were killed, among them 4 Americans, one British and one Japanese. The wreckage was found about 30 km southeast of Tribhuvan Airport.
Probable cause:
Loss of control on approach following the failure of a generator for undetermined reasons.

Crash of a Boeing 737-73V in San Andrés: 2 killed

Date & Time: Aug 16, 2010 at 0147 LT
Type of aircraft:
Operator:
Registration:
HK-4682
Survivors:
Yes
Schedule:
Bogotá – San Andrés
MSN:
32416/1270
YOM:
2002
Flight number:
ARE8250
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
125
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
7643
Captain / Total hours on type:
343.00
Copilot / Total flying hours:
1900
Copilot / Total hours on type:
800
Aircraft flight hours:
23485
Circumstances:
The aircraft departed Bogotá-El Dorado Airport at 0007LT on a night schedule service to San Andres Island, carrying 125 passengers and a crew of six. While approaching San Andres-Gustavo Rojas Pinilla Airport, the crew encountered poor weather conditions. Due to heavy rain falls, the crew was informed by ATC that the visibility dropped to 4 km. On short final, flaps were selected down to 30° then the autopilot system was deactivated. After passing 500 feet on approach, the captain repeated the procedures in case of a go-around would be needed due to windshear conditions. Shortly later, the copilot shouted 'go-around' but half a second later, the airplane impacted ground 49 metres short of runway. On impact, the undercarriage and both engines were torn off. The aircraft slid for few dozen metres before coming to rest, broken in three. Two passengers were killed while 129 other occupants were injured, nine seriously.
Probable cause:
Execution of the flight below the angle of approach, due to a misjudgment of the crew, believing to be much higher, leading the aircraft to fly a typical trajectory of a 'black hole' illusion, which was experienced during the night-time approach to a runway with low contrast surrounded in bright focused lights, aggravated by bad weather of heavy rain.
Final Report:

Crash of an Antonov AN-24RV in Igarka: 12 killed

Date & Time: Aug 3, 2010 at 0119 LT
Type of aircraft:
Operator:
Registration:
RA-46524
Survivors:
Yes
Schedule:
Krasnoyarsk - Igarka
MSN:
4 73 100 03
YOM:
1974
Flight number:
KTK9357
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
11
Pax fatalities:
Other fatalities:
Total fatalities:
12
Captain / Total flying hours:
17250
Captain / Total hours on type:
14205.00
Copilot / Total flying hours:
5838
Copilot / Total hours on type:
2670
Aircraft flight hours:
53760
Aircraft flight cycles:
38383
Circumstances:
The aircraft departed Krasnoyarsk on a night schedule flight to Igarka, carrying 11 passengers and 4 crew members. On approach to Igarka Airport, the crew encountered poor weather conditions with a visibility below minimums due to fog. On final, the pilot-in-command was unable to establish a visual contact with the ground but continued the approach. The aircraft descended below the glide, collided with trees and crashed 477 metres short of runway 12 and 234 metres to the right of its extended centerline, bursting into flames. All 11 passengers were killed while all four crew members survived. The following day, the stewardess died from her injuries.
Probable cause:
Controlled flight into terrain after the crew descended in IMC conditions below the glide without visual contact with the ground. The following contributing factors were identified:
- The failure of the crew to initiate a go-around procedure,
- Incorrect weather forecast with regards to cloud ceiling, visibility and severe weather (fog),
- Inaccurate information about the actual weather on the glide path at the Middle Marker with course 117°, radioed to the crew 40 minutes before the accident.
Final Report:

Crash of an ATR72-212A in Manila

Date & Time: Jul 28, 2010 at 1515 LT
Type of aircraft:
Operator:
Registration:
RP-C7254
Survivors:
Yes
Schedule:
Tuguegarao – Manila
MSN:
828
YOM:
2008
Flight number:
5J509
Country:
Region:
Crew on board:
0
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Cebu Pacific Air flight 5J509, an ATR 72-500, took off from Tuguegarao Airport, Philippines, bound for Manila-Ninoy Aquino International Airport. The first officer was the Pilot Flying (PF) while the captain was the Pilot Not Flying (PNF). Approaching Manila, the flight was under radar vector for a VOR/DME approach to runway 24. At 7 miles on finals the approach was stabilized. A sudden tailwind was experienced by the crew at 500 feet radio altitude (RA) which resulted in an increase in airspeed and vertical speed. The captain took over the controls and continued the approach. Suddenly, the visibility went to zero and consequently the aircraft experienced a bounced landing three times, before a go-around was initiated. During climb out the crew noticed cockpit instruments were affected including both transponders and landing gears. They requested for a priority landing and were vectored and cleared to land on runway 13. After landing the aircraft was taxied to F4 where normal deplaning was carried out. No injuries were reported on the crew and passengers.
Probable cause:
Primary Cause Factor:
- Failure of the flight crew to discontinue the approach when deteriorating weather and their associated hazards to flight operations had moved into the airport (Human Factor)
Contributory Factor:
- The adverse weather condition affected the judgment and decision-making of the PIC even prior to the approach to land. With poor weather conditions being encountered, the PIC still continued the approach and landing. (Environmental Factor)
Underlying Factor:
- As a result of the bounced landing, several cockpit instruments were affected including both transponders on board. One of the nosewheels was detached and all the landing gears could not be retracted. Further, the integrity of the structure may have been affected and chance airframe failure was imminent. With all of these conditions, the Captain still opted to request for a priority landing when emergency landing was needed.

Crash of an Airbus A321-231 in Islamabad: 152 killed

Date & Time: Jul 28, 2010 at 0941 LT
Type of aircraft:
Operator:
Registration:
AP-BJB
Survivors:
No
Site:
Schedule:
Karachi - Islamabad
MSN:
1218
YOM:
2000
Flight number:
ABQ202
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
146
Pax fatalities:
Other fatalities:
Total fatalities:
152
Captain / Total flying hours:
25497
Captain / Total hours on type:
1060.00
Copilot / Total flying hours:
1837
Copilot / Total hours on type:
286
Aircraft flight hours:
34018
Aircraft flight cycles:
13566
Circumstances:
Flight ABQ202, operated by Airblue, was scheduled to fly a domestic flight sector Karachi - Islamabad. The aircraft had 152 persons on board, including six crew members. The Captain of aircraft was Captain Pervez Iqbal Chaudhary. Mishap aircraft took-off from Karachi at 0241 UTC (0741 PST) for Islamabad. At time 0441:08, while executing a circling approach for RWY-12 at Islamabad, it flew into Margalla Hills, and crashed at a distance of 9.6 NM, on a radial 334 from Islamabad VOR. The aircraft was completely destroyed and all souls on board the aircraft, sustained fatal injuries.
Probable cause:
- Weather conditions indicated rain, poor visibility and low clouds in and around the airport. The information regarding prevalent weather and the required type of approach on arrival was in the knowledge of aircrew.
- Though aircrew Captain was fit to undertake the flight on the mishap day, yet his portrayed behavior and efficiency was observed to have deteriorated with the inclement weather at BBIAP Islamabad.
- The chain of events leading to the accident in fact started with the commencement of flight, where Captain was heard to be confusing BBIAP Islamabad with JIAP Karachi while planning FMS, and Khanpur Lake (Wah) with Kahuta area during holding pattern. This state continued when Captain of the mishap flight violated the prescribed Circling Approach procedure for RWY-12; by descending below MDA (i.e 2,300 ft instead of maintaining 2,510 ft), losing visual contact with the airfield and instead resorting to fly the non-standard self created PBD based approach, thus transgressing out of protected airspace of maximum of 4.3 NM into Margallas and finally collided with the hills.
- Aircrew Captain not only clearly violated the prescribed procedures for circling approach but also did not at all adhere to FCOM procedures of displaying reaction / response to timely and continuous terrain and pull up warnings (21 times in 70 seconds) – despite these very loud, continuous and executive commands, the Captain failed to register the urgency of the situation and did not respond in kind (break off / pull off).
- F/O simply remained a passive bystander in the cockpit and did not participate as an effective team member failing to supplement / compliment or to correct the errors of his captain assertively in line with the teachings of CRM due to Captain’s behavior in the flight.
- At the crucial juncture both the ATC and the Radar controllers were preoccupied with bad weather and the traffic; the air traffic controller having lost visual contact with the aircraft got worried and sought Radar help on the land line (the ATC does not have a Radar scope); the radar controller having cleared aircraft to change frequency to ATC, got busy with the following traffic. Having been alerted by the ATC, the Radar controller shifted focus to the mishap aircraft – seeing the aircraft very close to NFZ he asked the ATCO (on land line) to ask the aircraft to immediately turn left, which was transmitted. Sensing the gravity of the situation and on seeing the aircraft still heading towards the hills, the Radar controller asked the ATCO on land line “Confirm he has visual contact with the ground. If not, then ask him to immediately climb, and make him execute missed approach”. The ATCO in quick succession asked the Captain if he had contact with the
airfield – on receiving no reply from aircrew the ATCO on Radars prompting asked if he had contact with the ground. Aircrew announced visual contact with the ground which put ATS at ease.
Ensuing discussion and mutual situational update (on land line) continued and, in fact, the ATC call “message from Radar immediately turn left” was though transmitted, but by the time the call got transmitted, the aircraft had crashed at the same time.
- The accident was primarily caused by the aircrew who violated all established procedures for a visual approach for RWY-12 and ignored several calls by ATS Controllers and EGPWS system warnings (21) related to approaching rising terrain and PULL UP.
Final Report: