CEN09FA363 · Cirrus Design Corporation SR22
Cirrus Design Corporation SR22 · Accident: loss of control in flight on approach
From Charles B. Wheeler Downtown Airport (MKC) to Crystal Airport (MIC)
Event
- NTSB case
- CEN09FA363
- 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
- 1 · 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 Corporation 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
- N214BN
- Operator
- Steven K. Case · private individual
- Onboard fatalities
- Unknown
- Route
- From Charles B. Wheeler Downtown Airport (MKC), Kansas City, MOTo Crystal Airport (MIC), Crystal, 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
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The pilot reported having the runway in sight during the night landing. The tower controller reported that it appeared the airplane touched down on the runway after which time they closed and departed the tower. A witness, who was exiting a building on the south side of the airport when the accident occurred,reported that he heard the airplane and that the engine was very loud. He then heard the engine power increase as if the pilot was performing a “go-around.” He stated that he heard the impact and looked toward runway 14L where he saw the airplane engulfed in flames. The witness stated there was “moderate to heavy” rain at the time of the accident. Another witness reported that the airplane turned onto its right side and stalled. The airplane was destroyed by impact and a post impact fire. Inspection of the airplane and engine failed to reveal any pre-impact failure/malfunction. The pilot began the cross country flight about 10 hours and 30 minutes prior to the accident, and had flown about 7 hours and 17 minutes during that time.
Probable cause
The pilot's failure to maintain airspeed which resulted in a loss of aircraft control during a go-around. Factors associated with the accident were the dark night lighting conditions, moderate to heavy rain, and fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09FA363
- Event ID
- 20090617X05239
- Case number
- CEN09FA363
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-06-17.
- API snapshot SHA-256: 4a5ca638584171c621879ae89941c06cf247c840275ee788ba271533f4532117; retrieved 2026-09-13T20:16:52.653Z.