14 Oct 2016: CESSNA 208 A

14 Oct 2016: CESSNA 208 A (N208KM) — Unknown operator

1 fatality • Dunnellon, FL, United States

Probable cause

The jumpmaster's failure to guard the reserve parachute ripcord, which caused an inadvertent deployment of his reserve parachute.

— NTSB Determination

Accident narrative

On October 14, 2016, about 1735 eastern daylight time, a Cessna 208, N208KM, was substantially damaged during a skydiving event over Marion County Airport (X35), Dunnellon, Florida. One of the 10 skydivers on board was fatally injured, and the commercial pilot and the other 9 skydivers were not injured. The airplane was registered to a private individual and operated by the National Parachute Test Center, Inc., (NPTC) under the provisions of Title 14 Code of Federal Regulations Part 91 as a commercial skydiving flight. Visual meteorological conditions prevailed, and no flight plan was filed for the local flight, which departed X35 about 1700.According to a report prepared by NPTC, in addition to the pilot, there were 8 jumpers, a jumpmaster, and a training advisor assigned to the flight. Before boarding the airplane, the training advisor, who was a skydiving instructor familiar with the airplane, instructed the jumpmaster on the procedure used to make static line jumps from the Cessna 208. Upon boarding the airplane, the jumpmaster elected not to hook up the static line of his main parachute. When questioned by the training advisor, the jumpmaster replied, "I am not going to jump, so I do not have to."

The flight departed and climbed to an altitude of 1,250 ft above ground level. According to the NPTC report, the first three skydivers exited the airplane uneventfully, and the fourth moved into position. The training advisor observed that the fourth skydiver seemed to hesitate, and the jumpmaster leaned forward toward him. As the fourth jumper exited the airplane, the training advisor noticed a flash of white and watched as the jumpmaster's reserve parachute deployed and entered the airplane's slipstream. The jumpmaster attempted to pull the parachute back into the airplane and was pulled into the door frame before being dragged out of the airplane. Observers on the ground watched as the jumpmaster descended beneath his streaming (unopened) reserve parachute to the ground. The ground observers reported that the jumpmaster made no movements, appeared to be unconscious, and did not deploy his main parachute. The pilot reported that he was able to maintain control of the airplane and land without further incident.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed that the cargo door frame and fuselage were buckled. Inspection of the jumpmaster's main parachute by an FAA-certificated senior parachute rigger revealed that it was intact and remained in the deployment bag. Examination of the reserve parachute revealed that the injector spring was wrapped around the suspension lines. The deployment ring, connector snap, and part of the spreader bar were located midway up the suspension lines. The jump inspection booklet located on the parachute indicated that the reserve parachute was inspected 3 days before the accident. NPTC attributed the damage to the reserve parachute to impact with the door frame as the jumpmaster was pulled from the airplane.

The FAA inspector who examined the airplane reported that the jumpmaster was using a military-style parachute with the reserve parachute positioned below the chest. According to the FAA inspector, "the reason the reserve parachute deployed is unclear at this time but since the D ring [ripcord handle] is exposed on the front of the parachute speculation is that the D ring may have accidently caught or snagged on another jumper or something in the aircraft." According to NPTC, the accident resulted from the jumpmaster's "failure to guard his Reserve Ripcord Handle" and "was compounded by [his] failure to exit the aircraft immediately" when his reserve parachute deployed.

Contributing factors

  • cause Passenger

Conditions

Weather
VMC, wind 050/06kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.