CEN10CA467 · Cessna 152
Cessna 152 · Accident: collision with terrain/object (non-CFIT) during landing
From 3BS · Midland, MI to Breckenridge, MI (private airstrip)
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
- CEN10CA467
- 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 152
- Aircraft type
- Cessna 152
- 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
- N24472
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From 3BS · Midland, MITo Breckenridge, MI (private airstrip)
- 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
- 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
- Collision with terrain/object (non-CFIT)
- 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 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 was landing to the east on the turf runway. He said that there was a 5-knot, 90-degree crosswind from the north. He stated that he aborted two approaches when the airplane was over the runway because the crosswind was taking the airplane off course. On the third approach, the airplane touched down in the center of the runway. The pilot reported that the airplane became airborne again and he attempted to abort the landing. As he advanced the throttle, the airplane's left wing struck the corn crop along the left side of the runway. The airplane came to rest on the runway facing northwest. The pilot listed no mechanical malfunctions or failures of the airplane. The damage to the airplane included a bent right wing tip, bent propeller, and a buckled firewall.
Probable cause
The pilot's failure to mantain directional control during the aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA467
- Event ID
- 20100810X85131
- Case number
- CEN10CA467
- 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 2010-07-30.
- API snapshot SHA-256: 18a66a1b201c00fdecf9fba1eaf3b348e3cc6e915c53fc8416e4488f730fe71d; retrieved 2026-09-15T14:49:22.440Z.