ASN Wikibase Occurrence # 135311
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Wednesday 27 August 2003 |
| Time: | 10:45 |
| Type: |  Lancair LC41-550FG Columbia 400 |
| Owner/operator: | The Lancair Company |
| Registration: | N166PD |
| MSN: | 41001 |
| Total airframe hrs: | 91 hours |
| Engine model: | Continental TSIOF-550C1B |
| Fatalities: | Fatalities: 0 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Bend, OR -
 United States of America
|
| Phase: | En route |
| Nature: | Test |
| Departure airport: | Bend, OR (S07) |
| Bend, OR (S07) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The pilot, who had been conducting a series of spin entry and recovery tests, had intentionally entered a spin while applying left rudder and left aft stick. Because his flight control inputs did not result in recovery from the spin after three and one-half turns, he deployed the spin recovery/stabilization drogue parachute. Once the aircraft was established in an attitude from which the pilot could maintain controlled flight once the parachute was released, he pulled the drogue chute manual jettison handle. At that point, because the chute did not release, the pilot activated the electrical backup jettison system. When that action did not release the parachute, the pilot tried the electrical system a second time, and finding that this action did not release the chute, he tried the manual release a second time. At that point, because the parachute still remained attached, the pilot applied engine power in an attempt to establish controlled flight with the parachute in trail. Once he determined that the aircraft could not be satisfactorily flown in that configuration, he exited the aircraft and deployed his emergency parachute. During the investigation it was determined that the drogue chute either became entangled in the drogue chute tail boom after release from the tow hook mechanism, or it did not release from the tow hook mechanism when the pilot tried to activate it, but instead was released by the forces created by the impact with the terrain. It was also determined that the chute release system was not flight-load tested on this specific aircraft prior to the in-flight activation. Furthermore it was determined that the backup electrically activated cable guillotine system was wired incorrectly, and could not have been activated by the pilot in flight.
Probable Cause: The inadequate design of the drogue chute mechanical jettison system, which resulted in its failure to separate from the aircraft during in-flight spin recovery tests, and the incorrectly wired drogue chute cable cutter activation unit, which resulted in the inability of the pilot to activate the backup chute separation system after any failure of the primary system.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20030903X01449&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 21-Dec-2016 19:26 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 08-Dec-2017 19:10 | ASN Update Bot | Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation