Back to Search

NTSB investigation record

CHI07FA073

Completed

Cessna 340A· N111SC

NTSB Report
Date
February 17, 2007
Location
Council Bluffs, IA
Conditions
IMC
Record
Published September 2, 2021

Primary finding

Probable cause

The pilot's continued flight into adverse weather, and his failure to maintain altitude during the instrument approach. Contributing factors were the presence of severe icing, moderate turbulence, and low-level wind shear.

Investigator assessment

Analysis narrative

The flight was on a VHF Omni Range (VOR) instrument approach to the destination airport at the time of the accident. Radar track data indicated that the airplane passed the VOR at 2,800 feet. After passing the VOR, it turned right, becoming established on an approximate 017-degree magnetic course. The published final approach course was 341 degrees. The airplane subsequently entered a left turn, followed immediately by a right turn, until the final radar data point. Altitude returns indicated that the pilot initiated a descent from 2,800 feet upon passing the VOR. The airplane descended through 2,000 feet during the initial right turn, and reached a minimum altitude of 1,400 feet. The altitude associated with the final data point was 1,600 feet. The initial impact point was about 0.18 nautical miles from the final radar data point, at an approximate elevation of 1,235 feet. The minimum descent altitude for the approach procedure was 1,720 feet. Review of weather data indicated the potential for moderate turbulence and low-level wind shear in the vicinity of the accident site. In addition, icing potential data indicated that the pilot likely encountered severe icing conditions during descent and approach. The pilot obtained a preflight weather briefing, during which the briefer advised the pilot of current Airman's Meteorological Information advisories for moderate icing and moderate turbulence along the route of flight. The briefer also provided several pilot reports for icing and turbulence. A postaccident inspection of the airframe and engines did not reveal any anomalies associated with a preimpact failure or malfunction.

Source record

Factual narrative

HISTORY OF FLIGHT On February 16, 2007, at 2104 central standard time, a Cessna 340A, N111SC, piloted by an airline transport pilot, was destroyed during an in-flight collision with terrain and trees 3 nautical miles south-southeast of Council Bluffs Municipal Airport (CBF), Council Bluffs, Iowa. The business flight was operating under 14 CFR Part 91 on an instrument flight rules (IFR) flight plan. Night instrument meteorological conditions prevailed in the vicinity about the time of the accident. The pilot and three passengers sustained fatal injuries. The flight departed Northwest Arkansas Regional Airport (XNA), Fayetteville, Arkansas, about 1903. The intended destination was CBF. Earlier on the day of the accident, the pilot and passengers flew from CBF to Jasper County Airport (JAS), Jasper, Texas, with an intermediate fuel stop at Fort Smith Regional Airport (FSM), Fort Smith, Arkansas. The initial outbound flight departed CBF about 0719 and arrived at JAS approximately 1050. The airport manager at JAS reported that the pilot ate lunch at the airport, and that he contacted flight service to obtain a weather briefing. He added that the briefing seemed thorough, and the pilot appeared to be "very knowledgeable." He added that the airplane seemed to be well maintained. The pilot obtained a preflight weather briefing for the return flights from Montgomery County Automated Flight Service Station (AFSS) at 1553. The briefer informed the pilot of the possibility of encountering moderate icing conditions and moderate turbulence during the flight. The first leg of the return flight departed JAS about 1629 and arrived at XNA approximately 1827. The accident flight refueled and subsequently departed XNA approximately 1903. The Federal Aviation Administration (FAA) provided radar track data and a transcript of air traffic control communications with the accident flight. Altitudes related to the track data are referenced to mean sea level and distances are in nautical miles. At 1904:07 (HHMM:SS), the initial radar data point was recorded approximately 1.15 miles southwest of XNA. The Mode-C altitude associated with that data point was 3,700 feet. The track data indicated that the flight proceeded on-course toward the intended destination. The flight climbed to a cruise altitude of 10,000 feet until about 2002:02, when it initiated a climbed to 12,000 feet, while in the vicinity of Kansas City, Missouri. About 2039:05, the flight began a descent from 12,000 feet and leveled at 11,000 feet. At 2043:56, the flight established radio contact with Omaha Terminal Radar Approach Control (TRACON). The pilot reported that the airplane was in level flight at 11,000 feet at that time. At 2044:12, the flight was instructed to descend at pilot's discretion to 5,000 feet and proceed direct to the Omaha Very-High-Frequency Omni Range (VOR) navigation station. The pilot requested the VOR-A approach into CBF. Track data indicated that the pilot subsequently began the descent about 2044:51. The controller informed the pilot of reports of light to moderate icing below 9,000 feet. At 2051:23, the flight was cleared for the VOR-A approach into CBF. The controller instructed the pilot to maintain 3,000 feet until established on the approach. The aircraft was approximately 26 miles south of CBF at that time and descending through 7,000 feet. About 2055:34, the pilot leveled at 3,000 feet, at which time the aircraft was approximately 15 miles south of CBF. The controller informed the pilot of wind gusts to 39 knots at Omaha Eppley Airfield. The controller released the pilot to the CBF Common Traffic Advisory Frequency (CTAF) at 2058:20. The flight was approximately 10 miles south of CBF at that time. No further communications were received from the accident airplane. The VOR-A approach procedure into CBF required the pilot to cross the Omaha VOR at or above 2,800 feet. After passing the VOR inbound to the airport, the pilot was to track the 341-degree radial and initiate a descent to the minimum descent altitude (MDA) of 1,720 feet. Flight visibility of 1 statute mile was required to descend below the MDA and land. The track data indicated that the airplane passed approximately 0.25 miles east of the Omaha VOR about 2101:53 at 2,800 feet. In the 2 minutes prior to reaching the VOR, the aircraft's ground track was approximately 345 degrees magnetic. Upon passing the VOR, the track data indicated that the airplane began a turn to the right, reaching an approximate magnetic course of 017 degrees. During this time the Mode-C altitude returns indicated that the airplane began a descent, reaching 2,000 feet at 2102:34. The track indicated that about 2102:39, the airplane began a left turn followed by a right turn until the final data point at 2103:11. The altitude associated with this final data point was 1,600 feet. The data indicated the airplane reached a minimum altitude of 1,400 feet during the right turn about 2102:57. The magnetic bearing from the VOR to the final radar data point was approximately 345 degrees. The initial impact point was located approximately 0.18 miles northeast of the final radar track data point. This was about 2.2 miles from the VOR and 3.1 miles from CBF. The elevation of the initial impact point was about 1,235 feet. PERSONNEL INFORMATION The pilot held an airline transport pilot certificate with single and multi-engine land airplane ratings. His single engine rating was limited to commercial pilot privileges. He held a flight instructor certificate with single and multi-engine airplane, and instrument airplane ratings. He also held a ground instructor certificate with an advanced rating. The pilot held a first-class airman medical certificate issued on August 29, 2006. The certificate was issued without restrictions or limitations. Logbook endorsements indicated that the pilot had completed a flight review, instrument proficiency check, and high altitude/pressurized aircraft checkout on December 21, 2005. His most recent logbook entry was dated February 9, 2007. Additionally, on the day of the accident, he had flown approximately 7 additional hours. According to the information available, the pilot had accumulated about 3,275 hours total flight time. Of that total, 1,045 hours were in multi-engine airplanes, 105 hours were in actual instrument conditions, and 94 hours under simulated instrument conditions. Total night flight time at the time of the accident was about 326 hours. During the 30-day period prior to the accident, the pilot had flown about 55 hours total flight time, all of which were in multi-engine airplanes. Of that flight time, approximately 12 hours were in the accident airplane and about 11 hours were at night. He had flown about 4 hours in actual instrument conditions, including 10 instrument approaches. During the 90-day period prior to the accident, the pilot had accumulated approximately 124 hours total flight time, of which 109 hours were in multi-engine airplanes. About 16 hours were in the accident airplane, and 28 hours were at night. He had flown about 8 hours in actual instrument conditions and 1 hour under simulated instrument conditions, including 16 instrument approaches. During the 6-month period prior to the accident, he had flown approximately 306 hours total flight time. Of that total, about 26 hours were in actual instrument conditions and 1 hour was under simulated instrument conditions, including 26 instrument approaches. AIRCRAFT INFORMATION The accident airplane was a 1977 Cessna 340A, s/n 340A0335. It was a pressurized, six-place, twin-engine airplane, equipped with retractable tricycle landing gear. It was equipped with inflatable deice boots to provide in-flight icing protection. Two 310-horsepower Continental TSIO-520-NB engines powered the airplane. According to the maintenance logbooks, the mo

Continue research

Find similar accidents

Continue with the strongest shared characteristics.