CEN19FA148 · Cessna S550
Cessna S550 · Accident: aerodynamic stall/spin during initial climb
From Indianapolis Regional Airport (MQJ) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- CEN19FA148
- 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
- 2 · 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
- Instrument Meteorological Cond
Cessna S550
- Aircraft type
- Cessna 550
- 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
- N311G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Indianapolis Regional Airport (MQJ), Greenfield, INTo Minden-Tahoe Airport (MEV), Minden, NV
- Aircraft age
- About 34 years (built 1985)
- 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
- Initial climb
- 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
- Aerodynamic stall/spin
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a personal cross-country flight in a turbofan-powered airplane. Shortly after departure, the airplane entered a witness-estimated 90° left bank with the nose parallel to the horizon; as the airplane began to roll out of the turn, the nose remained at or below the horizon before it dropped and the airplane impacted the ground. Flight track data revealed that, shortly after departure, the airplane's ground speed immediately began decreasing from its maximum of 141 knots during takeoff and continued decreasing until the last recorded data point, which showed that the airplane had a ground speed of 100 knots.
The surface wind reported about 10 minutes before the accident was from 170° at 9 knots, gusting to 14 knots, which resulted in a 1- to 2-knot tailwind component. Given this information and the airplane's configuration at the time of the accident, the airplane's indicated airspeed (IAS) would have been between about 86 and 93 knots. The airplane's stall speed was calculated to be 100 knots IAS (KIAS) with a bank angle of 45° and 118 KIAS with a bank angle of 60°. Thus, the pilot failed to maintain airspeed or accelerate after departure, which resulted in an aerodynamic stall
A pilot who had flown with the accident pilot twice before the accident reported that, during these flights, the pilot had flown at reduced power settings and slower-than-normal airspeeds. During the flight 1 year before the accident, he reached over and pushed the power levers forward himself. He also stated that every time he had flown with the pilot, he was "very behind the airplane."
Postaccident examination of the engines revealed no signs of preimpact mechanical failures or malfunctions that would have precluded normal operation, and both engines exhibited circumferential rub marks on all rotating stages, blade tip bending opposite the direction of rotation, and debris ingestion through the gas path, indicating that the engine had power at impact. Further, the right engine full authority digital electronic control (FADEC) nonvolatile memory recorded no faults. (The left engine FADEC could not be downloaded due to damage.)
The Airplane Flight Manual stated that the pilot must, in part, advance the throttle lever to the maximum takeoff detent for the FADEC's nonvolatile memory to record a logic trend snapshot 2 seconds after takeoff.
The lack of a FADEC logic trend snapshot is consistent with the pilot not fully advancing the throttles during the takeoff and initial climb and is likely why he did not attain or maintain sufficient airspeed.
The flight track data, pilot witness account, and airplane damage are consistent with the pilot failing to fully advance the power levers while maneuvering shortly after takeoff, which led to his failure to maintain sufficient airspeed and resulted in the exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.
Probable cause
The pilot's failure to fully advance the power levers during the takeoff and initial climb, which led to his failure to maintain sufficient airspeed and resulted in the exceedance of the airplane's critical angle of attack and a subsequent aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19FA148
- Event ID
- 20190522X55002
- Case number
- CEN19FA148
- 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: 366dbf6f47dc22394ae0509fab5e49ae9ebf8535ff5076953b8a3f0a7ce444ba; retrieved 2026-09-15T06:58:34.577Z.