CHI04CA088 · Cessna 172A
Cessna 172A · Accident: hard landing
From Flying Bar H Ranch Airport (MO2) to Flying Bar H Ranch Airport (MO2)
Event
- NTSB case
- CHI04CA088
- 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
- Unknown
- 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 172A
- 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
- N7265T
- Operator
- Otis A. Keller · private individual
- Onboard fatalities
- Unknown
- Route
- From Flying Bar H Ranch Airport (MO2), Springfield, MOTo Flying Bar H Ranch Airport (MO2), Springfield, 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
- Hard landing
- 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 › Go-around, not performed
- Pilot in command › Porpoise/pilot-induced oscillation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane experienced a nose gear collapse following a loss of control while landing on a grass airstrip. The pilot stated that as he cleared the trees at the approach end of the runway he noted his airspeed was indicating 60 miles per hour, but his ground speed seemed fast. He stated that upon touchdown, the airplane bounced and porpoised contacting the grass airstrip on the nose gear. The pilot reported the nose gear collapsed and the nose of the airplane dug into the grass. The pilot stated he should have performed a go around when he noticed the fast ground speed.
Probable cause
The pilot failed to initiate a go-around and the airplane porpoised during the hard landing. Factors associated with the accident were the excessive groundspeed and the overload failure of the nose gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04CA088
- Event ID
- 20040324X00363
- Case number
- CHI04CA088
- 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: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d64a92b61f2a09bd2b2394e33b79d8dccde447c45f829366b52896965aef0f7c; retrieved 2026-09-21T19:16:32.379Z.