IAD97LA036
1996-12-27 · MANVILLE, New Jersey, United States · Minor · 1 aircraft · Status: Completed
Airport 47N
Current FAA registration · N738UW
- Make / Model
- CESSNA 172N
- Year of manufacture
- 1978 · 18 years old at event
- Engine
- LYCOMING 0-320 SERIES (180 hp)
- Seats / Engines
- 4 seats · 1 engine
- Last airworthiness date
- 19780126
- ADS-B equipped
- Yes — Mode-S A9EA9A
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to perform a go-around, and his failure to retract the flaps in increments.
Factual narrative
On December 27, 1996, approximately 1545 eastern standard time, a Cessna 172N, N738UW, was substantially damaged during a collision with trees after an aborted landing at the Kupper Airport, Manville, New Jersey. The certificated private pilot and the passenger received minor injuries. Visual meteorological conditions existed and no flight plan was filed for the personal flight conducted under 14 CFR Part 91. The pilot and passenger took off for a local flight, and upon his return to the airport, the pilot stated that he entered the airport traffic pattern for runway 25. The pilot recalled that there was one airplane in front and one following him in the traffic pattern. He reported that "he kept track of the airplane in front of him because the sun set almost totally wiped out the runway environment." The pilot also stated that the glare from the (old) windscreen was also very bad. The pilot stated that his approach to the runway was "a little too high and with a little too much airspeed." After the airplane touched down it bounced twice, and the pilot decided to abort his landing. The pilot stated that he added full power, raised the flaps in 10 degree increments, and the airplane proceeded to "mush into the bushes and trees on the north side of the runway." A Federal Aviation Administration Inspector examined the wreckage the following day. The airplane was in an upright position, two thirds of the way down the 3,450 foot runway, and approximately 180 feet to the right of centerline The Inspector was able to confirmed flight control continuity; flaps in the "up" position, and the carburetor heat switch in the "on" position. The Inspector interviewed the pilot, who reported that he did not experience any mechanical problems with the airplane or engine. After a local flight, the pilot entered the traffic pattern for runway 25, which was 3,450 feet in length. The pilot reported that he kept track of the airplane in front due to the sun glare from a setting sun and a very old windscreen, which 'almost totally wiped out the runway environment.' The pilot stated that the approach to the runway was high and fast. After touchdown just beyond the windsock, the airplane bounced twice and the pilot decided to abort the landing. The pilot stated that he added full power, raised the flaps in 10 degree increments, and the airplane proceeded to 'mush into the bushes and trees' prior to the end of the runway on the north side. Examination of the wreckage revealed that the flaps were up, and the carburetor switch in the 'on' position. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_IAD97LA036.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 (go-around). All research papers
- 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…