FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19FA212 · Cessna 172 R

6 Jul 2019 · Oxford, MS, United States

Civil Air Patrol Cessna 172 R · Accident: loss of control in flight on approach

From Golden Triangle Regional Airport (GTR) to University Oxford Airport (UOX)

Report a problem

Event

NTSB case
CEN19FA212
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
1 · 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 R

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
N994CP
Onboard fatalities
Unknown
Route
From Golden Triangle Regional Airport (GTR), Columbus/W Point/Starkville, MSTo University Oxford Airport (UOX), Oxford, MS
Aircraft age
About 22 years (built 1997)
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
Approach · VFR go-around
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

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 student pilot was conducting a solo cross-country flight and was heard on the common traffic advisory frequency announcing her intention to land at the destination airport. A witness at the airport indicated that the pilot's voice sounded "panicked" and that she did not finish her sentences. The pilot did not respond to a request for the airplane’s location from a helicopter in the area. The witness saw the airplane approach the runway with a tailwind present. Additionally, recorded wind was consistent with a quartering tailwind. The airplane did not touch the runway and about midfield, started to climb at a "steep" angle. The witness indicated that he did not hear any engine anomalies. He stated that the airplane veered toward the golf course and then went "straight down behind the trees."

A witness at the golf course first saw the airplane above the trees and stated that it appeared to be "struggling" to maintain airspeed, was nose up, and appeared to be “very close to stalling.” The witness indicated that the airplane then made a hard left turn and lost altitude, struck the ground, and slid to nearby trees. A ground fire subsequently occurred.

Postaccident examination of the wreckage and engine revealed migration of molten metal under the No. 4 exhaust valve. However, no preimpact anomalies that would have prevented normal operation of the airplane were detected. The flap jackscrew did not exhibit any thread extension, which is consistent with retracted flaps.

Based on the available information, it is likely that the student pilot did not maintain airplane control during an attempted go-around with a tailwind, and the airplane subsequently impacted terrain during an uncontrolled descent.

Probable cause

The student pilot's failure to maintain airplane control during a go around with a tailwind, which resulted in an uncontrolled descent and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19FA212
Event ID
20190706X70756
Case number
CEN19FA212
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, cause areas. 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: 30ff3acbc5e8fdb5860717eb5aa940657c925105f3882bb70a3d41f7050bac0c; retrieved 2026-09-15T07:01:31.567Z.