NTSB CAROL · Event
Event CHI96LA339
Aircraft involved
Probable cause & findings
failure of the Piper PA-25 tow pilot to see-and-avoid the Blanik L-23 glider. A factor relating to the accident was: neither aircraft was equipped with a communication radio.
Factual narrative
On September 14, 1996, at 1430 central daylight time, a Piper PA-25, N7753Z, operated by the St. Louis Soaring Association, landed on top of a Blanik glider, L-23, N7906, also operated by the St. Louis Soaring Association, that had just touched down on the airstrip. The were no injuries to the pilot of the PA-25, or to the instructor pilot and the student pilot in the glider. The glider received substantial damage and the PA-25 received minor damage. Both aircraft were operating under 14 CFR 91 flight rules and had departed the Highland-Winet Airport, Highland, Illinois, on local flights. Visual meteorological conditions prevailed and no flight plans were filed. The pilot of the PA-25 reported she had towed the Blanik to an altitude of about 1,200 feet above ground altitude (AGL). After the sail plane executed a release, she entered the right hand traffic pattern for runway 36. She reported that she was making an approach to land on runway 36. She reported that sail planes normally land on the parallel sail plane runway, except in emergencies when they land on the powered runway. She reported that she did not see the sail plane that was underneath and in front of her on the final approach to runway 36. As the Blanik touched down on the runway, the PA-25 landed on top of the sail plane. The landing gear of the PA-25 straddled the empennage behind the wings and the nose of PA-25 rested on the top of the sail plane just behind the cockpit of the sail plane. Both aircraft rolled out for about 150 feet before stopping. The pilot in command of the Blanik sail plane reported that he had been towed to an altitude of about 1,200 feet AGL to an area west of the airport where "good lift" had been found earlier in the day. The pilot reported he did not get the lift he had expected after the release, and as a result, was back at the entry point for landing within 10 minutes. He reported that he was at about 800 feet AGL on left downwind, west of the sail plane runway. The pilot reported that another sail plane, a Schweizer 1-34, was ahead of him in the pattern and was making an approach to the sail plane runway. He elected to extend the downwind to gain separation from the Schweizer. The pilot reported that when he turned base leg, the sail plane was further from the runway and lower than normal. He reported he saw the PA-25 on a right base leg east of the field for the parallel powered runway. The Blanik pilot determined it was necessary for him to land on the powered runway since the Schweizer had just landed. He reported that he had expected the pilot of the PA-25 to execute a go-around. Neither the Blanik nor the PA-25 were equipped with radios. He reported that the sail plane was in front and lower than the PA-25 on final approach to runway 36. As the Blanik touched down on the runway, the PA-25 settled on the T-tail of the Blanik, and they rolled out for about 150 feet before coming to a stop. A witness on the ground reported seeing the Blanik sail plane approaching final for runway 36 about 100 yards from the runway threshold. Immediately behind and above the Blanik was the PA-25 tow plane approaching from the same direction. The PA-25 was slowly overtaking the Blanik. He reported that at the instant the Blanik touched down, the PA-25 gently made contact with the top of the Blanik. The PA-25's engine stopped immediately and the two rolled to a stop. The St. Louis Soaring Association owned and operated both the Blanik and the PA-25. Neither aircraft were equipped with radios. A Piper PA-25 tow plane was used to tow a Blanik L-23 Glider (sailplane) to about 1,200 feet AGL, west of the airport. After release of the glider, the tow pilot returned to the airstrip and entered a right traffic pattern (from the east) to land on the runway for powered aircraft (powered runway 36). Meanwhile, the Blanik/glider pilot did not get the expected lift and had entered a left downwind for landing on the parallel runway for sailplanes (sailplane runway 36). Another sailplane was ahead of the Blanik, so the Blanik pilot extended the downwind turn to base. When he turned base leg, he was further from the runway and lower than normal. At about that same time, the PA-25 tow plane was on the base leg for the powered runway 36. Because the Blanik was lower than expected and because the other glider had just landed, the pilot of the Blanik chose to land on the powered runway, which could be used by gliders in emergency situations. The PA-25 pilot reported that she did not see the Blanik in front and underneath the PA-25. At about the time the Blanik touched down, the PA-25 landed on top of the Blanik, straddling the glider until both aircraft rolled to a stop. Both aircraft were owned and operated by the same sailplane soaring association, and neither aircraft was equipped with a radio. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_CHI96LA339.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 (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