Crash of a Canadair CL-601 Challenger off Aruba: 3 killed

Date & Time: Jan 29, 2015
Type of aircraft:
Operator:
Registration:
N214FW
Flight Phase:
Flight Type:
Survivors:
No
MSN:
3008
YOM:
1983
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The aircraft left an airfield located somewhere in the State of Apure, Venezuela, apparently bound for the US with three people on board. While flying north of Punto Fijo, above the sea, the crew was contacted by ATC but failed to respond. Convinced this was an illegal flight, the Venezuelan Authorities decided to send a fighter to intercept the Challenger that was shot down. Out of control, it dove into the Caribbean Sea and crashed off the coast of Aruba Island. All three occupants were killed and on site, more than 400 boxes containing cocaine were found.
Probable cause:
Shot down by the pilot of a Venezuelan Air Force fighter.

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

Date & Time: Jan 15, 2015 at 1900 LT
Operator:
Registration:
D-EMBZ
Flight Type:
Survivors:
Yes
MSN:
46-22148
YOM:
1993
Country:
Region:
Crew on board:
1
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The approach to Donaueschingen-Villingen Airport runway 36 was completed by night. On final, the single engine airplane struck the ground about 50 metres short of runway threshold, collided with runway light equipments and came to rest near the threshold with its left wing partially torn off. All five occupants escaped with minor injuries and the aircraft was destroyed.

Crash of a Partenavia P.68C-TC in La Bonanza: 1 killed

Date & Time: Dec 23, 2014
Type of aircraft:
Operator:
Registration:
YV1706
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Valencia – Charallave
MSN:
242-07-TC
YOM:
1982
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Circumstances:
The pilot Amílcar Suárez, sole on board, was killed when the twin engine aircraft crashed in unknown circumstances in a mountainous area located near La Bonanza. The aircraft was destroyed by a post crash fire. It was en route from Valencia to Charallave.

Crash of a Learjet 25D in Champotón: 2 killed

Date & Time: Dec 19, 2014 at 1800 LT
Type of aircraft:
Operator:
Registration:
N265TW
Flight Type:
Survivors:
No
MSN:
265
YOM:
1979
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
The crew was performing a flight from Texas and the aircraft was carrying a load consisting of six fuel drums according to a Campeche daily newspaper. The Learjet 25D was flying at a very low altitude, maybe in an attempt to land, when it crashed and burned in an open field located in Champotón, some 40 km south of Campeche. Both crew members were killed. Illegal flight suspected.

Crash of an Embraer EMB-500 Phenom 100 in Gaithersburg: 6 killed

Date & Time: Dec 8, 2014 at 1041 LT
Type of aircraft:
Operator:
Registration:
N100EQ
Flight Type:
Survivors:
No
Site:
Schedule:
Chapel Hill - Gaithersburg
MSN:
500-00082
YOM:
2009
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
4737
Captain / Total hours on type:
136.00
Aircraft flight hours:
634
Aircraft flight cycles:
552
Circumstances:
The airplane crashed while on approach to runway 14 at Montgomery County Airpark (GAI), Gaithersburg, Maryland. The airplane impacted three houses and the ground about 3/4 mile from the approach end of the runway. A postcrash fire involving the airplane and one of the three houses, which contained three occupants, ensued. The pilot, the two passengers, and the three people in the house died as a result of the accident. The airplane was destroyed by impact forces and postcrash fire. The flight was operating on an instrument flight rules flight plan under the provisions of 14 Code of Federal Regulations (CFR) Part 91. Visual meteorological conditions prevailed at the time of the accident. Data from the airplane’s cockpit voice and data recorder (CVDR) indicated that the takeoff about 0945 from Horace Williams Airport, Chapel Hill, North Carolina, and the cruise portion of the flight were uneventful. CVDR data showed that about 15 minutes after takeoff, the passenger in the right cockpit seat made a statement that the airplane was “in the clouds.” A few seconds later, the airplane’s engine anti-ice system and the wing and horizontal stabilizer deice system were manually activated for about 2 minutes before they were manually turned off. About 6 minutes later, a recording from the automated weather observing system (AWOS) at GAI began transmitting over the pilot’s audio channel, containing sufficient information to indicate that conditions were conducive to icing during the approach to GAI. The CVDR recorded no activity or faults during the rest of the flight for either ice protection system, indicating that the pilot did not turn the systems back on. Before the airplane descended through 10,000 ft, in keeping with procedures in the EMB-500 Pilot Operating Handbook, the pilot was expected to perform the Descent checklist items in the Quick Reference Handbook (QRH), which the pilot should have had available in the airplane during the flight. Based on the AWOS-reported weather conditions, the pilot should have performed the Descent checklist items that appeared in the Normal Icing Conditions checklist, which included turning on the engine anti-ice and wing and horizontal stabilizer deice systems. That action, in turn, would require the pilot to use landing distance performance data that take into account the deice system’s activation. CVDR data show that, before beginning the descent, the pilot set the landing reference (Vref) speed at 92 knots, indicating that he used performance data for operation with the wing and horizontal stabilizer deice system turned off and an airplane landing weight less than the airplane’s actual weight. Using the appropriate Normal Icing Conditions checklist and accurate airplane weight, the pilot should have flown the approach at 126 knots (a Vref of 121 knots +5 knots) to account for the icing conditions.
Probable cause:
The National Transportation Safety Board determines that the probable cause of this accident was the pilot’s conduct of an approach in structural icing conditions without turning on the airplane’s wing and horizontal stabilizer deice system, leading to ice accumulation on those surfaces, and without using the appropriate landing performance speeds for the weather conditions and airplane weight, as indicated in the airplane’s standard operating procedures, which together resulted in an aerodynamic stall at an altitude at which a recovery was not possible.
Final Report:

