NYC02LA199 · Cessna 208B
Boston-Providence Skydiving Center Cessna 208B · Accident: propeller/rotor contact to person while standing
From North Central State Airport (SFZ) to North Central State Airport (SFZ)
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
- NYC02LA199
- 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
Cessna 208B
- Aircraft type
- Cessna 208
- 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
- N9347B
- Onboard fatalities
- Unknown
- Route
- From North Central State Airport (SFZ), Pawtucket, RITo North Central State Airport (SFZ)
- 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 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
- First occurrenceThe 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
- Propeller/rotor contact to 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
- Other person › Proper touchdown point, not obtained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
After a parachute drop flight, the airplane taxied back to the ramp area. The airplane was parked on the ramp, with the engine running, while the next group of parachutists were boarding the airplane. During that time, a parachutist who had just landed, contacted the propeller and sustained a serious injury. Witnesses reported observing the parachutist descending toward the airplane without altering her course. One witness reported he "tackled" the parachutist to the ground; however, the parachute became entangled in the airplane's propeller and subsequently dragged the parachutist into the propeller. The parachutist had completed an estimated 18 prior jumps, which included 4 jumps at the accident airport. Winds reported at the airport, about the time of the accident were calm.
Probable cause
The parachutist's failure to obtain the proper touchdown point, which resulted in contact with the operating propeller of a parked airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC02LA199
- Event ID
- 20021002X05256
- Case number
- NYC02LA199
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: d95a44ae8edfe516390ea0534b3cab176c7ffde3740a5e22f2ca1e76ae8e8d45; retrieved 2026-09-21T09:34:16.932Z.