# NTSB ERA18LA034: Aero Commander 112, N690RU, Westminister, MD, November 29, 2017 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: November 29, 2017, 09:30 local (14:30 UTC) - Place: Westminister, MD - Coordinates: 39.466945, -77.017501 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.4669&lon=-77.0175&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report July 23, 2019 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 96400 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA18LA034 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96400/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96400 - Page: https://openairdocs.org/ntsb/ERA18LA034 ## 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 NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Aero Commander 112, 3 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=0144701), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Aero Commander 112, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=0144701), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Attention/monitoring: attention](https://openairdocs.org/ntsb-findings/02021510): Personnel issues › Psychological · Student/instructed pilot (probable cause); cases with it: [Aero Commander 112, 1 case](https://openairdocs.org/ntsb-findings/02021510/cases.md?model=0144701), [All aircraft, 226 cases](https://openairdocs.org/ntsb-findings/02021510/cases.md) - [Communications system](https://openairdocs.org/ntsb-findings/01022300): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Aero Commander 112, 1 case](https://openairdocs.org/ntsb-findings/01022300/cases.md?model=0144701), [All aircraft, 7 cases](https://openairdocs.org/ntsb-findings/01022300/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area undershoot](https://openairdocs.org/ntsb-events/370) (defining event); cases with it: [Aero Commander 112, 1 case](https://openairdocs.org/ntsb-events/370/sequence.md?model=0144701), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md) - [Landing: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Aero Commander 112, 5 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=0144701), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing: Part(s) separation from AC](https://openairdocs.org/ntsb-events/338); cases with it: [Aero Commander 112, 1 case](https://openairdocs.org/ntsb-events/338/sequence.md?model=0144701), [All aircraft, 563 cases](https://openairdocs.org/ntsb-events/338/sequence.md) ## 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](https://openairdocs.org/deregistered/N690RU-2018-10-27), registration cancelled 2018-10-27, S/N 33, built 1973 (OpenAirDocs) - Reported make and model: AERO COMMANDER 112 (UNDESIGNAT) - Registry model: [Aero Commander 112](https://openairdocs.org/model/aero-commander-112) (registry code 0144701) (OpenAirDocs) - Registry engine: [Continental IO-360 series](https://openairdocs.org/engine/continental-io-360-series) (registry code 17025, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 33 - Year built: 1973 - Airframe hours: 3692 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 62; injuries: none; 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 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20171129022189A](https://openairdocs.org/incident/20171129022189A), Nov 29, 2017: Aero Commander 112, Westminster, MD, Substantial damage. On November 29, 2017 the pilot stated that he was on a solo cross country flight from kmtn (martin state) to kmrb (martinsburg). While enroute he experienced… ## Docket (4 files) The files NTSB released with the investigation on December 3, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96400. 2.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468814&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Interview Summary (item 2, .PDF, 52 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468815&FileExtension=.PDF&FileName=Interview%20Summary-Master.PDF - Weather Report (item 3, .PDF, 113 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468816&FileExtension=.PDF&FileName=Weather%20Report-Master.PDF - Photo (item 4, .PDF, 1 photo, 196 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40468817&FileExtension=.PDF&FileName=Photo-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.