Aviation Accident Summaries

Aviation Accident Summary LAX04CA309

Willits, CA, USA

Aircraft #1

N897TW

Cessna 172S

Analysis

While maneuvering to locate the runway during a dark, nighttime flight, the airplane descended until colliding with trees. As the pilot approached his home base airport, he attempted to activate the pilot controlled runway lights. However, he was unsuccessful. Thereafter, the pilot performed a low altitude pass over what he believed was runway 16/34 to ascertain if a portion of the runway's lights were operating. During the maneuver, the pilot failed to detect that the airplane was not aligned with the runway. Also, the pilot failed to maintain adequate altitude to avoid colliding with trees 1/8-mile west of the airport. Neither prior to taking off, nor at any time during the accident flight, did the pilot become aware that a Notice to Airman had been issued indicating that the airport's runway lights were "out of service."

Factual Information

On September 1, 2004, about 2100 Pacific daylight time, a Cessna 172S, N897TW, operated by the airplane's pilot-owner, descended into trees about 1/8-mile west of the Willits Municipal Airport, Willits, California. The airplane was destroyed, and the private pilot received minor injuries. Visual meteorological conditions prevailed for the dark, nighttime personal flight, and no flight plan had been filed. The pilot was operating the airplane under the provisions of 14 CFR Part 91, and the flight originated from Watsonville, California, at 1936. The pilot reported to the National Transportation Safety Board investigator that he experienced no mechanical malfunctions during the flight. The airplane's landing light was functional, although he did not use it. According to the pilot, seconds prior to the crash he was attempting to locate his home base airport. The pilot reported to the Safety Board investigator and to an officer from the Mendocino County Sheriff's department that, upon arriving in the vicinity of the airport, he keyed the airplane's radio transmitter to activate the airport's runway lights. The pilot reported that he made two such attempts, and both were unsuccessful. Thereafter, he maneuvered toward what he believed was the airport, with the intention of making a low pass over runway 16/34 to ascertain the possibility that the runway lights were partially operating. The pilot additionally reported that while looking for the runway he initially intended to level out about 500 feet above the traffic pattern altitude. But evidently, the airplane continued descending until it collided with trees and terrain, west of the runway. The pilot also acknowledged to the Safety Board investigator that neither prior to taking off, nor at any time during the accident flight, did he become aware of the fact that the destination airport's runway lights were out of service. According to the Federal Aviation Administration's Automated Flight Service Station in Oakland, California, in September 2004, NOTAM (Notice to Airman) number 08/104 was issued. The NOTAM was in effect on the accident date, and it stated: "Runway 16/34 runway lights out of service."

Probable Cause and Findings

the pilot's inadvertent descent and controlled flight into obstacles while maneuvering to land. Contributing factors were the dark, nighttime condition, which impaired the pilot's visual perceptions, and the pilot's failure to obtain a pertinent Notice to Airman regarding inoperative runway lights.

 

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