Crash of a Cessna 421C Golden Eagle III in Huntsville: 1 killed

Date & Time: Apr 25, 2017 at 1038 LT
Registration:
N421TK
Flight Type:
Survivors:
No
Schedule:
Conroe – College Station
MSN:
421C-0601
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1567
Captain / Total hours on type:
219.00
Aircraft flight hours:
7647
Circumstances:
While conducting a post maintenance test flight in visual flight rules conditions, the private pilot of the multi-engine airplane reported an oil leak to air traffic control. The controller provided vectors for the pilot to enter a right base leg for a landing to the south at the nearest airport, about 7 miles away. The pilot turned toward the airport but indicated that he did not have the airport in sight. Further, while maneuvering toward the airport, the pilot reported that the engine was "dead," and he still did not see the airport. The final radar data point recorded the airplane's position about 3.5 miles west-northwest of the approach end of the runway; the wreckage site was located about 4 miles northeast of the runway, indicating that the pilot flew past the airport rather than turning onto a final approach for landing. The reason that the pilot did not see the runway during the approach to the alternate airport, given that the airplane was operating in visual conditions and the controller was issuing guidance information, could not be determined. Regardless, the pilot did not execute a precautionary landing in a timely manner and lost control of the airplane. Examination of the airplane's left engine revealed that the No. 2 connecting rod was broken. The connecting rod bearings exhibited signs of heat distress and discoloration consistent with a lack of lubrication. The engine's oil pump was intact, and the gears were wet with oil. Based on the available evidence, the engine failure was the result of oil starvation; however, examination could not identify the reason for the starvation.
Probable cause:
The pilot's failure to identify the alternate runway, to perform a timely precautionary landing, and to maintain airplane control. Contributing to the accident was the failure of the left engine due to oil starvation for reasons that could not be determined based on the post accident examination.
Final Report:

Ground fire of a GippsAero GA8 Airvan in Gibb River

Date & Time: Apr 22, 2017 at 1255 LT
Type of aircraft:
Operator:
Registration:
VH-AJZ
Flight Type:
Survivors:
Yes
Schedule:
Derby - Gibb River
MSN:
GA8-05-96
YOM:
2005
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On 22 April 2017, a Gippsland Aeronautics GA-8 aircraft, registered VH-AJZ, was being used to conduct incendiary bombing aerial work operations in the Prince Regent River area of northern Western Australia (WA). On board were a pilot, a navigator seated in the co-pilot seat and a bombardier in the rear of the aircraft cabin. While conducting the incendiary bombing operations, the bombardier advised the pilot that he was suffering from motion sickness. The pilot elected to land at Gibb River aircraft landing area (ALA), WA, to take a lunch break and provide the bombardier with time to recover from the motion sickness. At about 1255 Western Standard Time (WST), the aircraft landed on runway 07 at Gibb River. During the landing roll, the engine failed. The aircraft had sufficient momentum to enable the pilot to turn the aircraft around on the runway and begin to taxi to the parking area at the western end of runway 07. Shortly after turning around, the aircraft came to rest on the runway. The pilot attempted to restart the engine, but the engine did not start. The pilot waited about 10–20 seconds before again attempting to restart the engine. While attempting the second restart of the engine, the pilot heard a loud noise similar to that of a backfire. The navigator then observed flames and smoke coming from around the front of the engine and immediately notified the pilot. After being notified of the fire, the pilot immediately shut down the engine and switched off the aircraft electrical system. As the pilot switched off the aircraft electrical system, the navigator located the aircraft fire extinguisher and evacuated from the aircraft through the co-pilot door. After evacuating from the aircraft, the navigator observed fire on the aircraft nose wheel. The navigator had difficulty preparing the fire extinguisher for use and was unable to discharge the fire extinguisher onto the fire. While the navigator was attempting to extinguish the fire, the pilot exited the aircraft through the pilot door and assisted the bombardier to exit the aircraft. After assisting the bombardier, the pilot moved to the front of the aircraft to assist the navigator with the firefighting. The pilot was able to activate the fire extinguisher and extinguished the fire on the nose wheel. The pilot observed fire continuing to burn within the engine compartment. Due to the heat of the fire, the pilot was unable to access the engine compartment to extinguish this fire. The pilot determined that no more could be done to contain the fire, and therefore, the pilot, navigator and bombardier moved clear of the aircraft to a safe location as the fire continued. The crew members were not injured. As a result of the fire, the aircraft was destroyed.
Probable cause:
These findings should not be read as apportioning blame or liability to any particular organisation or individual.
- The cause of the engine failure and fire could not be determined.
- After the fire was identified, two steps in the emergency procedure were omitted. This included not closing the fuel shutoff valve, which likely resulted in the fire not being extinguished and subsequently intensifying.
Final Report:

Crash of a Let L-410UVP-E9 in Yei

Date & Time: Apr 1, 2017 at 1030 LT
Type of aircraft:
Operator:
Registration:
5X-EIV
Flight Phase:
Survivors:
Yes
Schedule:
Yei - Arua
MSN:
96 26 32
YOM:
1996
Flight number:
H7360
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
17
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, at a relative high speed, the pilot-in-command rejected takeoff and initiated an emergency braking procedure, apparently following an engine problem. The twin engine aircraft deviated to the left and veered off runway. While contacting soft ground, the nose gear collapsed and the airplane came to rest in the bush. All 20 occupants were rescued, among them both pilots were slightly injured.

Crash of a Piper PA-42-720 Cheyenne III in Sorocaba: 2 killed

Date & Time: Mar 31, 2017 at 1445 LT
Type of aircraft:
Operator:
Registration:
PP-EPB
Flight Type:
Survivors:
No
Schedule:
Manaus - Sorocaba
MSN:
42-8001035
YOM:
1980
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3382
Captain / Total hours on type:
118.00
Circumstances:
The twin engine aircraft departed Manaus-Aeroclub de Flores Airport on a flight to Barra do Garças, carrying one passenger and one pilot. After takeoff from Manaus, the pilot changed his mind and decided to fly to Sorocaba. On final approach to Sorocaba-Bertram Luiz Leupolz Airport in good weather conditions, the aircraft impacted trees and crashed in a wooded area located about one km short of runway 18. The aircraft was destroyed and both occupants were killed. There was no fire.
Probable cause:
Contributing factors:
- Flight indiscipline – a contributor
The pilot failed to comply with the minimum fuel requirements laid down in the regulations, providing conditions for both engines to stop operating in flight, due to lack of fuel.
- Piloting judgment – a contributor
It was found in this flight an inadequate evaluation for certain parameters related to aircraft operation, particularly with regard to the influence of the chosen flight level on fuel consumption. This misjudgment led to the decision to proceed with the flight to the Aerodrome where it was intended to land, to the detriment of the more conservative option of finding a suitable place for an intermediate landing and a refueling, which led to the depletion of usable fuel in flight.
- Flight planning – a contributor
Inadequate flight preparation work, especially with regard to fuel calculation and cruise level selection, has degraded the safety level and also contributed to the actual accident.
- Decision-making process – undetermined
Difficulties in perceiving, analyzing, choosing alternatives, and acting appropriately due to inadequate judgment, may have resulted in poor assessment of flight parameters (available fuel, distance to destination, verified consumption, etc.), which may have favored the occurrence of lack of fuel failure.
Final Report:

Crash of a Quest Kodiak 100 in Moretecocha

Date & Time: Mar 29, 2017 at 1100 LT
Type of aircraft:
Operator:
Registration:
HC-CRF
Flight Phase:
Survivors:
Yes
Schedule:
Moretecocha – Shell Mera
MSN:
100-0116
YOM:
2014
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Moretecocha Airfield, while climbing in poor weather conditions, the single engine airplane impacted trees and crashed in a river bed. All seven occupants were injured and the aircraft was destroyed.

Crash of a Boeing 737-3M8 in Jauja

