DEN06FA114 · Cirrus Design Corp. SR20
West Valley Flying Club Cirrus Design Corp. SR20 · Accident: in flight encounter with weather en route
From Cedar City Regional Airport (CDC) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- DEN06FA114
- 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
- 0 · 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 Design Corp. SR20
- Aircraft type
- Cirrus SR20
- 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
- N8127J
- Operator
- West Valley Flying Club
- Onboard fatalities
- Unknown
- Route
- From Cedar City Regional Airport (CDC), Cedar City, UTTo Rocky Mountain Metropolitan Airport (BJC), Denver, CO
- Aircraft age
- Not recorded
- 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
- First occurrenceThe 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
- In flight encounter with weather
- 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
- Pilot in command › Missed approach, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While maneuvering in night visual meteorological conditions, the airplane impacted mountainous terrain and was destroyed by impact forces. Prior to departure, the pilot obtained a weather briefing which reported thunderstorms and moderate to severe precipitation along the intended route of flight. During the flight, the pilot inquired to air traffic control on several occasions that he thought about diverting; however, he elected to continue along the route of flight until the weather conditions deteriorated to a point that he decided to divert. After diverting to an alternate airport, the pilot attempted a non-precision approach. During the approach, the pilot failed to turn on the runway lights, which were to be activated by the pilot through the UNICOM frequency. A witness observed the airplane over fly the runway and the runway lights were not illuminated. Because the pilot could not see the runway during the approach, he executed a missed approach; however, he did not fly the published missed approach procedure resulting in an impact with mountainous terrain. Rescue personnel reported that the pilot stated he was "flying last night in bad weather, it was a stupid thing to do and he should not have been flying." The accident site was located on rock and sagebrush covered terrain at an elevation of 8,350 feet approximately 4 miles west from the runway threshold. At the time of the accident, the weather conditions at the airport were reported as visibility 10 statute miles, rain, scattered clouds at 3,300 feet, and density altitude of approximately 9,500 feet. The pilot had accumulated approximately 20 hours in the accident airplane make and model, 11 night flight hours, and no actual instrument meteorological conditions (IMC) flight experience as a single pilot. No anomalies were noted with the airframe and engine.
Probable cause
The pilot's failure to properly execute the published missed approach procedure resulting in an impact with mountainous terrain. Contributing factors were the pilot's attempted flight into known adverse weather conditions, failure to obtain the UNICOM frequency during the approach which resulted in the pilot's failure to illuminate the runway lights, and the pressure induced on the pilot by the night, weather and terrain conditions encountered during the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06FA114
- Event ID
- 20060828X01248
- Case number
- DEN06FA114
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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 2006-08-16.
- API snapshot SHA-256: 783b09bbd7110491fe6178200ed61c99a24b90f2e27cb4eceecccaca9a350461; retrieved 2026-09-21T08:54:21.838Z.