Crash of a Piper PA-31T Cheyenne II near Catacamas: 1 killed

Date & Time: Jul 3, 2012
Type of aircraft:
Operator:
Registration:
PT-OFH
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
31-7920034
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The twin engine aircraft was engaged in an illegal flight, carrying two pilots and a load consisting of 600 kilos of cocaine. After being tracked by the Honduran Police, the crew apparently attempted an emergency landing when the aircraft crashed. While the copilot was injured, the captain was killed.

Crash of a Technoavia SM-92G Turbo Finist in Bollullos de la Mitación

Date & Time: Jul 1, 2012 at 1045 LT
Registration:
HA-NAH
Flight Phase:
Survivors:
Yes
Schedule:
Bollullos de la Mitación - Bollullos de la Mitación
MSN:
003
YOM:
1994
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
8
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
340
Captain / Total hours on type:
24.00
Aircraft flight hours:
2575
Circumstances:
The aircraft started taking off from runway 27 threshold. Upon reaching a speed deemed proper by the pilot for rotation, the pilot noticed that the aircraft was not taking off, so he decided to abort the takeoff. While trying to stop the aircraft, it exited via the left side of the runway near the end, breaking through the fence that surrounds the aerodrome before coming to rest in trees. While all ten occupants were uninjured, the aircraft was damaged beyond repair with both wings sheared off.
Probable cause:
Whenever this aircraft is doing a short-field takeoff with a high weight, it is recommended that the flaps be set to their takeoff position of 20°. The evidence indicates that the pilot was attempting to take off on runway 27 and forgot to place the flaps in the takeoff position (20°).
Final Report:

Crash of an Ilyushin II-76MD in Tver

Date & Time: Jun 27, 2012 at 0029 LT
Type of aircraft:
Operator:
Registration:
RA-76761
Flight Type:
Survivors:
Yes
Schedule:
Tver - Tver
MSN:
00734 79401
YOM:
1987
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The crew was completing a local training mission at Migalovo AFB and was performing touch-and-go manoeuvres. By night, the aircraft was approaching in a nose-down attitude when the nose gear landed hard first. It penetrated the floor just behind the cockpit. The aircraft slid for few dozen metres before coming to rest on runway. All four crew members evacuated safely while the aircraft was damaged beyond repair as the fuselage was wrinkled.
Probable cause:
It is likely that following a wrong approach configuration, the aircraft landed nose first with a high aerodynamic acceleration.

Crash of a Beechcraft C90GT King Air in Morgantown: 1 killed

Date & Time: Jun 22, 2012 at 1001 LT
Type of aircraft:
Registration:
N508GT
Flight Type:
Survivors:
No
Schedule:
Tidioute - Farmington - Morgantown
MSN:
LJ-1775
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
22000
Aircraft flight hours:
1439
Circumstances:
The airplane, operated by Oz Gas Aviation LLC, was substantially damaged when it struck a communications tower near Morgantown, West Virginia. The certificated airline transport pilot was fatally injured. No flight plan had been filed for the positioning flight from Nemacolin Airport (PA88), Farmington, Pennsylvania, to Morgantown Municipal Airport (MGW), Morgantown, West Virginia conducted under Title14 Code of Federal Regulations (CFR) Part 91. At 0924 on the morning of the accident, the airplane departed from Rigrtona Airport (13PA), Tidioute, Pennsylvania for PA88 with the pilot and three passengers onboard. The airplane landed on runway 23 at PA88 at 0944. The pilot then parked the airplane; shutdown both engines, and deplaned the three passengers. He advised them that he would be back on the following day to pick them up. After the passengers got on a shuttle bus for the Nemacolin Woodlands Resort, the pilot started the engines. He idled for approximately 2 minutes, and then back taxied on runway 23 for takeoff. At 0957, he departed from runway 23 for the approximately 19 nautical mile positioning flight to MGW, where he was going to refuel and spend the night. After departure from PA88, the airplane climbed to 3,100 feet above mean sea level (msl) on an approximately direct heading for MGW. The pilot then contacted Clarksburg Approach Control and was given a discrete code of 0130. When the airplane was approximately nine miles east of the Morgantown airport, the air traffic controller advised the pilot that he had "radar contact" with him. The airplane then descended to 3,000 feet, and approximately one minute later struck the communications tower on an approximate magnetic heading of 240 degrees. According to a witness who was cutting timber across the road from where the accident occurred; the weather was cloudy with lighting and thunder, and it had just started "sprinkling". He then heard a loud "bang", turned, and observed the airplane descending upside down, and then impact. About 20 minutes later it stopped "sprinkling". He advised that he could still see the top of the tower when it was "sprinkling".
Probable cause:
The pilot's inadequate preflight route planning and in-flight route and altitude selection, which resulted in an in-flight collision with a communications tower in possible instrument
meteorological conditions. Contributing to the accident were the pilot's improper use of the enhanced ground proximity warning system's terrain inhibit switch and the air traffic controller's failure to issue a safety alert regarding the proximity of the tower.
Final Report:

