Runway excursion Accident Cirrus SR22T N3636E,
ASN logo
ASN Wikibase Occurrence # 200493
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Friday 20 October 2017
Time:17:56
Type:Silhouette image of generic S22T model; specific model in this crash may look slightly different    
Cirrus SR22T
Owner/operator:Private
Registration: N3636E
MSN: 1591
Year of manufacture:2017
Total airframe hrs:31 hours
Engine model:Continental TSIO-550-K1B
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:San Carlos Airport (KSQL), San Carlos, CA -   United States of America
Phase: Take off
Nature:Private
Departure airport:San Carlos Airport, CA (SQL/KSQL)
Destination airport:Santa Monica Airport, CA (SMO/KSMO)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.



Probable Cause: 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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR18LA012
Status: Investigation completed
Duration: 1 year and 3 months
Download report: Final report

Sources:

NTSB
https://flightaware.com/live/flight/N3636E/history/20171021/0056Z/KSQL/KSQL

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=3636E

Location

Images:


Photo: NTSB

Revision history:

Date/timeContributorUpdates
21-Oct-2017 03:34 Geno Added
21-Oct-2017 14:53 Geno Updated [Source, Narrative]
04-Jan-2018 09:34 Aerossurance Updated [Aircraft type]
10-Feb-2019 10:49 ASN Update Bot Updated [Operator, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ]
10-Feb-2019 12:33 harro Updated [Departure airport, Destination airport, Source, Narrative, Photo]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org