LAX08CA189 · Cirrus Design Corp. SR22
Cirrus Design Corp. SR22 · Accident: loss of control in flight on approach
From Sioux Falls Regional Airport (FSD) to Laramie Regional Airport (LAR)
Event
- NTSB case
- LAX08CA189
- 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
- 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
- N877CM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sioux Falls Regional Airport (FSD), Sioux Falls, SDTo Laramie Regional Airport (LAR), Laramie, WY
- 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
- 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 pilot performed a normal landing approach and said he flew over the numbers at his normal airspeed of 77 knots. The airplane floated as the pilot began the flare, and he noticed that the ground speed was very fast. He continued the flare and realized that the airplane was about 10 to 15 feet above the runway when the stall warning horn sounded. The pilot applied full power and right rudder to perform a go-around, but the airplane did not climb as expected and drifted to the left. He also added right aileron control inputs to maintain airplane control, but the airplane continued to descend, and the left wing touched the ground and hit a taxiway light. The airplane veered off the runway and impacted the ground before coming to rest upright. The winds at the time were from 220 degrees at 6 knots.
Probable cause
The pilot's failure to attain and maintain an adequate airspeed during a go around, that resulted in a stall/mush. Contributing to the accident was the tailwind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA189
- Event ID
- 20080714X01041
- Case number
- LAX08CA189
- 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. 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: abfc5dab204932d664b794b4edb0ce7afee75b8d89927186bcedaf6292ff9b50; retrieved 2026-09-15T09:54:22.104Z.