CEN10CA356 · Beech C23
Inflight Pilot Traning Beech C23 · Accident: abnormal runway contact during landing
From Flying Cloud Airport (FCM) to Flying Cloud Airport (FCM)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination and operator. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10CA356
- 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
Beech C23
- Aircraft type
- Beechcraft 23
- 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
- N9253S
- Operator
- Inflight Pilot Traning Possible conflict
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Flying Cloud Airport (FCM), Eden Prarie, MNTo Flying Cloud Airport (FCM), Eden Prarie, MN
- 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
- Abnormal runway contact
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot and his certified flight instructor performed three takeoff and landings at the accident airport in preparation for the student pilot's second solo flight. During the takeoff and landings, the wind was from the northwest at 8 to 11 knots with no wind gusts. After approximately 0.7 hours of flight time, the certified flight instructor exited the airplane and the student pilot taxied to the runway for takeoff. About the time of departure, the wind began to gust to 17 knots. The student pilot stated that during the landing flare, he experienced a downwash and that the airplane ballooned and turned to the right. He added power and applied rudder, but the nosewheel hit the runway and the airplane veered off the runway. The certified flight instructor placed a maximum wind limitation of 15 knots on the student pilot's initial solo endorsement.
Probable cause
The student pilot’s loss of airplane control while landing with gusting wind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA356
- Event ID
- 20100629X34423
- Case number
- CEN10CA356
- 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: investigation status. 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: aac035bf21a7398deac1ab4fcac2ca26aa1c406bed318a7edc157ac2948f225f; retrieved 2026-09-15T14:32:32.157Z.