WPR13FA399 · Tyler Ives SD-1 TG
Tyler Ives SD-1 TG · Accident: abrupt maneuver while maneuvering
From U77 · Spanish Fork, UT to U77 · Spanish Fork, UT
Event
- NTSB case
- WPR13FA399
- 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
- 1 · 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
Tyler Ives SD-1 TG
- Aircraft type
- Tyler Ives SD-1
- 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
- N123SD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From U77 · Spanish Fork, UTTo U77 · Spanish Fork, UT
- 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
- Maneuvering
- Defining eventThe 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
- Abrupt maneuver
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR13FA399
- Event ID
- 20130906X73030
- Case number
- WPR13FA399
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 7d7ed09d38b83c52976f38a889eab7261db45cc40704f0e6a00c4c93b669ad54; retrieved 2026-09-14T16:03:39.943Z.