FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA093 · Cirrus SR22

6 Dec 2012 · Eden Prairie, MN, United States

Glick Farms Cirrus SR22 · Accident: ground handling event while standing

From Flying Cloud Airport (KFCM) to Minot International Airport (KMOT)

Report a problem

Event

NTSB case
CEN13CA093
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
N8161M
Operator
Glick Farms
Onboard fatalities
Unknown
Route
From Flying Cloud Airport (KFCM), Eden Prairie, MNTo Minot International Airport (KMOT), Minot, ND
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
Standing · engine(s) start-up
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
Ground handling event
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 handling/service
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

When the pilot attempted to start the engine, the starter motor turned, but the starter did not engage. The pilot said he turned off the battery master switch, exited the airplane, and walked around to the front of the airplane. He reached through the door and thought the ignition key was off. He pushed the propeller down through one compression stroke. The engine immediately started. The pilot jumped on the left wing, but fell off. The airplane traveled across the ramp and struck a ditch between runways 28R and 28L, breaking off the nose gear and buckling the firewall. Postaccident examination disclosed the ignition switch functioned normally.

Probable cause

The pilot's failure to ensure the airplane was secured prior to attempting an engine start by handpropping.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA093
Event ID
20121210X34552
Case number
CEN13CA093
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: f529cb7d81107343409c6a8355263e83c78d2d7b74c1f444ed1b9935cc5781b2; retrieved 2026-09-15T20:33:02.390Z.