NTSB CAROL · Event
Event CEN16LA206
Registry · N5771V
FAA Aircraft Registry record.
Make / Model
BEECH A23-24
Year of manufacture
1966 · 50 years old at event
Engine
LYCOMING I0360 SER (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19660408
ADS-B equipped
Yes — Mode-S A76AF9
Registrant of record
LOW & SLOW AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain the proper glidepath during the night visual approach, which resulted in impact with a runway threshold light, and his improper landing flare, which resulted in a hard landing. Contributing to the accident was the pilot's fatigue.
Factual narrative
On May 30, 2016, about 0330 central daylight time (all times cdt), a Beech A23-24, N5771V, sustained substantial damage during a hard landing on runway 32 (4,600 ft by 75 ft, asphalt) at the Clintonville Municipal Airport (CLI), Clintonville, Wisconsin. The pilot and one passenger were not injured. The airplane was registered to and operated by a private individual under the provisions of the 14 Code of Federal Regulations Part 91 as a personal flight. Night visual meteorological conditions prevailed for the cross-country flight, which was not operated on a flight plan. The flight departed the Perry County Municipal Airport (TEL), Tell, Indiana, about 0100. The pilot reported that he initially departed North Perry Airport (HWO), Hollywood, Florida, on May 29, 2016, and landed at the Palatka Municipal Airport (28J), Palatka, Florida, after a 3 hour 20 minute flight. A fuel receipt indicated that the airplane was fueled with 38.8 gallons of fuel at 1430 while at 28J. The pilot's next fuel stop was at TEL and the fuel receipt indicated that the airplane was fueled with 47 gallons of fuel at 2359. The pilot reported that he planned to land at CLI for fuel and then proceed to his destination airport, Langlade County Airport, Antigo, Wisconsin, about 36 nm northwest of CLI. The pilot reported that the total time from when he departed HWO until the time of the accident was about 15 hours 30 minutes. He stated that he had a full night of sleep before the initial flight, and was able to eat and "chill out" at TEL before departing on the last leg of flight. He reported that he felt "great" during the last leg of flight and was not tired when he arrived at CLI for landing. The pilot reported that the weather during the accident flight was good and without any thunderstorms or rain showers. However, although the surface weather observation at CLI indicated visual meteorological conditions, the pilot reported that there was ground fog at CLI when he arrived for landing. He could see the runway and precision approach path indicator (PAPI) lights through the ground fog on his approach. During the final approach, the PAPI lights were white/red down to about 250 ft above ground level. Then the lights went red/red, indicating that the airplane was below the glidepath. He corrected for the low altitude by adding power. The airplane was lined up with the runway, and he was "looking to land at the start of the lighted runway." He stated that the airplane touch down felt normal, perhaps with the back tire[s] hitting the runway first. However, he stated that, "once on the ground, then I felt the nose wheel give out, dropping the plane down on top of the nose wheel and using it as a skid plate until we stopped about 300 feet down the runway." A Federal Aviation Administration inspector examined the airplane and runway at CLI. The examination of runway 32 revealed that one of the runway threshold lights, which was painted yellow, had been struck. There was a tire impact mark near the beginning of the runway's asphalt surface about 40 ft right of the runway's centerline. This tire skid mark continued down the runway for about 22 ft to where the first propeller strike was observed. A second propeller strike mark was located about 5 1/2 ft from the first propeller strike. A long scrape mark began near the second propeller strike and continued to where the airplane came to rest, which was about 370 ft from the start of the asphalt and near the runway centerline. The examination of the airplane revealed that the leading edge of the left horizontal stabilizer was dented and had a yellow paint transfer mark on it. The nose landing gear had collapsed. The nose wheel was lodged under the airplane and it formed an indentation into the belly skin. Both wings exhibited buckling and twisting with damage to the wing spars. The pilot was completing a cross-country flight from Florida to Wisconsin. He stated that he got a full night's sleep prior to departing on the flight around 1100. About 0330, he was approaching the airport for the third and final fuel stop of the trip. Although the surface observation at the airport indicated that night visual meteorological conditions prevailed, the pilot noticed that, as he approached the airport, the runway and precision approach path indicator (PAPI) lights were partially obscured by ground fog. About 250 ft above ground level on final approach, the PAPI lights indicated that the airplane was below the approach path, and the pilot attempted to correct by applying engine power. He reported that the landing felt normal, then the nose landing gear "gave out," and the airplane skidded about 300 ft down the runway before coming to rest. Examination of the runway surface revealed tire skid marks consistent with the airplane touching down about 40 ft right of the runway centerline at the beginning of the paved surface. The airplane's left horizontal stabilizer displayed an indentation and paint transfer consistent with impact with a runway threshold light. Postaccident examination of the airplane revealed no preexisting anomalies that would have precluded normal operation. It is possible that the pilot may have lost visual contact with the airport environment due to ground fog as the airplane neared the runway, which resulted in the short and right-of-centerline landing. Although the pilot stated that he did not feel tired during the accident flight, it is likely that he was experiencing symptoms of fatigue as a result of his extended time awake prior to the accident. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- F Personnel issues-Physical-Alertness/Fatigue-(general)-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2016_CEN16LA206.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 (thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
- NASA NTRS 2019 · Technical Memorandum (TM)
Thunderstorm hazards flight research: Storm hazards 1980 overview
A highly instrumented NASA F-106B aircraft, modified for the storm hazards mission and protected against direct lightning strikes, was used in conjunction with various ground based radar and lightning…
- NASA NTRS 2019 · Conference Proceedings
Operational evaluation of thunderstorm penetration test flights during project Storm Hazards '80
The National Aeronautics and Space Administration is conducting a research project called Storm Hazards '80 in order to study the prediction, detectability and avoidance of the hazards of severe storm…
- NASA NTRS 2019 · Preprint (Draft being sent to journal)
Nowcasting Thunderstorm Anvil Clouds Over KSC/CCAFS
Electrified thunderstorm anvil clouds extend the threat of natural and triggered lightning to space launch and landing operations far beyond the immediate vicinity of thunderstorm cells.
- NASA NTRS 2019 · Contractor Report (CR)
An Examination of Aviation Accidents Associated with Turbulence, Wind Shear and Thunderstorm
The focal point of the study reported here was the definition and examination of turbulence, wind shear and thunderstorm in relation to aviation accidents.
- NASA NTRS 2019 · Reprint (Version printed in journal)
Observations of severe turbulence near thunderstorm tops
Data derived from the flight tapes of two airliners that experienced severe turbulence near thunderstorm tops are used to produce quantitative descriptions of the turbulence and its environment.
Browse the full corpus — academia portal ↗