NTSB CAROL · Event
Event CHI01LA031
Registry · N8611B
FAA Aircraft Registry record.
Make / Model
CESSNA 172
Engine
CONT MOTOR 0-300 SER (145 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19571102
ADS-B equipped
Yes — Mode-S ABD50B
Registrant of record
CRIDER RAYMOND K
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the misjudged touchdown point by the pilot. Factors were the runway lights not on, the dark night, and the plowed field.
Factual narrative
On October 28, 2000, at 2050 central daylight time, a Cessna 172, N8611B, piloted by a private pilot, sustained substantial damage when it ran off of the end of runway 36 (2,600 feet by 50 feet asphalt), crossed a ditch, and nosed over in a corn field, during a precautionary landing at the Carrollton Memorial Airport (K26), Carrollton, Missouri. According to the pilot, the weather en route was deteriorating and he elected to divert to K26. The 14 CFR Part 91 personal flight was not on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot, who was the sole occupant, reported no injuries. The flight originated from the Springfield-Branson Regional Airport, Springfield, Missouri, at about 1915 and was en route to the Trenton Municipal Airport, Trenton, Missouri. In a written statement, the pilot said, "Just north of Carrollton, the ceiling began to deteriorate and I dropped down in altitude as I progressed for several minutes north. When I had reached 1800 feet (ASL) I decided that I was not going to be able to continue. I made a 180-degree turn back south to the Carrollton airport. I flew over the airport and observed all the lights were on except the runway lights. I tried to trigger the lights with my radio but to no avail...." The pilot said that he called 911 on his cellular phone to have the lights turned on. He said that he circled the airport for about 30 minutes before a highway patrol car arrived. He said that he circled until the ceiling had deteriorated to about 400 feet agl and then attempted to land on the unlighted runway. He said, "My touchdown was a little long and I did not think that I would get stopped before the end of the runway. I chose to do a go around and applied power. The plane did not attain sufficient speed to lift off more than a few inches and although I cleared the drainage ditch at the end of the runway, the plane settled back down in the plowed field beyond...." The Carrollton Fire Chief said, in a telephone conversation, that he was at the airport at the time of the accident and that the runway lights were not on. No notices to airmen had been issued regarding the runway lights at the accident airport. A weather report for the Kansas City Downtown Airport, Kansas City, Missouri, located about 52 nautical miles and 257 degrees magnetic from the accident airport, listed the sky condition, at 2054 cdt, as clear with mist. A weather report for the Whiteman Air Force Base, located about 35 nautical miles and 183 degrees magnetic from the accident airport, listed the sky condition, at 2055 cdt, as few clouds at 10,000 feet and broken clouds at 25,000 feet. A weather report for the Rosecrans Memorial Airport, Saint Joseph, Missouri, located about 70 nautical miles and 292 degrees magnetic from the accident airport, listed the sky condition, at 2053 cdt, as broken clouds at 1,300 feet and haze. A weather report for the Kirksville Regional Airport, Kirksville, Missouri, located about 64 nautical miles and 43 degrees magnetic from the accident airport, listed the sky condition, at 2055 cdt, as few clouds at 1,700. The pilot reported no mechanical difficulties in his written report. During a precautionary landing, the airplane ran off of the end of the runway, crossed a ditch, and nosed over in a corn field. The pilot said that he diverted due to deteriorating weather. At his selected alternate, he found that the runway lights were not on and he could not activate them using the aircraft radio. The pilot called 911 on his cellular phone to have the lights turned on. He said that he circled the airport for about 30 minutes before a highway patrol car arrived. He said that he circled until the ceiling had deteriorated to about 400 feet agl and then attempted to land on the unlighted runway. He said that he landed long and decided to abort the landing. The airplane nosed over in a plowed field. No notices to airmen had been issued regarding the runway lights at the accident airport. The pilot reported no mechanical difficulties in his written report. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_CHI01LA031.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. 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 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
Validation of Training Satisfaction Survey
The Training Satisfaction Survey (TSS) was developed as part of a larger project to examine the features of Virtual Reality software and supporting devices as a training program on visual illusions an…
- Semantic Scholar 2021 · Article (Data in Brief)
Cockpit voice recorder transcript data: Capturing safety voice and safety listening during historic aviation accidents
Cockpit Voice Recorder (CVR) transcripts capture audio data within cockpit environments. This aids the investigation of causal factors contributing to aviation accidents by revealing communication and…
- Semantic Scholar 2021 · Article (Safety Science)
Safety voice and safety listening during aviation accidents: Cockpit voice recordings reveal that speaking-up to power is not enough
Abstract Safety voice is theorised as an important factor for mitigating accidents, but behavioural research during actual hazards has been scant.
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Can Backward-Chained, Ab-Initio Pilot Training Decrease Time to First Solo?
Flight simulation has made progressively significant inroads into pilot training at all levels of a pilot’s career – typically starting with training for the Instrument rating in light aircraft and co…
Browse the full corpus — academia portal ↗