CEN16CA070 · Cessna 172 M
Hawk Aviation Cessna 172 M · Accident: runway excursion during landing
From Rush City Regional Airport (ROS) to Rush City Regional Airport (ROS)
Event
- NTSB case
- CEN16CA070
- 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
- 0
- 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 172 M
- 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
- N1180U
- Operator
- Hawk Aviation
- Onboard fatalities
- Unknown
- Route
- From Rush City Regional Airport (ROS), Rush City, MNTo Rush City Regional Airport (ROS), Rush City, MN
- Aircraft age
- About 39 years (built 1976)
- 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
- Runway excursion
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot was completing his first solo flight and had already done eight takeoffs and landings. On the ninth landing, the airspeed was higher than normal and the airplane porpoised. When the airplane touched down the student pilot applied excessive right rudder. The airplane veered right and departed the right side of the runway into the soft wet ground. The airplane nosed into the mud and then came to rest upright. The left wing impacted the ground and was substantially damaged. The operator reported there were no pre-impact mechanical failures or malfunctions with the airframe that would have precluded normal operation.
Probable cause
The student pilot did not maintain directional control of the airplane and applied excessive right rudder during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16CA070
- Event ID
- 20151228X35743
- Case number
- CEN16CA070
- 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: 7d67d7c9b7a3e04a08549132c0915c016fc558ebcf15bcd9d4394951af92825c; retrieved 2026-09-16T03:03:30.372Z.