ASN Wikibase Occurrence # 160182
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: | Friday 6 September 2013 |
| Time: | 08:09 |
| Type: | Spacek SD-1 TG Minisport |
| Owner/operator: | Private |
| Registration: | N123SD |
| MSN: | USA00103 |
| Total airframe hrs: | 5 hours |
| Engine model: | Hirth F-23 LW |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | 1 mile from Spanish Fork Airport (U77), Spanish Fork, UT -
 United States of America
|
| Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
| Nature: | Test |
| Departure airport: | Spanish Fork, UT (U77) |
| Spanish Fork, UT (U77) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The owner/builder reported that the accident flight was the fourth test flight for the experimental airplane. One of the three ground crewmembers reported that, for this flight, the pilot wanted to test the airplane’s G limits, perform stalls, and conduct touch-and-go takeoffs and landings. While the pilot was flying the airplane in the traffic pattern, two of the ground crewmembers observed the airplane perform an unscheduled roll. About 1 minute later, they observed the airplane perform a second roll. One of the ground crewmembers reported that, about midway through the second roll, the pilot lost airplane control, and the ballistic parachute subsequently deployed with the airplane traveling at a high rate of speed; almost immediately after deployment, the parachute separated from the airframe. The airplane then spun toward the ground and was destroyed by impact forces.
The Pilot’s Operating Handbook (POH) contained a warning that aerobatics and intentional spins were prohibited. The POH also indicated that the minimum deployment altitude for the parachute was 210 ft and recommended that the parachute be deployed at the lowest airspeed possible and not above 150 mph; the airplane was operating at the airport’s traffic pattern altitude of about 1,000 ft above ground level when the parachute deployed. The airplane’s never-exceed speed was 131 mph; the airplane’s actual speed at the time of the parachute’s deployment could not be determined. Although the airplane was likely traveling within the speed and altitude specified for parachute deployment, the pilot was performing a prohibited roll when it deployed.
All of the parachute system’s hardware was accounted for during the postaccident examination of the system. The examination of the three parachute lines that were attached to the fuselage per the kit specifications revealed that two of the lines had been cut and that the third line exhibited overstress fractures. It is likely that the lines were severed when the parachute was deployed during the roll and that the remaining line then failed due to overload. Due to the severity of the damage and fragmentation of the airframe, it could not be determined if the pilot intentionally deployed the parachute following the loss of control during the roll maneuver or if a malfunction occurred that caused the parachute to deploy unintentionally. Once the parachute separated, the airplane was likely uncontrollable. Although postaccident toxicological tests detected chlorpheniramine, a sedating antihistamine, in the pilot’s cavity, it is unlikely that the pilot was impaired at the time of the accident.
Probable Cause: The pilot’s failure to maintain airplane control while performing prohibited aerobatic maneuvers and the deployment and separation of the ballistic parachute system from the airframe for reasons that could not be determined due to the severity of impact damage to the system.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=123SD
https://flightaware.com/photos/view/168017-46c15deda718d5ea972c68b13a8ca7fb0369ac12/aircrafttype/
Location
Media:
One fatality this morning in Spanish Fork plane crash according to @UCSO pic.twitter.com/mOZTKLskEV
— KSL_Photography (@KSL_Photography) September 6, 2013
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 06-Sep-2013 18:01 | harro | Added |
| 06-Sep-2013 19:06 | Geno | Updated [Registration, Cn, Operator, Location, Phase, Nature, Departure airport, Destination airport, Source, Embed code, Narrative] |
| 07-Sep-2013 06:07 | Anon. | Updated [Registration, Narrative] |
| 09-Sep-2013 21:54 | Geno | Updated [Registration, Source, Narrative] |
| 10-Sep-2013 06:34 | Anon. | Updated [Registration, Source, Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 09:15 | ASN Update Bot | Updated [Other fatalities, Nature, Departure airport, Destination airport, Source, Embed code, 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