Summary
On November 01, 2000, a Piper PA-32R-301 (N8139A) was involved in an incident near Dayton Valley, NV. All 2 people aboard were uninjured. The aircraft sustained substantial damage.
The National Transportation Safety Board determined the probable cause of this incident to be: The pilot's failure to attain a proper glide path during the final approach resulting in an undershoot of the runway. Factors were the lack of runway lights and night lighting condition.
On October 31, 2000, at 1746 hours Pacific standard time, a Piper PA-32R-301, N8139A, undershot the runway and collided with desert brush at the Dayton Valley Airpark Airport, Dayton Valley, Nevada. The airplane, operated by Aero Leasing, d.b.a. Union Flights, under the provisions of 14 CFR Part 91, sustained substantial damage. The commercial pilot and pilot rated passenger were not injured. Visual meteorological conditions prevailed for the business flight that departed the Redding Municipal Airport, Redding, California, at 1645, and no flight plan was filed.
This incident is documented in NTSB report LAX01LA030. AviatorDB cross-references NTSB investigation data with FAA registry records to provide comprehensive safety information for aircraft N8139A.
Accident Details
Probable Cause and Findings
The pilot's failure to attain a proper glide path during the final approach resulting in an undershoot of the runway. Factors were the lack of runway lights and night lighting condition.
Aircraft Information
Registered Owner (Historical)
Analysis
On October 31, 2000, at 1746 hours Pacific standard time, a Piper PA-32R-301, N8139A, undershot the runway and collided with desert brush at the Dayton Valley Airpark Airport, Dayton Valley, Nevada. The airplane, operated by Aero Leasing, d.b.a. Union Flights, under the provisions of 14 CFR Part 91, sustained substantial damage. The commercial pilot and pilot rated passenger were not injured. Visual meteorological conditions prevailed for the business flight that departed the Redding Municipal Airport, Redding, California, at 1645, and no flight plan was filed. The flight was scheduled to terminate at the Dayton Valley Airpark.
In an interview with a Safety Board investigator, the pilot stated that he and the passenger, who is a mechanic for Union Flights, had flown to Redding earlier in the day to work on a company airplane. No abnormalities were noted on the flight to Redding or the return trip to Dayton. He noted that the arrival to Dayton was after sunset, and reported that the airport does not have lighting.
In the pilot's written statement to the Safety Board, he reported that he oriented himself to runway 23 utilizing the surrounding ground lighting and lights from the company's open hangar. He indicated that he did not like what he saw on the first approach and initiated a go-around. On final for the second approach, at 200 feet above ground level (agl), he verified that there was a three green light indication on the instrument panel, confirming that the landing gear was in the down and locked position. When he looked outside he stated that the "lights were fuzzy and not sharp." He thought he had flown through a dust cloud. The next thing he remembered was the passenger stating that they had just crashed. The pilot further reported that the weather was clear and the winds were calm.
According to a Sun and Moon program utilized by the Safety Board, official sunset was 1703.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# LAX01LA030