Crash of a Gulfstream GIII in Biggin Hill

Date & Time: Nov 24, 2014 at 2030 LT
Type of aircraft:
Operator:
Registration:
N103CD
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Biggin Hill - Gander
MSN:
418
YOM:
1984
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4120
Captain / Total hours on type:
3650.00
Circumstances:
On 24 November 2014 the crew of Gulfstream III N103CD planned for a private flight from Biggin Hill Airport to Gander International Airport in Canada. The weather reported at the airport at 2020 hrs was wind ‘calm’, greater than 10 km visibility with fog patches, no significant cloud, temperature 5°C, dew point 4°C and QNH 1027 hPa. At 2024 hrs, the crew was cleared to taxi to Holding Point J1 for a departure from Runway 03. After the crew read back the taxi clearance, the controller transmitted: “we are giving low level fog patches on the airfield, general visibility in excess of 10 km but visibility not measured in the fog patches. it seems to be very low, very thin fog from the zero three threshold to approximately half way down the runway then it looks completely clear”. The crew acknowledged the information. At 2028 hrs, the aircraft was at the holding point and was cleared for takeoff by the controller. The aircraft taxied towards the runway from J1 but lined up with the runway edge lights, which were positioned 3 m to the right of the edge of the runway. The aircraft began its takeoff run at 2030 hrs, passing over paved surface for approximately 248 m before running onto grass which lay beyond. The commander, who was the handling pilot, closed the thrust levers to reject the takeoff when he realized what had happened and the aircraft came to a halt on the grass having suffered major structural damage. The crew shut down the engines but were unable to contact ATC on the radio to tell the controller what had happened. The co-pilot moved from the flight deck into the passenger cabin and saw that no one had been injured. He vacated the aircraft through the rear baggage compartment and then helped the commander, who was still inside, to open the main exit door. The commander and the five passengers used the main exit to vacate the aircraft. The controller saw that the aircraft had stopped but did not realize that it was not on the runway. He attempted to contact the crew on the radio but, when he saw the lights of the aircraft switch off, he activated the crash alarm, at 2032 hrs, declaring an aircraft ground incident. At 2034 hrs the airport fire service reached the aircraft and declared an aircraft accident, after which the airport emergency plan was activated.
Probable cause:
This was a private flight which could not depart in conditions of less than 400 m RVR. RVR cannot be measured at the threshold end of Runway 03 but the prevailing visibility was reported as being more than 10 km. The crew reported that there was moisture on the windscreen from the mist and they could see a “glow” around lights which were visible to them. They were also aware while taxiing that there was some patchy ground fog on the airfield. The ATC controller transmitted that visibility had not been measured in the fog patches but there seemed to be ‘very low, very thin fog from the zero three threshold to approximately half way down the runway’. With hindsight, this piece of information is significant but, at the time, the crew did not consider the fog to be widespread or thick; operating under FAR Part 91 in the United States, they were used to making their own judgments as to whether the visibility was suitable for a takeoff. However, after the aircraft came to a halt following its abortive takeoff attempt, the controller could only see the top of the fuselage and tail above the layer of fog. It is likely, therefore, that the visibility was worse than the crew appreciated at the time N103CD taxied from Holding Point J1. The route from J1 to the runway The information on the aerodrome chart used by the crew, and the source of information in the UK AIP, suggested that the aircraft would be required to taxi in a straight line from J1 to the runway and then make a right turn onto the runway heading. In fact, in order to taxi from J1 onto the runway, an aircraft must: taxi in a straight line; follow a curve to the right onto runway heading but still displaced to the right of the runway itself; turn left towards the runway; and then turn right again onto runway heading. The UK AIP states that there is no centreline lighting on Runway 03, and that the pavement width at the beginning of the runway is twice the normal runway width. It recognizes the potential for confusion and urges crews to ensure that they have lined up correctly. This information was not available to the crew on their aerodrome charts and both crew members believed that the runway had centreline lighting. Further, the light from those left-side runway edge lights covered in fog would have been scattered, making it harder for the crew to perceive them as a distinct line of lights. The situation is likely to have been made worse by the bright lights reflecting off the top of the fog layer, making the underlying runway lights even harder to see, or swamping them completely as shown in Figure 5. The CCTV images in Figure 5 show that peripheral lighting can interact with low fog layers to reduce the visibility of underlying aerodrome lighting. Current standards associated with apron lighting only address the minimum light levels required to make the areas safe and there are no standards relating to light spilling into other areas.
Human and environmental factors Five of the factors identified by the ATSB as being present in misaligned takeoffs were present in this accident:
1. It was dark.
2. It was potentially a confusing taxiway environment given that the aerodrome chart did not reflect the actual layout of the taxiways. Pilots had previously reported having difficulty when vacating the runway near the Runway 03 threshold because of a lack of taxiway lighting.
3. There was an additional paved area (the ORP) near the runway.
4. There was no runway centreline lighting and the runway edge lights before the displaced threshold were recessed.
5. There was reduced visibility.
It appeared that the information available to the crew caused them to develop an incorrect expectation of their route to the runway. Both crew members believed that the runway had centreline lighting and, when the first right turn almost lined the aircraft up with some lights, their incorrect expectation was reinforced and they believed that the aircraft was lined up correctly. Cues to the contrary, such as runway edge lights on the other side of the runway, or the fact that the first three lights ahead of the aircraft were red (indicating that they were edge lights before the displaced threshold), did not appear to have been strong enough to make the crew realize that they had lost situational awareness. Figure 8 indicates that the apparent intensity of the white left-side runway edge lights was significantly less than that of the right-side lights, when viewed from the position where the aircraft lined up. This, along with other visual issues relating to contrast and the fog, is a plausible explanation as to why they were not noticed by the crew. The aircraft began its takeoff roll from a location beyond the first red runway edge light and approximately 46 m short of the next light, as shown in Figure 1. Aircraft structure only obscures approximately the first 13 m of pavement ahead of pilots within a Gulfstream III aircraft and therefore these lights would not have been obscured by the aircraft. However, it is likely that the recessed nature of the red edge lights before the displaced threshold made them less compelling than the elevated white edge lights beyond, which would explain why their significance – that they could only have been runway edge lights – was not appreciated by the flight crew.
Final Report:

