CEN17CA116 · Cessna 162
Toadsuck Sport Aviation Cessna 162 · Accident: aircraft/propeller/rotor contact with person while standing
From Conway Regional Airport (KCXW) to Conway Regional Airport (KCXW)
Event
- NTSB case
- CEN17CA116
- 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
Cessna 162
- Aircraft type
- Cessna 162
- 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
- N3028G
- Operator
- Toadsuck Sport Aviation
- Onboard fatalities
- Unknown
- Route
- From Conway Regional Airport (KCXW), Conway, ARTo Conway Regional Airport (KCXW), Conway, AR
- Aircraft age
- About 6 years (built 2011)
- 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
- Standing · engine(s) operating
- 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
- Aircraft/propeller/rotor contact with person
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Psychological
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 was conducting a local personal flight. The pilot said he developed "unnecessary anxiety" and hurried his landing due to approaching traffic. He failed to brake aggressively and, as a result, was unable to turn in time to exit the runway. The airplane rolled off the taxiway and became bogged down in the wet grass from a previous rain. Instead of shutting the engine off, the pilot closed the throttle to idle, exited the airplane, and tried to push the airplane with the left strut. "Without thinking," the pilot walked toward the nosewheel to inspect the airplane and walked into the rotating propeller.
Probable cause
The pilot's failure to shut down the engine before exiting the airplane and his failure to focus his attention on the task at hand, which led to his walking into a rotating propeller.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17CA116
- Event ID
- 20170306X05343
- Case number
- CEN17CA116
- 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, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-03-04.
- API snapshot SHA-256: 794bc5871b84a94022e6f408fa9c12d82bfe694492c402c00f495c8e485249eb; retrieved 2026-09-16T05:04:05.022Z.