CEN12CA064 · Cessna 210F
Cessna 210F · Accident: loss of control in flight during landing
From St Clair County International Airport (PHN) to Phillipsburg Municipal Airport (PHG)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN12CA064
- 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 210F
- Aircraft type
- Cessna 210
- 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
- N615BT
- Operator
- Cheney Dustin S
- Onboard fatalities
- Unknown
- Route Possible conflict
- From St Clair County International Airport (PHN), St. Clair, MITo Phillipsburg Municipal Airport (PHG), Phillipsburg, KS
- 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
- Defining eventThe 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 in flight
- 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
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he made a normal landing on the main tires, but when the nosewheel touched down it began to shimmy violently. In response, he pulled back on the control yoke, and the airplane became momentarily airborne, bounced several times, and porpoised down the runway. Postaccident examination of the airplane revealed that the nosewheel tire was crushed and partially attached to the rim; the firewall was wrinkled, the nose landing gear doors were damaged, the nose gear strut was slightly bent, and all three propeller blades were bent aft at the tips. Examination of the runway indicated that there were two propeller strike marks on the runway followed by impact scars from the nosewheel. Just past the nosewheel impact marks, there were four additional propeller strike marks. The pilot stated that he did not observe any abnormality with the nosewheel tire before the flight.
Probable cause
The pilot’s improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA064
- Event ID
- 20111115X30049
- Case number
- CEN12CA064
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-10-10.
- API snapshot SHA-256: 63b956448ce1adb4543687e075234094134ea73f5734a40d4275de116398ee52; retrieved 2026-09-15T16:56:11.258Z.