Cirrus SR22T N3636E

Summary

On 21 October 2017 at about 00:56 local time, a Cirrus SR22T registered N3636E was involved in an accident near San Carlos, California, United States. 2 people were on board and 2 had minor injuries. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

Date

21 October 2017 at 00:56

Classification

Accident

Location

San Carlos, California, United States

Nearest airport

San Carlos (SQL)

Coordinates

37.5158, -122.2536

Aircraft

Cirrus SR22T

Registration

N3636E

Category

Airplane

Year built

2017

Engines

1

Operator

Not recorded

Operating rule

Part 91: General Aviation

Purpose of flight

Personal

Phase of flight

Not recorded

Route

San Carlos → Santa Monica

Aircraft damage

Substantial

Weather

VMC

Light

Day

NTSB number

WPR18LA012

2 people had minor injuries.

The pilot's failure to follow the Before-Takeoff checklist and properly set the flaps before takeoff, which altered the airplane’s flight characteristics, and the pilot’s failure to recognize the problem and abort the takeoff in a timely manner, which resulted in a runway overrun. Contributing to the accident was the pilot’s lack of experience in the high-performance airplane.

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

Read the full NTSB narrative

The private pilot departed for a cross-country flight in the high-performance single-engine airplane. Immediately after the airplane became airborne, it remained in ground effect longer than usual, and he perceived a change in engine power, and the airplane did not climb as expected. The pilot then chose to abort the takeoff; however, with limited runway available, the airplane overran the end of the runway and then struck a ditch and came to rest on the perimeter road. Postaccident examination of the airframe and engine did not reveal any evidence of preimpact anomalies that would have precluded normal operation, and review of data from the airplane's data recording system revealed that the engine was operating normally and accelerating appropriately. However, the data also indicated that the flaps were fully retracted during takeoff, rather than set to 50%, as recommended in the Pilot's Operating Handbook. The data further revealed that the pilot checked the operation of the flaps during the preflight check but failed to move them to the takeoff setting as required by the Before-Takeoff checklist. Although takeoff with fully retracted flaps is permissible, the airplane manufacturer does not provide performance data for that configuration, and the pilot was likely not used to the airplane's altered handling characteristics under such conditions. Although an accurate assessment of whether the pilot could have stopped the airplane after rotation could not be made due to the lack of performance data for a retracted flaps takeoff, it is likely that, with prompt recognition of the reduced performance, the pilot could have stopped the airplane before it overran the runway; however, surveillance video, recorded data, and the pilot's recollection indicated that he did not reduce the engine power and subsequently apply the brakes until the airplane reached the end of the runway. The pilot had recently been issued his private pilot certificate and had purchased the high-performance single-engine airplane about 1 month before the accident. He had accrued just over 22 hours of solo flight time, all in the accident make and model. It is likely that the pilot's lack of experience in the high-performance airplane led to his failure to respond to the airplane's altered flight characteristics due to the incorrect flaps setting.

Quoted verbatim from the NTSB record.