Crash of a Piper PA-46-500TP Meridian in Omaha: 1 killed

Date & Time: Dec 10, 2015 at 1153 LT
Registration:
N145JR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Omaha - Trinidad
MSN:
46-97166
YOM:
2003
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4840
Captain / Total hours on type:
280.00
Aircraft flight hours:
1047
Circumstances:
The private pilot was conducting a personal cross-country flight. Shortly after takeoff, the pilot told the air traffic controller that he needed to return to the airport due to an attitude heading reference system (AHRS) "miscommunication." Air traffic control radar data indicated that, at that time, the airplane was about 1.75 miles north of the airport on a southeasterly course about 2,000 ft. mean sea level. About 20 seconds after the pilot requested to return to the airport, the airplane began to descend. The airplane subsequently entered a right turn, which appeared to continue until the final radar data point. The airplane struck power lines about 3/4 of a mile from the airport while maneuvering within the traffic pattern. The power lines were about 75 ft. above ground level. A postaccident examination of the airframe and engine revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. Although the pilot reported a flight instrumentation issue to air traffic control, the investigation was unable to confirm whether such an anomaly occurred based on component testing and available information. Examination of the standby airspeed indicator revealed that the link arm had separated from the pin on the rocking shaft assembly; however, it likely separated during the accident sequence. No other anomalies were observed. Functional testing indicated that the standby airspeed indicator was likely functional and providing accurate airspeed information to the pilot throughout the flight. Finally, examination of the left and right annunciator panel bulb filaments associated with the left fuel pump advisory revealed that they were stretched, indicating that the left fuel pump advisory indication annunciated at the time of the accident; however, this likely occurred during the accident sequence as a result of an automatic attempt to activate the left fuel pump due to the loss of fuel pressure immediately after the left wing separated. Toxicology testing of the pilot detected low levels of three different sedating antihistamines; however, antemortem levels could not be determined nor could the underlying reason(s) for the pilot's use of these medications. As a result, it could not be determined whether pilot impairment occurred due to the use of the medications or the underlying condition(s) themselves. Although the pilot reported a flight instrumentation issue, this problem would not have affected his ability to control the airplane. Further, the pilot should have been able to see the power lines given the day/visual weather conditions. It is possible that the pilot become distracted by the noncritical anomaly, which resulted in his failure to maintain clearance from the power lines.
Probable cause:
The pilot's failure to maintain clearance from power lines while returning to the airport after becoming distracted by a noncritical flight instrumentation anomaly indication.
Final Report:

Crash of a Cessna 340A in Augsburg

Date & Time: Dec 8, 2015 at 0942 LT
Type of aircraft:
Operator:
Registration:
D-IBEL
Flight Type:
Survivors:
Yes
Schedule:
Mönchengladbach – Augsburg
MSN:
340A-1814
YOM:
1984
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5188
Captain / Total hours on type:
75.00
Aircraft flight hours:
3747
Circumstances:
The twin engine aircraft departed Mönchengladbach on a flight to Augsbourg, carrying four passengers and one pilot. On descent to Augsburg Airport, the pilot was informed by ATC that weather conditions at destination were worse than predicted, that the visibility was estimated between 225 and 250 metres, thus below minimums. The pilot acknowledged and informed ATC about his intention to attempt an approach and that he would divert to Oberpfaffenhofen if necessary. On short final, at a height of 200 feet, the pilot established a visual contact with the runway lights and decided to continue. After passing over the threshold, he reduced the engine power when the aircraft entered a stall and impacted the runway surface. On impact, the undercarriage were torn off and the aircraft slid for 104 metres before coming to rest, bursting into flames. Four occupants were seriously injured and the fifth was slightly injured. The aircraft was partially destroyed by a post crash fire.
Probable cause:
The accident is the consequence of the pilot's decision to continue the approach and not to initiate a go-around procedure, which resulted in the aircraft entering an attitude he was unable to control. Poor approach planning on part of the pilot and poor decision making during the approach contributed to the accident, as well as the fact that the runway visual range (RVR) was 250 metres, which was below minimums.
Final Report:

Crash of a De Havilland DHC-8-402Q in Jabalpur