Crash of a Fokker F27 Friendship 400M in Jakarta: 11 killed

Date & Time: Jun 21, 2012 at 1450 LT
Type of aircraft:
Operator:
Registration:
A-2708
Flight Type:
Survivors:
No
Schedule:
Jakarta - Jakarta
MSN:
10546
YOM:
1976
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
The crew (one instructor and six pilot under training) were engaged in a training flight and departed Jakarta-Halim Perdanakusuma Airport at 1310LT for a local flight consisting of touch-and-go manoeuvres. After a circuit, the pilot-in-command completed a last turn to the left to join the glide for runway 18 when the aircraft stalled and crashed onto several houses located less than one km from the runway threshold. The aircraft was destroyed as well as several houses. Six occupants in the aircraft and four people on the ground were killed while the copilot was critically injured. Unfortunately, he did not survive to his severe injuries and died few hours later at hospital.
Probable cause:
It was reported that the approach speed was too low during the last turn, causing the aircraft to stall. The distance between the aircraft and the ground was insufficient to expect recovery.

Crash of a Grumman G-159 Gulfstream GI in Pweto

Date & Time: Jun 20, 2012
Type of aircraft:
Registration:
9Q-CIT
Survivors:
Yes
Schedule:
Lubumbashi - Pweto
MSN:
193
YOM:
1968
Location:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful charter flight from Lubumbashi-Lueno Airport, the crew made a steep approach followed by a hard landing. The aircraft bounced and climbed to a height of about 20 feet, landed again and went out of control. It veered off runway to the left, collided with a rocky embankment, lost its undercarriage and came to rest, broken in several pieces. All five occupants escaped uninjured while the airplane was destroyed.
Probable cause:
Wrong approach configuration after the crew made a sharp turn late on final to join the glide. The rate of descent was excessive during the last segment, causing the aircraft to land hard and to bounce. Due to excessive g-loads and aerodynamic forces, the airplane went out of control.

Crash of a Beechcraft Beechjet 400A in Atlanta

Date & Time: Jun 18, 2012 at 1006 LT
Type of aircraft:
Operator:
Registration:
N826JH
Survivors:
Yes
Schedule:
Gadsden - Atlanta
MSN:
RK-70
YOM:
1993
Crew on board:
2
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
10800
Captain / Total hours on type:
1500.00
Copilot / Total flying hours:
3500
Copilot / Total hours on type:
150
Aircraft flight hours:
4674
Circumstances:
The second-in-command (SIC) was the pilot flying for most of the flight (takeoff, climb, cruise, and descent) and was in the left seat, while the pilot-in-command (PIC) was the pilot monitoring for most of the flight and was in the right seat. Before takeoff, the PIC calculated reference speed (Vref) for the estimated landing weight and flaps 30-degree extension was 120 knots, with a calculated landing distance of 3,440 ft. Further, before takeoff, there were no known mechanical difficulties with the brakes, flaps, antiskid, or traffic alert and collision avoidance (TCAS) systems. After takeoff and for most of the flight, the PIC coached/instructed the SIC, including instructions on how to set the airspeed command cursor, a request to perform the after-takeoff checklist, and a comment to reduce thrust to silence an overspeed warning aural annunciation. When the flight was northwest of Dekalb Peachtree Airport (PDK), Atlanta, Georgia, on a right base leg for a visual approach to runway 20L with negligible wind, air traffic controllers repeatedly announced the location and distance of a Cessna airplane (which was ahead of the Beech 400A on a straight-in visual approach to runway 20R). Because the Beech 400A flight crew did not see the other airplane, the controllers appropriately instructed them to maintain their altitude (which was 2,300 ft mean sea level [msl]) for separation until they had the traffic in sight; radar data indicated the Beech 400A briefly descended to 2,200 ft msl then climbed back to 2,300 ft msl. According to the cockpit voice recorder (CVR) transcript, at 1004:42, which was about 12 seconds after the controller instructed the Beech 400A flight crew to maintain altitude, the on board TCAS alerted "traffic traffic." While the Beech 400A did climb back to 2,300 ft msl, this was likely a response to the air traffic control (ATC) instruction to maintain altitude and not a response to the TCAS "traffic traffic" warning. At 1004:47, the CVR recorded the SIC state, "first degree of," likely referring to flap extension, but the comment was not completed. The CVR recorded an immediate increase in background noise, which was likely due to the landing gear extension. The PIC then advised the local controller that the flight was turning onto final approach. The CVR did not record any approach briefing or discussion of runway length or Vref speed. After landing on runway 20L at Atlanta-DeKalb Peachtree Airport, aircraft did not stop as expected. It overrun the runway, went through a fence and came to rest near a road, broken in two. All four occupants were injured, both pilots seriously.
Probable cause:
The flight crew's failure to obtain the proper airspeed for landing, which resulted in the airplane touching down too fast with inadequate runway remaining to stop and a subsequent
runway overrun. Contributing to the accident were the failure of either pilot to call for a go-around and the flight crew's poor crew resource management and lack of professionalism.
Final Report:

