NTSB CAROL · Event
Event CHI97LA028
Registry · N8308V
FAA Aircraft Registry record.
Make / Model
PIPER PA-32R-301T
Year of manufacture
1980 · 16 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
19801230
ADS-B equipped
Yes — Mode-S AB5BDE
Registrant of record
CLEARY PAUL D
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's improper planning/decision, and his failure to go around, while there was still sufficient runway remaining. The unfavorable wind condition was a related factor.
Factual narrative
On November 16, 1996, at 2134 central standard time, a Piper PA- 32R-301T, N8308V, operated by a private pilot collided with a ditch at the departure end of the runway while landing on runway 27 (3,655' x 75') at the Lansing Municipal Airport, Lansing, Illinois. The personal 14 CFR Part 91 flight was operating in visual meteorological conditions without a flight plan. The pilot and one passenger received minor injuries. Two other passengers were seriously injured. The airplane as substantially damaged. The flight originated from Romeo, Michigan, at 2130 eastern standard time. The pilot stated that while en route from Romeo, Michigan, to Lansing he monitored the Automated Weather Observation Station (AWOS) located at Lansing. He stated the AWOS was reporting strong southerly winds. He stated that upon reaching the Lansing Municipal Airport he flew over the airport and noticed the "directional plane" moving from 180 degrees to 240 degrees and that it contradicted what the AWOS was reporting. He stated runway 27 was favored due to the variable wind direction. According to the pilot he made one landing attempt on runway 27 which ended in a go-around as he was unable to maintain alignment with the runway centerline. He stated that during the second attempt he used two notches of flaps instead of three which was what he used during the first attempt. He stated the airplane touched down near the runway numbers at an indicated airspeed of 85 to 90 knots. He stated that seconds later the airspeed had decreased to 70 knots; however, it was still 60 knots when the airplane was half way down the runway. The pilot continued to report, "I pulled the last notch of flaps on and forcefully applied the brakes at this time... ." He stated that with 1,000 feet of runway remaining the airspeed was indicating 50 knots. The pilot reported, "Realizing that due to my present airspeed, amount of runway I had remaining, the darkness of the area in front and above me and the winds I most probably could not rotate the plane off of the pavement... ." He stated that as he passed the runway end lights he noted the airspeed had slowed to 35 knots. The airplane continued off the end of the runway where it contacted a guard rail prior to coming to a stop. The Lansing AWOS was reporting winds from 160 degrees at 16 knots gusting to 24 knots at the time of the accident. The pilot stated the 'directional plane' at the airport was indicating winds from 180 to 240 degrees, which favored runway 27. He stated that this information contradicted what the AWOS had reported. Subsequently, the pilot realized he would not be able stop the airplane on the runway. However, given the length of runway remaining, the airspeed, and the dark night conditions, he doubted he could 'rotate' the airplane off the runway. The airplane traveled off the end of runway 27 at a speed of about 35 knots. AWOS at the time of the accident was reporting winds from 160 degrees at 16 knots gusting to 24 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1996_CHI97LA028.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 ↗