WPR22LA114 · Cessna 208B Supervan
Cessna 208B Supervan · Accident: collision with terrain/object (non-CFIT) on approach
Event
- NTSB case
- WPR22LA114
- 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
- Event fatalities
- Unknown
- 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
- N10JA
- Operator
- GoJump
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 20 years (built 2002)
- 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
- Collision with terrain/object (non-CFIT)
- 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 propeller/rotor
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was performing skydiving operations in the turboprop-equipped airplane. During the fourth flight of the day, after the skydivers departed the airplane, the pilot initiated a steep, turning descent with the power at idle, during which the airplane reached a maximum descent rate of 6,400 ft per min (fpm). While the airplane was on the base leg of the traffic pattern, the pilot attempted to arrest the descent by adding power; however, the engine did not respond to his movements of the power lever. He moved the propeller speed lever, which was also had no effect. He applied full nose-up trim and pulled the control yoke full aft against the stop, but the airplane would not maintain a level attitude, and subsequently collided with terrain short of the runway in a nose-low attitude.
There were numerous publications from the STC holder and the engine and propeller manufacturers warning pilots to not use beta mode during inflight operations unless it is certified for those operations. If the power lever is placed below the flight idle gate into beta mode while inflight, the blade position will move to a fine blade angle. Depending on propeller rpm and flight speed, this adjustment may cause the moment from the aerodynamic load on the blade to shift from coarsening to fining, and may result in the propeller blades entering reverse and remaining “aerodynamically locked” in that position. No power lever input from the pilot can alter this, and using the feather valve is ineffective. It is likely that the only viable option to unlock the propeller is to shut down the engine to reduce the moments locking the propeller in place, given it could overcome windmilling speed loads on the blades.
Postaccident examinations revealed no evidence of a mechanical malfunction with the engine, propeller, or airframe. A bench-flow test and subsequent teardown examination of the propeller governor revealed a few test points outside of limits that would not have precluded normal governor operation. The propeller rigging was incorrect and it is unknown if the rigging was changed on purpose to aid with faster descent rates; if this was the rigging at the time of the accident flight, it would have contributed to entering an aerodynamic lock sooner.
A performance study of the flight based on Automatic Dependent Surveillance – Broadcast (ADS-B) data revealed high negative thrust values that can only be achieved with the power lever below the flight idle gate. It is likely that the propeller blade pitch angle was in beta and that the aerodynamic moment on the blades had reversed, locking the propeller in place and preventing the pilot from recovering control of the propeller.
Probable cause
The pilot’s intentional inflight operation of the propeller in beta, which led to an aerodynamic lock, his inability to restore forward thrust, and subsequent collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA114
- Event ID
- 20220301104712
- Case number
- WPR22LA114
- 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: f537e9627f11643edab60ee3c658021ca03a8dd032a1fb74785d7d4329ae9b55; retrieved 2026-09-16T15:00:20.667Z.