FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA300 · Cessna 172K

31 May 2010 · Wellington, KS, United States

Cessna 172K · Accident: ground handling event while standing

From Wellington Municipal Airport (EGT) to Wellington Municipal Airport (EGT)

Report a problem

Event

NTSB case
CEN10CA300
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 172K

Aircraft type
Cessna 172
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
N78612
Operator
Lind Edward
Onboard fatalities
Unknown
Route
From Wellington Municipal Airport (EGT), Wellington, KSTo Wellington Municipal Airport (EGT), Wellington, KS
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

The pilot tried to start his single-engine airplane but realized that the battery was dead and his attempt to charge the battery was unsuccessful. He then prepared to hand-prop the engine by setting the hand brake, priming the engine and turning the ignition on to both magnetos. The throttle was set to the idle position. The pilot moved the propeller and the engine started immediately; however, the hand brake could not hold the thrust of the engine and it started to accelerate. The pilot was unable to catch the airplane as it crossed the taxiways and interposed grass before it finally stopped when it collided with terrain prior to the runway. Examination of the airplane revealed that the engine and engine mounts were displaced to the right and that the lower part of the nose landing gear was sheered away.

Probable cause

The pilot's failure to properly secure the airplane while manually starting the engine with the propeller.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA300
Event ID
20100607X93442
Case number
CEN10CA300
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: 226e555d6915633db87bbaad58cfebb69d431585b93069594bfb229a00abdca4; retrieved 2026-09-15T14:23:43.791Z.