Crash of a BAe 125-700A in Saltillo: 8 killed

Date & Time: Apr 19, 2014 at 1946 LT
Type of aircraft:
Registration:
XA-UKR
Survivors:
No
Site:
Schedule:
Cozumel - Saltillo
MSN:
257191
YOM:
1982
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
6
Pax fatalities:
Other fatalities:
Total fatalities:
8
Captain / Total flying hours:
12984
Captain / Total hours on type:
4470.00
Copilot / Total flying hours:
620
Copilot / Total hours on type:
67
Aircraft flight hours:
6166
Aircraft flight cycles:
4699
Circumstances:
Following an uneventful flight from Cozumel, the crew initiated an ILS/DME2 approach to Saltillo-Plan de Guadalupe Airport Runway 17. On final, the crew encountered poor visibility due to foggy conditions. Despite he was unable to establish a visual contact with the runway, the crew continued the approach and descended below the MDA when the aircraft collided with power cables and crashed on a building located in an industrial park, 1,448 metres short of runway. The aircraft was destroyed by impact forces and a post crash fire and all eight occupants were killed. The building was also destroyed by fire. At the time of the accident, the horizontal visibility was estimated to be 800 metres with a vertical visibility of 200 feet.
Probable cause:
The accident was the consequence of the decision of the crew to continue the approach below MDA in IMC conditions until the aircraft collided with power cables and impacted ground. The following contributing factors were identified:
- The approach was unstable,
- The decision of the crew to continue the approach below MDA without visual contact with the runway,
- Poor safety culture by the operator,
- The crew failed to comply with procedures related to an ILS/DME2 approach to runway 17,
- Lack of crew resources management,
- The crew failed to respond to the GPWS alarm,
- The crew did not monitor the altitude during the final approach,
- Poor weather conditions with a visibility below minimums,
- Inadequate maintenance controls,
- The crew failed to follow the SOP's.
Final Report:

Crash of a Rockwell 690B Turbo Commander in New Haven: 4 killed

Date & Time: Aug 9, 2013 at 1121 LT
Registration:
N13622
Flight Type:
Survivors:
No
Site:
Schedule:
Teterboro - New Haven
MSN:
11469
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
2067
Aircraft flight hours:
8827
Circumstances:
The pilot was attempting a circling approach with a strong gusty tailwind. Radar data and an air traffic controller confirmed that the airplane was circling at or below the minimum descent altitude of 720 feet (708 feet above ground level [agl]) while flying in and out of an overcast ceiling that was varying between 600 feet and 1,100 feet agl. The airplane was flying at 100 knots and was close to the runway threshold on the left downwind leg of the airport traffic pattern, which would have required a 180-degree turn with a 45-degree or greater bank to align with the runway. Assuming a consistent bank of 45 degrees, and a stall speed of 88 to 94 knots, the airplane would have been near stall during that bank. If the bank was increased due to the tailwind, the stall speed would have increased above 100 knots. Additionally, witnesses saw the airplane descend out of the clouds in a nose-down attitude. Thus, it was likely the pilot encountered an aerodynamic stall as he was banking sharply, while flying in and out of clouds, trying to align the airplane with the runway. Toxicological testing revealed the presence of zolpidem, which is a sleep aid marketed under the brand name Ambien; however, the levels were well below the therapeutic range and consistent with the pilot taking the medication the evening before the accident. Therefore, the pilot was not impaired due to the zolpidem. Examination of the wreckage did not reveal any preimpact mechanical malfunctions.
Probable cause:
The pilot's failure to maintain airspeed while banking aggressively in and out of clouds for landing in gusty tailwind conditions, which resulted in an aerodynamic stall and uncontrolled descent.
Final Report:

Crash of a Beechcraft 200 Super King Air in Palwaukee

Date & Time: Jun 25, 2013 at 2030 LT
Operator:
Registration:
N92JR
Flight Type:
Survivors:
Yes
Site:
Schedule:
Springfield - Palwaukee
MSN:
BB-751
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
7125
Captain / Total hours on type:
572.00
Aircraft flight hours:
6709
Circumstances:
Before departure, the pilot performed fuel calculations and determined that he had enough fuel to fly to the intended destination. While enroute the pilot flew around thunderstorms. On arrival at his destination, the pilot executed the instrument landing system approach for runway 16. While on short final the right engine experienced a total loss of power. The pilot switched the fuel flow from the right tank to the left tank. The left engine then experienced a total loss of power and the pilot made an emergency landing on a road. The airplane received substantial damage to the wings and fuselage when it struck a tree. A postaccident examination revealed only a few gallons of unusable fuel in the left fuel tank. The right fuel tank was breached during the accident sequence but no fuel smell was noticed. The pilot performed another fuel calculation after the accident and determined that there were actually 170 gallons of fuel onboard, not 230 gallons like he originally figured. He reported no preaccident mechanical malfunctions that would have precluded normal operation and determined that he exhausted his entire fuel supply.
Probable cause:
The pilot's improper fuel planning and management, which resulted in a loss of engine power due to fuel exhaustion.
Final Report:

Crash of a Beechcraft B200GT Super King Air in Baker: 1 killed

Date & Time: Jun 7, 2013 at 1310 LT
Operator:
Registration:
N510LD
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Baton Rouge - McComb
MSN:
BY-24
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
15925
Captain / Total hours on type:
5200.00
Aircraft flight hours:
974
Circumstances:
The accident pilot and two passengers had just completed a ferry flight on the recently purchased airplane. A review of the airplane’s cockpit voice recorder audio information revealed that, during the ferry flight, one of the passengers, who was also a pilot, was pointing out features of the new airplane, including the avionics suite, to the accident pilot. The pilot had previously flown another similar model airplane, but it was slightly older and had a different avionics package; the new airplane’s avionics and flight management system were new to the pilot. After completing the ferry flight and dropping off the passengers, the pilot departed for a short cross-country flight in the airplane. According to air traffic control recordings, shortly after takeoff, an air traffic controller assigned the pilot a heading and altitude. The pilot acknowledged the transmission and indicated that he would turn to a 045 heading. The radio transmission sounded routine, and no concern was noted in the pilot’s voice. However, an audio tone consistent with the airplane’s stall warning horn was heard in the background of the pilot’s radio transmission. The pilot then made a radio transmission stating that he was going to crash. The audio tone was again heard in the background, and distress was noted in the pilot’s voice. The airplane impacted homes in a residential neighborhood; a postcrash fire ensued. A review of radar data revealed that the airplane made a climbing right turn after departure and then slowed and descended. The final radar return showed the airplane at a ground speed of 102 knots and an altitude of 400 feet. Examination of the engines and propellers indicated that the engines were rotating at the time of impact; however, the amount of power the engines were producing could not be determined. The examination of the airplane did not reveal any abnormalities that would have precluded normal operation. It is likely that the accident pilot failed to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain, and that his lack of specific knowledge of the airplane’s avionics contributed to the accident.
Probable cause:
The pilot’s failure to maintain adequate airspeed during departure, which resulted in an aerodynamic stall and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of specific knowledge of the airplane’s avionics.
Final Report:

Crash of a Comp Air CA-8 in Sorocaba: 2 killed

Date & Time: May 29, 2013 at 1540 LT
Type of aircraft:
Operator:
Registration:
PP-XLR
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Sorocaba - Jundiaí
MSN:
0204CA8
YOM:
2006
Country:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
Shortly after take off from Sorocaba Airport, while climbing, the pilot encountered technical problems and elected to return. While trying to land in a wasteland, the single engine aircraft crashed in a street and was destroyed by impact forces and a post impact fire. Both occupants were killed as a house was also destroyed.

Crash of a Learjet 60 in Valencia: 2 killed

Date & Time: May 5, 2013 at 1000 LT
Type of aircraft:
Operator:
Registration:
N119FD
Flight Type:
Survivors:
No
Site:
Schedule:
Charallave – Valencia
MSN:
60-029
YOM:
1994
Country:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Circumstances:
On final approach to Valencia-Arturo Michelana Airport in marginal weather conditions, the aircraft crashed in a residential area some 2,055 metres short of runway. The aircraft was totally destroyed by impact forces and a post impact fire and both pilots were killed. A building, several houses and cars were also damaged by fire.

Crash of a Raytheon 390 Premier I in South Bend: 2 killed

Date & Time: Mar 17, 2013 at 1623 LT
Type of aircraft:
Operator:
Registration:
N26DK
Survivors:
Yes
Site:
Schedule:
Tulsa - South Bend
MSN:
RB-226
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
613
Captain / Total hours on type:
171.00
Copilot / Total flying hours:
1877
Copilot / Total hours on type:
0
Aircraft flight hours:
457
Circumstances:
According to the cockpit voice recorder (CVR), during cruise flight, the unqualified pilot-rated passenger was manipulating the aircraft controls, including the engine controls, under the supervision and direction of the private pilot. After receiving a descent clearance to 3,000 feet mean sea level (msl), the pilot told the pilot-rated passenger to reduce engine power to maintain a target airspeed. The cockpit area microphone subsequently recorded the sound of both engines spooling down. The pilot recognized that the pilot-rated passenger had shutdown both engines after he retarded the engine throttles past the flight idle stops into the fuel cutoff position. Specifically, the pilot stated "you went back behind the stops and we lost power." According to air traffic control (ATC) radar track data, at the time of the dual engine shutdown, the airplane was located about 18 miles southwest of the destination airport and was descending through 6,700 feet msl. The pilot reported to the controller that the airplane had experienced a dual loss of engine power, declared an emergency, and requested radar vectors to the destination airport. As the flight approached the destination airport, the cockpit area microphone recorded a sound similar to an engine starter spooling up; however, engine power was not restored during the attempted restart. A review of the remaining CVR audio did not reveal any evidence of another attempt to restart an engine. The CVR stopped recording while the airplane was still airborne, with both engines still inoperative, while on an extended base leg to the runway. Subsequently, the controller told the pilot to go-around because the main landing gear was not extended. The accident airplane was then observed to climb and enter a right traffic pattern to make another landing approach. Witness accounts indicated that only the nose landing gear was extended during the second landing approach. The witnesses observed the airplane bounce several times on the runway before it ultimately entered a climbing right turn. The airplane was then observed to enter a nose low, rolling descent into a nearby residential community. The postaccident examinations and testing did not reveal any anomalies or failures that would have precluded normal operation of the airplane. Although the CVR did not record a successful engine restart, the pilot was able to initiate a go-around during the initial landing attempt, which implies that he was able to restart at least one engine during the initial approach. The investigation subsequently determined that only the left engine was operating at impact. Following an engine start, procedures require that the respective generator be reset to reestablish electrical power to the Essential Bus. If the Essential Bus had been restored, all aircraft systems would have operated normally. However, the battery toggle switch was observed in the Standby position at the accident site, which would have prevented the Essential Bus from receiving power regardless of whether the generator had been reset. As such, the airplane was likely operating on the Standby Bus, which would preclude the normal extension of the landing gear. However, the investigation determined that the landing gear alternate extension handle was partially extended. The observed position of the handle would have precluded the main landing gear from extending (only the nose landing gear would extend). The investigation determined that it is likely the pilot did not fully extend the handle to obtain a full landing gear deployment. Had he fully extended the landing gear, a successful single-engine landing could have been accomplished. In conclusion, the private pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls directly resulted in the inadvertent dual engine shutdown during cruise descent. Additionally, the pilot's inadequate response to the emergency, including his failure to adhere to procedures, resulted in his inability to fully restore airplane systems and ultimately resulted in a loss of airplane control.
Probable cause:
The private pilot's inadequate response to the dual engine shutdown during cruise descent, including his failure to adhere to procedures, which ultimately resulted in his failure to
maintain airplane control during a single-engine go-around. An additional cause was the pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls, which directly resulted in the inadvertent dual engine shutdown.
Final Report:

Crash of a Piper PA-31T Cheyenne II in Fort Lauderdale: 3 killed

Date & Time: Mar 15, 2013 at 1621 LT
Type of aircraft:
Registration:
N63CA
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Fort Lauderdale - Fort Lauderdale
MSN:
31-7820033
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
10000
Aircraft flight hours:
5006
Circumstances:
The multiengine airplane had not been flown for about 4 months and was being prepared for export. The pilot was attempting a local test flight after avionics upgrades had been performed. Shortly after takeoff, the pilot transmitted that he was experiencing an "emergency"; however, he did not state the nature of the emergency. The airplane was observed experiencing difficulty climbing and entered a right turn back toward the airport. It subsequently stalled, rolled right about 90 degrees, and descended. The airplane impacted several parked vehicles and came to rest inverted. A postcrash fire destroyed the airframe. Both engines were destroyed by fire and impact damage. The left propeller assembly was fire damaged, and the right propeller assembly remained attached to the gearbox, which separated from the engine. Examination of wreckage did not reveal any preimpact malfunctions. It was noted that the left engine displayed more pronounced rotational signatures than the right engine, but this difference could be attributed to the impact sequence. The left propeller assembly displayed evidence of twisting and rotational damage, and the right propeller assembly did not display any significant evidence of twisting or rotational damage indicative of operation with a difference in power. The lack of flight recorders and the condition of the wreckage precluded the gathering of additional relevant information.
Probable cause:
The pilot's failure to maintain airplane control following an emergency, the nature of which could not be determined because of crash and fire damage, which resulted in an aerodynamic stall.
Final Report:

Crash of a Fokker 50 in Goma: 7 killed

Date & Time: Mar 4, 2013 at 1744 LT
Type of aircraft:
Operator:
Registration:
9Q-CBD
Flight Type:
Survivors:
Yes
Site:
Schedule:
Kananga - Lodja - Goma
MSN:
20270
YOM:
1992
Location:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
The aircraft was completing a cargo flight from Kananga to Goma with an intermediate stop in Lodja, carrying four passengers, 6 crew members and a load of various goods. On final approach to Goma Airport Runway 36, the crew encountered poor weather conditions with limited visibility due to heavy rain falls. On final, the aircraft contacted the roof of a house and crashed in the garden of a residential area, coming to rest upside down. Three passengers were seriously injured while seven other occupants were killed.

Crash of an Antonov AN-26 in Sanaa: 10 killed

Date & Time: Nov 21, 2012
Type of aircraft:
Operator:
Registration:
420
Flight Phase:
Flight Type:
Survivors:
No
Site:
Country:
Region:
Crew on board:
10
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
10
Circumstances:
After takeoff from Sana'a Airport, while climbing, the crew informed ATC about technical problems and elected to make an emergency landing in a wasteland. The aircraft went out of control and crashed in an abandoned market building located in the Al-Hasaba District, some 9 km south of Sanaa' Airport. All 10 occupants were killed. According to Yemen Officials, the aircraft was registered 420 but no AN-26 seems to be operated in Yemen under this registration.