Crash of a PZL-Mielec AN-2R near Serov: 13 killed

Date & Time: Jun 11, 2012 at 2211 LT
Type of aircraft:
Operator:
Registration:
RA-40312
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Serov - Serov
MSN:
1G221-48
YOM:
1986
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
12
Pax fatalities:
Other fatalities:
Total fatalities:
13
Captain / Total flying hours:
8281
Captain / Total hours on type:
5977.00
Aircraft flight hours:
3966
Aircraft flight cycles:
12000
Circumstances:
In the evening of 11JUN2012, a group of 13 people departed Serov Airport at 2200LT on an illegal trip with an unknown destination, maybe for fishing, sauna or any other party. The aircraft failed to return and was lost without trace. Local Authorities performed search and rescue on more than 275,000 square km until 23JUL2012 without success. It seems that all occupants were intoxicated when they took the airplane, among them the Chief of Serov City Police, three of his deputies, an airport guard and several others. On Saturday 05MAY2013, local hunters found the burnt wreckage and the skeletonized remains of the bodies on a marshland, some 10 km southwest of Serov Airport.
Probable cause:
It is believed that the airplane was flying at low height when its left lower wing impacted tree tops. The aircraft then rolled to the left to an angle of 90° and crashed, bursting into flames. At the time of the accident, the pilot and other occupants were intoxicated.
Final Report:

Crash of a Pilatus PC-12/47 in Lake Wales: 6 killed

