Accident Details
Probable Cause and Findings
The pilot's loss of control due to spatial disorientation shortly after takeoff into low instrument meteorological conditions.
Aircraft Information
Registered Owner (Historical)
Analysis
HISTORY OF FLIGHTOn August 30, 2015, about 0918 central standard time, a Cirrus SR22 airplane, N765CD, was destroyed when it collided with terrain shortly after takeoff from Kewanee Municipal Airport (EZI), Kewanee, Illinois. The private pilot and one passenger were fatally injured; the second passenger sustained serious injuries. The airplane was privately owned, and the personal flight was operated under the provisions of 14 Code of Federal Regulations Part 91. Instrument meteorological conditions prevailed throughout the area, and an instrument flight rules (IFR) flight plan was filed for the cross-country flight, with an intended destination of Hot Springs, Arkansas.
A family member drove the pilot and passengers to EZI at 0745. During the short drive, the pilot discussed the fact that the airplane's autopilot had stopped working during the flight to EZI a few days before. The pilot thought that this would make the trip a little harder but that it was not a critical system preventing his departure. The pilot said that he initially planned to fly under the clouds then climb above the clouds to his desired cruise altitude of 11,000 ft. Upon arriving at the airport, the pilot decided to delay the flight due to the amount of fog in the area. The pilot and passengers subsequently returned to the airport about 0900 for departure.
There were no witnesses to the accident and no distress calls were broadcast via radio. According to Flight Service, the pilot called before takeoff to file an IFR flight plan. He was given clearance to take off with a void time of ten minutes to activate the flight plan. The airport manager reported that the pilot taxied for takeoff on runway 27; however, the pilot's radio calls indicated that he thought he was using runway 19. After an aborted takeoff, the pilot completed a back-taxi on runway 27, but again his radio calls were for runway 19. The airplane subsequently departed runway 27.
The surviving passenger, who was seated in the left rear seat, stated that the aborted takeoff was due to an open door. After securing the door, the airplane subsequently departed. She stated that when the airplane took off, it went quickly into the clouds. She stated that it did not feel as if the airplane was "going up." She stated that she heard a discussion between the pilot and then passenger seated in the front seat: the front seat passenger had reached for the activation handle for the airframe parachute system, and the pilot stated that the airplane was "too low." She then saw the ground approaching, and the impact occurred.
According to radar data obtained from the Federal Aviation Administration (FAA) Quad City Terminal Radar Approach Control facility, identified targets corresponded with the accident airplane's assigned transponder code. Additionally, five subsequent primary targets were consistent with the track of the accident airplane. There were no other aircraft operating in the immediate vicinity. The radar data corresponding to the airplane's transponder code began at 0914:53 at a Mode C reported altitude of 1,500 ft after the airplane departed EZI. The target continued in a left turn to the west and south and climbed to an altitude of 1,800 ft before beginning a descent to 1,200 ft. That data ended, and the primary radar returns consistent with the accident airplane begin at 0915:37 and continued until the last associated target at 0916:35 and an altitude of 1,600 ft. EZI airport elevation was 858 ft. A flight path superimposed between the primary targets suggested that the pilot made three nearly 360° left turns in close succession before impacting the ground. See figure 1.
Figure 1. Flight track after takeoff PERSONNEL INFORMATIONThe pilot held a private pilot certificate with ratings for airplane single-engine land and instrument airplane. His most recent FAA third-class medical certificate was issued on August 14, 2014. Review of the pilot's logbooks indicated a total flight experience of 922 hours of which 37 hours were in the accident airplane make and model. The pilot completed a Cirrus Advanced Transitional Instrument Training Course in May 2015. The pilot had logged 130 hours of actual instrument flight experience and 94.1 hours of simulated instrument experience. In the 90 days before the accident, the pilot logged 3.1 hours simulated instrument experience and 4.8 hours actual instrument experience, all of which were in the accident airplane make and model. AIRCRAFT INFORMATIONThe airplane's most recent annual inspection was completed on March 5, 2015, at a Hobbs meter time of 1,635.1 hours. On June 25, 2015, at a Hobbs time of 1,635.2 hours, a new Engine Data Management System was installed. The aircraft logbook included an entry stating that the Cirrus Airframe Parachute System (CAPS) was replaced on October 4, 2011, at a Hobbs time of 1,134.2 hours. At the time of the accident, the Hobbs time was 1,734.8 hours.
The co-owner of the airplane reported that he had flown the airplane 9 days before the accident. He reported that there were no problems with the aileron trim or the autopilot. He flew using GPS navigation and with the autopilot engaged for the entire flight. The 5.4-hour flight had 3 occupants onboard with 50 pounds of baggage. He also stated that he had talked to the accident pilot the morning before the accident. The pilot told him that the autopilot would hold altitude, but it would not hold the horizontal situation indicator (HSI) heading bug or the GPS. The pilot also told him that the trim on the sidestick was not working and that he could hold straight and level flight with a bit of right aileron. The co-owner and pilot agreed to have the trim looked at upon his return flight.
A family member reported that he and the pilot had flown the airplane on a local flight from EZI for about 15-20 minutes on the morning before the accident. He reported that the flight was normal and that they did not experience any problems. METEOROLOGICAL INFORMATIONFirst responders reported foggy conditions and low cloud ceilings about the time of the accident.
EZI listed no official weather reporting capability; however, an unofficial weather station was collocated at EZI and reported the following conditions at 0910: wind from 090° at 1 knot, temperature 18.9°C, dew point 18°C, relative humidity 99%, altimeter 30.11 inches of mercury (Hg). Visibility and sky conditions were not reported.
The closest reporting station to the accident site was from Galesburg Municipal Airport (GBG), Galesburg, Illinois, located 28 miles southwest of the accident site at an elevation of 764 ft. The airport had an Automated Weather Observation System (AWOS), which issued observations every 20 minutes. The 0915 observation included: calm wind, visibility 1 miles in mist, ceiling overcast at 200 ft, temperature and dew point 19°C, altimeter 30.09 inches of Hg.
A review of the observations for the day indicated that IFR conditions were reported as early as 2215 the previous evening, with low ceilings and visibility in fog and mist continuing through the time of the accident, and clearing by 1115. A weather study was completed by a NTSB staff meteorologist and is referenced in the public docket to this report. AIRPORT INFORMATIONThe airplane's most recent annual inspection was completed on March 5, 2015, at a Hobbs meter time of 1,635.1 hours. On June 25, 2015, at a Hobbs time of 1,635.2 hours, a new Engine Data Management System was installed. The aircraft logbook included an entry stating that the Cirrus Airframe Parachute System (CAPS) was replaced on October 4, 2011, at a Hobbs time of 1,134.2 hours. At the time of the accident, the Hobbs time was 1,734.8 hours.
The co-owner of the airplane reported that he had flown the airplane 9 days before the accident. He reported that there were no problems with the aileron trim or the autopilot. He flew using GPS navigation and with the autopilot engaged for the entire flight. The 5.4-hour flight had 3 occupants onboard with 50 pounds of baggage. He also stated that he had talked to the accident pilot the morning before the accident. The pilot told him that the autopilot would hold altitude, but it would not hold the horizontal situation indicator (HSI) heading bug or the GPS. The pilot also told him that the trim on the sidestick was not working and that he could hold straight and level flight with a bit of right aileron. The co-owner and pilot agreed to have the trim looked at upon his return flight.
A family member reported that he and the pilot had flown the airplane on a local flight from EZI for about 15-20 minutes on the morning before the accident. He reported that the flight was normal and that they did not experience any problems. WRECKAGE AND IMPACT INFORMATIONExaminations of the airframe and engine were accomplished at the accident site and a secured hangar located at the Kewanee Airport.
The accident occurred in a planted soybean field, about 1.5 miles west of the Kewanee airport. The airplane impacted terrain in an approximate 45° nose-down, right-wing-low attitude on a heading of about 130-140°. The debris field extended to the east about 260 ft from the initial point of impact on a headings from 080 to 110°. The main wreckage came to rest on a heading about 190°.
An examination of the ground impact scars and debris path showed that the tip of the right wing struck the ground at the western end of the debris field. The scar from the right wing tip was the initial point of impact. Propeller cuts, dirt clumps, and an impact depression were noted in the soft soil about 38 to 45 ft from the initial impact point. The separated propeller was located at 55 ft, and the right cabin door was located at 65 ft. The tip of the right wing and aileron were at 67 ft. The upper engine cowling was at 72 ft and the lower engine cowling was at 78 ft. The CAPS enclosure cover was at 75 ft. The left cabin door was at 120 ft, the main wreckage wa...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# CEN15FA388