NTSB CAROL · Event
Event LAX00GA185
Aircraft involved
Probable cause & findings
the inadvertent early deployment of the test parachute lines and dummy and it's entanglement with the horizontal stabilizer, which resulted from the operator's inadequate test plan substantiation process for shortening the parachute's static line. .
Factual narrative
On May 5, 2000, at 1015 Pacific daylight time, a Beech King Air 65-90 twin-engine airplane, N32229, lost control during cruise flight after becoming entangled with a deploying parachute north of China Lake, California. The airplane sustained substantial damage and one crewmember received serious injuries. The pilot, copilot, and second crewmember were not injured. The airplane was registered to a private individual and was being operated as a public-use flight by Aerospace Equipment Research Organization (AERO), Wilmington, Delaware, under 14 Code of Federal Regulation Part 91 at the time of the accident. The local flight originated from Armitage Field, Naval Air Warfare Center, China Lake, at 0945. Visual meteorological conditions prevailed at the time of the accident and a military visual flight rules flight plan had been filed. The crew was in the process of conducting an experimental parachute test with a 331-pound anthropomorphic dummy that was rigged with a main and reserve parachute. The parachute assembly consisted of a pilot chute (which is a spring-loaded canopy and deploys when a ripcord pin is extracted (in this case by a static line)), a drogue chute (which is a small canopy released prior to the main canopy to provide descent stabilization), and a main canopy parachute. The accident sequence was filmed by several video cameras from different angles and perspectives, and National Transportation Safety Board investigators reviewed the footage. While stabilized at 20,000 feet mean sea level (msl) and 180 knots, the two crewmembers in the back of the airplane positioned the dummy at the open cabin door. The static line was attached to a ring that, in turn, was secured by a line to the left outboard seat track, about 1-foot forward of the doorway. One crewmember crouched behind the dummy while the second knelt just forward of the open door with his hands on the static line. As the dummy cleared the doorway, the pilot chute deployed. This was immediately followed by the deployment of the drogue chute. The drogue chute cleared the top of the left horizontal stabilizer while the dummy fell below. Initially, the dummy trailed behind the left elevator but as the drogue chute fully inflated, the dummy was drawn back underneath the horizontal stabilizer. At this point the dummy began oscillating, contacting the empennage and the lower side of the horizontal stabilizer. As the oscillations increased in magnitude, the left horizontal stabilizer began separating at about midspan, folding back on top of itself. At nearly the same moment, the soft link for the deployment of the main parachute separated and the main canopy deployed. Almost simultaneously, the drogue chute lines separated and the dummy fell freely from the airplane as the main canopy opened. As the dummy became entangled on the left horizontal stabilizer, the airplane made an uncommanded noseover into a negative G arc. The crouching crewmember was thrown about the cabin while the kneeling crewmember held onto the static line. As the dummy fell away, the airplane pitched up and began an uncommanded roll to the right, stopping in a fully inverted attitude. The airplane initially nosed forward and then began a slow roll to the left, stabilizing in level attitude. The pilot's then returned the airplane to the airport and landed without further incident. An inspection of the airplane after the accident revealed that the static line had been shortened from 14 feet 6 inches to 7 feet 9 inches. Measurements from the static line attachment point further revealed that the static line was in tension with the dummy in the aircraft doorway. The installation aviation safety officer had been informed by test personnel that the static line had been intentionally shortened. This was due to an incident during a previous test in which a pin at the end of the static line had become lodged in the left elevator hinge. On April 21, 2000, the crew of another test flight experienced a situation where a pin at the end of the static line (originally 14 feet 6 inches) became lodged in the horizontal stabilizer control surface. The cabin crew was able to remove the static line from the control surface after several attempts by releasing the line and letting it trail behind the aircraft. The line and its pin were never recovered. After the April 21st event, the crew discussed the hazard with AERO and the parachute test program personnel and a decision was made to shorten the static line to a maximum length of 9 feet. The static lines were shortened and the test dummies were installed and underwent their final quality assurance (QA) check on May 4, 2000. According to one of the crewmembers, "throughout the entire chain of events, from the previous airdrop until after the final QA, it was agreed by all involved that the length of the static line (being too long) was a hazardous situation. From the time that we identified the length of the static line as a potential problem throughout the rigging and QA process I do not believe that anyone realized that there may have been a hazard induced from shortening the static line." According to the Chief Test Pilot of the Navel Weapons Test Squadron, the parachute test program personnel did not obtain the proper approval for the test plan, specifically, the Chief Test Pilot requested that they address the "out of aircraft" hazards in the Test Hazard Analysis. According to the Test Hazard Analysis, approved on April 21, 2000, under the section titled 3. Test item strikes aircraft upon release," the cause, effect, assessment and mitigation of this particular hazard was addressed as follows: "Cause- Aero forces cause test item to deviate from anticipated path and strike rear portions of aircraft." "Effect- Since no antennas or other sensitive, protruding items are present, only minor cosmetic skin damage would likely result." "Assessment- Based on prior experience the probability of this occurrence is low." "Mitigation- Trained and briefed personnel will deploy the dummies aggressively to prevent subsequent aircraft contact." There were no known changes to the Test Hazard Analysis after the April 21st event. The twin-engine airplane experienced a loss of control after becoming entangled with a deploying parachute during cruise flight at 20,000 feet and 180 knots. The test flight was conducted to test an experimental parachute with a 331-pound anthropomorphic dummy that was rigged to the parachute. Two crewmembers in the airplane's cabin were to push the dummy out of the door and the parachute would deploy by pulling on a static line that was secured to a floor seat track. The static line for this flight had been reduced in length from 14 feet to 9 feet because of a previous test flight where a pin on the end of the static line became entangled with the elevator hinge and caused control problems. With the shortened static line, it was in tension when the dummy was positioned in the doorway. During the accident flight, once the dummy cleared the doorway, the static line deployed the pilot chute which in turn deployed the drogue chute. The drogue chute cleared the top of the left horizontal stabilizer while the dummy fell below. The dummy began oscillating and impacted the empennage and lower side of the horizontal stabilizer, eventually resulting in the partial separation and bending down of the stabilizer about midspan. As the dummy became entangled on the left horizontal stabilizer, the airplane made an uncommanded nose over into a negative G arc, which threw one crewmember about the cabin while the second crewmember was able to restrain himself by holding onto the static line. As the main parachute deployed, the drogue chute lines separated and the dummy and canopies fell away from the airplane. As the dummy fell away, the airplane pitched up and began an uncommanded roll to the right, stopping in a fully inverted attitude. The airplane initially nosed forward and then began a slow roll to the left, eventually stabilizing in wings level attitude. The pilots then returned the airplane to the airport and landed without further incident. Review of the parachute test program's Test Hazard Analysis revealed that the plan's cause/effect assessment and hazard mitigation actions inadequately addressed all potential "out of aircraft" hazard possibilities, including the effect of the parachute lines and/or dummy becoming entangled on the horizontal stabilizer. Additionally, no revision to the Test Hazard Analysis was noted after the previous static line entanglement incident and subsequent shortening of the static line. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_LAX00GA185.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Semantic Scholar 2016 · Article (Interacción)
Trajectory Recovery System: Angle of Attack Guidance for Inflight Loss of Control
This paper describes the design and development of an ecological display to aid pilots in the recovery of an In-Flight Loss of Control event due to a Stall (ILOC-S).
- NTSB Aircraft Accident Reports 2010 · Accident report
Loss of Control on Approach — Colgan Air Flight 3407
Colgan Air 3407 / Continental Connection (Q400) Buffalo NY, February 12, 2009 — 50 fatalities. Definitive investigation of the Colgan 3407 stall-stick-pusher crash on approach to Buffalo.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- arXiv 2025 · arXiv preprint
Quadratic Programming Approach to Flight Envelope Protection Using Control Barrier Functions
Ensuring the safe operation of aerospace systems within their prescribed flight envelope is a fundamental requirement for modern flight control systems.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