Date & Time: Jun 7, 2012 at 1235 LT
Type of aircraft:
Registration:
N950KA
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Fort Pierce - Junction City
MSN:
730
YOM:
2006
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
755
Captain / Total hours on type:
38.00
Aircraft flight hours:
1263
Circumstances:
The airplane, registered to and operated by Roadside Ventures, LLC, departed controlled flight followed by subsequent inflight breakup near Lake Wales, Florida. Instrument meteorological conditions prevailed at the altitude and location of the departure from controlled flight and an instrument flight rules (IFR) flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 personal flight from St Lucie County International Airport (FPR), Fort Pierce, Florida, to Freeman Field Airport (3JC), Junction City, Kansas. The airplane was substantially damaged and the private pilot and five passengers were fatally injured. The flight originated from FPR about 1205. After departure while proceeding in a west-northwesterly direction and climbing, air traffic control communications were transferred to Miami Air Route Traffic Control Center (Miami ARTCC). The pilot remained in contact with various sectors of that facility from 1206:41, to the last communication at 1233:16. About 6 minutes after takeoff the pilot was advised by the Miami ARTCC Stoop Sector radar controller of an area of moderate to heavy precipitation twelve to two o'clock 15 miles ahead of the airplane's position; the returns were reported to be 30 miles in diameter. The pilot asked the controller if he needed to circumnavigate the weather, to which the controller replied that deviations north of course were approved and when able to proceed direct LAL, which he acknowledged. A trainee controller and a controller providing oversight discussed off frequency that deviation to the south would be better. The controller then questioned the pilot about his route, to which he replied, and the controller then advised the pilot that deviations south of course were approved, which he acknowledged. The flight continued in generally a west-northwesterly direction, or about 290 degrees, and at 1230:11, while at flight level (FL) 235, the controller cleared the flight to FL260, which the pilot acknowledged. At 1232:26, the aircraft's central advisory and warning system (CAWS) recorded that the pusher system went into "ice mode" indicating the pilot had selected the propeller heat on and inertial separator open. At that time the aircraft's engine information system (EIS) recorded the airplane at 24,668 feet pressure altitude, 110 knots indicated airspeed (KIAS), and an outside air temperature of minus 11 degrees Celsius. At 1232:36, the Miami ARTCC Avon Sector radar controller advised the pilot of a large area of precipitation northwest of Lakeland, with moderate, heavy and extreme echoes in the northwest, and asked him to look at it and to advise what direction he needed to deviate, then suggested deviation right of course until north of the adverse weather. The pilot responded that he agreed, and the controller asked the pilot what heading from his position would keep the airplane clear, to which he responded at 1233:04 with, 320 degrees. At 1233:08, the Miami ARTCC Avon Sector radar controller cleared the pilot to fly heading 320 degrees or to deviate right of course when necessary, and when able proceed direct to Seminole, which he acknowledged at 1233:16. There was no further recorded communication from the pilot with the Miami ARTCC. Radar data showed that between 1233:08, and 1233:26, the airplane flew on a heading of approximately 290 degrees, and climbed from FL250 to FL251, while the EIS recorded for the same time the airplane was at either 109 or 110 KIAS and the outside air temperature was minus 12 degrees Celsius. The radar data indicated that between 1233:26 and 1233:31, the airplane climbed to FL252 (highest recorded altitude from secondary radar returns). At 1233:30, while at slightly less than 25 degrees of right bank based on the NTSB Radar Performance Study based on the radar returns, 109 KIAS, 25,188 feet and total air temperature of minus 12 degrees Celsius based on the data downloaded from the CAWS, autopilot disengagement occurred. This was recorded on the CAWS 3 seconds later. The NTSB Performance Study also indicates that based on radar returns between 1233:30, and 1233:40, the bank angle increased from less than approximately 25 degrees to 50 degrees, while the radar data for the approximate same time period indicates the airplane descended to FL249. The NTSB Performance Study indicates that based on radar returns between 1233:40 and 1234:00, the bank angle increased from 50 degrees to approximately 100 degrees, while the radar data indicates that for the approximate same time frames, the airplane descended from FL249 to FL226. The right descending turn continued and between 1233:59, and 1234:12, the airplane descended from 22,600 to 16,700, and a change to a southerly heading was noted. The NTSB Performance Study indicates that the maximum positive load factor of 4.6 occurred at 1234:08, while the NTSB Electronic Device Factual Report indicates that the maximum recorded airspeed value of 338 knots recorded by the EIS occurred at 1234:14. The next recoded airspeed value 1 second later was noted to be zero. Simultaneous to the zero airspeed a near level altitude of 15,292 feet was noted. Between 1234:22, and 1234:40, the radar data indicated a change in direction to a northeast occurred and the airplane descended from 13,300 to 9,900 feet. The airplane continued generally in a northeasterly direction and between 1234:40 and 1235:40 (last secondary radar return), the airplane descended from 9,900 to 800 feet. The last secondary radar return was located at 27 degrees 49.35 minutes North latitude and 081 degrees 28.6332 minutes West longitude. Plots of the radar targets of the accident site including the final radar targets are depicted in the NTSB Radar Study which is contained in the NTSB public docket. At 1235:27, the controller asked the pilot to report his altitude but there was no reply. The controller enlisted the aid of the flight crew of another airplane to attempt to establish contact with the pilot on the current frequency and also 121.5 MHz. The flight crew attempted on both frequencies but there was no reply. At 1236:30, the pilot of a nearby airplane advised the controller that he was picking up an emergency locator transmitter (ELT) signal. The pilot of that airplane advised the controller at 1237:19, that, "right before we heard that ELT we heard a mayday mayday." The controller inquired whether the pilot had heard the mayday on the current frequency or 121.5 MHz, to which he replied that he was not sure because he was monitoring both frequencies. The controller inquired with the flight crews of other airplanes if they heard the mayday call on the frequency and the response was negative, though they did report hearing the ELT on 121.5 MHz. The controller verified with the flight crew's that were monitoring 121.5 MHz whether they heard the mayday call on that frequency and they advised they did not. A witness who was located about 1.5 nautical miles south-southwest from the crash site reported that on the date and time of the accident, he was inside his house and first heard a sound he attributed to a propeller feathering or later described as flutter of a flight control surface. The sound lasted 3 to 4 cycles of a whooshing high to low sound, followed by a sound he described as an energy release. He was clear the sound he heard was not an explosion, but more like mechanical fracture of parts. He ran outside, and first saw the airplane below the clouds (ceiling was estimated to be 10,000 feet). He noted by silhouette that parts of the airplane were missing, but he did not see any parts separate from the airplane during the time he saw it. At that time it was not raining at his location. He went inside his house, and got a digital camera, then ran back outside to his pool deck, and videotaped the descent. He reported the airplane was in a spin but could not recall the direction. The engine sound was consistent the whole time; there was no revving; he reported there was no forward movement. He called 911 and reported the accident. Another witness who was located about .4 nautical mile east-southeast of from the crash site reported hearing a boom sound that he attributed to a lawn mower which he thought odd because it had just been raining, though it was not raining at the time of the accident. He saw black smoke trailing the airplane which was spinning in what he described as a clockwise direction and flat. He ran to the side of their house, and noted the airplane was still spinning; the smoke he observed continued until he lost sight. His brother came by their back door, heard a thud, and both ran direct to the location of where they thought the airplane had crashed. When they arrived at the wreckage, they saw fire in front of the airplane which one individual attempted to extinguish by throwing sand on it, but he was unable. The other individual reported the left forward door was hard to open, but he pushed it up and then was able to open it. Both attempted to render assistance, and one individual called 911 to report the accident. One individual then guided local first responders to the accident site. The airplane crashed in an open field during daylight conditions. The location of the main wreckage was determined to be within approximately 100 feet from the last secondary radar return. Law Enforcement personnel responded to the site and accounted for five occupants. A search for the sixth occupant was immediately initiated by numerous personnel from several state agencies; he was located the following day about 1420. During that search, parts from the airplane located away from the main wreckage were documented and secured in-situ.
Probable cause:
The failure of the pilot to maintain control of the airplane while climbing to cruise altitude in instrument meteorological conditions (IMC) following disconnect of the autopilot. The reason for the autopilot disconnect could not be determined during postaccident testing. Contributing to the accident was the pilot's lack of experience in high-performance, turbo-propeller airplanes and in IMC.
Final Report:

