WPR22FA196 · Beech 19A
Beech 19A · Accident: aerodynamic stall/spin on approach
Event
- NTSB case
- WPR22FA196
- 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
- Visual Meteorological Cond
Beech 19A
- Aircraft type
- Beechcraft 19
- 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
- N7641R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 53 years (built 1969)
- 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 · VFR pattern crosswind
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident pilot was a partial owner of the accident airplane, which had not flown for several months until he attempted to fly the airplane about 2 weeks before the accident. During this previous flight the pilot and his student were forced to abort two takeoff attempts after the airplane failed to climb. The pilot and pilot-rated passenger, who was also a flight instructor, had planned to fly the airplane on the day of the accident to troubleshoot the performance deficiency. During takeoff on the accident flight, the airplane reached an intermediate altitude before it started to settle momentarily. The airplane then continued to climb to a peak altitude of about 100 ft above ground level and then it started a right turn that progressively became steeper. Subsequently, the airplane impacted the ground in a nose-down attitude. An analysis of the engine harmonics during takeoff suggested that the engine may have encountered anomalies when the airplane began its right turn, but this could not be substantiated as postaccident examination of the airframe and engine did not reveal any preimpact mechanical anomalies. The fuel selector was found between the RIGHT tank detent and the OFF position at the accident site. During the flight 2 weeks earlier the accident the pilot had placed the handle in a similar position before takeoff. As there were no preimpact mechanical anomalies with the engine, it is likely that the improper placement of the fuel selector in the OFF position during takeoff resulted in fuel starvation and a partial loss of engine power. Performance computations indicated that the airplane was capable of a successful takeoff as it was below its maximum gross weight. The airplane’s center of gravity (CG) was nose-heavy, which likely would have resulted in difficulty in lifting the nose during takeoff and during reduced power situations. However, this CG condition is only likely to have affected takeoff and likely did not contribute to the accident. Recorded data suggests the airplane entered an accelerated stall in the turn when it exceeded the critical angle of attack without maintaining adequate airspeed. The investigation was unable to determine if the pilot-rated passenger was aware of the airplane’s takeoff issues 2 weeks before the accident. It is also unclear who was piloting the airplane in its final moments; however, the pilot was likely flying at the time considering he was a part owner in the airplane and given his motivation to troubleshoot the performance deficiency. While cardiovascular conditions placed the pilot at an increased risk for a sudden cardiac event, operational evidence does not suggest that this occurred and was likely not a factor in this accident.
Probable cause
The pilot’s failure to maintain proper airspeed during a turn and his exceedance of the airplane’s critical angle of attack, which resulted in an accelerated stall. Contributing to the accident was the improper placement of the fuel selector, which resulted in fuel starvation and a partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA196
- Event ID
- 20220602105179
- Case number
- WPR22FA196
- 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, coordinates, 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: 9e9ee7b6379645c4b8c4137700b8ebf101e0021a4353baeefa09b487af4e2fd0; retrieved 2026-09-15T07:45:24.316Z.