18 Sep 2008: CESSNA AIRCRAFT CO E162 — Cessna Aircraft Company

18 Sep 2008: CESSNA AIRCRAFT CO E162 (N162XP) — Cessna Aircraft Company

No fatalities • Douglas, KS, United States

Probable cause

The airplane's inability to recover from an intentional spin, despite proper control inputs by the flight test pilot. Contributing to the accident was the failure of the airplane's ballistic parachute system to properly deploy.

— NTSB Determination

Accident narrative

On September 18, 2008, approximately 1145 central daylight time, a single-engine Cessna 162, Skycatcher experimental airplane, N162XP, was destroyed when it impacted terrain during an uncontrolled descent after the pilot parachuted from the airplane near Augusta, Kansas. The airplane was registered to and was operated by Cessna Aircraft Company. The commercial pilot, the sole occupant of the airplane, was not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the 14 Code of Federal Regulations Part 91 test flight.

The flight originated at approximately 1100, to obtain an assessment of the aircraft's spin characteristics. Sixteen spins; with the aircraft in four different configurations were planned. The aircraft had successfully completed the first configuration with a set of four spins. The pilot then completed three of the four spins in the second set of spin testing. With the aircraft at 10,000 feet, the pilot initiated a spin to the left. Once the spin was established, the pilot made the planned control inputs. The airplane failed to recover from the spin. Despite several attempts by the test pilot to recover the aircraft from the maneuver, the aircraft continued with to spin. At the planned altitude of 6,000 feet the pilot elected to deploy the aircraft's recovery parachute and pulled the chute's activation handle. The aircraft's parachute did not deploy, and the aircraft continued to spin. The pilot then elected to, jettison the cabin door, exit the airplane, and deploy his parachute.

The airplane impacted the ground in a wooded area. The airplane wreckage was retrieved and secured for further evaluation. There were no reported ground injuries.

An examination of the aircraft was conducted on September 24, 2008, at the Cessna Aircraft Company facility in Wichita, Kansas, under the supervision of the NTSB and FAA. Technical representatives from the engine, parachute, and aircraft manufacturers were present.

The airplane was destroyed upon impact with the ground. Control continuity was established to the respective flight controls. An initial examination of the aircraft's parachute system revealed that the rocket system used to deploy the chute had activated, however; the parachute failed to be pulled from its canister.

In order to measure the force required to pull the parachute from its canister, the packed parachute assembly was tested at BRS, Inc. facilities. The parachute required approximately 50-lbs (of pull force) to extract the parachute from its container. The manufacturer reported a 50-lb pull, could be considered to be near the upper limit for this particular system.

The BRS parachute is equipped with an incremental cord that is used to pull the parachute out of the container. On one end of the incremental cord are four Kevlar straps which are sewn on the parachute bag; the other end of the incremental cord is attached to a steel cable that is looped around a steel collar assembly. The steel collar is then placed over the rocket. The incremental cord has a series of "Bar tabs" (stitching that tears apart at a predetermined load) that attenuates the shock load on the parachute. The parachute would normally be pulled from the canister, before the entire series of "Bar tabs" are separated. The accident parachute's incremental cord was found "undamaged", but the entire series of "Bar tabs" were torn; an indication that the rocket motor pulled with its full force. The steel cable end had separated during the rocket activation; the cable displayed signs consistent with ductile overload and shear type separation. A section of the failed cable was tested in the Cessna Laboratory; and it was determined that the cable met specifications.

The four Kevlar straps were numbered and indexed to their position relative to the canister. Three of the four straps appeared typical; the fourth strap (labeled #3) displayed two signatures: tightening of the weave, resulting in a "deformation set" in the strap. The second signature was that some of the stitching securing the #3 strap to the horizontal parachute bag strap had separated. The marks are consistent with a large tension load applied to the #3 strap. During parachute installation the #3 strap was positioned towards the left-rear quarter of the airplane.

The steel cable had a Nicopress sleeve and thimble eye attachment. The sleeve and thimble assembly displayed two areas of impact damage. The soft copper sleeve displayed signature consistent with cable contact; a steel thimble eye displayed an area of impact damage and was bent to one side, distorting the eye.

An inspection of the airplane's right flap cable swage, revealed two contact areas that consisted of a "light" gouge, and scratch marks. Signatures observed on the BRS system and aircraft components were consistent with an incremental cable contacting the right flap cable/turn buckle cable during the rocket launch sequence, compromising the parachute's deployment.

A video of the incident was recorded by a chase airplane; a review of the video indicates that the angle between the rocket trajectory and the parachute canister may have been too severe to allow for proper extraction of the parachute assembly.

During flight testing and the subsequent review of test data, it was discovered that an unrecoverable spin could develop. The accident airplane was a preliminary configuration and the manufacturer abandoned the configuration for production airplanes.

Contributing factors

  • cause Attain/maintain not possible
  • factor Parachute — Failure

Conditions

Weather
VMC, 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.