Crash of a Socata TBM-850 in Truckee

Date & Time: Dec 13, 2009 at 1738 LT
Type of aircraft:
Registration:
N850MT
Flight Type:
Survivors:
Yes
Schedule:
San Carlos – Truckee
MSN:
489
YOM:
2008
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
1738
Captain / Total hours on type:
1098.00
Aircraft flight hours:
196
Circumstances:
During the flight, the instrument-rated private pilot was monitoring the weather at his intended destination. He noted the weather and runway conditions and decided to conduct a global-positioning-system instrument approach to a known closed runway with the intention of circling to a different runway. As the airplane neared the missed approach point, the pilot established visual contact with the airport's runway environment and canceled his instrument flight rules clearance. As he entered the left downwind leg of the traffic pattern for his intended runway, the pilot noticed that the first part of the runway was covered in fog and that the visibility was 0.75 of a mile with light snow. With at least 5,000 feet of clear runway, he opted to land just beyond the fog. Prior to touchdown, the pilot concluded that there was not enough runway length left to make a landing and performed a go-around by applying power, pitching up, and retracting the landing gear. During the go-around, the pilot focused outside the airplane cockpit but had no horizon reference in the dark night conditions. He heard the stall warning and realized that the aircraft was not climbing. The pilot pitched the nose down and observed only snow and trees ahead. Not being able to climb over the trees, the airplane subsequently impacted trees and terrain, coming to rest upright in a wooded, snow-covered field. The pilot stated that there were no anomalies with the engine or airframe that would have precluded normal operation of the airplane.
Probable cause:
The pilot’s failure to maintain an adequate airspeed and clearance from terrain during an attempted go-around. Contributing to the accident was the pilot's decision to land on a partially obscured runway.
Final Report:

Crash of a Lockheed C-130H Hercules off San Clemente Island: 7 killed

Date & Time: Oct 29, 2009 at 1909 LT
Type of aircraft:
Operator:
Registration:
1705
Flight Phase:
Survivors:
No
Schedule:
McClellan AFB - McClellan AFB
MSN:
4993
YOM:
1984
Crew on board:
7
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
While performing a SAR mission for a 12 foot boat that was missing since two days, the aircraft collided with a Bell AH-1 Suber Cobra operated by the US Marine Corps. Both machines crashed into the sea some 24 km off the San Clemente Island and all occupants were missing. SAR were abandoned on 01NOV2013 as no trace of the Hercules and the Cobra were found. It appears that the Cobra's crew was taking part of an exercise in an area reserved for training missions. At the time of the accident, the Cobra had its anticollision lights and IFF transponder switched off.
Probable cause:
USAF and US authorities concluded that no single factor or individual act or omission was the cause of the collision. Investigations concluded that it was the consequence of a tragic confluence of events, missed opportunities, and procedure/policy issues in an airspace where most aircraft fly under a "see-and-avoid" regime. A contributory factor was that FACSFAC San Diego did not provide operational priority to the crew of the Lockheed Hercules.

Crash of a Beechcraft B200 Super King Air in Hayward

Date & Time: Sep 16, 2009 at 1215 LT
Registration:
N726CB
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Hayward - San Carlos
MSN:
BB-1750
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2913
Captain / Total hours on type:
1707.00
Aircraft flight hours:
1229
Circumstances:
The airplane just had undergone a routine maintenance and this was planned to be the first flight after the inspection. During the initial climb, the pilot observed that the airplane was drifting to the left. The pilot attempted to counteract the drift by application of right aileron and right rudder, but the airplane continued to the left. The pilot reported that, despite having both hands on the control yoke, he could not maintain directional control and the airplane collided into a building. The airplane subsequently came to rest on railroad tracks adjacent to the airport perimeter. A post accident examination revealed that the elevator trim wheel was located in the 9-degree NOSE UP position; normal takeoff range setting is between 2 and 3 degrees NOSE UP. The rudder trim control knob was found in the full left position and the right propeller lever was found about one-half inch forward of the FEATHER position; these control inputs both resulted in the airplane yawing to the left. The pilot did not adequately follow the airplane manufacturer's checklist during the preflight, taxi, and before takeoff, which resulted in the airplane not being configured correctly for takeoff. This incorrect configuration led to the loss of directional control immediately after rotation. A post accident examination of the airframe, engines, and propellers revealed no anomalies that would have precluded normal operation.
Probable cause:
The pilot's failure to maintain directional control after takeoff. Contributing to the accident was the pilot's inadequate preflight and failure to follow the airplane manufacturer's checklist to ensure that the rudder trim control and right propeller control lever were positioned correctly.
Final Report:

