FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA272 · de Havilland DHC 6 200

1 Jun 2014 · Middletown, OH, United States

Win Win Aviation de Havilland DHC 6 200 · Accident: aircraft/propeller/rotor contact with person while standing

From Middletown Regional Airport (MWO) to Middletown Regional Airport (MWO)

Report a problem

Event

NTSB case
CEN14LA272
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
1 · all aircraft and ground
Ground fatalities
1
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

de Havilland DHC 6 200

Aircraft type
de Havilland DHC-6
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
N223AL
Onboard fatalities
Unknown
Route
From Middletown Regional Airport (MWO), Middletown, OHTo Middletown Regional Airport (MWO), Middletown, OH
Aircraft age
About 45 years (built 1969)
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
Minor

Cause areas

  • Personnel issues › Psychological

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

NTSB narrative

The skydiving airplane was on a ramp with its engines operating while the pilot waited for passengers to board. The pilot asked an employee of the skydiving operator if he could order something to eat for lunch. The employee responded that she had time to come see the pilot at the airplane because she was expecting a small delay before the next flight. The pilot thought the delay was not long enough to justify shutting down the engines. The pilot observed the employee exit the manifest office and run toward the airplane. The skydiving operator typically flew single-engine airplanes with the propeller located in front of the cockpit; however, the accident airplane was a twin-engine airplane with its propellers located under each wing. The operator's employee subsequently walked into the operating propeller under the airplane's left wing, sustaining fatal injuries.

Probable cause

The skydiving operator employee’s failure to see and avoid the rotating propeller blades when she walked toward the cockpit while the airplane’s engines were running.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA272
Event ID
20140603X24039
Case number
CEN14LA272
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: ef1760a9e9ff44a86797eef1353dbab58ebebe42f3776da9f5f17476c807e607; retrieved 2026-09-13T18:01:18.453Z.