CEN13CA087 · Cessna 150F
Call One Cessna 150F · Accident: loss of control in flight during landing
From Shenandoah Municipal Airport (SDA) to Red Oak Municipal Airport (RDK)
Event
- NTSB case
- CEN13CA087
- 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 150F
- Aircraft type
- Cessna 150
- 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
- N8000S
- Operator
- Call One
- Onboard fatalities
- Unknown
- Route
- From Shenandoah Municipal Airport (SDA), Shenandoah, IATo Red Oak Municipal Airport (RDK), Red Oak, IA
- 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 student pilot was on the third leg of a VFR solo cross country flight. His intent was to do a touch-and-go landing and then return to his initial departure airport. During his first and second approaches, he executed go-around maneuvers due to what he described as turbulence when the airplane came into ground effect. During the third approach, he landed to the left of centerline and the airplane began to skid to the left. The student pilot stated that he applied the wrong rudder correction and the airplane went off the runway. He added power to try to pull up and the right wing stalled. The left wing hit the ground and the airplane came to rest nose down in a bean field adjacent to the runway. Both wings sustained substantial damage. The student pilot had a total of 25 flight hours in the airplane, with 4.2 hours as pilot-in-command (solo). The wind was calm at the time of the accident. Postaccident examination of the airplane did not reveal any evidence of preimpact mechanical malfunction or abnormalities.
Probable cause
The loss of control while landing due to the solo student pilot's delay to execute a go-around and his improper control inputs during a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13CA087
- Event ID
- 20121203X43852
- Case number
- CEN13CA087
- 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, 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: 7e546671d516f05c5e4603c9415e0235ea09783db681c3feee024ce3d5149e7e; retrieved 2026-09-15T20:30:56.503Z.