CHI96LA062 · Cessna 172M
Cessna 172M · Accident: loss of control on ground/water during landing
From Jefferson City Memorial Airport (JEF) to Rosecrans Memorial Airport (STJ)
Event
- NTSB case
- CHI96LA062
- 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 172M
- 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
- N172DA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jefferson City Memorial Airport (JEF), Jefferson City, MOTo Rosecrans Memorial Airport (STJ), ST. JOSEPH, 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 · flare/touchdown
- 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
- Loss of control on ground/water
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Aborted landing, delayed
- Pilot in command › Wrong runway, selected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot flew off course during the flight and became disoriented, and was attempting to land at an unfamiliar airport. He made three passes down the runway but was unable to see a wind sock. He stated he then landed on Runway 19 on the numbers and applied brakes; however, when the airplane did not slow down he applied full power to take off. The airplane became airborne and contacted trees near the end of the runway. A witness stated the airplane touched down then porpoised on the runway prior to taking off. The pilot reported the last wind information he received from flight service indicated winds from 330 degrees at 10 mph. The witness reported local winds at the time were from 350 degrees at 9 knots.
Probable cause
the pilot's selection of the wrong runway for landing and the delayed aborted landing. Factors associated with the accident were the tailwind condition and the pilot's inadequate level-off.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI96LA062
- Event ID
- 20001207X04983
- Case number
- CHI96LA062
- 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 1995-12-27.
- API snapshot SHA-256: a03f28be3116b7be333919261e77e50645c9228f79612e1ce6665e43d50591f7; retrieved 2026-09-21T12:56:52.929Z.