FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14CA501 · Cirrus Design Corp SR22

16 Sept 2014 · Longville, MN, United States

Cirrus Design Corp SR22 · Accident: loss of control on ground during landing

From Denison Municipal Airport (DNS) to Longville Municipal Airport (XVG)

Report a problem

Event

NTSB case
CEN14CA501
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
N6081K
Operator
Unknown
Onboard fatalities
Unknown
Route
From Denison Municipal Airport (DNS), Denison, IATo Longville Municipal Airport (XVG), Longville, MN
Aircraft age
About 11 years (built 2003)
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 · aborted after touchdown
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 on ground
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During landing, the main landing gear touched down to the right of the runway centerline. The airplane bounced twice on the runway and began to veer left. The left wing dragged through the grass on the left side of the runway and the airplane continued into a drainage ditch. The airplane came to rest upright after it impacted the ditch; a postimpact fire ensued and consumed most of the fuselage. The wings and empennage sustained some fire damage and were mostly intact. Federal Aviation Administration inspectors and a Cirrus investigator provided on-scene assistance to ensure that the Cirrus Airframe Parachute System (CAPS) rocket motor was safely disarmed. The pilot stated that after the airplane bounced on the runway, he attempted to go around but the airplane did not respond to his aileron control inputs; he then lost control of the airplane.

Probable cause

The pilot's loss of control during an attempted go-around following a multiple bounce landing

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14CA501
Event ID
20140918X74534
Case number
CEN14CA501
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. 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: 9184e66f1d8f276c171e45a8a8179949ba4163855528695a8cd0a407bb3e81f3; retrieved 2026-09-16T01:46:22.610Z.