WPR19FA266 · American Aviation AA5 A
Western Air Flight Academy American Aviation AA5 A · Accident: controlled flight into terrain/object (CFIT) en route
From Santa Fe, NM to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- WPR19FA266
- 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
- 2 · 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
American Aviation AA5 A
- Aircraft type
- American AA5
- 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
- N9774U
- Operator
- Western Air Flight Academy
- Onboard fatalities
- Unknown
- Route
- From Santa Fe, NMTo Rocky Mountain Metropolitan Airport (BJC), Denver, CO
- Aircraft age
- About 42 years (built 1977)
- 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 · climb to 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
- Controlled flight into terrain/object (CFIT)
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and passenger completed a cross-country flight across an area of mountainous terrain. After departing on the return flight, the pilot flew into a box canyon within a nearby mountain range. Flight track data showed the airplane at 400 ft above ground level as it entered the mountain range just before the track ended. An alert from the airplane's emergency locator transmitter indicated that the airplane impacted a mountain slope 26 minutes after departure at an elevation of about 10,300 ft mean sea level. The airplane was mostly consumed by a postcrash fire, which precluded an examination of the flight controls, magnetos, fuel pump, and other fuel system components. Examination of the remaining flight control systems and the engine did not reveal any anomalies that could have precluded normal operation, and signatures on the propeller blades indicated that the propeller was turning at the time of the impact. Performance calculations showed that the airplane likely exceeded its maximum gross takeoff weight at the time of the accident. The combination of high gross weight and high-density altitude conditions likely resulted in degraded climb performance and increased the time required to reach a suitable altitude to maintain clearance from surrounding terrain. Based on the airplane’s estimated weight, the airplane would have required about 28 minutes at a maximum airspeed of 75 kts to climb to an altitude of 500 ft above the approaching terrain. The circumstances of the accident are consistent with the pilot's failure to maintain clearance from trees and terrain and his decision to fly into terrain that required climb performance that exceeded the airplane’s performance capabilities. Impact signatures at the accident site indicated that the airplane collided with trees over a mountain slope. The steep impact angle suggests that the airplane was either slow when it collided with the trees or contacted the trees following an aerodynamic stall. Due to a lack of evidence, the investigation was unable to determine if the pilot had intended to overfly the mountain slope as part of his route of flight or if he was repositioning the airplane to execute a turn in search of lower terrain when the accident occurred. Although the pilot's autopsy showed evidence of severe premature coronary artery disease, the airplane's known final movements were not consistent with the loss of control more typical of sudden severe impairment/incapacitation associated with acute cardiac events. Thus, it is unlikely that the pilot's coronary artery disease contributed to this accident.
Probable cause
The pilot's decision to fly into terrain that exceeded the performance capabilities of the airplane, which resulted in failure to maintain clearance from trees and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR19FA266
- Event ID
- 20190929X73348
- Case number
- WPR19FA266
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-09-27.
- API snapshot SHA-256: 6064627ae41a58778f8b53ba5ff3f53a55c6589e2b269064750b9303e78c8e15; retrieved 2026-09-15T07:06:13.688Z.