- Date
- November 29, 2017, 09:30 local (14:30 UTC)
- Place
- Westminister, MD
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N690RUAero Commander 112
- Defining event
- Landing: Landing area undershoot
- Weather
- Visual (VMC) · Day
- Status
- Completed · report July 23, 2019
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20171129022189A
- Case key
- 96400
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The student pilot's failure to maintain a proper glidepath during the approach due to his distraction by the failure of an avionics panel, which resulted in a runway undershoot.
Findings · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
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.
Aircraft
- Registration
- N690RU
- Reported as
- Aero Commander 112 (UNDESIGNAT)
- Category
- Airplane
- Serial number
- 33
- Built
- 1973
- Airframe hours
- 3,692
- Engine
- Lycoming IO-360, 200 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · May 12, 2017 · 19 hours before
- Departed
- MTN · Baltimore, MD
- Destination
- MRB · Martinsburg, WV
- Airport
- 2W2 · Clearview Airpark, runway 32, 1,840 × 30 ft, asphalt
- Equipment
- Angle of attack indicator, ADS-B, Stall warning system, Onboard weather, Handheld GPS, Electronic flight bag or handheld device, Auto-pilot
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 62
- Injuries
- None
- Certificate
- Student
- Medical
- BasicMed
- Seat
- Left
- Restraint
- 3-point
- Flight hours
- 179 total · 39 in this make and model · 16 as pilot in command · 16 in the last 90 days · 3 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 230° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 54 °F, dew point 32 °F
- Altimeter
- 30.17 inHg
- Observed at
- DMW, 10 nm away
Docket · 4
The files NTSB released with the investigation on December 3, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.3 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.