CHI01LA031 · Cessna 172
Cessna 172 · Accident: overrun during landing
From Springfield Branson National Airport (SGF) to Trenton Municipal Airport (TRX)
Event
- NTSB case
- CHI01LA031
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N8611B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Springfield Branson National Airport (SGF), Springfield, MOTo Trenton Municipal Airport (TRX), Trenton, MO
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Overrun
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Proper touchdown point, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
the misjudged touchdown point by the pilot. Factors were the runway lights not on, the dark night, and the plowed field.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI01LA031
- Event ID
- 20001212X22134
- Case number
- CHI01LA031
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-10-29.
- API snapshot SHA-256: e80a840a8e3778483e97f6f3f94822d483f9d584fe474ac97e5ca7b96a666006; retrieved 2026-09-22T12:21:11.048Z.