ERA13LA433 · Enstrom F-28C
Heritage Rotors Enstrom F-28C · Accident: aircraft/propeller/rotor contact with person while standing
From Bloomsburg, PA to Bloomsburg, PA
Event
- NTSB case
- ERA13LA433
- 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
Enstrom F-28C
- Aircraft type
- Enstrom F-28
- Category
- Helicopter
- 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
- N631DP
- Operator
- Heritage Rotors
- Onboard fatalities
- Unknown
- Route
- From Bloomsburg, PATo Bloomsburg, PA
- Aircraft age
- About 33 years (built 1980)
- 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
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot/owner had just taken control of the helicopter from another pilot. As the relieved pilot was walking away from the helicopter and between the 10- and 11-o'clock position forward of the helicopter, he came into contact with a rotating main rotor blade. The pilot/owner stated that, when exiting the helicopter, it was the company's practice to disengage the rotor drive system and secure the collective control. In this condition, the rotor blades droop below the normal height, and the drooping is most pronounced in the 9- to 12-o'clock position of the rotor disk. According to the helicopter manufacturer representative, the main rotor height can vary depending on how the helicopter landing gear was serviced. In addition, depending on the position of the cyclic, the main rotor can descend lower than 6 feet when the main rotor is operating. It is likely that the pilot/owner unintentionally moved the cyclic, which resulted in the rotor blade descending, and, in combination with the rotor droop, the main rotor blade would have been low enough to strike the relieved pilot's head.
Probable cause
The relieved pilot’s failure to maintain clearance from the rotating main rotor blades after he exited the helicopter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA433
- Event ID
- 20130928X12809
- Case number
- ERA13LA433
- 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: dd5ee50c4631f56d78f36a62beb36005c20d58c7d08c57165dbf7f704a7eaca0; retrieved 2026-09-13T18:01:09.054Z.