Aviation Accident Summaries

Aviation Accident Summary LAX02LA091

San Jose, CA, USA

Aircraft #1

N131Y

Beech V35

Analysis

The airplane made a forced landing in a field, following a total loss of engine power. While en route, the pilot reported moderate turbulence at 4,000 feet; however, he was able to maintain level flight, and directional control of the airplane. About 2,000 feet agl, the pilot setup for the approach to land and increased the power to offset the strong turbulent conditions. The engine did not respond to the throttle input. He then applied full throttle, mixture, and propeller in an effort to execute a go-around, but again, the engine failed to respond. After colliding with several objects, the airplane landed on a grassy field in a residential area. The pilot never made an attempt to restart the engine after it lost power. Post accident inspections revealed no power plant abnormalities. No other airframe or fuel system related discrepancies that could explain a loss of power were found.

Factual Information

On February 22, 2002, about 1800 Pacific standard time, a Beech V35, N131Y, lost engine power and made a forced landing in a field near San Jose, California. The airplane was owned and operated by San Jose Flying Club under the provisions of 14 CFR Part 91. The commercial pilot, the sole occupant, was not injured; the airplane sustained substantial damage. Day visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed. The personal cross-country flight originated at Santa Monica Municipal Airport (SMO), Santa Monica, California, about 1615, with a planned destination of the Norman Y. Mineta San Jose International Airport (SJC), San Jose, California. In a written statement, the pilot reported that prior to departing SMO he filled both fuel tanks with full fuel. After an uneventful preflight, he departed with the left fuel tank selected. About 90 minutes into the flight he switched the fuel selector to the right tank. While en route, he received weather information for SJC via the automated terminal information service (ATIS), which reported wind shear. Air traffic control (ATC) cleared him to descend to 4,000 feet above ground level (agl). The pilot reported moderate turbulence about 4,000 feet agl; however, he was able to maintain level flight, and directional control of the airplane. The pilot continued the decent and reported turbulent conditions to ATC. About 2,000 feet agl, the pilot set up for the approach to runway 29 at SJC, which included the before-landing checklist. He increased the power to offset the turbulent conditions during the approach. The engine did not respond to the throttle input. He then applied full throttle, mixture, and propeller in an effort to execute a go-around, but again, the engine failed to respond. With the runway in sight, he pitched for level flight, but realized that he would be unable to make it to SJC with his given altitude and airspeed. He contacted the tower reporting that he did not have engine power and began looking for an unpopulated area to land. The airplane's sink rate increased, and he headed for a grassy football field in a residential area. The airplane collided with bleachers, a fence, and several trees. The pilot exited the airplane and reported seeing fuel spilling out of the damaged wings. During a telephone interview with the National Transportation Safety Board investigator-in-charge (IIC), the pilot reported that turbulence was strong enough where he repeatedly hit his head on the roof of the airplane. He said objects in the cabin were flying around, and the only thing keeping him in his seat was the seatbelts. He also noted that he did not try to restart the engine after experiencing the loss of power. He felt that he was too close to the ground, and his focus was on landing the airplane in an unpopulated area. A recovery team transported the wreckage to Plain Parts, Pleasant Grove, California. A Federal Aviation Administration (FAA) inspector and an engine manufacturer's representative examined the wreckage and engine on March 27, 2002. The engine manufacturer's representative reported that there was no evidence of mechanical failure or malfunction of the engine. The fuel pump was operational and fuel was in the main fuel strainer bowl, the metering unit, and the fuel lines at the fuel pump.

Probable Cause and Findings

a loss of engine power for undetermined reasons, which resulted in a forced landing into a residential area.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports