Zone

Crash of a Socata TBM-850 in Las Vegas

Date & Time: Nov 5, 2017 at 1145 LT
Type of aircraft:
Operator:
Registration:
N893CA
Flight Type:
Survivors:
Yes
Schedule:
Tomball – Las Vegas
MSN:
393
YOM:
2007
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3000
Captain / Total hours on type:
1850.00
Aircraft flight hours:
2304
Circumstances:
The pilot of the turbine-powered airplane reported that, while landing in a gusting crosswind, it was "obvious" the wind had changed directions. He performed a go-around, but "the wind slammed [the airplane] to the ground extremely hard." Subsequently, the airplane veered to the right off the runway and then back to the left before coming to rest. The airplane sustained substantial damage to the fuselage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The automated weather observation system located at the accident airport reported that, about the time of the accident, the wind was from 270° at 19 knots, gusting to 25 knots. The pilot landed on runway 20.
Probable cause:
The pilot's inadequate compensation for gusting crosswind conditions during the go-around.
Final Report:

Crash of a Rockwell Aero Commander 500A in McDade: 1 killed

Date & Time: Nov 23, 2014 at 0945 LT
Operator:
Registration:
N14AV
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Tomball – Austin
MSN:
500-914-22
YOM:
1960
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
7075
Captain / Total hours on type:
168.00
Aircraft flight hours:
12859
Circumstances:
The airline transport pilot was conducting a cross-country repositioning flight. While en route to the destination airport, the pilot contacted air traffic control and stated that he was beginning to descend. No further radio transmissions were made by the pilot. Radar and GPS information showed, about the same time as the pilot's last transmission, the airplane's flightpath began descending in a westerly direction. The last recorded GPS point showed the airplane about 200 ft southwest of the initial impact point, 90 ft above ground level, and at a groundspeed of 66 knots. The airplane wreckage was located in an open field and impact signatures were consistent with a stall/spin, which had resulted in a near-vertical impact at a slow airspeed. The right propeller blades were found in the feathered position. Examination of the right engine found that the oil gauge housing extension was improperly secured to the oil gauge housing, which resulted in a loss of engine oil. Additionally, the examination revealed a hole in the right engine's crankcase, metal material in the oil sump, and signatures consistent with the lack of lubrication. Cockpit switches were positioned in accordance with the in-flight shutdown of the right engine. No anomalies were found with the left engine or airframe that would have precluded normal operation. Another pilot who had flown with the accident pilot reported that the pilot typically used the autopilot, and the autopilot system was found with the roll, heading, and pitch modes active. During the descent, no significant changes of heading were recorded, and the direction of travel before the stall was not optimal for the airplane to land before a fence line. It is likely that the autopilot was controlling the airplane's flightpath before the stall. Despite one operating engine, the pilot did not maintain adequate airspeed and exceeded the airplane's critical angle-of-attack (AOA), which resulted in an aerodynamic stall/spin. Correcting the last GPS recorded airspeed for prevailing wind, the airplane's indicated airspeed would have been about 72 knots, which is above the airplane's 0-bank stall speed, but an undetermined mount of bank would have been applied to maintain heading, which would have accelerated the stall speed. It could not be determined why the pilot did not maintain adequate airspeed or notify air traffic controller of an engine problem. Although a review of the pilot's medical records revealed that he had several historical medical conditions and the toxicology tests detected several sedating allergy medications in his system, it was inconclusive whether the medical conditions or medications impaired the pilot's ability to fly the airplane or if the pilot was incapacitated. It is also possible that the pilot was distracted by the loss of oil from the right engine and that this resulted in his failure to maintain adequate airspeed, his exceedance of the airplane's critical AOA, and a subsequent stall/spin; however, based on the available evidence, the investigation could not determine the reason for the pilot's lack of corrective actions.
Probable cause:
The pilot's failure to maintain adequate airspeed and his exceedance of the airplane's critical angle-of-attack for reasons that could not be determined based on the available evidence, which resulted in an aerodynamic stall/spin. Contributing to the accident was the improperly installed oil gauge housing extension, which resulted in a loss of oil quantity and right engine power.
Final Report:

Crash of a Cessna 340A in Angel Fire

Date & Time: Aug 31, 2008 at 2045 LT
Type of aircraft:
Registration:
N397RA
Flight Type:
Survivors:
Yes
Schedule:
Tomball – Angel Fire
MSN:
340A-0009
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4725
Captain / Total hours on type:
625.00
Aircraft flight hours:
6507
Circumstances:
The pilot reported that he was cleared for a GPS approach and broke out of the clouds at 1,800 feet. He entered a left hand traffic pattern and his last recollection was turning base. He woke up in the crashed airplane which was on fire. The airplane was destroyed. An examination of airplane systems revealed no anomalies.
Probable cause:
Controlled flight into terrain for unknown reasons.
Final Report:

Crash of a Cessna 414 Chancellor in Rocksprings: 2 killed

Date & Time: Feb 9, 2007 at 1715 LT
Type of aircraft:
Operator:
Registration:
N69845
Survivors:
No
Schedule:
Houston – Rocksprings
MSN:
414-0637
YOM:
1975
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2212
Aircraft flight hours:
5466
Circumstances:
The 2,212-hour instrument rated commercial pilot collided with terrain while circling to land after completing an instrument approach to an uncontrolled non-towered airport. The airport had two instrument approaches to Runway 14; a VOR and a RNAV(GPS). The published minimums for a circling approach to Runway 32 are a 500 foot ceiling and one mile visibility (VOR14) and a 700 foot ceiling and one mile visibility for RNAV(GPS) to Runway 14. The weather at the airport at the time of the accident was reported as 300 overcast, visibility of 3/4 of a mile in mist, with winds from 020 degrees at 10 knots gusting to 14 knots. Two witnesses reported that the airplane circled over the airport and then descended straight to the ground. Radar data revealed that after the airplane made the instrument approach to Runway 14, at approximately 2,800 feet mean sea level (msl), the airplane initiated a circling turn to the left and a slight descent. The last radar hit showed the airplane at 2,600 feet at a groundspeed of 186 knots. A post impact fire consumed some of the airframe. The pilot's logbooks were not located during the course of the investigation and his instrument experience and currency could not be determined. The pilot was reported to be very familiar with the airport and the 2 instrument approaches. A detailed examination of the wreckage of the airplane failed to reveal any anomalies with the airframe, structure, or systems. Flight control continuity was established at the accident site. The engines were examined, and no mechanical anomalies were found. The propellers were shipped to the manufacturer's facility for examination and teardown. Both propellers were rotating at the time of ground impact. Neither of the two propellers was found in the feathered position. Blade damage was consistent with both propellers operating under power at the time of impact. No mechanical defects were noted with either propeller.
Probable cause:
The pilot's failure to maintain clearance with terrain. Contributing factors were the below approach/landing minimums weather and the drizzle/mist weather conditions.
Final Report:

Crash of a Cessna 340A in Tomball: 1 killed

Date & Time: Dec 18, 1986 at 0621 LT
Type of aircraft:
Registration:
N8CD
Flight Phase:
Survivors:
No
Schedule:
Tomball - Tulsa
MSN:
340A-0727
YOM:
1979
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
2450
Captain / Total hours on type:
200.00
Aircraft flight hours:
2070
Circumstances:
The pilot took off in fog and light rain and climbed into clouds at about 300-400 feet above the ground while both landing lights were extended and illuminated. Also the airport's rotating beacon (located about a mile from the accident site) was flashing on the clouds according to a ground witness. Just after entering the clouds the pilot was issued a left turn from his present heading of 350° to a heading of 270° and told to contact departure control. He did not make this contact and he continued the left turn (now descending) to a heading of 210° at which time the aircraft collided with trees and a large electrical transmission line and then the ground. The engines were operating at a high power setting at the time of impact. All broken flight control cables revealed evidence of overstress separation. No evidence of preimpact mechanical failure or malfunction was found. The pilot, sole on board, was killed.
Probable cause:
Occurrence #1: in flight encounter with weather
Phase of operation: climb - to cruise
Findings
1. (c) directional control - not maintained - pilot in command
2. (f) equipment,other - improper use of - pilot in command
3. (c) proper altitude - not maintained - pilot in command
4. (c) spatial disorientation - pilot in command
5. (f) light condition - dark night
6. (f) weather condition - fog
7. (f) weather condition - rain
----------
Occurrence #2: in flight collision with object
Phase of operation: descent - uncontrolled
Findings
8. (f) object - wire, transmission (marked)
9. (f) object - tree(s)
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
----------
Occurrence #4: fire
Phase of operation: other
Final Report: