Crash of a Boeing 737-4Q8 in Antalya

Date & Time: Oct 10, 2011 at 1315 LT
Type of aircraft:
Operator:
Registration:
TC-SKF
Survivors:
Yes
Schedule:
Karlsruhe-Baden-Baden – Antalya
MSN:
26291/2513
YOM:
1993
Flight number:
SHY8756
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
156
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Karlsruhe-Baden-Baden, the crew started the descent to Antalya Airport runway 18C and completed the landing checklist. After touchdown, the aircraft started to vibrate and deviated to the right. Suddenly, the right main gear collapsed , causing the right engine nacelle to struck the ground. Metal rub the ground and a fire erupted in the right main wheel well. The aircraft eventually came to a complete stop, slightly to the right of the centerline. All 162 occupants evacuated safely while the aircraft was damaged beyond repair.
Probable cause:
It seems that a tyre on the right main gear burst after touchdown, causing the gear to collapse. A fire erupted, caused by the rubbing of the engine nacelle on ground.

Crash of a Cessna 550 Citation II in Manhuaçu

Date & Time: Oct 7, 2011 at 1738 LT
Type of aircraft:
Registration:
PT-LJJ
Survivors:
Yes
Schedule:
Belo Horizonte – Manhuaçu
MSN:
550-0247
YOM:
1981
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4300
Captain / Total hours on type:
1200.00
Copilot / Total flying hours:
8000
Copilot / Total hours on type:
100
Circumstances:
The aircraft departed Belo Horizonte-Pampulha on an executive flight to Manhuaçu, carrying two pilots and three passengers, among them the Brazilian singer Eduardo Costa. Following an uneventful flight, the crew started the descent to Manhuaçu-Elias Breder Airport. After touchdown on runway 02, the crew activated the reverse thrust systems but the aircraft did not decelerate as expected. So the crew started to brake when the tires burst. Unable to stop within the remaining distance, the aircraft overran, lost its undercarriage, collided with a fence and came to rest. There was no fire. All five occupants were rescued. Nevertheless, Eduardo Costa broke his nose and right hand during the accident.
Probable cause:
Late use of the normal brake systems on part of the crew after landing, causing the aircraft to overran. The captain had the habit of braking the aircraft while using the reverse thrust systems only in order to save the braking systems. Doing so, the use of the normal brakes was delayed.
Final Report:

Crash of a Cessna 207A Stationair 7 in Matinicus Island: 1 killed

Date & Time: Oct 5, 2011 at 1730 LT
Operator:
Registration:
N70437
Flight Type:
Survivors:
No
Schedule:
Rockland - Matinicus Island
MSN:
207-0552
YOM:
1980
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3100
Aircraft flight hours:
17106
Circumstances:
About the time of departure, the wind at the departure airport was reported to be from 330 degrees at 13 knots with gusts to 22 knots. The pilot departed with an adequate supply of fuel for the intended 15-minute cargo flight to a nearby island. He entered a left traffic pattern to runway 36 at the destination airport and turned onto final approach with 30 degrees of flaps extended. Witnesses on the island reported that, about this time, a sudden wind gust from the west occurred. A witness (a fisherman by trade) at the airport estimated the wind direction was down the runway at 35 to 40 knots, with slightly higher wind gusts. After the sudden wind gust, he noted the airplane suddenly bank to the right about 80 degrees and begin descending. It impacted trees and powerlines then the ground. The same witness reported the engine sound was steady during the entire approach and at no time did he hear the engine falter. About 30 minutes before the accident, a weather observing station located about 6 nautical miles south-southeast of the accident site indicated the wind from the north-northwest at 24 knots, with gusts to 27 knots. About 30 minutes after the accident, the station indicated the wind from the northwest at 30 knots, with gusts to 37 knots. Postaccident examination of the airplane, its systems, and engine revealed no evidence of preimpact failures or malfunctions that would have precluded normal operation. The evidence is consistent with the airplane’s encounter with a gusty crosswind that led to the airplane’s right bank and the pilot’s loss of control, resulting in an accelerated stall.
Probable cause:
The pilot’s failure to maintain airplane control during the approach after encountering a gusty crosswind, which resulted in an accelerated stall and uncontrolled descent.
Final Report:

Ground accident of a Dassault Falcon 20F in Newnan

Date & Time: Oct 3, 2011
Type of aircraft:
Registration:
XA-NCC
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
264
YOM:
1972
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
A technician was in charge to ferry the airplane to a hangar for a maintenance control. While taxiing, the Falcon went out of control, rolled down an embankment and collided with a utility pole. The nose was severely damaged and the aircraft was damaged beyond repair. According to the technician, who escaped uninjured, the brakes failed while taxiing.
Probable cause:
No investigation was conducted by the NTSB.

Crash of a Fokker 50 in Khartoum