Crash of a Learjet 60 in Aspen

Date & Time: Jun 7, 2012 at 1224 LT
Type of aircraft:
Registration:
N500SW
Flight Type:
Survivors:
Yes
Schedule:
Miami-Opa Locka - Aspen
MSN:
60-017
YOM:
1993
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18000
Captain / Total hours on type:
600.00
Copilot / Total flying hours:
13500
Aircraft flight hours:
6456
Circumstances:
While the first officer was flying the airplane on a visual approach to the airport located in a steep mountain valley, the tower controller informed him that the pilot of a Citation that had landed about 10 minutes earlier had reported low-level windshear with a 15-knot loss of airspeed on short final. The first officer used the spoilers while on the left base leg and then maneuvered the airplane in an "S-turn" on the final leg to correct for a too-steep approach. Just as the airplane was about to touch down with the airspeed decreasing, the captain made several calls for "power" and then called for a "go around." However, the first officer did not add power for a go-around, and the captain did not take control of the airplane. Both pilots reported that, when the airplane was about 30 ft above ground level (agl), they felt a sensation that the airplane had "stopped flying" with a simultaneous left roll, which is indicative of an aerodynamic stall, followed by an immediate impact with terrain. After striking obstructions that completely separated the right main landing gear and the right flap, the airplane came to rest upright in the dirt on the side of the runway about 4,000 ft from the initial impact point. The airplane sustained substantial damage to the fuselage and both wings. All eight occupants evacuated through the main cabin door. There was a substantial fuel spill but no postimpact fire. Both pilots reported no mechanical malfunctions or failures of the airplane, and neither pilot reported an uncommanded loss of engine power. Data from the enhanced ground proximity warning system showed that seven warning events occurred in the last 3 minutes before the accident. The first warning was for "sink rate," and it occurred when the airplane was about 1,317 ft agl and in a 3,400-ft-per-minute descent. The last warning was for "bank angle," and it occurred about 10 seconds before touchdown as the airplane exceeded 42 degrees of bank when it was about 200 ft agl. The wind recorded at the airport at the time of the accident would have resulted in a 12-knot variable tailwind with gusts to 18 knots. The evidence is consistent with the first officer flying a non stabilized approach with a decreasing airspeed during low-level windshear conditions. The first officer did not properly compensate for the known low-level windshear conditions and allowed the airspeed to continue to decrease and the bank angle to increase until the airplane experienced an aerodynamic stall.
Probable cause:
The first officer's failure to maintain adequate airspeed and his exceedance of the airplane's critical angle-of-attack during the final approach in known low-level windshear conditions, which resulted in an aerodynamic stall. Contributing to the accident were the first officer's failure to initiate a go-around when commanded and the captain's lack of remedial action when he recognized that the approach was unstabilized.
Final Report: