NTSB CAROL · Event
Event NYC99FA037
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control during touch-and-go landing, and his failure to maintain obstacle clearance. A factor was the tree.
Factual narrative
HISTORY OF FLIGHT
On December 12, 1998, about 1530 Eastern Standard Time, a Taylorcraft BC12-D, N43778, was destroyed when it collided with trees during landing practice at Greenville Municipal Airport (4G1), Greenville, Pennsylvania. The student pilot received fatal injuries. Visual meteorological conditions prevailed at the time of the accident. No flight plan was filed for the local instructional flight, which was conducted under 14 CFR Part 91. According to a witness who was flying in the airport traffic pattern at the time, the accident airplane touched down in a grassy landing area to the right of, and parallel to, a paved Runway 15. It then appeared to veer to the left, and crossed the paved runway, towards a large briar patch. The witness thought the airplane would hit the patch, but it managed to fly over it, and headed towards the "wide open space" of a turf cross-runway. Then, instead of continuing toward the cross-runway, the airplane entered a steep left turn with a steep climb. It looked like it was in a stall attitude, and flying very slow. The witness then saw the airplane's nose drop, and the airplane "go over," but felt it may have been the result of hitting a tree. Another witness saw the accident from inside the airport office. He looked outside the window, and saw the accident airplane cross over the briar patch. He then saw it make a climbing left turn, but "not excessively steep, not like a stall climb." He wasn't sure of the angle of bank, but it was "maybe 25 degrees, it wasn't less." The airplane then leveled off and hit trees, and the witness "saw wood flying." The witness said that if the airplane had continued to climb straight ahead instead of turned, it would have avoided the trees. He also felt that the student pilot did not see the trees, and that the airplane didn't stall before hitting the trees. He said the winds were calm during the event, and that it was a perfect day to fly. A third witness stated that the student pilot had been flying earlier in the day, for about an hour, at the most. The student pilot landed the airplane, got some fuel, and went into the airport office to chat. He then decided that since it was still a nice day, he'd go flying again. He took off about 15-20 minutes prior to the accident, and remained in the airport traffic pattern for touch and go's. The witness stated that she was inside the airport office, and that her attention was drawn to the accident airplane when someone else said: "Hope he makes it over those trees." She then looked out the window, and saw the accident airplane in a climb, with its wings level. Then, "it just hit trees." She felt the student pilot probably didn't see the trees because the nose of the airplane was high in the climb. She said that the initiating event did not look like a stall - that the airplane was climbing wings level, but "not so nose up that it would stall." The accident occurred during the hours of daylight, and the accident site was located at 41 degrees, 26.96 minutes north latitude, 80 degrees, 23.44 minutes west longitude.
PERSONNEL INFORMATION
The student pilot was 79 years old, and had 109 total flight hours. He had some initial flight training in 1944, then began flying again in 1995.
METEORLOGICAL INFORMATION
Approximately 20 minutes after the accident, at an airport about 17 nautical miles to the southwest, the observed weather included a broken cloud layer at 23,000 feet above ground level, and a visibility of 10 statute miles. The sun was in the southwest quadrant.
WRECKAGE AND IMPACT INFORMATION
The wreckage was found approximately 800 feet northeast of Runway 15 and 200 feet northwest of Runway 23. It was just inside the edge of a wooded area with 70-foot trees. There were cut tree branches, commencing about 60 feet above the ground, in a descending 45 degree path, on a heading of 030 degrees magnetic. The airplane was found on its left side, with the left wing broken upwards. The wooden propeller was shattered, still attached to the engine, and wedged up against a tree trunk. Cockpit examination revealed that the mixture knob was full rich, and the throttle knob was full forward. The magnetos had been turned off by rescue personnel. The main and left fuel controls were on, and the right fuel control was off. Control continuity was established to the rudder and elevator, and within both wings. The right wing held about 2 gallons of fuel, while the left wing held only trace amounts. When the wreckage was removed, there was a moist area underneath the left wing, with a strong odor of fuel. Engine examination revealed the presence of fuel in the strainer. All spark plugs were grayish brown in color except bottom number 2, which was saturated in oil. Throttle continuity was confirmed, and compression established in all cylinders. Magnetos were not tested due to impact damage, but appeared new. The carburetor heat was on.
MEDICAL AND PATHOLOGICAL INFORMATION
On December 13, 1998, an autopsy was conducted on the pilot by the Forensic Pathologist, Elwood City Hospital, Elwood City, Pennsylvania. Toxicological testing was performed by the FAA Toxicology and Accident Research Laboratory, Oklahoma City, Oklahoma. Results were negative for carbon monoxide, cyanide, ethanol, and illegal drugs. Verapamil was detected in the blood and urine, and norverapamil was detected in the urine.
ADDITIONAL INFORMATION
On December 12, 1998, the wreckage was released to the president of Motovation Air, Incorporated. A witness reported that the student pilot had been in the traffic pattern for 15 - 20 minutes during his second flight of the day. A second witness, who was in the pattern at the time of the accident, reported seeing the aircraft touch down in a grassy landing area to the right of, and parallel to, paved runway 15. It then veered left, crossed runway 15, and continued towards a large briar patch and an intersecting turf runway, during which the aircraft entered a steep, climbing left turn. The witness reported that he then observed the aircraft nose drop, and 'go over.' A third (ground) witness reported seeing the aircraft cross over the briar patch and make a climbing left turn which was described as 'not excessively steep', and with the angle of bank of at least 25 degrees. This was followed by the aircraft leveling off, and then impacting trees. This witness reported the winds as calm. On site examination revealed that the aircraft first encountered trees approximately 10 feet below the 70 foot high tops, and the wreckage distribution progressed toward 030 degrees magnetic to ground impact. There was no evidence of pre-impact control or engine malfunction. The student pilot had 109 total flight hours. He had some initial flight training in 1944, then began flying again in 1995. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_NYC99FA037.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). 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 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 …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