Crash of a Beechcraft C99 Airlines near Avenal: 1 killed

Date & Time: Nov 16, 1994 at 0240 LT
Type of aircraft:
Operator:
Registration:
N63995
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Burbank - Oakland
MSN:
U-178
YOM:
1981
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
4880
Aircraft flight hours:
20031
Circumstances:
The pilot was on an IFR flight plan level at 10,000 feet msl in VFR conditions. The ATP rated pilot was the sole occupant, and there was no autopilot installed in the Beech C99 Airliner. About 10 minutes after a hand-off from Los Angeles center to Oakland center was acknowledged, radar contact was lost at 0239 hours. A review of the radar data revealed that over the last 4 minutes the airplane's altitude increased to 10,500 feet, then it started a left descending turn with a maximum diameter of about 2.1 nm. The last radar returns indicate the airplane continuing the left turn and descending through 5,600 feet msl, with a descent rate of about 18,000 feet per minute. There was no evidence of a mechanical malfunction of the aircraft, engines, or propellers.
Probable cause:
Loss of aircraft control at night by the pilot for unknown reasons.
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in Frazier Park: 1 killed

Date & Time: Mar 3, 1994 at 2346 LT
Operator:
Registration:
N78DE
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Burbank - Oakland
MSN:
31-7852087
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
3600
Captain / Total hours on type:
135.00
Aircraft flight hours:
9136
Circumstances:
The pilot elected not to use the stored instrument flight plan, and he departed with a special VFR clearance. The flight was being followed by radar. After reaching visual flight conditions, the pilot proceeded toward his intended destination and climbed to 8,500 feet. Minimum safe altitude warning service was available, but not requested by the pilot. A review of radar data indicates that the airplane's track remained almost constant at 300° with a 160-knot ground speed. The last radar hit on the airplane occurred about 0.3 miles from where the airplane cruised into 8,500 foot msl terrain while still tracking along a northwesterly course. The accident occurred in dark, night time conditions.
Probable cause:
The pilot's failure to select a cruise altitude which would ensure adequate terrain clearance. Contributing factors related to the dark, nighttime condition and to the pilot's lack of attentiveness.
Final Report:

Crash of a Beechcraft C-45G Expeditor in Oakland

Date & Time: Mar 7, 1993 at 0302 LT
Type of aircraft:
Operator:
Registration:
N494
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Oakland - Honolulu
MSN:
AF-466
YOM:
1951
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2400
Captain / Total hours on type:
50.00
Copilot / Total hours on type:
25
Aircraft flight hours:
5480
Circumstances:
The non-certificated foreign military pilot (first pilot) and a U.S. Certificated airline transport pilot (second pilot) planned to ferry an airplane to Australia with an intermediate stop in Hawaii. Auxiliary fuel and engine oil tanks were installed in the airplane. The airplane had been authorized a special airworthiness certificate for over gross weight operations for the ferry flight. The first pilot had accrued 50 hours and the second pilot accrued 25 hours in the accident airplane prior to the overweight departure. During the takeoff, the airplane became airborne at 100 knots of airspeed. The airplane pitched up and began to dutch roll. At about 50 feet above the ground, the airplane stalled and descended to the runway. A fire erupted in the cabin area.
Probable cause:
A premature lift off and inadvertent stall by the pilot-in-command. Contributing to the accident was insufficient available aircraft performance data after a ferry tank installation and both pilots lack of total experience in the airplane.
Final Report:

Crash of a Cessna 421B Golden Eagle II in Shelter Cove

Date & Time: Jul 4, 1992 at 1709 LT
Registration:
N929DB
Flight Phase:
Survivors:
Yes
Schedule:
Shelter Cove - Oakland
MSN:
421B-0864
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
2479
Captain / Total hours on type:
218.00
Aircraft flight hours:
2198
Circumstances:
The pilot said he was on the takeoff ground roll at about 100 knots when he discovered that the control lock was still in place. The pilot said he attempted to remove the control lock but could not prior to the aircraft over running the departure end of the 3,400 foot long runway. The aircraft collided with a county sewage treatment building, separating the wings from the fuselage. The aircraft fuselage continued through the building and came to rest on rocks near the beach. All four occupants were seriously injured.
Probable cause:
The pilot's inadequate preflight inspection of the aircraft and his failure to ensure that the control surface locks were removed prior to flight.
Final Report:

Crash of a Cessna 208A Cargomaster in Fresno

