CIRRUS SR-22 near North Las Vegas, NV — 2019-11-27
- Date
- 2019-11-27
- Location
- North Las Vegas, NV, USA
- Airport
- VGT
- Aircraft
- CIRRUS SR-22
- Registration
- N7GA
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 3
- Phase of flight
- Descent
Probable cause
The pilot’s failure to maintain clearance from terrain during cruise flight in dark night conditions.
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.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Pilot could have maintained altitude or altered course to avoid terrain.
NTSB coding
Evidence available
- ATC audio
- ADS-B / radar
- Photos
- 18 docket documents
Docket documents18
- AIR TRAFFIC CONTROL ATTACHMENT 1 - ATC AUDIO RECORDINGatc
- AIR TRAFFIC CONTROL ATTACHMENT 2 - ATC TRANSCRIPTSatc
- AIR TRAFFIC CONTROL ATTACHMENT 3 A�� FAA RADAR DATAatc
- AIR TRAFFIC CONTROL ATTACHMENT 4 - CONTROLLERS STATEMENTSatc
- AIR TRAFFIC CONTROL ATTACHMENT 5 - FACILITY DOCUMENTSatc
- AIR TRAFFIC CONTROL SPECIALIST REPORTatc
- EVIDENCE CONTROL FORMform
- RELEASE OF AIRCRAFT WRECKAGE, NTSB FORM 6120.15form
- STATEMENT OF PARTY REPRESENTATIVES TO NTSB INVESTIGATION - CIRRUSform
- AUTOPSY MEMOother
- FILED FLIGHT PLANother
- FOREFLIGHT CORRESPONDENCEother
- RECORD OF CONVERSATION - FAAother
- SUN AND MOON DATAother
- PHOTO ARRAYphotos
- AIRFRAME AND ENGINE EXAMINATION SUMMARY REPORTreport
- FOREFLIGHT EXPERIENCE REPORT - PILOTreport
- TOXICOLOGICAL REPORT - PILOTreport
Related mishaps
- PIPER PA-32-300
2025-01-02 · Round Mountain, NV · 1 fatality
- CESSNA 150F
2024-10-31 · Wilder, TN · 1 fatality
- LUSCOMBE 8A
2024-06-12 · South Lake Tahoe, CA · 2 fatalities
- ENSTROM 280FX
2024-02-15 · Lewistown, MT
- CESSNA T206H
2023-10-27 · Orangeville, UT · 1 fatality
- EUROCOPTER DEUTSCHLAND GMBH EC 135 P2+
2023-03-09 · Franklin, NC