FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23LA022 · Cessna 172S

16 Oct 2022 · Statesboro, GA, United States

American Aviation Cessna 172S · Accident: aircraft/propeller/rotor contact with person while standing

From Savannah Hilton Head International Airport (SAV) to Statesboro Bulloch County Airport (TBR)

Report a problem

Event

NTSB case
ERA23LA022
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 172S

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
N2476Y
Onboard fatalities
Unknown
Route
From Savannah Hilton Head International Airport (SAV), Savannah, GATo Statesboro Bulloch County Airport (TBR), Statesboro, GA
Aircraft age
About 17 years (built 2005)
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
None

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

After the pilot and the pilot-rated passenger taxied to the ramp after landing, their two passengers (who were seated in the rear of the airplane) exited the airplane and were rushing to get to a waiting ride. The first passenger exited toward the engine (forward), while the second passenger exited toward the tail of the airplane. The pilot stated that he was busy following the checklist to turn off the airplane and the two passengers exited without him knowing. The power was at idle, and before he could shut off the mixture control, the first passenger was struck by the propeller. According to the pilot-rated passenger, while the pilot was trying to shut down the engine, the passengers exited the airplane, and the first passenger ran into the propeller. According to the surviving passenger, she exited the left side of the airplane, and the first passenger exited the right side of the airplane. No instructions were given to them as they exited. She could hear that the propeller was turning as she walked away from the airplane to get into her ride. Although the pilot stated that the passengers exited without him knowing, the airplane had seats for only 4 occupants. Review of the airplane manufacturer’s published guidance indicated that entry and exit from the airplane was accomplished through either of two entry doors, one on each side of the cabin at the front seat positions; the door handles used to open the doors were located on the forward part of the armrests for the front seats. Unlike an automotive type of door handle, they had to be rotated from a “LOCK” position, past a “CLOSE” position, and then aft to a “OPEN” position, so that the door could be pushed open to be able to exit the airplane. Review of photographs also indicated that the mounting positions of both the left and right door handles were located about 3 feet forward of the rear seating position, in close proximity to each of the pilots, and were not accessible to the rear seat passengers unless the passengers reached around the front seats, which the pilots were occupying at the time. No checklist or amplified procedure for the conduct of normal operation was discovered that required the opening of the airplane’s doors before engine shutdown. The manufacturer’s and Federal Aviation Administration guidance also indicated that stopping the engine was the most effective way to ensure the passengers arrived and departed the vicinity of an airplane safely. No medications were found during toxicological testing of the fatally injured passenger that would have contributed to the accident. The pilot and pilot-rated passenger likely unlatched and opened the doors before shutting the engine down and disembarked the passengers without instructions for deplaning.

Probable cause

The pilot’s failure to include deplaning procedures as part of a passenger safety briefing and failure to have the passengers remain onboard until the engine was shut down, which resulted in a passenger subsequently being struck by the rotating propeller.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23LA022
Event ID
20221017106133
Case number
ERA23LA022
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: local date, investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2022-10-17.
  • API snapshot SHA-256: 98bdb591e4ed9b4f71601fdb578c6d3a3a53062663eba855e448a0be57e5cc59; retrieved 2026-09-15T07:52:52.687Z.