WPR20FA034 · Cirrus SR-22
Cirrus SR-22 · Accident: controlled flight into terrain/object (CFIT) en route
From Lake Havasu, AZ to North Las Vegas Airport (VGT)
Event
- NTSB case
- WPR20FA034
- 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
- 3 · 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
Cirrus SR-22
- Aircraft type
- Cirrus SR-22
- 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
- N7GA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lake Havasu, AZTo North Las Vegas Airport (VGT), North Las Vegas, NV
- Aircraft age
- About 18 years (built 2001)
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a visual flight rules (VFR) personal flight with two passengers during dark night conditions. Prior to the flight, the pilot had filed and subsequently activated a VFR flight plan from his point of departure to his intended destination.
As the pilot neared his intended destination, he contacted Nellis Air Traffic Control Facility and reported his altitude of 6,500 ft and that he had the weather at his destination airport. He also requested a practice instrument landing system (ILS) approach. The controller acknowledged the request and advised the pilot to expect the ILS approach. Throughout the following 7 minutes, the controller issued various heading changes to the pilot due to departing traffic at a nearby Air Force base, which the pilot acknowledged. The controller then issued the pilot a left turn to a westerly heading and informed the pilot that altitude was his discretion, which the pilot acknowledged.
About 1 minute, 54 seconds later, the pilot transmitted “we’re getting a low altitude alert for N7GA, we gotta turn left.” Shortly after, the controller instructed the pilot to “turn left heading 250°,” which the pilot acknowledged. No further communications from the pilot were received despite multiple attempts from the controller. Throughout this timeframe, recorded radar data showed the airplane at an altitude of 6,500 ft msl.
The airplane impacted mountainous terrain at an elevation of 6,500 ft msl, about 400 ft below the peak. The wreckage was fragmented and mostly consumed by fire. Examination revealed no anomalies with the airframe or engine that would have precluded normal operation.
Based on the available evidence, it is likely that the pilot had some sort of terrain awareness warning available; however, it was undetermined what type of system it was. While the pilot reported that he received a “low altitude alert” from an unknown source about 22 seconds before the last radar target, it’s likely that the pilot did not have sufficient time to maneuver to avoid terrain.
Probable cause
The pilot’s failure to maintain clearance from terrain during cruise flight in dark night conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR20FA034
- Event ID
- 20191127X61744
- Case number
- WPR20FA034
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-11-27.
- API snapshot SHA-256: 892f5435467d85f0ef45686a990421d2d545ffd3692c26e3b451ffe9564587a7; retrieved 2026-09-15T07:08:54.773Z.