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 Antonovv AN-26B in Tallinn

Date & Time: Aug 25, 2010 at 1747 LT
Type of aircraft:
Operator:
Registration:
SP-FDP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
EXN3788
MSN:
119 03
YOM:
1982
Flight number:
Tallinn - Helsinki
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5569
Captain / Total hours on type:
4432.00
Copilot / Total flying hours:
738
Copilot / Total hours on type:
485
Aircraft flight hours:
21510
Circumstances:
On 25th August 2010 cargo aircraft An-26B, registration SP-FDP started from Tallinn-Lennart Meri-Ülemiste Airport to Helsinki. After uneventful flight preparations, the aircraft started its take-off roll on runway 08. Based on pilots statements and FDR/CVR recordings the aircraft entered runway 08 from taxiway B on the West end of the runway and lined up for takeoff. On 16:47:22 the aircraft started its takeoff roll. The calculated V1 was 182 and Vr was 201 km/h. 10 seconds later PF started rotation without Vr callout at 123 km/h. The aircraft pitch angle increased to 4.6˚ 2 seconds later. At 16:47:38 the navigator made V1 call-out at 160.5 km/h. 1 second later flight engineer called “Retracting” in Polish. The aircraft started to pitch down and 3 seconds later it contacted the runway and continued on its belly for 1,228 m before coming to its rest position 3 m right from the runway centerline. No persons were injured and no fire broke up. The occurrence was classified as an accident due to the substantial damage to the aircraft structures.
Probable cause:
The investigation determined the inadequate action of the flight engineer, consisting in early and uncommanded landing gear retraction, as a cause of the accident.
Contributing factors to the accident were:
1. Inadequate crew recourse management and insufficient experience in cooperation and coordination between crewmembers.
2. Start of aircraft rotation at low speed and with fast elevator movement to 17˚, which resulted in:
Lifting the aircraft sufficiently to close the WOW switch and allow the retraction of the landing gear at the speed not sufficient for the climb.
Providing misleading information to FE about the aerodynamic status of the aircraft.
3. Inadequate adjustment of the WOW switch, which allowed the gear retraction to be activated before the aircraft was airborne. The position of the landing gear selector on the central console is not considered as a contributing factor to the accident. However, investigation finds necessary to point it out as a safety concern, specifically in situations, where crewmembers are trained and/or used to operate the aircrafts with gear selector location according to the EASA Certification Standards CS-25. Positioning of the gear lever to the location which is compliant to EASA document CS-25, would create additional safety barrier to avoid similar occurrences, specifically in aircrafts where landing gear is operated by FE.
Final Report:

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 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 a Piper PA-42-1000 Cheyenne 400LS in Mercedes

Date & Time: Aug 13, 2010 at 1530 LT
Type of aircraft:
Operator:
Registration:
LQ-BLU
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mercedes - La Plata
MSN:
42-5527037
YOM:
1987
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4294
Captain / Total hours on type:
390.00
Copilot / Total flying hours:
2827
Copilot / Total hours on type:
14
Aircraft flight hours:
1526
Circumstances:
During the takeoff roll on runway 19 at Mercedes Airport, the twin engine aircraft deviated to the right then to the left. Control was lost and the aircraft veered off runway to the left, lost its undercarriage and came to rest in bushed with its left wing partially torn off. All four occupants escaped uninjured while the aircraft was damaged beyond repair. Both passengers were Ricardo Casal, Minister of Justice and Security, and Maria del Carmen Falbo, Attorney.
Probable cause:
Loss of control during takeoff following the crew's decision to perform the operation outside of the procedures established in the flight manual. The overconfidence of the crew as well as the operation of both engines at low regime were considered as contributing factors.
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 a McDonnell Douglas C-17A Globemaster III at Elmendorf AFB: 4 killed

Date & Time: Jul 28, 2010 at 1822 LT
Operator:
Registration:
00-0173
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Elmendorf AFB - Elmendorf AFB
MSN:
P-73
YOM:
2000
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Circumstances:
The crew was engaged in a training exercise in preparation to the 'Thunder Air Show' taking part at Elmendorf-Richardson AFB on 31JUL2010. Shortly after take off from runway 06, the pilot-in-command initiated a first turn to the left then a steep turn to the right when the aircraft entered an uncontrolled descent and crashed in a huge explosion in a wooded area located some 3 km northwest of the airbase. The aircraft was totally destroyed by impact forces and a post crash fire and all four crew members were killed.
Probable cause:
The board president found clear and convincing evidence that the cause of the mishap was pilot error. The pilot violated regulatory provisions and multiple flight manual procedures, placing the aircraft outside established flight parameters at an attitude and altitude where recovery was not possible. Furthermore, the copilot and safety observer did not realize the developing dangerous situation and failed to make appropriate inputs. In addition to multiple procedural errors, the board president found sufficient evidence that the crew on the flight deck ignored cautions and warnings and failed to respond to various challenge and reply items. The board also found channelized attention, overconfidence, expectancy, misplaced motivation, procedural guidance, and program oversight substantially contributed to the mishap.

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.