Date & Time: Dec 4, 2015 at 1922 LT
Operator:
Registration:
VT-SUC
Survivors:
Yes
Schedule:
Mumbai – Jabalpur
MSN:
4377
YOM:
2011
Flight number:
SG2458
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
49
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7748
Captain / Total hours on type:
2148.00
Copilot / Total flying hours:
7804
Copilot / Total hours on type:
137
Aircraft flight hours:
11928
Aircraft flight cycles:
11214
Circumstances:
Bombardier Q-400 aircraft VT-SUC belonging to M/s Spice jet Ltd. was involved in wild life strike accident during landing roll at Jabalpur while operating scheduled flight SG2458 from Mumbai to Jabalpur on 04.12.2015. The aircraft was under the command of pilot holding ATPL & duly qualified on type with First Officer also an ATPL holder and qualified on type. There were 49 passengers and 02 cabin crew on board the aircraft. The aircraft VT-SUC took-off from Mumbai for Jabalpur at around 1200 UTC. The enroute flight was uneventful. The aircraft came in contact with ATC Jabalpur at around 1323 UTC. The ATC reported prevailing weather at Jabalpur as surface winds calm, visibility 5000 meters, weather Haze, nonsignificant clouds, and temp 24° C. At 1342 UTC the pilot requested ATC for visual approach runway 06. The ATC cleared VT-SUC for visual approach runway 06 and asked to confirm when runway in sight. At 1347 UTC the pilot confirmed the runway in sight and requested for landing clearance and the same was acknowledged by ATC. The aircraft landed on runway 06 and about 05 to 06 seconds after touch down at around 1350 UTC the aircraft hit wild boars on the runway. The pilot stated that as it was dawn they did not see the wild boars on runway during approach, and saw the wild boars only after touch down and when they were very close to them, also they did not had adequate time to react so as to take any evasive action. Hence, one of the wild boars on runway impacted with LH main landing gear due which the LH Main landing gear got collapsed and the aircraft started drifting towards left. Thereafter LH engine propeller blades came in contact with ground and got sheared off. The aircraft dragged on its belly for around 182 feet and in the process the nose landing gear also collapsed. The aircraft then veered to the left of the center line and subsequently exited the runway onto the left side and came to final halt position in Soft Ground. The pilot then confirmed with first officer about fire and once getting assured that there was no fire gave evacuation call outs. The pilot then contacted ATC for assistance and informed that there were 10 to 11 pigs on the runway and the aircraft had hit the pig and gone off the runway. The Crash Fire Tender (CFT) team along with operational jeep reached the accident site. The pilot shut down the engines. All the passengers were then evacuated safely from the RH side. There was no injury to any of the occupants on board the aircraft and there was no fire.
Probable cause:
The aircraft during its landing roll had a wild life (Wild Boars) strike on the runway, resulting in collapse of left main landing gear and subsequently the aircraft veered to the left of the runway.
Contributory factor:
The presence of wild life in the operational area and the runway was due to several breaches in the boundary wall.
Final Report:

Crash of a BAe 125-800SP in Palm Springs

Date & Time: Dec 4, 2015 at 1420 LT
Type of aircraft:
Registration:
N164WC
Flight Type:
Survivors:
Yes
Schedule:
Palm Springs – Boise
MSN:
258072
YOM:
1986
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
2500
Circumstances:
After takeoff from Palm Springs Airport, while on a positioning flight to Boise, the crew encountered technical problems with the undercarriage. Following a holding circuit, the crew decided to return to Palm Springs and to complete a gear up landing. Upon touchdown, the aircraft slid on its belly for few dozen metres before coming to rest. Both pilots evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
No investigations completed by the NTSB.

Crash of a Piper PA-46-350P Malibu Mirage in Mammoth Lakes

Date & Time: Dec 3, 2015 at 1220 LT
Operator:
Registration:
N546C
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mammoth Lakes - Mammoth Lakes
MSN:
46-36626
YOM:
2014
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4000
Captain / Total hours on type:
2000.00
Aircraft flight hours:
230
Circumstances:
According to the pilot, he checked the winds via his onboard weather reporting device during the run-up, and he stated that the 25 knot wind sock was about ¾ full just moments before the takeoff roll. He reported that during the takeoff roll the airplane encountered a significant wind gust from the right. He stated that the wind gust forced the airplane to exit the left side of the runway, the landing gear collapsed, and the airplane collided with metal pylons which surrounded the wind sock. The airplane sustained substantial damage to both wings, fuselage, horizontal stabilizer and elevator. The pilot reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal flight operation. According to the Airport/Facility Directory, the Airport Remarks state: Airport located in mountainous terrain with occasional strong winds and turbulence. Lighted windsock available at runway ends and centerfield. With southerly crosswinds in excess of 15 knots, experiencing turbulence and possible windshear along first 3000´ of Runway 27. The reported wind at the airport during the time of the accident was from 200 degrees true at 22 knots, with gusts at 33 knots, and the departure runway heading was 27. According to the pilot operating hand book the maximum demonstrated crosswind component for this airplane is 17 knots. The crosswind component during the time of the accident was 26 knots.
Probable cause:
The pilot's decision to takeoff in high crosswind conditions resulting in the inability to maintain an adequate crosswind correction, consequently failing to maintain directional control and departing the runway, and subsequently colliding with fixed airfield equipment.
Final Report:

Crash of a Boeing 737-322 in Mexico City

Date & Time: Nov 26, 2015 at 1828 LT
Type of aircraft:
Operator:
Registration:
XA-UNM
Survivors:
Yes
Schedule:
Cancún – Mexico City
MSN:
24248/1636
YOM:
1988
Flight number:
GMT779
Country:
Crew on board:
5
Crew fatalities:
Pax on board:
139
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
12945
Copilot / Total flying hours:
7606
Aircraft flight hours:
64171
Aircraft flight cycles:
39245
Circumstances:
The aircraft departed Cancún on a regular schedule flight to Mexico City, carrying 139 passengers and five crew members. The flight was uneventful. Following an unstabilized approach, the aircraft landed on runway 05L at an excessive speed. After touchdown, severe vibrations occurred when the left main gear collapsed after a course of 1,097 metres. The airplane slid for 980 metres before coming to rest. All 144 occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Fracture of the shimmy damper piston and subsequent retraction of the left leg assembly of the landing gear due to vibrations caused during the landing run, which could not be damped due to wear and play existing between the dynamic parts of the links, fittings and apex joint of the shimmy damper.
The following contributing factors were identified:
- Unstabilized approach,
- Inadequate service to shimmy damper and shock strut,
- Landing with a low rate of descent,
- Wear in the Apex joint due to a play between this and the lower torsion link,
- Landing with high ground speed and low descent rate.
Final Report:

Crash of a Boeing 737-3Y0 in Osh

Date & Time: Nov 22, 2015 at 0800 LT
Type of aircraft:
Operator:
Registration:
EX-37005
Survivors:
Yes
Schedule:
Krasnoyarsk – Osh
MSN:
24681/1929
YOM:
1990
Flight number:
AVJ768
Location:
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
148
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10600
Captain / Total hours on type:
6362.00
Copilot / Total flying hours:
16400
Copilot / Total hours on type:
3731
Aircraft flight hours:
50668
Aircraft flight cycles:
43958
Circumstances:
The crew departed Krasnoyarsk-Yemilianovo Airport on a night flight to Osh, Kyrgyzstan. En route, he was informed that a landing in Osh was impossible to due low visibility caused by foggy conditions. The captain decided to divert to Bishkek-Manas Airport where the aircraft landed safely at 0520LT. As weather conditions seems to improve at destination, the crew left Bishkek bound for Osh some ninety minutes later. On approach to Osh, the vertical visibility was reduced to 130 feet when the aircraft hit violently the runway 12 surface. Upon impact, the left main gear was sheared off, the aircraft slid for several yards, overran, hit obstacles and came to rest in a field located 529 meters past the runway end with its left engine detached and its right engine destroyed. All 154 occupants were evacuated, ten passengers were injured, six of them seriously. The aircraft was damaged beyond repair.
Probable cause:
It was determined that the accident occurred in poor weather conditions with an horizontal visibility reduced to 50 meters and a vertical visibility limited to 130 feet. It was reported that the accident was caused by the combination of the following factors:
- the crew decided to leave Bishkek Airport for Osh without taking into consideration the weather forecast and the possibility of deteriorating weather,
- the competences of the captain for a missed approach procedure in poor weather conditions were limited to a simulator training despite the fact that he was certified for Cat IIIa approaches,
- failure of the crew to comply with the standard operating procedures for a missed approach,
- wrong actions on part of the pilot in command while crossing the runway threshold at a height of 125 feet and about five seconds after the initiation of the TOGA procedure, disrupting the go around trajectory and causing the aircraft to continue the descent,
- lack of reaction of the copilot who did not try to correct the wrong actions of the pilot in command,
- lack of concentration on part of the crew who failed to control the approach speed and failed to recognize the pitch angle that was increasing,
- it is possible that the crew suffered somatogravic illusions caused by fatigue due to a duty time period above 13 hours,
- a non proactive reaction of the crew when the GPWS alarm sounded.
Final Report:

