Plane Crash List

Cirrus SR22 N507TX

12 May 2018 · Lone Tree, Colorado, United States · Fatal

Summary

On 12 May 2018 at about 03:19 local time, a Cirrus SR22 registered N507TX was involved in an accident near Lone Tree, Colorado, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 03:19
Classification
Accident
Location
Lone Tree, Colorado, United States
Nearest airport
Centennial Airport (APA)
Coordinates
39.5161, -104.8339
Aircraft
Cirrus SR22
Registration
N507TX
Category
Airplane
Year built
2005
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Denver → Grand Junction
Aircraft damage
Destroyed
Weather
VMC
Light
Night/Dark
NTSB number
CEN18FA168

People

1 person died.

On board Died Serious Minor Uninjured
1 1 0 0 0

Probable cause

The pilot's loss of control due to spatial disorientation. Contributing to the accident was the pilot's self-induced pressure to fly the airplane at night in marginal weather conditions.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The instrument-rated private pilot departed on a visual flight rules cross-country flight just before the end of civil twilight. After departing to the north, the pilot turned onto a left downwind to depart the area toward the south; the controller advised the pilot to stay west of the extended runway centerline, which the pilot acknowledged. However, about 2 minutes after takeoff, the airplane turned east and crossed the extended centerline. After crossing the centerline, the controller asked the pilot to state his intentions, and the pilot replied that he was going to return to the airport. The airplane turned back toward the airport and began tracking west toward the extended centerline; radar contact was lost several minutes later. The airplane impacted a field about 2.5 miles to the south of the approach end of the runway. The airplane was massively fragmented during the impact and debris was scattered for about 1,200 ft. The damage to the airplane and the ground scars at the accident site were consistent with the airplane impacting in a right wing low, nose low attitude with relatively high energy. The postaccident examination of the engine and propeller assembly did not reveal any preimpact anomalies that would have precluded normal operation. Signatures were consistent with the engine producing power and the propeller developing thrust at the time of impact. While the massive fragmentation precluded functional testing of the flight controls, there was no damage or failure that suggested preimpact anomalies with the airframe or flight controls. While visual meteorological conditions prevailed at the airport, statements from two pilots flying instrument approaches to runway 35R suggest that the pilot likely encountered and was flying in the clouds to the south of the airport just before the accident. A review of radar data and voice communications revealed that the instructions issued by the controller, to the pilot, were reasonable and in accordance with air traffic control procedures. Investigators were not able to establish why the pilot did not comply with air traffic control instructions. The accident flight was the airplane's first flight after completion of an annual inspection, and the pilot was flying to meet his family for an event in another state. It is likely that the pilot was experiencing self-induced pressure to complete the flight as planned in order to maintain the family's schedule of events, and as a result, chose to depart on the visual flight rules flight over mountainous terrain at night in marginal weather conditions. The pilot's logbook was not recovered, and the recency of his instrument flight experience could not be determined. Based upon the reported weather conditions, the location and fragmentation of the wreckage, and radar data, it is likely that the pilot experienced spatial disorientation shortly after entering the clouds which resulted in a loss of control and descent into terrain. The reason for the pilot's stated intention to return to the airport after takeoff could not be determined, but it is possible that he became distracted and that distraction contributed to his disorientation and loss of control.

Quoted verbatim from the NTSB record.

Other Cirrus SR22 accidents

Date Aircraft Location Operator Outcome Died
23 Nov 2018 Cirrus SR22
N82SN
Greenville, South Carolina, United States Scs Aero Llc No injuries -
1 Jun 2018 Cirrus SR22
N670SR
Midland, Texas, United States - Fatal 2
12 Oct 2018 Cirrus SR22
N729TG
Midland, Texas, United States TJG Equipment LLC Minor injuries -
19 Apr 2018 Cirrus SR22
N451TD
Williamsburg, Pennsylvania, United States - Fatal 2
10 Dec 2018 Cirrus SR22
F-HUGE
Beauberry, France
no coordinates
Aeroclub D Aeroports De Paris Fatal 3
24 Aug 2018 Cirrus SR22
LZ-SEV
Balchik, Bulgaria
no coordinates
- Fatal 1

All 365 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
26 Jan 2018 Robinson R44 II
N878BC
Loveland, Colorado, United States - Minor injuries -
15 Apr 2018 Cessna T210N
N6988N
Colorado Springs, Colorado, United States - Minor injuries -
23 Aug 2018 Piper PA32R
N2880W
Falcon, Colorado, United States - No injuries -
13 Oct 2018 Cessna 120
N1881N
Hudson, Colorado, United States - Minor injuries -
25 Dec 2018 Van's RV 6
N711KJ
Watkins, Colorado, United States - No injuries -
22 Jul 2018 Cessna 172
N99243
Colorado Springs, Colorado, United States - No injuries -

All 170,864 records in United States