MIA00LA038
1999-12-03 · PALM BCH GARDEN, Florida, United States · None · 1 aircraft · Status: Completed
Aircraft involved
Probable cause & findings
The sailplane pilot's failure to comply with standard emergency procedures for 'sailplane release failure' upon its occurrence and his maneuvering of the sailplane while still tethered to the tow plane resulting in the inflight loss of control and engine stoppage of the tow airplane during it's uncontrolled descent and inflight collision with trees and swampland.
Factual narrative
On December 3, 1999, about 1430 eastern standard time, a Maule MX-7-160, N9235N, registered to Barry Aviation, Inc., operating as a Title 14 CFR Part 91 sailplane tow flight, crashed during towing climb from North Palm Beach County Airport, West Palm Beach, Florida. Visual meteorological conditions prevailed and no flight plan was filed. The tow airplane received substantial damage and the sailplane, N2780Z released from the towline and was not damaged. The commercially-rated tow pilot was not injured. The flight originated about 14 minutes before the accident. According to the tow pilot, this was the second tow of the day for he and the glider pilot, and they were in towed climb at about 2,800 feet agl, when the sailplane abruptly pulled up and to the right, stalling the tow airplane. The tow airplane entered a spin, the tow and the sailplane both released their respective towline releases at about 1,200 feet agl, and during the three-turn spin, the tow's engine quit. The pilot recovered from the spin at about 700 feet agl, but did not have time to restart the engine. He performed a forced landing to swampy terrain overgrown with pine and palmetto. The tow pilot added that the first tow and release went uneventfully at 3,000 feet agl, and that both he and the glider pilot had previously conducted a positive release check of the towline and each airplane's hardware. It was the tow pilot who had conducted the glider pilot's mandatory dual checkout as a new customer, as well as his glider biennial flight review some months previously, and he felt confident that standard signals and procedures were in effect since the glider was not radio equipped. Additionally, the tow pilot stated, one day after the accident that the sailplane pilot admitted to him that he did not see the tow rope release before he started maneuvering the sailplane. The sailplane was inspected for release mechanism operation at the time of its return on December 3, 1999. No difficulties were noted then, nor have any difficulties been noted in at least 12 subsequent releases as of January 7, 2000. According to the sailplane pilot, at about 3,000 feet agl, the sailplane could not release and neither did the tow plane release. Repeated efforts by him to release were not successful until about 1,200 feet agl, at which time he did effect a release, and he proceeded back to North Palm Beach County, (F45) for an uneventful landing. He saw the tow airplane spin, lose power, and force land in the swamp area. According to FAR 91.309, (5), "The pilots of the towing aircraft and the glider [must] have agreed upon a general course of action, including takeoff and release signals, airspeeds, and emergency procedures for each pilot". The Soaring Society of America Private/Commercial Flight Manual states under the section titled, "Tow Release", the following: "When the [sailplane] pilot is ready, the release handle is pulled and the release confirmed visually. A level right turn is then made to clear the towline and towplane. This turn should never be made before release." The flight manual also states, under the section titled, "Aero Tow Emergencies-Sailplane Release Failure", the following: "If the sailplane's release mechanism fails, the sailplane pilot can signal by moving into a position where the sailplane can be seen easily by the tow pilot and then deliberately rocking the wings. After the sailplane pilot is sure the tow pilot has received the signal, the sailplane should be maneuvered into the proper high tow position for return to the gliderport. The tow pilot should release the sailplane at a safe altitude over the field. The sailplane can then maneuver to an unobstructed area on the airport. A higher-than-normal final approach should be planned to avoid snagging the towline". The tow pilot stated that he remembers selling a copy of the SSA flight manual referenced above to the sailplane pilot. The glider pilot stated that he could not get a towline release at the prebriefed release altitude of 3,000 feet agl, and kept trying until he did effect a release at about 1,200 feet agl. The tow pilot stated that they were still in the towed climb at about 2,800 feet agl, when he experienced an abrupt pull up to the right by the glider that caused a stall and spin of the tow airplane. The towline was finally released simultaneously at about 1,200 feet agl, by both aircraft, and the glider made it back to the gliderport for a normal landing. The tow pilot recovered from the spin at about 700 feet agl, but the engine quit running in the spin, and there was no time to get it restarted. The tow airplane performed a forced landing to a swamp area. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_MIA00LA038.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, loss of control). All research papers
- 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…
- 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.
- Semantic Scholar 2024 · Article (International Conference on Networking and Services) Risk Assessment of Loss of Control In-Flight Trajectories for Urban Air Mobility Safety
In Urban Air Mobility (UAM), maintaining a minimum separation between aircraft is a safety requirement, which becomes challenging amidst congested air traffic and off-nominal conditions, such as Loss …