The U.S. aircraft register, updated daily
Accidents · NTSB WPR18FA093 · Final report

Cirrus Design CORP SR22T accident near San Diego, California, February 21, 2018

On February 21, 2018 at about 2:31 pm local time, a 2017 Cirrus Design CORP SR22T, registered N707DF, was substantially damaged in an accident during approach near San Diego, California (Montgomery-Gibbs Executive Air airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's exceedance of the airplane's critical angle of attack during an attempted return to the runway following a total loss of engine power after takeoff, which resulted in an aerodynamic stall. Contributing to the accident was the excessive amount of fuel being delivered to the engine for reasons that could not be determined based on the available information.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 21, 2018 · about 2:31 pm local time
Place
San Diego, California · Montgomery-Gibbs Executive Air · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22T, built 2017
Registration
N707DF · no longer on the register · serial 1621
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot was taking off in the airplane when witnesses heard the airplane lose engine power at low altitude and described a sequence of events consistent with an aerodynamic stall/spin. Data retrieved from onboard the airplane recorded 47 power cycles, including the accident takeoff. The data revealed an abnormally high fuel flow, about 46 gallons per hour (gph), when takeoff power was applied, reaching 50.1 gph as the airplane entered the initial climb. About 300 ft above ground level (agl), the airplane experienced a total loss of engine power and began to decelerate and roll to the right. The airplane then entered a steep left bank and nearly vertical nose-down attitude as it descended to ground contact. The final data point at 50 ft agl indicated that the airplane was in an 81° nose-down pitch attitude and a 157° (inverted) left roll. The data is consistent with the pilot attempting to return to the runway following a loss of engine power at low altitude and an aerodynamic stall/spin when the pilot exceeded the airplane's critical angle of attack during the turn. Examination of the engine revealed signatures consistent with an excessively rich fuel/air mixture. The fuel manifold and engine-driven fuel pump were removed from the engine and installed onto a slave engine for a test run, during which the slave engine began to surge when the power was increased to 2,300 rpm; the fuel pressure indicated 234 psi (about 39 gph); a nominal value was 210-220 psi. The engine-driven fuel pump adjustment screw was adjusted in the lean direction, and the engine operated within normal parameters; however, when the test cell fuel boost pump was turned on, the engine lost total power. The airplane was equipped with an electric fuel boost pump that could be manually activated by the pilot via a cockpit switch. The pump had two modes; the BOOST position supplied an additional 4-6 psig at 19 gph to the engine and was used for vapor suppression when required and during takeoff, climb, landing, and when switching fuel tanks. The HIGH BOOST/PRIME position provided a capacity of 42 gph at 16 psig with a maximum full relief (no flow) pressure of 23 psig to the engine, and was used for priming the engine before start and suppressing vapor formation at flight altitudes above 18,000 ft with hot fuel. It is likely that the excess fuel being delivered to the engine during the initial climb resulted in the total loss of power; however, the reason for the excessive fuel flow values could not be determined. According to the manufacturer, the initial fuel flow adjustments occurred at the factory about 4 months before the accident and before the pilot took delivery of the airplane. There were no maintenance logbook entries to indicate that the fuel flow had been adjusted since that time. The data did not indicate a gradual increase in fuel flow values over time; therefore, it is unlikely that the engine-driven fuel pump adjustment screw was becoming loose. It is possible that the pilot placed the fuel boost pump in the HIGH BOOST/PRIME position before takeoff, which would have increased fuel flow to about 42 gph, but this scenario does not account for the 50-gph fuel flow value reflected in the data. (The fuel boost pump position was not a recorded parameter and the position of the switch at the time of takeoff could not be determined.) Thus, based on the available information, the reason for the fuel flow rates being  so high during the takeoff could not be determined.

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

  1. Fuel related during initial climb
  2. Loss of engine power (total) during initial climb
  3. Abrupt maneuver during approach defining event
  4. Aerodynamic stall/spin during approach
  5. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • factor Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
  • Aircraft › Aircraft systems › Fuel system › Fuel pumps › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 2,700 hours in all; 1,000 in this make and model; 15 in the last 90 days; 2,600 as pilot in command
  • Last flight review: March 28, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 66 hours
  • Last inspection: condition inspection, February 16, 2017; 2 hours since
  • Seats: 5
  • Landing gear: fixed
  • Engine: Continental Motors TSIO-550-K (piston); 66 hours total

The flight

  • Departed from: MYF San Diego CA at 2:30 pm
  • Destination: YUM Yuma AZ
  • Flight plan: none
  • Runway 5, 3,400 ft by 75 ft

Weather at the time

  • Light: dawn
  • Wind: from 120° at 6 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 10,000 ft; clear
  • Temperature: 45°F (7°C), dew point 25°F (-4°C)
  • Altimeter: 30.12 inHg
  • Observation at 2:53 pm from MYF, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

14 documents, released by the NTSB on October 30, 2019. 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.

#DocumentWhat it is
1 Recorded Flight Data Factual Report PDF, 11 pages View Download
2 Recorded Flight Data Factual Report - Attachment 1 data file Download
3 Recorded Flight Data Factual Report - Attachment 2 data file Download
4 Recorded Flight Data Factual Report - Attachment 3 data file Download
5 Witness Statements PDF, 3 pages View Download
6 Accident Location - Google Earth PDF, 1 page View Download
7 Air Traffic Control Statement - Courtesy of the Federal Aviation Administration PDF, 1 page View Download
8 On Scene Observations PDF, 10 pages View Download
9 Airframe and Engine Examination Observations PDF, 4 pages View Download
10 Engine Examination/run and Propeller Examination Observations PDF, 14 pages View Download
11 Engine Maintenance Logbook PDF, 4 pages View Download
12 Statement of Party Representatives to NTSB Investigation PDF, 3 pages View Download
13 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 1 page View Download
14 Toxicological Report PDF, 1 page 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.