FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA046 · Cirrus SR22

23 Oct 2016 · Kirksville, MO, United States

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

From Kirksville Regional Airport (IRK) to Kirksville Regional Airport (IRK)

Report a problem

Event

NTSB case
GAA17CA046
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 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
N528HB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kirksville Regional Airport (IRK), Kirksville, MOTo Kirksville Regional Airport (IRK), Kirksville, MO
Aircraft age
Built the same year (2016)
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
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
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • 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 recently certificated pilot reported that, during the initial climb, he heard a whistling noise and noticed that the passenger door was not secured. Subsequently, he returned to the departure airport to secure the door.

He added that, during the landing flare, he believed that the wind decreased significantly, which resulted in him having "too much right rudder engaged." The airplane touched down 30° relative to the runway centerline, veered off the runway to the right, and the nose gear collapsed.

The airplane sustained substantial damage to the firewall.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s improper compensation for changing wind during the landing flare, which resulted in an off-centered landing and a subsequent loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA046
Event ID
20161025X01520
Case number
GAA17CA046
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: 7335d8965d212ff226016d8a6b9c0da8378e3f0a9c929837ec93f528da36f5d1; retrieved 2026-09-16T04:46:26.589Z.