Date & Time: Jun 6, 1990 at 1715 LT
Type of aircraft:
Operator:
Registration:
N803FE
Flight Type:
Survivors:
Yes
Schedule:
Fresno - Oakland
MSN:
208-0015
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
9275
Captain / Total hours on type:
335.00
Circumstances:
The engine lost oil pressure while climbing through 6,000 feet, and the pilot requested to return to his departure airport. ATC informed the pilot of a closer airport. The pilot secured the engine, feathered the prop, and made a power-off descent to the airport. The pilot elected to make a downwind approach to runway 12L due to his altitude. The airplane overflew the runway and touched down past the departure end. It penetrated the airport perimeter fence, struck several trees, a sign post, a light pole, and an auto before coming to rest in a residential area. Examination of the wreckage revealed the loss of pressure was due to oil leaking. The oil filler cap was found improperly adjusted after the original installation. The maintenance manual does not approve any field repairs on the oil filler cap engaging mechanisms. The airplane's flaps were found at a 7° intermediate setting.
Probable cause:
A loss of engine oil pressure due to improper maintenance performed on the engine oil filler cap by an unknown person. In addition, the pilot misjudged his landing approach to the runway during the forced landing which resulted in an overshoot and collision with objects. A tailwind contributed to the overshoot.
Final Report:

Crash of a Cessna 414 Chancellor in Pleasanton: 1 killed

Date & Time: Jan 9, 1989 at 1124 LT
Type of aircraft:
Operator:
Registration:
N1672T
Flight Type:
Survivors:
No
Site:
Schedule:
Santa Ana - Oakland
MSN:
414-0465
YOM:
1974
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
471
Captain / Total hours on type:
149.00
Circumstances:
During arrival, the pilot was cleared for an ILS runway 27R approach to the metro Oakland Intl Airport. As she began the approach, the ATC controller noted the aircraft had descended thru 2,900 feet msl. He provided a low altitude alert to the pilot and warned her the aircraft should be at 3,300 feet. The pilot acknowledged by saying 'thank you.' The ATC controller suggested the pilot climb to 3,300 feet immediately, then he canceled the clearance and told the pilot to climb immediately to 3,300 feet. Subsequently, the aircraft crashed approximately 15 miles east of the airport. Impact occurred with a 1,500 feet ridge at about the 1,000 feet level. No preimpact part failure or malfunction of the aircraft was found. The pilot, sole on board, was killed.
Probable cause:
Failure of the pilot to properly follow the IFR (instrument flight rules) procedures by not maintaining the minimum descent altitude for that segment of the approach. The weather conditions and mountainous terrain were considered to be related factors.
Occurrence #1: in flight collision with terrain/water
Phase of operation: approach - iaf to faf/outer marker (ifr)
Findings
1. (c) ifr procedure - improper - pilot in command
2. (f) weather condition - low ceiling
3. (f) weather condition - fog
4. (f) terrain condition - mountainous/hilly
5. (c) minimum descent altitude - not maintained - pilot in command
Final Report:

Crash of a Cessna 208A Caravan I near Travis AFB: 1 killed

Date & Time: Oct 23, 1987 at 0423 LT
Type of aircraft:
Operator:
Registration:
N828FE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Oakland - Reno
MSN:
208-0073
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
10495
Captain / Total hours on type:
642.00
Aircraft flight hours:
1721
Circumstances:
While cruising on a scheduled cargo flight in IMC the pilot encountered moderate to severe turbulence near an area where weather cells could have been observed on the aircraft's radar. The pilot reversed course, declared an emergency and lost control of the aircraft. The aircraft entered an uncontrolled descent, collided with terrain and was destroyed. The recently hired pilot had completed the FAA approved ground and flight training program in the aircraft. During the pilot's recent training, neither the FAA nor the operator required the pilot to demonstrate proficiency in unusual attitude recoveries or have knowledge in the operation of the aircraft's weather radar. Company employees, which included the pilot's husband, stated that the pilot had no previous experience with weather radar and did not understand the weather radar installed in this aircraft. They further stated that the pilot appeared to be tired. The pilot, sole on board, was killed.
Probable cause:
The National Transportation Safety Board determines the probable cause(s) of this accident to be:
Pilot's encounter with severe turbulence which precipitated a loss of Aircraft control.
Findings
Occurrence #1: in flight encounter with weather
Phase of operation: cruise - normal
Findings
1. Light condition - dark night
2. (f) weather condition - turbulence in clouds
3. (f) weather radar - not understood - pilot in command
4. (f) inadequate initial training - company/operator management
5. (f) inadequate initial training - faa (principal operations inspector)
6. (c) flight into known adverse weather - continued - pilot in command
----------
Occurrence #2: loss of control - in flight
Phase of operation: maneuvering - turn to reverse direction
Findings
7. (c) spiral - uncontrolled - pilot in command
8. (f) spatial disorientation - pilot in command
9. (f) fatigue (lack of sleep) - pilot in command
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: descent - uncontrolled
Final Report:

Crash of a Cessna 340A off Monterey

