FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN09CA469 · Piper PA-25-235

23 Jul 2009 · Miller, MO, United States

Plane Cents Aviation Piper PA-25-235 · Accident: ground handling event while standing

From Miller, MO (private airstrip) to Miller, MO (private airstrip)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN09CA469
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

Piper PA-25-235

Aircraft type
Piper PA-25
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
N6689Z
Onboard fatalities
Unknown
Route
From Miller, MO (private airstrip)To Miller, MO (private airstrip)
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 137: Agricultural
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
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
None

Cause areas

  • Aircraft › Aircraft handling/service
  • Organizational issues › Support/oversight/monitoring
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The aerial application airplane completed its last flight for the day and was parked with the engine running for cooling purposes before it was shut down. A ground support person, who was an aircraft loader, assisted in the cleaning of the airplane with the engine running. The loader began rinsing underneath the airplane and progressed inwards toward the wing root. The loader received serious injuries when he stood up and was stuck three times by the rotating propeller.

Probable cause

The failure of the operator to shut down aircraft while conducting servicing which resulted in a ground person being struck by the rotating aircraft propeller.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN09CA469
Event ID
20090728X52636
Case number
CEN09CA469
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, damage. 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: 630cb2994cf046f225b0316349902d1567ed7135a55fd4311e85b5a9822799b2; retrieved 2026-09-15T12:02:56.897Z.