CHI08FA039 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: loss of control in flight on approach
From Aberdeen Regional Airport (ABR) to Faribault Municipal Airport-Liz Wall Strohfus Field (FBL)
Event
- NTSB case
- CHI08FA039
- 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
- 4 · 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
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
- N482SR
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aberdeen Regional Airport (ABR), Aberdeen, SDTo Faribault Municipal Airport-Liz Wall Strohfus Field (FBL), Faribault, MN
- 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 go-around
- First occurrenceThe 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- 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
- Destroyed
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall/spin, encountered
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane's recorded airspeed indicated that the airplane slowed on final approach and subsequently encountered a recorded stall/spin condition during go-around from runway 12. A post impact ground fire and explosion occurred. The recorded winds at the airport were 190 degrees at 15 knots, gusting to 22 knots. On-scene and follow-up examinations of the wreckage and recorded data from the airplane's recoverable data module revealed no airplane or engine pre-impact anomalies. The maximum demonstrated crosswind component for the aircraft was 20 knots. Subsequent to the accident a remark was entered to the airport's master record. The remark advised pilots landing on runway 12 to be alert for turbulence and possible windshear when winds are out of the south.
Probable cause
The pilot not maintaining adequate airspeed for the gusty crosswind conditions and the stall/spin encountered during the go-around. Contributing to the accident were the crosswinds and wind gusts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08FA039
- Event ID
- 20071130X01880
- Case number
- CHI08FA039
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 81a779f1004a9c0d164608ad65075ba010d56cde06ff5856d4279b8164d3c491; retrieved 2026-09-20T16:05:53.049Z.