Date & Time: Oct 2, 2011
Type of aircraft:
Operator:
Registration:
ST-ASD
Survivors:
Yes
Schedule:
Khartoum – Malakal
MSN:
20201
YOM:
1990
Flight number:
SD312
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
41
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Khartoum, the crew started the descent to Malakal, completed the checklist and lowered the landing gear. A technical problem occurred with the left main gear that remained stuck in its wheel well and failed to deploy. The crew decided to return to Khartoum. On approach to Khartoum-Haj Yusuf Airport runway 18, the crew elected to lower the gear manually but without success. The aircraft landed with both nose and right main gear deployed. After touchdown, the left wing contacted the runway surface. The aircraft slid for about 1,350 metres then veered to the left and came to rest. All 45 occupants evacuated safely and the aircraft was later considered as damaged beyond repair.

Crash of a Mitsubishi MU-2B-25 Marquise in Cobb County

Date & Time: Sep 28, 2011 at 1715 LT
Type of aircraft:
Registration:
N344KL
Survivors:
Yes
Schedule:
Huntsville - Cobb County
MSN:
257
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
11100
Captain / Total hours on type:
1500.00
Aircraft flight hours:
6196
Circumstances:
The pilot stated that after landing, the nose landing gear collapsed. Examination of the airplane nose strut down-lock installation revealed that the strut on the right side of the nose landing gear trunnion was installed incorrectly; the strut installed on the right was a left-sided strut. Incorrect installation of the strut could result in the bearing pulling loose from the pin on the right side of the trunnion, which could allow the nose landing gear to collapse. A review of maintenance records revealed recent maintenance activity on the nose gear involving the strut. The design of the strut is common for the left and right. Both struts have the same base part number, and a distinguishing numerical suffix is added for left side and right side strut determination. If correctly installed, the numbers should be oriented facing outboard. The original MU-2 Maintenance Manual did not address the installation or correct orientation of the strut. The manufacturer issued MU-2 Service Bulletin (SB) No. 200B, dated June 24, 1994, to address the orientation and adjustment. Service Bulletin 200B states on page 8 of 10 that the “Part Number may be visible in this (the) area from the out board sides (Inked P/N may be faded out).”
Probable cause:
The improper installation of the nose landing gear strut and subsequent collapse of the nose landing gear during landing.
Final Report:

Crash of a Douglas DC-9-51 in Puerto Ordaz

Date & Time: Sep 26, 2011 at 0922 LT
Type of aircraft:
Operator:
Registration:
YV136T
Survivors:
Yes
Schedule:
Caracas – Puerto Ordaz
MSN:
47738/830
YOM:
1976
Flight number:
VH342
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
125
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
14000
Copilot / Total flying hours:
275
Aircraft flight hours:
71817
Circumstances:
The aircraft departed Caracas-Maiquetía-Simón Bolívar Airport on a schedule service to Puerto Ordaz, carrying 125 passengers and a crew of 5. On this flight, the copilot was the PIC with the captain acting as instructor and a second copilot who was seating in the jump seat and acting as an observer. During the takeoff roll from Caracas Airport, the liftoff was completed quickly, causing the base of the empennage to struck the runway surface (tail strike). Nevertheless, the captain decided to proceed to Puerto Ordaz. On final to Puerto Ordaz, the approach speed was too low (123,8 knots). The aircraft sank and landed hard, causing the fuselage to be bent at the aft cabin, just prior to the tail, and both engine pylons to fail and to break from the fuselage. The aircraft was brought to a stop on the main runway and all 130 occupants evacuated safely.
Probable cause:
The accident investigators, taking into account the characteristics of the accident and the evidence collected in the course of the investigation, considered the Human Factor as the reason for this accident, being able to demonstrate convincingly the following causes:
- There was a breach of the provisions in Chapter 4 (flight operations policies), paragraph 6 (sterile cabin) of the Operations Manual of the airline due to carrying out activities that were not related to the conduct of the flight.
- Lack of situational awareness of the Flight Instructor, the observer pilot and the first officer.
- The captain performed other duties, adding to the duties already being accomplished in his role as a flight instructor.
Final Report:

Crash of a Beechcraft 1900D in Kathmandu: 19 killed

