Event ERA18LA034

Factual narrative

On November 29, 2017, about 0930 eastern standard time, an Aero Commander 112, N690RU, owned and operated by the student pilot, was substantially damaged during a precautionary landing at Clearview Airpark (2W2), Westminster, Maryland. The student pilot was not injured. The solo instructional flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the flight that originated from Martin State Airport (MTN), Baltimore, Maryland, about 0900. The flight was destined to Eastern WV Regional Airport (MRB), Martinsburg, West Virginia.The student pilot reported that 2W2 was his second checkpoint along the cross-country flight. Upon reaching 2W2, the airplane experienced an electrical failure that affected the communication radios and GPS. The student pilot then elected to divert to 2W2 and entered the airport traffic pattern for runway 32, an 1,840-foot long, 30-foot wide asphalt runway. While completing landing procedures, the student pilot extended the landing gear, but did not observe the corresponding green indicator lights in the cockpit. He could not be certain if he did not see the lights due to the electrical failure or because of sun glare. While on the left base leg of the traffic pattern, the student pilot lowered the nose of the airplane to cease the stall warning horn and the airplane flew beyond the extended runway centerline; however, the student pilot corrected and aligned the airplane on final approach. While on short final approach, the airplane descended suddenly and the student pilot immediately compensated by increasing engine power, but the landing gear contacted a grass area before runway and all three landing gear separated. The airplane came to rest upright just prior to the runway. Examination of the wreckage by a Federal Aviation Administration inspector revealed substantial damage to the fuselage. When the inspector tested the airplane's electrical system, it functioned, but the avionics panel extinguished after approximately 10 seconds of operation. The recorded wind at an airport located about 10 miles north of the accident site, at 0925, was from 230° at 6 knots. The student pilot reported that the wind at 2W2 was from 140° at 8 knots, gusting to 12 knots, at the time of the accident. The student pilot reported that, during the cross-country flight, he thought that the airplane had experienced an electrical failure, and he chose to divert to an airport. During final approach to the diversion airport, the student descended the airplane too low and then attempted to correct it by increasing engine power. Subsequently, the airplane impacted a grassy area just before the runway, which resulted in all three landing gear separating. Examination of the wreckage revealed that the electrical system was functional but that an avionics panel had failed. The failed avionics panel likely distracted the student pilot and led to his failure to maintain a proper glidepath during the approach, which resulted in the runway undershoot. The student reported that there were no other preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• C Personnel issues-Task performance-Use of equip/info-Aircraft control-Student/instructed pilot - C
• C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
• C Personnel issues-Psychological-Attention/monitoring-Attention-Student/instructed pilot - C
• C Aircraft-Aircraft systems-Communications system-(general)-Failure - C