CHI05LA223 · Cirrus Design Corp. SR20
Cirrus Design Corp. SR20 · Accident: hard landing
From Flying Cloud Airport (FCM) to Brainerd Lakes Regional Airport (BRD)
Event
- NTSB case
- CHI05LA223
- 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. SR20
- Aircraft type
- Cirrus SR20
- 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
- N795WW
- Operator
- Robert B. Whitmore · private individual
- Onboard fatalities
- Unknown
- Route
- From Flying Cloud Airport (FCM), Minneapolis, MNTo Brainerd Lakes Regional Airport (BRD), Brainerd, 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Pilot in command › Flare, inadequate
- Pilot in command › Go-around, delayed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane received substantial damage on impact with terrain during a bounced landing and excursion from runway 30, from which the pilot attempted a go-around. The pilot stated that while over the runway numbers, the airplane experienced a hard landing, which caused the airplane to porpoise and bounce upward. When the airplane settled onto the runway, it appeared to him that the airplane moved off the west side of runway 30 and the left tire and nose wheel may have contacted the grass area adjacent to the runway. He "immediately" applied power in order to attempt a go-around. When he initiated the go-around, the airplane "immediately" veered into the grass and did not gain altitude. The airplane came to rest south of the intersection of runway 12/30 and runway 5/23.
Probable cause
The delayed go-around and inadequate flare by the pilot during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI05LA223
- Event ID
- 20050815X01246
- Case number
- CHI05LA223
- 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, 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: ddd8585afdfcf22d8be58f7bb2d41cd3bfee2062b7b47e8eb7c5c41f903364bf; retrieved 2026-09-22T05:30:13.510Z.