FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA18LA199 · Cessna 182 P

26 Jul 2018 · Cleveland, TN, United States

Cessna 182 P · Accident: aircraft/propeller/rotor contact with person while standing

From Cleveland Regional Jetport (RZR) to Blairsville Airport (DZJ)

Report a problem

Event

NTSB case
ERA18LA199
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
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 182 P

Aircraft type
Cessna 182
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
N1311S
Operator
Unknown
Onboard fatalities
Unknown
Route
From Cleveland Regional Jetport (RZR), Cleveland, TNTo Blairsville Airport (DZJ), Blairsville, GA
Aircraft age
About 42 years (built 1976)
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
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

  • Aircraft › Aircraft power plant

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

NTSB narrative

After completing a personal flight with his wife, the private pilot secured the engine by placing the mixture control in the idle cut-off position. Based on physical evidence observed after the accident, he likely moved the ignition switch toward the off position and removed the key. The pilot's wife indicated that, after they performed local errands and returned to the airport, the pilot was performing his preflight inspection of the airplane with the ignition key in his pocket. Although airport security video did not capture the accident sequence and the pilot's wife, who was by the airplane's right cabin door, did not see her husband move the propeller, she heard the propeller move and the engine starting or trying to start. The pilot likely slightly moved the propeller and the engine briefly started; the propeller then rotated and fatally injured the pilot. The engine did not sustain operation, and the propeller ceased rotating.

Postaccident examination of the 42-year-old ignition switch revealed that it appeared to be in the off position when observed visually from the pilot's seat, but its actual selected position was more toward the right magneto position. The switch and key were determined to be slightly misaligned with the instrument panel placard markings. On- and off-airframe operational testing of the ignition switch in the as-found position revealed the right magneto was hot, or not grounded. In addition, examination of the cut surfaces of the key notches revealed relatively smooth and reflective surface features consistent with a worn surface on the flank of the notch adjacent to the key retention ridge and on the tip end of the shank opposite the notched side. Examination of the key cylinder revealed an area with a smooth and reflective surface consistent with wear on the lower side of the key slot. The location and shape of the worn area was consistent with wear contact with the tip of the key as it was inserted and removed. The key could be removed from the switch in any of the five positions due to the wear of the switch's internal components, contrary to its intended function that would retain the key in any position except the off position. Although the switch manufacturer tested all new switches to ensure this functionality when new, that test is not specified to be performed at any time as part of any inspection or checklist by the switch manufacturer, airframe manufacturer, or Title 14 Code of Federal Regulations Part 43 Appendix D.

Although the mechanic who performed the last annual inspection reported the key-to-switch integrity was satisfactory with no discrepancies, the worn condition of the ignition switch likely existed at the time of the annual inspection, which was about 31 flight hours before the accident flight (excluding the pilot's previous flight the day of the accident). Additionally, during the annual inspection when the mechanic installed the ignition switch after repairs, he failed to properly align the switch positions with the marks on the instrument panel placard.

Probable cause

The undetected wear of the ignition switch and key, which allowed removal of the key from an intermediate position and subsequently led to an unintended engine start-up. Contributing to the undetected wear of the 42-year-old ignition switch was the lack of guidance by the switch manufacturer and airframe manufacturer for procedures to detect lack of integrity between the ignition key and switch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA18LA199
Event ID
20180726X90912
Case number
ERA18LA199
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, 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: d1ee43e1a66aecc1ff0d683beb737a13b473c8b44ddae57fc846f6634848d9a6; retrieved 2026-09-15T06:44:57.286Z.