Crash of a Piper PA-31-425 Pressurized Navajo in Conrado Castillo: 6 killed

Date & Time: Nov 14, 2014 at 1730 LT
Type of aircraft:
Operator:
Registration:
XB-ZAX
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
San Luis Potosí – Ciudad Victoria – Torreón
MSN:
31-46
YOM:
1967
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
6
Circumstances:
The twin engine aircraft departed San Luis Potosí on a flight to Torreón with an intermediate stop in Ciudad Victoria, carrying five passengers and one pilot. At the end of the afternoon, while descending to Ciudad Victoria Airport, the pilot encountered poor weather conditions. Too low, the aircraft impacted trees and crashed in a hilly terrain located near Conrado Castillo. The wreckage was found the following morning about 60 km northwest of Ciudad Victoria Airport. The aircraft disintegrated on impact and all six occupants were killed.
Pilot:
Juan José Castro Maldonado
Passengers:
Maribel Lumbreras,
Paulina García Lumbreras,
Lucero Salazar Méndez,
Juana Lumbreras Ruiz,
Guadalupe Lumbreras Ruiz.

Crash of a Piper PA-46-310P Malibu in Dubuque: 1 killed

Date & Time: Oct 13, 2014 at 2305 LT
Registration:
N9126V
Flight Type:
Survivors:
No
Schedule:
Ankeny – Dubuque
MSN:
46-08087
YOM:
1987
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
1003
Captain / Total hours on type:
100.00
Aircraft flight hours:
4785
Circumstances:
The instrument-rated private pilot was returning to his home airport after flying to another location to attend a meeting. At the departure airport, the pilot filed an instrument flight rules flight plan, had it activated, and then departed for his home airport. After reaching his assigned altitude, the pilot requested clearance directly to his destination with air traffic control, and he was cleared as requested. Before arriving at his airport, he requested off frequency to get the NOTAMs and weather conditions for his destination. The weather conditions at the arrival airport included a 200-ft overcast ceiling and 5 miles visibility with light rain and mist. The pilot then requested the instrument landing system (ILS) approach for landing. An air traffic controller issued vectors to the ILS final approach course and cleared the pilot to change off their frequency. Witnesses at the airport reported hearing and seeing the airplane break out of the clouds, fly over the runway about 100 ft above ground level (agl), and then disappear back into the clouds. Two witnesses stated that the engine sounded as if it were at full power and another witness stated that he heard the engine "revving" as if flew overhead. Shortly after the airplane was seen over the airport, it struck a line of 80-ft tall trees about 3,600 ft north-northwest of the airport and subsequently impacted the ground and a large tree near a residence. The published missed approach procedures required the pilot to climb the airplane to an altitude of 2,000 ft mean sea level (msl), or about 900 ft agl, while flying the runway heading. Upon reaching 2,000 ft msl, the pilot was required to begin a left turn to the northwest and then continue climbing to 3,300 ft msl. An examination of the airplane, the engine, and other airplane systems revealed no anomalies that would have precluded the airplane from being able to fully perform in a climb during the missed approach. It is likely that the pilot lost airplane control after initiating a missed approach in instrument meteorological conditions. Although it is possible that the pilot may have experienced spatial disorientation, there was insufficient evidence to conclude that spatial disorientation contributed to the accident.
Probable cause:
The pilot's loss of airplane control while attempting to fly a missed approach procedure in instrument meteorological conditions.
Final Report:

Crash of a Rockwell 690C Jetprop 840 off Los Roques

Date & Time: Oct 10, 2014 at 1000 LT
Operator:
Registration:
YV1315
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Los Roques - Charallave
MSN:
690-11618
YOM:
1980
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The twin engine aircraft was performing a private flight from the island of Los Roques to Charallave-Óscar Machado Zuloaga Airport. Shortly after take off, while in initial climb, the aircraft went out of control and crashed in a lagoon, few metres off shore. All seven occupants evacuated and were slightly injured while the aircraft broke in two in shallow water.

Crash of a Socata TBM-850 in Fayetteville

Date & Time: Oct 5, 2014 at 1255 LT
Type of aircraft:
Operator:
Registration:
N536EM
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Atlanta – Pine Mountain
MSN:
536
YOM:
2010
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4244
Captain / Total hours on type:
411.00
Aircraft flight hours:
719
Circumstances:
The private pilot was conducting a personal cross-country flight. The pilot reported that, during cruise flight at 6,000 ft mean sea level, he observed a crew alerting system oil pressure message, followed by a total loss of engine power. An air traffic controller provided vectors to a local airport; however, the pilot reported that the airplane would not reach the runway. He did not attempt to restart the engine. He feathered the propeller and placed the power lever to "idle" and the condition lever to "cut off." The pilot subsequently attempted a forced landing to a sports field with the gear and flaps retracted. The airplane collided with trees and the ground and then came to rest upright. Examination of the engine revealed that it displayed contact signatures to its internal components and evidence of ingested unburned organic debris, consistent with the engine likely being unpowered and the engine gas generator and power sections wind-milling at the time of impact. No evidence of any preimpact mechanical anomalies or malfunctions to any of the engine components was found that would have precluded normal operation. Recorded GPS flight track and systems data showed that the loss of engine power was preceded by about 5 minutes of flight on a constant heading and altitude with an excessive lateral g force of about 0.17 g and a bank angle between about 8 and 10 degrees, consistent with a side-slip flight condition. The airplane then entered a right turn with the autopilot engaged, and it lost power at the end of the turn. The data indicated that, even though the autopilot was engaged, the lateral g forces increased as the airplane leveled off and accelerated, indicating that the automatic rudder trim feature of the yaw damper system was not engaged. Given that the yaw damper system operated normally after the flight, it is likely that the pilot inadvertently and unknowingly disengaged the yaw damper during flight with the autopilot engaged. During a postaccident interview, the pilot stated that he was not aware of a side-slip condition before the loss of engine power. Although the fuel tank system was designed to prevent unporting of the fuel lines during momentary periods of uncoordinated flight, it was not intended to do so for extended periods of uncoordinated flight. Therefore, the fuel tank feed line likely unported during the prolonged uncoordinated flight, which resulted in the subsequent loss of engine power. If the pilot had recognized the side-slip condition, he could have returned to coordinated flight and prevented the engine power loss. Also, once the airplane returned to coordinated flight, an engine restart would have been possible.
Probable cause:
The pilot's inadvertent deactivation of the yaw damper in flight, which resulted in a prolonged side-slip condition that led to fuel starvation and the eventual total loss of engine power. Contributing to the accident was the pilot's failure to attempt to restart the engine.
Final Report: