GAA17CA012 · Cessna 172 N
Cessna 172 N · Accident: loss of control in flight during landing
From City of Murfreesboro Airport (MBT) to Ocean Springs Airport (5R2)
Event
- NTSB case
- GAA17CA012
- 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 172 N
- 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
- N3379E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From City of Murfreesboro Airport (MBT), Murfreesboro, TNTo Ocean Springs Airport (5R2), Ocean Springs, MS
- Aircraft age
- About 38 years (built 1978)
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that during landing the airplane "was pushed violently and unexpectedly to the right". She further reported that she immediately tried to correct with rudder, aileron and power inputs simultaneously. The airplane continued to drift farther to the right of the centerline and contacted several trees along the edge of the airport before the airplane landed nose first onto the runway.
The airplane sustained substantial damage to both wings and the fuselage.
The pilot reported that there were no pre impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
The pilot reported that the wind at the accident airport was 020 degrees true and 12 nautical miles per hours (knots), and that she was landing on runway 36. The nearest weather reporting station, 9 miles to the northwest, reported wind 360 degrees true and 15 knots.
Probable cause
The pilot's failure to maintain airplane control while landing in windy conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA17CA012
- Event ID
- 20161011X22742
- Case number
- GAA17CA012
- 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: 377de4ce5ee5da112c1e7cd3381597d8f0a3b087a1d3b80940d02df55e28f98b; retrieved 2026-09-16T04:22:36.269Z.