Aviation Accident Summaries

Aviation Accident Summary LAX03LA003

Avalon, CA, USA

Aircraft #1

N90168

Cessna 140

Analysis

The pilot was spotting fish for a boat and lost radio communication. In an attempt to reestablish contact, he attempted a series of low altitude passes. A box pattern was set up, and several attempts to communicate were made without success. The pilot decided to try to drop a message into the boat. The pilot said that he was distracted by the task and fatigued by the nearly 3-hour flight and did not maintain sufficient altitude. When he realized that a collision with the water was imminent, he added power and pulled back on the control yoke but was unable to avoid contact with the ocean surface. He stated that prior to impact, all controls were functioning and responsive and that the engine was operating smoothly and gave no indication of a malfunction. The only anomaly that the pilot could recall was that the engine did not seem to respond after he added power seconds before impact. Due to the low altitude the pilot did not have time to send out a distress call or troubleshoot the engine's lack of response.

Factual Information

On October 7, 2002, about 1350 Pacific daylight time, a Cessna140, N90168, inadvertently collided with water near Avalon, California. The pilot was operating the airplane for fish spotting operations in support of a fishing boat under the provisions of 14 CFR Part 91. The commercial pilot, the sole occupant, sustained serious injuries; the airplane sank and is considered to be destroyed. The local flight departed El Monte Airport (EMT), California, about 1100 en route to Corona Municipal Airport (AJO), Corona, California. Visual meteorological conditions prevailed, and a flight plan had not been filed. The primary wreckage is at 33 degrees 15 minutes north latitude and 118 degrees 30 minutes west longitude. The pilot submitted detailed written statements and further described the event in telephonic interviews. Several hours into the fish spotting operation, radio communication between the pilot and the fishing boat was lost. The pilot decided to set up a box like pattern over the boat hoping that he could establish visual contact with the crew of the fishing boat. Distracted by the task and experiencing fatigue after several hours of intense flying, altitude was not maintained. Suddenly the airplane was headed toward the ocean surface. He added power and pulled the yoke back in an attempt to avoid the impending collision, but there was not sufficient time, altitude, or airspeed to allow for a recovery. In later statements, the pilot indicated that prior to the accident controls were functioning smoothly, continuous, and responsive. The engine was operating normally, with no roughness, sputtering, or propeller stoppage. Having topped off both 15-gallon fuel tanks prior to departing El Monte, the airplane still had about 2 hours worth of fuel on board at the time of impact. Most of the flight had been conducted at moderate power levels, typically between 1500 and 1900 rpm, which was not unusual for the airplane or the type of operations that were being conducted. Carburetor heat was used whenever a descent initiated or there were indications that ice might be present, but neither he nor anyone else that he knew of had ever experienced any such problems in that particular airplane. On the final pass, the airplane was at an altitude of about 50 feet and flying at an airspeed of approximately 60 miles per hour. After realizing that the airplane was headed for the water, the pilot's usual recovery procedure was utilized, first adding power and then pulling back on the yoke. He stated that due to the low altitude, and combined with the stressfulness of the situation, he did not have time to troubleshoot the engine or send out a distress call. In addition, he maintains that the engine did not seem to respond after full power was added shortly before the collision.

Probable Cause and Findings

The pilot's failure to maintain sufficient altitude while maneuvering at low altitude. Factors were the pilot's fatigue and the distraction of trying to drop a message onto a boat.

 

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