Crash of an AMI Turbo DC-3-65TP in Mojave

Date & Time: Feb 4, 2009 at 0852 LT
Type of aircraft:
Operator:
Registration:
N834TP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Mojave - Mojave
MSN:
12590
YOM:
1947
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
18000
Captain / Total hours on type:
1326.00
Aircraft flight hours:
17277
Circumstances:
During the takeoff roll, the airplane began to drift to the right. Despite the certified flight instructor's and student's attempts, they were unable to stop the yaw and drift. As the airplane was about to depart the runway, the pilots did not reduce the throttles or apply brakes as they felt that it would be safer to attempt to get airborne. After departing the runway surface, the airplane collided with a series of berms, which sheared off the left landing gear and left engine. The right landing gear collapsed, and the airplane came to rest in a nose down attitude. Post accident e examination revealed that the student pilot had inadvertently set the rudder trim to the full right position when he adjusted the rudder pedals during the prestart checks. The rudder trim was in the full right position for the takeoff, and found in the same position upon post accident inspection.
Probable cause:
The student pilot failed to follow the checklist and set the takeoff trim properly prior to takeoff resulting in a loss of directional control. Contributing to the accident were the certified flight instructor's inadequate supervision and delayed remedial action.
Final Report:

Ground fire of a Boeing 767-281SF in San Francisco

Date & Time: Jun 28, 2008 at 2218 LT
Type of aircraft:
Operator:
Registration:
N799AX
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
San Francisco – Wilmington
MSN:
23432/145
YOM:
1986
Flight number:
ABX1611
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
On June 28, 2008, about 2215 Pacific daylight time, an ABX Air Boeing 767-200, N799AX, operating as flight 1611 from San Francisco International Airport, San Francisco, California, experienced a ground fire before engine startup. The captain and the first officer evacuated the airplane through the cockpit windows and were not injured, and the airplane was substantially damaged. The cargo flight was operating under the provisions of 14 Code of Federal Regulations Part 121. At the time of the fire, the airplane was parked near a loading facility, all of the cargo to be transported on the flight had been loaded, and the doors had been shut.
Probable cause:
The National Transportation Safety Board determines that the probable cause of this accident was the design of the supplemental oxygen system hoses and the lack of positive separation between electrical wiring and electrically conductive oxygen system components. The lack of positive separation allowed a short circuit to breach a combustible oxygen hose, release oxygen, and initiate a fire in the supernumerary compartment that rapidly spread to other areas. Contributing to this accident was the Federal Aviation Administration’s (FAA) failure to require the installation of nonconductive oxygen hoses after the safety issue concerning conductive hoses was initially identified by Boeing.
Final Report:

Crash of a Cessna 340A near Cabazon: 4 killed

Date & Time: Feb 2, 2008 at 1340 LT
Type of aircraft:
Registration:
N354TJ
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Palm Springs – Chino
MSN:
340A-0042
YOM:
1976
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
5972
Circumstances:
The airplane departed under daytime visual meteorological conditions on a cross-country flight from an airport on the east side of a mountain range to a destination on the west side of the mountains. The airplane, which had been receiving flight following, then collided with upsloping mountainous terrain in a mountain pass while in controlled flight after encountering instrument meteorological conditions. The controller terminated radar services due to anticipation of losing radar coverage within the mountainous pass area, and notified the pilot to contact the next sector once through the pass while staying northwest of an interstate highway due to opposing traffic on the south side of the highway. The pilot later contacted the controller asking if he still needed to remain on a northwesterly heading. The controller replied that he never assigned a northwesterly heading. No further radio communications were received from the accident airplane. Radar data revealed that while proceeding on a northeasterly course, the airplane climbed to an altitude of 6,400 feet mean sea level (msl). A few minutes later, the radar data showed the airplane turning to an easterly heading and initiating a climb to an altitude of 6,900 feet msl. The airplane then started descending in a right turn from 6,900 feet to 5,800 feet msl prior to it being lost from radar contact about 0.65 miles southeast of the accident site. A weather observation station located at the departure airport reported a scattered cloud layer at 10,000 feet above ground level (agl). A weather observation system located about 29 miles southwest of the accident site reported a broken cloud layer at 4,000 feet agl. A pilot, who was flying west bound at 8,500 feet through the same pass around the time of the accident, reported overcast cloud coverage in the area of the accident site that extended west of the mountains. The pilot stated that the ceiling was around 4,000 feet msl and the tops of the clouds were 7,000 feet msl or higher throughout the area. Postaccident examination of the airframe and both engines revealed no anomalies that would have precluded normal operation.
Probable cause:
The pilot's continued visual flight into instrument meteorological conditions and failure to maintain terrain clearance while en route. Contributing to the accident were clouds and mountainous terrain.
Final Report:

Crash of a Piper PA-60 Aerostar (Ted Smith 602P) in McFarland: 3 killed

Date & Time: Nov 9, 2007 at 1200 LT
Registration:
N6895Z
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Roseburg – Bakersfield
MSN:
62-0918-8165043
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1500
Captain / Total hours on type:
15.00
Aircraft flight hours:
3780
Circumstances:
The accident flight was the pilot's first 700 nm cross-country flight in the newly purchased airplane. Prior to departing he had the airplane refueled with the airplane on a slope. The individual who refueled the airplane estimated that the left wing tip was 12 to 14 inches lower than the right wing tip. He stated that the pilot was very concerned about getting as much fuel in the airplane as possible because of his up-coming flight. After climbing to his assigned cruising altitude of 21,000 feet and about two hours into the flight the pilot reported to ATC that he needed to divert. During the descent the pilot reported that he was experiencing a fuel problem and that one engine was sputtering. Two minutes later the pilot declared an emergency and reported that both engines were sputtering. The pilot reported at that time that he had 15 total gallons of fuel remaining A witness to the accident reported that he saw the airplane flying southbound and that the wings were rocking side-to-side. The airplane then rolled to the right before crashing into the citrus grove. Examination of the airframe revealed no pre-impact failure to any flight control surface or control system component. The power plant investigation did not disclose any pre-impact mechanical failure of any rotating or reciprocating component of the engine. Interviews with pilots who had flown with the accident pilot indicated that this was his first flight above 13,000 feet in the accident airplane, and was probably his longest distance attempted flight since he had purchased the airplane. According to information contained within the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual (VB-1190), "The full amount of usable fuel is based on the airplane sitting on a level ramp, laterally level, and longitudinally (approximately 1 1/2 degree nose up) with each tank fueled to 0.6 inches below filler neck. The wing tanks are extremely sensitive to attitude and if not level, they cannot be fueled to the full usable capacity." This information is also included in the FAA Type Certificate Data Sheet No. A17WE under the section Data Pertinent to All Models, Note 1.
Probable cause:
The pilot's inadequate preflight preparation and improper fueling procedures that led to fuel exhaustion.
Final Report:

Crash of a Beechcraft A100 King Air in Chino: 2 killed

Date & Time: Nov 6, 2007 at 0918 LT
Type of aircraft:
Operator:
Registration:
N30GC
Flight Phase:
Survivors:
No
Schedule:
Chino - Visalia
MSN:
B-177
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
3136
Aircraft flight hours:
11849
Circumstances:
The reported weather at the time of the accident was calm winds, a 1/4-mile visibility in fog and a vertical visibility of 100 feet. Shortly after takeoff for the instrument-flight-rules flight, the airplane made a slight turn to the left and impacted the tops of 25-foot trees about a 1/2 mile from the runway. An enhanced ground proximity warning system was installed on the airplane and data extraction from the system indicated that the airplane achieved an initial positive climb profile with a slight turn to the left and then a descent. A witness reported hearing the crash and observed the right wing impact the ground and burst into flames. The airplane then cartwheeled for several hundred feet before coming to rest inverted. The airframe, engines, and propeller assemblies were inspected with no mechanical anomalies noted that would have precluded normal flight.
Probable cause:
The pilot's failure to maintain a positive climb rate during an instrument takeoff. Contributing to the accident was the low visibility.
Final Report:

Crash of a Cessna 340 in Garberville: 3 killed

Date & Time: Nov 6, 2007 at 0855 LT
Type of aircraft:
Operator:
Registration:
N5049Q
Survivors:
No
Schedule:
Redding – Garberville
MSN:
340-0016
YOM:
1971
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
18500
Aircraft flight hours:
7691
Circumstances:
The pilot arrived in the vicinity of his destination airport, which was located in a narrow river valley. The airport was located within a large area of Visual Flight Rules (VFR) conditions with clear skies and almost unlimited visibility, but the pilot discovered that the airport was covered by a localized dense layer of fog about 200 to 250 feet thick. There were no instrument approaches to the non-controlled airport. Witnesses reported that the pilot flew at low-level up the valley, and eventually entered the fog as the flight approached the airport. About one mile prior to reaching the airport, the pilot attempted to climb out of the valley, but the airplane began impacting trees on the rising terrain. The airplane eventually sustained sufficient damage from impacting the trees that it descended into the terrain. Post-accident inspection of the airframe and engines found no evidence of a mechanical failure or malfunction.
Probable cause:
The pilot's intentional visual flight rules (VFR) flight into instrument meteorological conditions (IMC), and his failure to maintain clearance from the trees and terrain during climb. Contributing to the accident were the weather conditions of fog and a low ceiling, and the mountainous/hilly terrain.
Final Report:

Crash of a Beechcraft E90 King Air in Carlsbad: 2 killed

Date & Time: Jul 3, 2007 at 0606 LT
Type of aircraft:
Registration:
N47LC
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Carlsbad - Tucson
MSN:
LW-64
YOM:
1973
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1177
Captain / Total hours on type:
284.00
Aircraft flight hours:
9032
Circumstances:
The airport is on a plateau, and the surrounding terrain is lower than the runway. After departing runway 24, the airplane collided with the top conductor of a telephone line an estimated 2,500 feet from the departure end of the runway. The airport elevation was 331 feet msl and the estimated elevation of the line was 245 feet. The debris path was along a magnetic bearing of 270 degrees. Both left and right engines displayed contact signatures to their internal components that were characteristic of the engines producing power at the time of impact. Fire consumed the cabin and cockpit precluding a meaningful examination of instruments and systems. An aviation routine weather report (METAR) issued about 13 minutes before the accident stated that the winds were calm, visibility was 1/4 mile in fog; and skies were 100 feet obscured. An examination of the pilot's logbook indicated that the pilot had a total instrument flight time of 268 hours as of June 21, 2007. In the 90 prior days he had flown 11 hours in actual instrument conditions and logged 20 instrument approaches.
Probable cause:
The pilot's failure to maintain clearance from wires during an instrument takeoff attempt. Contributing to the accident were fog, reduced visibility, and the low ceiling.
Final Report: