FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA367 · Cirrus Design Corp SR22

25 Sept 2024 · Lakeway, TX, United States

Cirrus Design Corp SR22 · Accident: aerodynamic stall/spin on approach

From Tyler Pounds Regional Airport (TYR) to an unrecorded destination

Report a problem

Event

NTSB case
CEN24LA367
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
0 · all aircraft and ground
Ground fatalities
0
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

Cirrus Design Corp SR22

Aircraft type
Cirrus SR22
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
N565CP
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tyler Pounds Regional Airport (TYR), Tyler, TXTo not recorded
Aircraft age
Not recorded
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
  • 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

During descent to the destination airport, the pilot confirmed that the closest weather station reported the wind from 030° at 10 knots, gusting to 16 knots, so he planned to land on runway 34. While on the base leg of the traffic pattern, he extended the flaps to 100%, reduced the engine power, and slowed to 85 knots indicated airspeed (KIAS). While on final approach and after clearing a set of powerlines that were perpendicular to the runway, he made a steep approach to the runway. As the airplane was above the displaced threshold, the airspeed decreased to about 63 KIAS, entered an aerodynamic stall, and landed hard on the runway. As the airplane bounced, the pilot increased engine power to go around, then lost control, veered off the left side of the runway and impacted a tree and terrain. The airplane sustained substantial damage to the fuselage, wings, and engine mount. Postaccident examination of the runway revealed three distinct gouges where the landing gear impacted during the hard, bounced landing. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain adequate airspeed during landing, which resulted in an aerodynamic stall and loss of control during a go-around.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA367
Event ID
20240926195201
Case number
CEN24LA367
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: 9197f2597244045bd1bb7fc9462f1d5fa3c7d76dc8f6fd713f99dfcd59b7cdb6; retrieved 2026-09-16T19:19:16.016Z.