Date & Time: Jan 2, 1983 at 1720 LT
Type of aircraft:
Operator:
Registration:
N1947E
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Monterey – Oakland
MSN:
340A-0677
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3200
Captain / Total hours on type:
41.00
Circumstances:
The aircraft began to lose power at about 400 feet agl after takeoff and the pilot elected to land along the shoreline in the ocean. The aircraft ditched about 100 yards off shore. All 4 occupants were able to exit thru the airstair door and received only minor injuries. The aircraft sank after about 5 minutes. It was not recovered from the 27 feet deep water. Two occupants swam ashore and two were rescued by the coast guard. The line attendant who serviced the aircraft mistook it for a king air. The pilot requested that all four tanks be topped off. The line attendant added 110 gallons of Jet A fuel.
Probable cause:
Occurrence #1: loss of engine power(partial) - mechanical failure/malfunction
Phase of operation: takeoff - initial climb
Findings
1. (c) fluid,fuel grade - improper
2. (c) maintenance,service of aircraft/equipment - improper - airport personnel
3. (c) aircraft service - inattentive - pilot in command
----------
Occurrence #2: ditching
Phase of operation: landing - flare/touchdown
Final Report:

Crash of a Piper PA-31-350 Navajo Chieftain in the Pacific Ocean: 2 killed

Date & Time: Dec 9, 1982 at 0228 LT
Registration:
N74957
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Oakland - Honolulu
MSN:
31-7305106
YOM:
1973
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
6000
Captain / Total hours on type:
100.00
Aircraft flight hours:
5093
Circumstances:
The aircraft departed Oakland, CA at 1733 PST on a night flight to Honolulu, HI. The flight proceeded without incident until approximately 0050 PST when the pilot advised that the left engine was slowly losing oil pressure. At that time, the aircraft was at an altitude of 6,000 feet. At 0205, the pilot reported he shut down the engine and was unable to maintain 6000 feet. A descent was started. In his last transmission at 0228 PST, the pilot reported that he was at 500 feet, barely maintaining altitude. Radio contact was lost when the aircraft was approximately 500 miles east of Honolulu. At 1559, the crew of a search aircraft sighted floating debris and one body floating in that area. A marker buoy was deployed, but no recovery was accomplish. The aircraft was presumed to have been destroyed and both occupants were presumed to have been fatally injured. The aircraft crashed in moderate sea conditions with waves heights estimated at three to five feet.
Probable cause:
Occurrence #1: loss of engine power
Phase of operation: cruise
Findings
1. (c) reason for occurrence undetermined
2. (f) fluid,oil - pressure too low
3. Propeller feathering - intentional - pilot in command
----------
Occurrence #2: ditching
Phase of operation: landing
----------
Occurrence #3: in flight collision with terrain/water
Phase of operation: landing - flare/touchdown
Findings
4. (f) light condition - night
5. (f) terrain condition - water,rough
Final Report:

Crash of a Mitsubishi MU-2B-10 Marquise in Sonoma

Date & Time: Jul 13, 1982 at 1745 LT
Type of aircraft:
Registration:
N27GP
Flight Phase:
Flight Type:
Survivors:
Yes
Schedule:
Sonoma - Oakland
MSN:
27
YOM:
1967
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
6500
Captain / Total hours on type:
134.00
Aircraft flight hours:
2254
Circumstances:
At approximately 800 feet down the left side of the runway the left engine experienced a power loss. The aircraft swerved off the left side of the runway colliding with a drainage ditch and coming to rest inverted. Examination of the fuel control unit revealed that the bellows within the assembly were found in an extended position, indicating a leak into the evacuated area. A failure was noted at the seam in the bellows. In addition, examination of the propeller revealed that the start locks were engaged and the blades were at the start lock position at impact. In order to engage the start locks, the power lever has to be moved to reverse during shutdown with the engine rpm below 50%. After engine start the pilot must again retard the power levers to reverse to disengage the start locks. The locks will not disengage after the power lever is set to the flight range.
Probable cause:
Occurrence #1: loss of engine power(partial) - mechanical failure/malfunction
Phase of operation: takeoff - roll/run
Findings
1. (c) fuel system,fuel control - failure,partial
2. (c) fuel system,fuel control - leak
3. (c) propeller system/accessories - engaged
4. (c) propeller - improper use of - pilot in command
5. (c) performance data - not identified - pilot in command
----------
Occurrence #2: loss of control - on ground/water
Phase of operation: takeoff - roll/run
Findings
6. (f) directional control - not maintained - pilot in command
7. Ground loop/swerve - inadvertent - pilot in command
----------
Occurrence #3: on ground/water encounter with terrain/water
Phase of operation: takeoff
Findings
8. Aborted takeoff - performed - pilot in command
9. (f) terrain condition - ditch
----------
Occurrence #4: nose over
Phase of operation: takeoff
Final Report: