N227TX

HISTORY OF FLIGHT

On October 24, 2011, approximately 1135 central daylight time, a Cirrus SR22T single-engine airplane, N227TX, sustained substantial damage when it impacted terrain following a loss of engine power while maneuvering near Carrollton, Texas. The private pilot and one passenger sustained serious injuries and a second passenger sustained fatal injuries. The airplane was co-owned and operated by the pilot. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the 14 Code of Federal Regulations Part 91 personal flight. The flight departed the Addison Airport (ADS), Dallas, Texas, at 1058 and was destined for Houston, Texas.

According to PlaneSmart Aviation, LLC, the company that managed the airplane for the pilot and other co-owners, on August 24, 2011, the pilot requested a reservation for the airplane for October 25 and 26th. At that time, the pilot requested via electronic mail to PlaneSmart that the airplane be fueled to the "tabs or better." On September 6, 2011, the pilot changed the departure date to October 24th with the return date remaining on the 26th. There was no change to the original fuel request.

On October 19, 2011, a PlaneSmart staff pilot flew the airplane from ADS to Cincinnati, Ohio, and returned the following day. The pilot reported there was a total of 9.8 gallons of fuel on board at the time he shut down the airplane. The airplane was not flown again until the accident flight four days later.

According to a Landmark Aviation (the fixed based operator (FBO) that PlaneSmart and its customers used for fueling) line service technician, he fueled the airplane on October 18th with 51.8 gallons of fuel. On October 21st, a PlaneSmart representative contacted Landmark Aviation for a fuel request on three airplanes, to include N227TX, which was to be filled "to the tabs +5." The PlaneSmart representative asked that the airplanes be filled by 2000 on the 21st. The line service technician went to fill the airplanes; however, N227TX was not available or out on the ramp for him to service with fuel. The line service technician returned at 2040 to fuel N227TX and still did not locate the airplane. At that time, the line service technician returned to the FBO and moved N227TX's fuel request to October 22nd. The line service technician returned to work at the FBO later in the day on October 22nd. When he returned, he was not sure if N227TX had been fueled that morning, so he returned to PlaneSmart to locate the airplane. The technician passed through the PlaneSmart ramp and did not locate N227TX. He then returned to the FBO and cancelled the fuel request. There was no record from the FBO the accident airplane had been fueled prior to the accident flight.

PlaneSmart representatives noted the pilot entered their facility approximately 1000 on the day of the accident. The pilot indicated to PlaneSmart staff he was waiting for two individuals who were traveling with him. The two individuals arrived and the airplane was observed taxiing for departure from one of PlaneSmart's shaded parking stalls. PlaneSmart representatives did not observe the pilot's actions after he and his two passengers exited the facility and the airplane began to taxi.

According to air traffic control (ATC) communications, radar data, and data extracted from the airplane's recoverable data module (RDM), at 1043, the engine was started and the white advisory alert left fuel quantity crew alerting system (CAS) message illuminated on the Garmin Perspective primary flight display (PFD). At 1043, the pilot requested an IFR clearance to David Wayne Hooks Memorial Airport (DWH), Houston, Texas. At 1056, the amber FUEL QTY CAS message illuminated on the PFD when both tanks dropped below 14 gallons. At 1058, the airplane was cleared for takeoff on runway 15.

At 1110, the pilot contacted approach control and requested a direct route back to ADS because of a rough running engine. The controller asked if the pilot wanted to declare an emergency and he replied not at this time. The pilot was then given vectors to ADS. At 1118, the approach controller asked if the pilot needed assistance on the ground at ADS and the pilot responded negative. At 1123, the pilot contacted the ADS air traffic control tower (ATCT) and the controller inquired whether he needed any assistance. The pilot responded not at this time. At 1124, ADS ATCT issued the pilot a low altitude alert while on the instrument landing system (ILS) approach to runway 15 and reported he appeared to be right of the final approach course. A few seconds later, the pilot stated he would be executing a missed approach. At 1127, the pilot was given a traffic advisory call and instructed to contact approach control. Approach control vectored the pilot for a second ILS approach to runway 15.

At 1133:03, the pilot reported to approach control that he had no glideslope indication and he needed to execute another missed approach. At 1133:21, the pilot declared an emergency and requested vectors to ADS. At 1133:47, the pilot again requested vectors to ADS. No further communications were received by ATC from the pilot. Radar data showed the airplane turned east and then north. At 1134:35, the RDM data showed the Cirrus Airframe Parachute System (CAPS) rocket deployed. The last radar contact was at 1134:41 at an altitude of 600 feet mean sea level (msl). The last data point on the RDM was recorded at 1134:44 at a global positioning system (GPS) altitude of 593 feet msl.

A witness observed the airplane flying low in a north to south direction. He heard the engine "sputter...slightly rev up" and then no sound. The airplane then made a left turn to the north, the parachute deployed, and the airplane disappeared from the witness's view.

Another witness observed the airplane flying northwest to southeast going in and out of the clouds and fog. He reported the engine sounded "sick, like it was knocking, sputtering..." The airplane came out of the clouds in level flight low to the ground. The airplane then entered the clouds and the witness lost sight of the airplane.

The airplane impacted a ditch adjacent to a railroad track next to a high school. Several witnesses at the high school observed the airplane parachute deploy and the airplane impact terrain.

The pilot reported he had no recollection of the accident or proceeding 10 days.

PERSONNEL INFORMATION

The pilot, age 40, held a private pilot certificate with airplane single-engine land and instrument ratings. The pilot's third class medical certificate was issued on December 10, 2009, with no limitations or restrictions. The pilot reported 550 total flight hours, 209 flight hours in the accident airplane make/model, and 35 actual instrument flight hours.

Planesmart records showed the pilot accumulated 87.8 flight hours in Cirrus Garmin Perspective equipped airplanes.

AIRCRAFT INFORMATION

The airplane was a 2010 Cirrus SR22T, serial number 0029. The SR22T was a four-place, single-engine, low wing, composite structure airplane. The airplane was equipped from the factory with a Garmin Perspective PFD and a Garmin Perspective multi-function display (MFD). The airplane was powered by a Continental Motors TSIO-550-K, 315-horsepower engine, and equipped with a Hartzell propeller.

The airplane was issued a standard airworthiness certificate on September 23, 2010, and was registered to the owners on April 21, 2011.

A review of the maintenance logbooks revealed that the airplane's most recent annual inspection was completed on October 14, 2011. At that time, the airplane had accumulated 474.2 total hours. According to the flight meter, the airplane had accumulated 487.8 total hours at the time of the accident.

The airplane's total fuel capacity was 94.5 gallons (47.25 gallons each tank) and total usable fuel was 92.0 gallons. Fuel quantity was sensed by fuel level sensors in each tank. Their signals are passed to a Rochester fuel gauge visible to the pilot on the center pedestal, aft of the throttle. Fuel flow was measured at the engine by a fuel flow sensor just upstream of the throttle metering valve and injector manifold. Fuel used was calculated by integrating the measured fuel flow from engine start time. Both fuel flow and fuel used were recorded by the RDM; however, fuel remaining was not recorded.

When the sensed fuel drops below 14 gallons in either tank for 60 seconds, the Rochester fuel gauge sets the appropriate left or right "Fuel Tank Low Warn" discrete on the RDM and provides the low fuel alert to the Garmin avionics for the appropriate annunciation to the pilot. The 60 second delay is used to reduce noise in the data due to fuel slosh when maneuvering. If the sensed fuel rises above the 14 gallon threshold due to fuel slosh or refueling, the discrete recorded on the RDM is deactivated and the 60 second delay is again applied if sensed fuel in a particular tank drops below 14 gallons.

In order to prevent nuisance low fuel alerts to the pilot, another 60 second delay is applied in the Garmin avionics before a white "L/R FUEL QTY" advisory is displayed on the PFD, depending on the low tank. If the sensed fuel in the other tank falls below 14 gallons, the white advisory message is replaced with an amber "FUEL QTY" caution accompanied by a double chime. If the fuel totalizer calculates total fuel below 9 gallons, a red "FUEL QTY" warning appears accompanied by a continuous chime until acknowledged. Each fuel quantity annunciation is latched and is not removed, even if acknowledged. Unlike the white advisory and amber caution messages, the red warning message is not based on sensed fuel level, but dependent on the accurate input of fuel quantity that the pilot must confirm on the initial usable fuel page during the avionics startup sequence.

METEOROLOGICAL INFORMATION

At 1147, the ADS automated weather observing system, reported the wind from 230 degrees at 4 knots, 3 ...