Date & Time: Mar 28, 2017 at 1628 LT
Type of aircraft:
Operator:
Registration:
OB-2036-P
Survivors:
Yes
Schedule:
Lima - Jauja
MSN:
25071/2039
YOM:
1991
Flight number:
P9112
Location:
Country:
Crew on board:
7
Crew fatalities:
Pax on board:
142
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
13504
Copilot / Total flying hours:
7604
Aircraft flight hours:
62817
Aircraft flight cycles:
44025
Circumstances:
The aircraft departed Lima-Jorge Chavez Airport on a 20-minute flight to Jauja, carrying 142 passengers and 7 seven crew members. The approach to Jauja-Francisco Carlé was uneventful and completed in good weather conditions. Two seconds after the nose gear touched down on runway 31, the crew activated the reverse systems when he felt strong vibrations and oscillations. The aircraft started to bounce and became uncontrollable. The right main gear collapsed then the aircraft veered off runway to the right, lost its right engine and came to rest in a grassy area, bursting into flames. All 149 occupants evacuated safely and the aircraft was totally destroyed by fire.
Probable cause:
Failure of the mechanical components of the shimmy damper system in each of the main landing gears which, being out of tolerance range, did not allow the correct damping of the vibrations and lateral oscillations of the wheels after touchdown, generating sequential shimmy events in both gears and causing their collapse.
Contributing factors:
- Incorrect and probable absence of measurements on mechanical components of the 'cimmetic chain for shimmy damper operation', as indicated by the operator's PM AMM Task, which would have allowed for the timely detection and replacement of out-of-tolerance components, ensuring their integrity and correct operation.
- The Service Letter 737-SL-32-057-E 'broken torsion link', does not provide for mandatory actions, it only recommends maintenance practices to prevent fractures in mechanical components of the 'cimmetic chain for shimmy damper operation'.
- Service Letter 737-SL-32-057-E 'fractures in lower torsion link', makes a proper interpretation difficult; that could induce errors to choose the corresponding AMM Task and determine its scope.
Final Report:

Crash of an Antonov AN-26B in Wau

Date & Time: Mar 20, 2017 at 1525 LT
Type of aircraft:
Operator:
Registration:
S9-TLZ
Survivors:
Yes
Schedule:
Juba - Wau
MSN:
133 10
YOM:
1983
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
40
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Juba, the crew initiated the approach to Wau Airport when he encountered poor weather conditions and limited visibility. On short final, during the last segment, the aircraft collided with a fire truck and near the runway 27 threshold, bursting into flames. All 45 occupants were rescued, among them 18 were injured. The airplane was totally destroyed by a post crash fire.

Crash of a Pilatus U-28A at Cannon AFB: 3 killed

Date & Time: Mar 14, 2017 at 1835 LT
Type of aircraft:
Operator:
Registration:
08-0724
Flight Type:
Survivors:
No
Schedule:
Cannon - Cannon
MSN:
724
YOM:
2006
Flight number:
Demise 25
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
3400
Captain / Total hours on type:
3199.00
Copilot / Total flying hours:
448
Copilot / Total hours on type:
213
Circumstances:
On 14 Mar 17, at 1835 local time (L), a U-28A, tail number 0724, crashed one-quarter mile south of Clovis Municipal Airport (KCVN), New Mexico (NM). This aircraft was operated by the 318th Special Operations Squadron, 27th Special Operations Wing, Cannon Air Force Base (AFB), NM. The aircraft was destroyed and all three crewmembers died upon impact. The Mishap Aircraft (MA) departed Cannon AFB at 1512L for tactical training over Lubbock, Texas, followed by pilot proficiency training at KCVN. The Mishap Crew (MC) entered Lubbock airspace at 1545L, completed their tactical training, and departed Lubbock airspace at 1735L enroute to KCVN. The MC entered the KCVN traffic pattern at 1806L, where they conducted multiple approaches and landings prior to executing the mishap maneuver, a practice turnback Emergency Landing Pattern (ELP). The MC entered the practice turnback ELP with 0° flaps led to increased aircraft nose-down attitudes and higher descent rates required to maintain a safe angle of attack versus a comparative 15° flap approach. In addition, 0° flap stall speeds are higher than 15° flap stall speeds – 15 to 25 knots higher for the range of bank angles flown by the MC during the practice turnback ELP. The MC was also late to achieve the bank angle required to enable the MA to align with the extended centerline for the runway resulting in an overshoot condition. The MC attempted to arrest their excessive nose-down attitude, descent rate, and shallow bank angle by pulling back on the aircraft yoke and increasing bank angle. The g-load from the MC pull back, coupled with the MA's increased bank angle, slowed the MA airspeed below 0° flap stall speed and it departed controlled flight. Subsequent power increase and flight control inputs would not have enabled the aircraft to recover from the stall within remaining altitude. After entering the stall, the MC increased power; however, it was not enough to overcome the MA descent rate. At no point during the practice turnback ELP did the MA performance reflect a MC intent to abort the maneuver. The MA impacted the ground with a 13° nose-high, 7° left-wing low attitude. The aircraft was destroyed upon impact and all three occupants were killed.
Crew:
Cpt Andrew Becker, pilot,
1st Lt Frederick Dellecker, copilot,
Cpt Kenneth Dalga, combat systems officer.
Probable cause:
By a preponderance of the evidence, the Accident Investigation Board concluded the aircrew lost control of the aircraft when it entered a stall at low altitude during a turn back Emergency Landing Pattern procedure. There were no indications of mechanical malfunction. The board also surmised the crew delayed actions necessary to prevent the aircraft from entering the stall envelope and failed to accurately assess increasing risk throughout execution of the practice turn back Emergency Landing Pattern, thereby substantially contributing to the mishap.
Final Report:

