ERA26LA044 · Cirrus Design Corp SR22
Cirrus Design Corp SR22 · Accident: loss of control in flight on approach
From St George Island Airport (F47) to Apalachicola Regional Airport (AAF)
Event
- NTSB case
- ERA26LA044
- 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
- N508WH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From St George Island Airport (F47), Eastpoint, FLTo Apalachicola Regional Airport (AAF), Apalachicola, FL
- Aircraft age
- About 7 years (built 2018)
- 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 go-around
- 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
- Loss of control in flight
- 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
The purpose of the flight was to conduct practice instrument approaches at the departure airport before continuing to a nearby airport. The pilot reported that the glideslope for the practice approach appeared steeper than expected. During the approach, the pilot slowed the airplane, but became too slow, and attempted to accelerate to a normal approach airspeed. He noticed a gain in altitude and decided to abort the approach and initiated a go-around. During the go-around, the airplane pitched up and entered an aerodynamic stall. Due to the proximity to the ground, the pilot “pulled up” on the controls. The airplane then banked left, descended, and impacted terrain, which resulted in substantial damage to the empennage and fuselage. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot’s loss of airplane control during a go-around, which resulted in an aerodynamic stall. Contributing to the accident was the pilot’s improper recovery from an aerodynamic stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA26LA044
- Event ID
- 20251118202020
- Case number
- ERA26LA044
- 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: af26e829455334a84a5d7c836ff490a7ce3b49312e0f46212cf172cd92f99dbd; retrieved 2026-09-16T20:33:09.926Z.