Cirrus Design CORP SR22T accident near San Carlos, California, October 21, 2017
On October 21, 2017, a 2017 Cirrus Design CORP SR22T, registered N3636E, was substantially damaged in an accident during takeoff near San Carlos, California (San Carlos airport). It was a personal flight under general aviation rules (Part 91). 2 people had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 21, 2017
- Place
- San Carlos, California · San Carlos · map
- Type
- Accident
- Injuries
- 2 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cirrus Design CORP SR22T GTS, built 2017
- Registration
- N3636E · no longer on the register · serial 1591
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Preflight or dispatch event during prior to flight
- Miscellaneous/other during takeoff defining event
- Runway excursion during takeoff (rejected takeoff)
- Collision with terrain or object (not controlled flight into terrain) during takeoff (rejected takeoff)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
- cause Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- Environmental issues › Physical environment › Terrain › Sloped/uneven terrain › Contributed to outcome
- factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience › Pilot
- factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 114 hours in all; 22.2 in this make and model; 22.2 in the last 90 days; 4.9 in the last 30 days; 22.2 as pilot in command
- Last flight review: June 6, 2017
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 31.2 hours
- Last inspection: annual inspection, August 30, 2017; 31 hours since
- Maximum gross weight: 3,600 lb
- Seats: 5
- Landing gear: fixed
- Engine: Continental Engines TSIO-550-K1B (piston); 31 hours total
The flight
- Departed from: SQL San Carlos CA
- Destination: SMO Santa Monica CA
- Flight plan: none
- Runway 30, 2,600 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 290° at 11 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 20,000 ft; a few clouds at 2,000 ft
- Temperature: 59°F (15°C), dew point 45°F (7°C)
- Altimeter: 30.12 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on October 22, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 11 pages | View Download |
| 2 | Pilot Interview Summary | PDF, 2 pages | View Download |
| 3 | Raw Data from Recoverable Data Module | data file | Download |
| 4 | Raw Data from Integrated Flight System | data file | Download |
| 5 | Maintenance Logbooks | PDF, 11 pages | View Download |
| 6 | Pilot's Operating Handbook Excerpts | PDF, 9 pages | View Download |
| 7 | Statement of Party Representatives to NTSB Investigation | PDF, 11 pages | View Download |
| 8 | Image 1 - Airplane at Accident Site | PDF, 1 page | View Download |
| 9 | Image 2 - Airplane Track and Parameters Derived from the Rdm and Integrated Flight System | PDF, 1 page | View Download |
| 10 | Surveillance Camera Video | video | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