Date & Time: Sep 25, 2011 at 0731 LT
Type of aircraft:
Operator:
Registration:
9N-AEK
Survivors:
No
Schedule:
Kathmandu - Kathmandu
MSN:
UE-295
YOM:
1997
Flight number:
BHA103
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
16
Pax fatalities:
Other fatalities:
Total fatalities:
19
Copilot / Total hours on type:
18
Circumstances:
The aircraft was performing a special flight with tourists above the Himalayan mountains and especially a tour of the Everest in the early morning. While returning to Kathmandu-Tribhuvan Airport, the copilot (PIC) was cleared to descend to 6,000 feet for a landing on runway 02. In marginal weather conditions, he passed below 6,000 feet until the aircraft contacted trees and crashed in hilly and wooded terrain located near the village of Bishanku Narayan, some 6,7 km southeast of the airport. The aircraft was destroyed by impact forces and a post crash fire. A passenger was seriously injured while 18 other occupants were killed. Few hours later, the only survivor died from his injuries. The 16 tourists were respectively 10 Indians, 2 Americans, 1 Japanese and 3 Nepalese.
Probable cause:
The Accident Investigation Commission assigned by Nepal's Ministry of Tourism and Civil Aviation have submitted their report to the Ministry. The investigators said in a media briefing, that human factors, mainly fatigue by the captain of the flight, led to the crash. The aircraft was flown by the first officer and was on approach to Kathmandu at 5,000 feet MSL instead of 6,000 feet MSL as required, when it entered a cloud. While inside the cloud in low visibility the aircraft descended, hit tree tops and broke up. The captain had flown another aircraft the previous day and had been assigned to the accident flight on short notice in the morning of the accident day, but did not have sufficient rest. The commission analyzed that due to the resulting fatigue the captain assigned pilot flying duties to the first officer although she wasn't yet ready to cope with the task in demanding conditions. The newly assigned first officer had only 18 hours experience on the aircraft type. The mountain view round trip had to turn back about midway due to weather conditions. While on a visual approach to Kathmandu at 5,000 instead of 6,000 feet MSL the aircraft entered a cloud and started to descend until impact with tree tops. The crew did not follow standard operating procedures, that amongst other details required the aircraft to fly at or above 6,000 feet MSL in the accident area, the interaction between the crew members did not follow standard operating procedures, for example the captain distracted the first officer with frequent advice instead of explaining the/adhering to procedures. The commission said as result of the investigation they released a safety recommendation requiring all operators to install Terrain Awareness and Warning Systems (TAWS) in addition to eight other safety recommendations regarding pilot training, installation of visual aids, safety audit and fleet policies.

Crash of a Beechcraft B90 King Air in Hillsboro

Date & Time: Sep 17, 2011 at 1145 LT
Type of aircraft:
Registration:
N125A
Survivors:
Yes
Schedule:
Hillsboro - Hillsboro
MSN:
LJ-360
YOM:
1968
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1900
Captain / Total hours on type:
200.00
Aircraft flight hours:
9254
Circumstances:
While landing, the airplane touched down short of the runway, the left main landing gear impacted the edge of the runway and collapsed, and the airplane departed the edge of the runway into a culvert. The airplane’s left wing sustained substantial damage.
Probable cause:
The pilot's failure to obtain a proper touchdown point, which resulted in a runway undershoot.
Final Report:

Crash of an Embraer ERJ-190AR in Quito

Date & Time: Sep 16, 2011 at 1911 LT
Type of aircraft:
Operator:
Registration:
HC-CEZ
Survivors:
Yes
Schedule:
Loja - Quito
MSN:
190-00027
YOM:
2006
Flight number:
EQ148
Country:
Crew on board:
6
Crew fatalities:
Pax on board:
97
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6160
Captain / Total hours on type:
1879.00
Copilot / Total flying hours:
4891
Copilot / Total hours on type:
2807
Aircraft flight hours:
8752
Aircraft flight cycles:
13285
Circumstances:
Following an uneventful flight from Loja, the crew started the descent to Quito-Mariscal Sucre Airport runway 35 by night and poor weather conditions. After touchdown on wet runway 35, the aircraft encountered difficulties to decelerate properly. Unable to stop within the remaining distance, the airplane overran, went down an embankment, collided with a brick wall and came to rest. There was no fire. All 103 occupants were rescued, among them four passengers were slightly injured. The aircraft named 'Ciudad de Cuenca' was damaged beyond repair.
Probable cause:
The Board of Inquiry estimated that the probable cause of this accident was the crew's decision to continue the approach and landing without carrying out the procedures (ABNORMAL AND EMERGENCY PROCEDURES) established by Embraer in the Quick Reference Handbook when a malfunction occurred with the slat/flap system, resulting in a wrong approach configuration.
The following findings were identified:
- The slats were inoperative during the approach and the crew performed five trouble shooting without success,
- Despite this situation, the crew decided to continue the approach, failed to follow the approach checklist and failed to input the reference speed and distance for landing according to circumstances,
- The aircraft landed too far down the runway, about 880 metres past the runway 35 threshold,
- The braking action was low because the runway surface was wet,
- In normal conditions, with flaps down in second position and slats out, the landing reference speed was 119 knots with a landing distance of 880 metres,
- Because the slats were inoperative, the landing reference speed should be 149 knots and a landing distance of 1,940 metres was needed,
- The aircraft passed over the runway threshold at a height of 50 feet and at an excessive speed of 163,8 knots,
- Spoilers were activated 9 seconds after touchdown, 950 metres after the runway threshold,
- Reverse thrust systems were activated 1,280 metres after the runway threshold,
- The crew started to use brakes 2,300 metres after the runway threshold (runway 35 is 3,125 metres long), with the antiskid system activated,
- Due to an excessive approach speed (15 knots above Vref), a too long flare and a too late application of the brake systems, the aircraft could not be stopped within the remaining distance,
- The slats malfunction was the consequence of the failure of several actuators which did not support negative temperatures met during the last flight,
- Since last July 19, the slats failed 53 times on this aircraft, six times during the approach and 47 times in flight,
- The crew failed to initiate a go-around procedure.