Crash of a McDonnell Douglas MD-83 in Detroit

Date & Time: Mar 8, 2017 at 1452 LT
Type of aircraft:
Operator:
Registration:
N786TW
Flight Phase:
Survivors:
Yes
Schedule:
Detroit - Washington DC
MSN:
53123/1987
YOM:
1992
Flight number:
7Z9363
Crew on board:
6
Crew fatalities:
Pax on board:
110
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
15518
Captain / Total hours on type:
8495.00
Copilot / Total flying hours:
9660
Copilot / Total hours on type:
2462
Aircraft flight hours:
41008
Aircraft flight cycles:
39472
Circumstances:
A McDonnell Douglas MD-83, registration N786TW, suffered a runway excursion following an aborted takeoff from runway 23L at Detroit-Willow Run Airport, Michigan, USA. The aircraft had been chartered by the University of Michigan Basketball team for a flight to a game in Washington, DC. The flight crew prepared for take-off and calculated V-speeds (V1, VR, V2) using "Normal Thrust Takeoff", a 10 kts headwind, and a take-off weight of 146,600 lbs. The V-speeds for this configuration were 139 kts, 142 kts, and 150 kts, respectively. However, the flight crew chose to increase VR to 150 kts to allow for more control during take-off in the presence of windshear. During takeoff roll, at 14:51:56 (about 3,000 ft down the runway) and about 138 kts of airspeed, the control column was pulled back slightly from a non-dimensional value of -7 to -5.52. The airplane’s left elevator followed the control input and moved from a position of -15° trailing edge down to -13° trailing edge down. The right elevator did not change and stayed at approximately -16° trailing edge down. At 14:52:01 a large control column input was made (151 kts and 4100 ft down the runway) to a non-dimensional 18.5 and the left elevator moves to a position near 15° trailing edge up. After 14:52:05 the right elevator moves to -13° trailing edge down, but no more. The airplane does not respond in pitch and does not rotate. The captain decided to abort the takeoff. The maximum ground speed was 163 kts (173 kts airspeed) and the airplane began to decelerate as soon as the brakes were applied at 14:52:08. Spoilers were deployed at 14:52:10 and thrust reversers were deployed between 14:52:13 and 14:52:15. The aircraft could not be stopped on the runway. The airplane’s ground speed was 100 kts when it left the paved surface. The aircraft overran the end of the runway, damaged approach lights, went through the perimeter fence and crossed Tyler Road. It came to rest on grassy terrain, 345 meters past the end of the runway, with the rear fuselage across a ditch. The nose landing gear had collapsed. Runway 23L is a 7543 ft long runway.
Probable cause:
The NTSB determines that the probable cause of this accident was the jammed condition of the airplane’s right elevator, which resulted from exposure to localized, dynamic wind while the airplane was parked and rendered the airplane unable to rotate during takeoff. Contributing to the accident were (1) the effect of a large structure on the gusting surface wind at the airplane’s parked location, which led to turbulent gust loads on the right elevator sufficient to jam it, even though the horizontal surface wind speed was below the certification design limit and maintenance inspection criteria for the airplane, and (2) the lack of a means to enable the flight crew to detect a jammed elevator during preflight checks for the Boeing MD-83 airplane. Contributing to the survivability of the accident was the captain’s timely and appropriate decision to reject the takeoff, the check airman’s disciplined adherence to standard operating procedures after the captain called for the rejected takeoff, and the dimensionally compliant runway safety area where the overrun occurred.
Final Report:

Crash of a Pilatus PC-12/47E in Cat Cay

Date & Time: Mar 8, 2017 at 1246 LT
Type of aircraft:
Operator:
Registration:
N8TS
Flight Type:
Survivors:
Yes
Schedule:
Saint Petersburg - Cat Cay
MSN:
1650
YOM:
2016
Location:
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Pilot advised that upon making his approach to land at Cat Cay (MYCC), on short final he experienced an unexpected accelerated sink rate. To compensate for the sink rate he increased the pitch of the aircraft. While going over the threshold, a slight impact was felt as the landing gear came into contact with the seawall. He flew the aircraft until it came to a stop about 600 feet down the runway. No injuries were sustained, aircraft received substantial damage.
Final Report: