WPR23FA173 · Beech A36
Beech A36 · Accident: aerodynamic stall/spin on approach
From Corona Municipal Airport (AJO) to an unrecorded destination
Event
- NTSB case
- WPR23FA173
- 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
- 3 · 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 A36
- Aircraft type
- Beechcraft 36
- 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
- N2038Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Corona Municipal Airport (AJO), Corona, CATo not recorded
- Aircraft age
- About 44 years (built 1979)
- 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 final
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Nearing the end of a cross-country flight, the pilot entered the airport traffic pattern for a landing at an airport that was surrounded on all quadrants by mountainous terrain. ADS-B data showed the pilot overshot the extended runway centerline when turning onto final approach. On short final the airplane’s airspeed decreased, and surveillance video footage revealed that the airplane’s right wing dropped, followed by a right roll and rapid descent. Subsequent video footage showed the airplane momentarily entered a level attitude, followed by the right wing dropping again. The airplane then entered a roll to the right and a rapid uncontrolled descent until it impacted the ground. The airport’s automated weather observation system (AWOS) indicated that visual meteorological conditions (VMC) prevailed over the accident site, with unrestricted visibility and clear skies. The calculated density altitude at the time of the accident was about 8,200 ft. Weather data revealed thermodynamic and wind profiles that supported mountain wave activity, including updrafts and downdrafts near the accident site. Forecasting models indicated a hydraulic jump across the area at the time of the accident, which implied strong vertical motions that would likely have produced variations in the airplane’s airspeed and the potential for severe to extreme turbulence. A review of the airplane’s performance using ADS-B data and the environmental conditions, including the strong southerly wind at the time of the accident, determined that after the pilot overshot the final approach, he initiated a 20° left turn to rejoin the final approach track. Based on ADS-B heading, altitude, and airspeed data, the increased load factor of the pilot’s right-wing aileron deflection and low airspeed likely exceeded the right wing’s critical angle of attack. The National Weather Service (NWS) issued an urgent weather advisory about 1300, about 30 minutes before the accident flight departed. The urgent advisory identified that the accident site area was expected to encounter wind from the southwest at 25 to 35 mph with gusts to 60 mph. Additionally, the NWS issued a G-AIRMET valid for occasional moderate turbulence below 16,000 ft over the accident site, and advisories for mountain obscuration and strong surface winds immediately bordering the accident site.
A search of the FAA-contracted Automated Flight Service Station provider’s records indicated no contact from the pilot for any weather briefing information on the day of the accident. A separate search of ForeFlight weather products indicated that the pilot did not have an account, and no weather briefings or flight plans were filed for the accident airplane on the day of the accident. It is unknown what weather information, if any, the pilot checked or received before or during the accident flight.
Probable cause
The pilot’s exceedance of the airplane’s critical angle of attack and failure to maintain adequate airspeed on short final while operating in adverse wind conditions, which resulted in an aerodynamic stall and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23FA173
- Event ID
- 20230501107201
- Case number
- WPR23FA173
- 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: 119aaee42923446dc4012d8384f25603b71a303d16846188121e9fce64b56073; retrieved 2026-09-15T07:59:22.405Z.