Crash of a Learjet 60 in Zihuatanejo

Date & Time: Nov 16, 2015 at 1622 LT
Type of aircraft:
Operator:
Registration:
XA-UQP
Flight Type:
Survivors:
Yes
Schedule:
Toluca - Zihuatanejo
MSN:
60-202
YOM:
2001
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7673
Captain / Total hours on type:
1360.00
Copilot / Total flying hours:
9592
Copilot / Total hours on type:
3100
Aircraft flight hours:
3676
Circumstances:
The crew departed Toluca Airport on a positioning flight to Zihuatanejo. Following an uneventful flight, the crew was cleared for a VOR approach to runway 26. Due to the formation of clouds in the vicinity of the airport, ATC changed the clearance and instructed the crew for a VOR/DME approach to runway 08. Following an unstabilized approach, the aircraft landed on a wet runway. After touchdown, the aircraft skidded and veered off runway to the left. In a grassy area, the left main gear impacted a concrete block hosting the electrical system for the runway and was torn off. Then the aircraft slid for few dozen metres before coming to rest. Both pilots evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
Runway excursion due to loss of directional control of the aircraft during the landing run on an unstabilized approach.
The following contributing factors were identified:
a) Unstabilized approach,
b) Adverse atmospheric conditions in the "W" area of the airport,
c) Change of designation of runway in use for landing,
d) Lack of adherence to standard operating procedures "SOPS",
e) Lack of adherence to the concepts of "CRM" resource management in the cockpit,
f) Decreased situational awareness on the part of the commander of the aircraft,
g) Flying the approach and descent visually, following an IFR descent within IMC conditions (Instrument Meteorological Conditions),
h) Wet track,
i) Lack of crew coordination,
j) Poor judgement and incorrect decision,
k) Existence of a concrete marker with a level of 10cms protruding above the road surface in the runway safety zone.
Final Report:

Crash of a Piper PA-46-350P Malibu Mirage in Buttles Farm: 4 killed

Date & Time: Nov 14, 2015 at 1134 LT
Registration:
N186CB
Flight Type:
Survivors:
No
Schedule:
Fairoaks – Dunkeswell
MSN:
46-22085
YOM:
1989
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
600
Captain / Total hours on type:
260.00
Circumstances:
The aircraft was approaching Dunkeswell Airfield, Devon after an uneventful flight from Fairoaks, Surrey. The weather at Dunkeswell was overcast, with rain. The pilot held an IMC rating but there is no published instrument approach procedure at Dunkeswell. As the aircraft turned onto the final approach, it commenced a descent on what appeared to be a normal approach path but then climbed rapidly, probably entering cloud. The aircraft then seems to have stalled, turned left and descended to “just below the clouds”, before it climbed steeply again and “disappeared into cloud”. Shortly after, the aircraft was observed descending out of the cloud in a steep nose-down attitude, in what appears to have been a spin, before striking the ground. All four occupants were fatally injured.
Probable cause:
Whilst positioning for an approach to Dunkeswell Airfield, the aircraft suddenly pitched nose-up and entered cloud. This rapid change in attitude would have been disorientating for the pilot, especially in IMC, and, whilst the aircraft was probably still controllable, recovery from this unusual attitude may have been beyond his capabilities. The aircraft appears to have stalled, turned left and descended steeply out of cloud, before climbing rapidly back into cloud. It probably then stalled again and entered a spin from which it did not recover. All four occupants were fatally injured when the aircraft struck the ground. The investigation was unable to determine with certainty the reason for the initial rapid climb. However, it was considered possible that the pilot had initiated the preceding descent by overriding the autopilot. This would have caused the autopilot to trim nose-up, increasing the force against the pilot’s manual input. Such an out-of-trim condition combined with entry into cloud could have contributed to an unintentional and disorientating pitch-up manoeuvre.
Final Report:

Crash of a Hawker-Siddeley HS.780 Andover C.1 in Malakal

Date & Time: Nov 10, 2015
Operator:
Registration:
TL-AEW
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Malakal – Wau
MSN:
Set13
YOM:
1966
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was performing a flight from Malakal to Wau on behalf of the World Food Program. Shortly after takeoff, during initial climb, an unexpected situation forced the captain to attempt an emergency landing. The aircraft crash landed in a field past the runway end, slid for few dozen metres and came to rest, bursting into flames. All four crew members evacuated safely and the aircraft was totally destroyed by a post crash fire.