CEN12CA361 · Cessna 172H
Cessna 172H · Accident: runway excursion during takeoff
From Greensfield Airport (M71) to Greensfield Airport (M71)
Event
- NTSB case
- CEN12CA361
- 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 172H
- 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
- N3736R
- Operator
- Sydney Grgurich
- Onboard fatalities
- Unknown
- Route
- From Greensfield Airport (M71), Moscow Mills, MOTo Greensfield Airport (M71), Moscow Mills, MO
- 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
- Takeoff · rejected takeoff
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that she took off on runway 27 with the wind from 180 degrees at 13 knots gusting to 23 knots. When the airplane was about 5 to 10 feet above the runway, the airplane encountered a strong gust of wind, and the airplane drifted left of centerline and descended back onto the runway. The pilot steered the airplane back to the centerline and attempted to abort the takeoff by applying full brakes and pulling the throttle back to idle. The airplane went off the end of the 3,227 foot long runway onto wet grass and continued down an embankment, across a road, and into a steep ditch. The airplane’s firewall sustained substantial damage. The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.
Probable cause
The pilot's failure to maintain control of the airplane during takeoff in a gusty crosswind, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12CA361
- Event ID
- 20120612X61430
- Case number
- CEN12CA361
- 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: 9de27d47bd656d63c4c4e119325378eacfb40fea35684ce714f7304144a05ed9; retrieved 2026-09-15T18:28:53.224Z.