CEN10CA033 · Cessna 172N
Cessna 172N · Accident: loss of control on ground during landing
From The Ohio State University Airport - Don Scott Field (OSU) to The Ohio State University Airport - Don Scott Field (OSU)
Event
- NTSB case
- CEN10CA033
- 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 172N
- 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
- N4753D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From The Ohio State University Airport - Don Scott Field (OSU), Columbus, OHTo The Ohio State University Airport - Don Scott Field (OSU), Columbus, OH
- 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 · landing roll
- 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 on ground
- 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
While on a solo flight, the student pilot was attempting to land on runway 09 when the airplane exited the left side of the runway onto a grassy median. The airplane sustained damage to the landing gear and firewall during the accident. In a statement to law enforcement officers, the pilot reported that he was landing in a crosswind which pushed the airplane to the left. He stated that he was unable to control the drift of the airplane and the left wheel entered the grass and pulled the airplane into the grass. He remarked that the damage to the airplane happened when it struck a bump in the grass near the taxiway at about 20 knots. The recorded winds at a nearby airport were 180 degrees at 8 knots about 30 minutes prior to the accident.
Probable cause
The student pilot's failure to maintain directional control during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA033
- Event ID
- 20091030X72236
- Case number
- CEN10CA033
- 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: 148df4ad1f1b1f07edfe53d8e35c0da9c824a89f6e6538ac1efc0c038cc71966; retrieved 2026-09-15T13:27:16.128Z.