FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA197 · Cessna 208B Supervan

3 Jun 2022 · Oceanside, CA, United States

Cessna 208B Supervan · Accident: landing area undershoot

Report a problem

Event

NTSB case
WPR22FA197
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

Cessna 208B Supervan

Aircraft type
Cessna 208
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
N7581F
Operator
GoJump
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 28 years (built 1994)
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
Landing
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
Landing area undershoot
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 › Action/decision
  • Personnel issues › Experience/knowledge

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

NTSB narrative

The pilots were performing skydiving flights while the right-seated pilot was training the left-seated pilot on the operation. The pilots completed six flights without incident and completed the drop of the skydivers on the accident flight normally. The right-seated pilot could not completely recollect the minutes leading up to the accident due to his injuries. He did recall that airplane was descending as expected with the power at idle. The recorded ADS-B data revealed that after turning onto final approach, the airplane then completed a right 360° turn presumably because the altitude was too high. The right-seated pilot attempted to increase the power by slightly nudging the throttle forward and thought the engine power did not increase as expected.

A performance study revealed that in the last 70 seconds of recorded data, the airplane underwent a series of speed and thrust oscillations consistent with a pilot increasing and then decreasing the power lever. The right seat pilot recalls aiming for an open dirt field and observing a berm in the immediate flight path. In an effort to avoid the berm, he maneuvered the airplane into a right turn. The airplane landed short of the runway, resulting in a collision with the berm.

The engine was producing power at the time of impact. Postaccident examination of the airplane revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.

The right-seated pilot was in the process of training the left-seated pilot and stated that he took over the controls during the final approach. It is unknown when he took over the controls, so it is unknown which pilot was at the controls during the speed oscillations. The right-seated pilot likely took over the controls too late and the airplane impacted the terrain. The left-seated pilot’s ability to hear the changes in engine power might have been hindered because she was listening to music through her headset at an elevated decibel level.

The airplane was modified by a Supplemental Type Certificate that replaces the original Pratt & Whitney PT-6 turbine engine with a Honeywell TPE331 turbine engine. The TPE331 engine’s characteristics are such that if the airplane is on final approach with the power near idle, the throttle sensitivity (change in thrust per unit of power lever movement) increases around the transition between the propeller-governing and underspeed-governing modes of the engine, which corresponds to a zero-thrust condition. Near this transition point, small movements of the power lever (about ¼ to ½ inch of deflection) can result in relatively large thrust changes that can surprise pilots inexperienced with this behavior and result in pilot-induced oscillations (PIO). Given the thrust oscillations observed shortly before the end of the ADS-B data, it is likely that the left-seated pilot was at the controls and experienced such a PIO on a short final approach to land.

Probable cause

The right-seated pilot’s failure to correct the left-seated pilot’s mismanagement of the engine thrust, which resulted in undesired speed and thrust oscillations during the final approach and a subsequent descent into terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA197
Event ID
20220603105183
Case number
WPR22FA197
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, cause areas. 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: eca84577c571c714b51e9ef41e8d3e92132e1be0d39d4500727e243f52f524c9; retrieved 2026-09-15T07:45:30.635Z.