N8127J

Destroyed
Serious

Cirrus Design Corp. SR20S/N: 1350

Accident Details

Date
Wednesday, August 16, 2006
NTSB Number
DEN06FA114
Location
Kremmling, CO
Event ID
20060828X01248
Coordinates
40.035278, -106.451385
Aircraft Damage
Destroyed
Highest Injury
Serious
Fatalities
0
Serious Injuries
1
Minor Injuries
1
Uninjured
0
Total Aboard
2

Probable Cause and Findings

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.

Aircraft Information

Registration
N8127J
Make
CIRRUS DESIGN CORP.
Serial Number
1350
Engine Type
Reciprocating
Year Built
2003
Model / ICAO
SR20SR20
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1

Registered Owner (Historical)

Name
NIV AVIATION INC
Address
27240 NATOMA RD
Status
Deregistered
City
LOS ALTOS HILLS
State / Zip Code
CA 94022-4306
Country
United States

Analysis

HISTORY OF FLIGHT

On August 15, 2006, approximately 2220 mountain daylight time, a Cirrus Design Corporation SR20 single-engine airplane, N8127J, was destroyed when it impacted mountainous terrain while maneuvering near Mc Elroy Airfield (20V), Kremmling, Colorado. The commercial pilot sustained serious injuries and the passenger sustained minor injuries. The airplane was operated by West Valley Flying Club, Palo Alto, California, and registered to NIV Aviation, Los Alto Hills, California. Dark night visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the Title 14 Code of Federal Regulations Part 91 personal flight. The flight departed Cedar City Regional Airport (CDC), Cedar City, Utah, approximately 1900, with a planned destination of Jeffco Airport (BJC), Denver, Colorado.

According to the pilot and air traffic control (ATC) communications, prior to departure from Palo Alto (PAO), California, he obtained a standard weather briefing and filed an IFR flight plan. His plan was to fly from PAO to BJC with a planned stop at CDC to refuel. During the flight, the pilot utilized portable oxygen for the high altitude flight operations. Shortly after departure from PAO, ATC informed the pilot that the Mode C function of the transponder was not functioning. The pilot attempted to recycle the transponder; however, the attempts were unsuccessful. In addition to the Mode C problem, the pilot stated that the autopilot would not engage in the "NAV" mode, so the pilot decided to use the autopilot in the "APP" mode. The pilot continued the flight, and the airplane landed uneventfully at CDC.

During a 45-minute stop at CDC, the airplane was refueled, the pilot obtained another standard weather briefing and filed an IFR flight plan to BJC. According to the weather briefing transcript, the briefer informed the pilot of a convective SIGMET (Significant Meteorological Information) for thunderstorm activity in the mountains of Colorado. Moderate to strong weather radar echoes were reported along the pilot's intended route of flight. The pilot inquired to the briefer whether another route of flight had less thunderstorms, and the briefer responded, "no, those thunderstorms pretty much start at up toward the Rock Springs (Wyoming) area and go through to the Phoenix (Arizona) area...so it looks like no matter which way you go, you're going to be flying through something this afternoon."

According to the pilot's statement, which was taken by another individual (employee of West Valley Flying Club) and submitted to the NTSB investigator-in-charge (IIC) as part of the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1), the pilot decided to take off, and if the weather was not good enough, he would ask for vectors around the bad weather. If he could not be vectored, he would turn around and return to CDC.

Shortly after departure from CDC, the pilot again experienced problems with the Mode C function of the transponder and the "NAV" mode for the autopilot. According to communications with Denver Air Route Traffic Control Center (ARTCC), at 2025:05, the controller advised the pilot that an area of weather, moderate to severe precipitation, started at the pilot's 12 o'clock position in approximately 30 miles and extended for 75 miles past that point. The pilot acknowledged and requested to be rerouted around the weather. Based on the weather observation, the controller suggested the pilot divert to the south of Grand Junction, Colorado, and the pilot elected to divert to the south. At 2033:25 and an altitude of 16,000 feet mean sea level (msl), the pilot informed the controller that he was experiencing turbulence, requested alternate options, and if nothing else was possible, "we'd like to head to the nearest field and call it a day." The controller then cleared the pilot to 15,000 feet. At 2039:29, the pilot stated the turbulence was much better at that altitude and requested to continue his route as filed. At 2105:39, the pilot requested to land at Grand Junction "because the weather is just too bad..." The controller informed the pilot that Grand Junction's airport was closed due to a lightning strike and the airport lighting was not operating. The controller then reported that Rifle, Colorado, had an airport that was approximately 35 miles ahead of him. The pilot then inquired if the weather improved past Rifle, and the controller informed the pilot that he would be exiting the heavier precipitation in about 5 miles. The pilot elected to continue the flight, and then asked, "just wonder if Eagle Country Regional Airport is open, would like to keep our options open in case the weather turns (unintelligible) after Rifle."

At 2150:54, the controller informed the pilot that the minimum IFR altitude was 16,000 feet, and he cleared the pilot to climb and maintain 16,000 feet. The pilot responded, "at 15,500 feet...that's the maximum we can do..." The pilot reported that during this portion of the flight, the pitot heat was on; however, the airspeed went to 0 knots and the primary flight display (PFD) was lost. The airspeed indication on the PFD was intermittent and the engine data on the multi-function display was lost. The pilot reverted to the standby instruments and set the engine to 2,650 RPM, which resulted in a 85-90 knot airspeed at 15,000 feet. The pilot also heard 2 to 3 "piercing tones" which he thought might have been the stall warning horn or something else. He reported it was raining at the time of these events. At 2200:34, the pilot informed the controller that he just lost [the airplane's] engine sensor and he wondered what the closest field was in case he needed to divert. The controller advised the pilot that Granby, Colorado, airport was 12 miles ahead of him and Mc Elroy Airfield (20V), Kremmling, Colorado, was 12 miles behind him. The pilot told the controller he'd like to divert to Granby. The controller inquired whether the pilot was in visual flight rules (VFR) conditions, and the pilot responded in the negative. The controller stated that Granby did not have an IFR approach; however, 20V did have an IFR approach. At 2203:07, the pilot stated he was unable to maintain altitude and was descending to 14,000 feet. Shortly thereafter, the pilot requested a lower altitude; however, the controller stated the minimum IFR altitude was 14,000 feet. The pilot acknowledged and stated he was heading to 20V.

During the next 10 minutes of flight, the controller and pilot were communicating about headings, altitudes, and fixes for an approach to 20V. Radar data depicted the airplane heading to the west toward 20V, then execute a reverse in direction (east, southeast), and then a turn back toward 20V. At 2213:34, the pilot reported he was at the ZUMNY fix and descending to 9,400 feet for the final approach fix LARNE for runway 27. At 2216:49, the controller stated that 20V was at the 12 o'clock position and 3 miles ahead. At 2216:54, the pilot reported the airport in sight and the controller requested the pilot contact ATC when on the ground at 20V.

According to a witness, who was located in his residence adjacent to 20V, he observed an airplane flying over the runway in a east to west direction. The airplane was approximately 150 to 200 feet above the runway and had its position lights on, but no landing light. He stated the runway lights were not on at any time. The witness heard the airplane's engine running just above idle and observed the airplane continue to the west at a low altitude above the town. Approximately 2,000 feet beyond the runway, the witness heard the engine "rev back up", and then he stopped watching the airplane. He reported the following weather conditions at the time: not raining, winds were calm, and visibility was good.

At 2219:17, the pilot stated, "we're still in the air doing the missed approach, going around." The controller then informed the pilot that the airport in Hayden, Colorado, was reporting VFR conditions and had a precision instrument approach. The pilot acknowledged and stated he'd be more comfortable with a precision approach. The controller requested that the pilot climb and maintain 15,500 feet. The pilot responded, "negative, that's going to be hard for us, I think the best we'll be able to do is 14,000..." The controller asked for the pilot's current altitude and position, and the pilot responded, "we're heading 250 [degrees], 4 miles from Kremmling Airport, at 8,200 feet..." No further communications from the airplane were received by ATC.

Shortly after his last communication with ATC, the pilot heard a huge crash, like a car hitting something, and he then was unconscious for 5 to 10 minutes. After he regained consciousness, the pilot heard his son crying outside the airplane. The pilot attempted to get out of the airplane; however, his left foot was pinned under the rudder pedal. He attempted to communicate with ATC, but was unsuccessful. The pilot then turned off the airplane's electrical power and finally was able to free his foot. The pilot decided to stay in the airplane with his son until help arrived.

The airplane impacted mountainous terrain approximately 4 miles west of 20V. Search and rescue operations located the airplane approximately 0615 on August 16, 2006.

According to the individual who located the airplane and occupants, the pilot reported to him that he was "flying last night in bad weather, it was a stupid thing to do and he should not have been flying."

During a NTSB interview with the pilot, he stated that the airplane broke out of the clouds at decision height altitude for 20V and he could see houses and lights; however, he did not see the runway. The IIC asked the pilot if he switched over from ARTCC's frequency to 20V's UNICOM frequency; the pilot stated he did not think he did.

PERSONNEL INFORMATION

The pilot, who w...

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# DEN06FA114