FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18FA093 · Cirrus Design Corp SR22T

21 Feb 2018 · San Diego, CA, United States

Cirrus Design Corp SR22T · Accident: abrupt maneuver on approach

From Montgomery-Gibbs Executive Airport (MYF) to Yuma International Airport / Marine Corps Air Station Yuma (YUM)

Report a problem

Event

NTSB case
WPR18FA093
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cirrus Design Corp SR22T

Aircraft type
Cirrus SR22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N707DF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Montgomery-Gibbs Executive Airport (MYF), San Diego, CATo Yuma International Airport / Marine Corps Air Station Yuma (YUM), Yuma, AZ
Aircraft age
About 1 year (built 2017)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Abrupt maneuver
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18FA093
Event ID
20180221X04610
Case number
WPR18FA093
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e60eb87545b0779d07fc141d882a5b99aae02dcdb3b1c4352f79417d052ade0e; retrieved 2026-09-15T06:34:22.825Z.