CEN15FA044 · Mooney Aircraft CORP. M20K
Mooney Aircraft CORP. M20K · Accident: loss of control in flight en route
From Rick Husband Amarillo International Airport (AMA) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- CEN15FA044
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mooney Aircraft CORP. M20K
- Aircraft type
- Mooney M20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N231JF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rick Husband Amarillo International Airport (AMA), Amarillo, TXTo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
- Aircraft age
- About 35 years (built 1979)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
Before departing on the westbound cross-country flight, the noninstrument-rated pilot checked the weather and voiced concern to another pilot about the conditions along the route. The area forecast called for instrument flight rule (IFR) and marginal visual flight rule conditions. An Airmen Meteorological Information (AIRMET) was active for IFR conditions. mountain obscuration due to clouds. and precipitation and mist along the route of flight. Another AIRMET for moderate ice below 16,000 ft was active for an area just north of the route of flight.
Despite these conditions, the pilot decided to depart; he obtained flight following from air traffic control. While in contact with the Albuquerque Air Route Traffic Control Center (ZAB), the pilot stated that he was picking up ice; he asked about the cloud tops and then stated that he was going to have to turn around and return to his departure airport, which was to the east. The controller offered the pilot several closer airports. The pilot continued westbound toward higher terrain and, when asked, stated that he was familiar with the terrain. However, the weather continued to deteriorate, and the pilot asked the controller for the closest airports; the pilot ultimately decided to fly to an airport that was located 28 miles west of his location at that time. The pilot reported that he was below the clouds and asked where the cloud tops were, but the controller had no cloud top reports. The pilot's last communication was that he would just keep going and "hopefully it'll break up here for me open up." Although the pilot did not declare an emergency, the controller had numerous indications that the pilot was having difficulty and needed to land. Such indicators were the pilot's statement that he was picking up ice; his indecisiveness about where to go; and his questions about the cloud tops, which likely indicated he was flying in the clouds and wanted to get above them because the clouds were too low to fly below. The controller should have queried the pilot to better determine the nature of the issues affecting the flight and to determine if the pilot was capable of instrument flight.
The airplane impacted terrain in a 60-degree nose-down attitude in an area of open rolling hills. Examination of the wreckage did not reveal any anomalies that would have precluded normal operation of the airplane. The angle of impact indicated that the pilot was not in control of the airplane when it impacted the terrain. The pilot most likely lost control of the airplane as he flew into the deteriorating weather, which included blowing snow and gusting wind. While the airplane may have been accumulating ice at the time of the accident, the investigation was unable to determine how much ice it had accumulated and what effect it had on the airplane's performance.
The controller stated that he did not have the current weather conditions at two of the airports that he offered because the airports' automated weather observing system (AWOS) information was not available to him because neither was "adapted" into (included in) the ZAB en route automation modernization system. In addition, the controller did not direct the pilot to the AWOS frequencies for those airports, nor did he ask his supervisor to assist in obtaining airport weather. He also did not ask the supervisor to solicit airport-specific weather, which was available from the center weather service unit (CWSU), because he was not aware of the services that the CWSU could provide.
Probable cause
The noninstrument-rated pilot's decision to initiate the flight into known deteriorating weather conditions and his continued visual flight into instrument meteorological conditions, which ultimately resulted in a loss of airplane control. Contributing to the accident was the air traffic controller's failure to provide additional assistance to the pilot when it was apparent the pilot was having difficulties.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA044
- Event ID
- 20141112X21844
- Case number
- CEN15FA044
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2014-11-13.
- API snapshot SHA-256: e3fec4dd1dcccee96d7055ce0b3b23178c8687b61a94e6e97db6e4dd6684f4b2; retrieved 2026-09-14T17:28:43.247Z.