Limon, CO, USA
N9738J
JONES KENT C VANS RV-10
The pilot reported that, during a night approach, the runway precision approach path indicator lights indicated that the airplane was on a proper glidepath. Shortly after, the airplane encountered a "strong gust of wind" and "lost significant altitude." He added engine power and raised the airplane's nose to intercept the glidepath. A few seconds later, he felt a slight bump and heard a scraping noise to his right. He looked to the right, and when he returned his focus to the approaching runway, he noticed that the airport lights were no longer lit, and the airport was in "complete darkness." He added that he "couldn't really see anything and wasn't sure exactly where the runway was, [but he] knew [he] was going to have a hard landing." He then pulled the power back, moved the mixture to idle cut off, and turned the fuel selector off. Subsequently, the airplane landed hard off the runway, bounced, slid sideways, struck a tree, and then came to rest. The airplane sustained substantial damage to the fuselage, both wings, and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Following the accident, it was discovered that, during the approach, the airplane struck a power line that supplied the airport power. The automated weather observation system at the accident airport reported that, about the time of the accident, the wind was from 330° at 6 knots. The pilot was on a visual approach for runway 34. According to the Federal Aviation Administration inspector assigned to the accident, the power line was estimated to be 75 ft above the ground and 1/2 mile from the runway threshold. The power line crossed perpendicular to the runway.
The pilot reported that, during a night approach, the runway Precision Approach Path Indicator lights indicated the airplane was on a proper glide path. Shortly afterward, the airplane encountered a "strong gust of wind" and "lost significant altitude". He added engine power and raised the airplane's nose to intercept the glide path. A few seconds later, he felt a slight bump and heard a scraping noise to his right. He looked to the right and when he returned his focus to the approaching runway, he noticed that the airport lights were no longer lit, and the airport was in "complete darkness". He added that, he "couldn't really see anything and wasn't sure exactly where the runway was, [but he] knew [he] was going to have a hard landing". He then pulled the power back, moved the mixture to idle cut off, and turned the fuel selector off. Subsequently, the airplane landed hard off the runway, bounced, and slid sideways coming to rest after striking a tree. The airplane sustained substantial damage to the fuselage, both wings and empennage. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. Following the accident, it was discovered that during the approach the airplane struck a powerline that supplied the airport power. The automated weather observation system at the accident airport reported, about the time of the accident that the wind was from 330° at 6 knots. The pilot was on a visual approach for runway 34. According to the Federal Aviation Administration investigator assigned to the accident, stated in a telephone conversation with the National Transportation Safety Board investigator in charge, the powerline was estimated to be 75 ft. above the ground and one half mile from the runway threshold. The powerline crossed perpendicular to the runway.
The pilot’s unstabilized approach and failure to go around at night, which resulted in the airplane impacting a power line and a subsequent hard landing.
Source: NTSB Aviation Accident Database
Aviation Accidents App
In-Depth Access to Aviation Accident Reports
