FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA17CA079 · Cessna 172 M

20 Nov 2016 · Dayton, TN, United States

Consolidated Aviation Services Cessna 172 M · Accident: wildlife encounter (non-bird) during landing

From Knoxville Downtown Island Airport (DKX) to Mark Anton Airport (2A0)

Report a problem

Event

NTSB case
GAA17CA079
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 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
N4331R
Onboard fatalities
Unknown
Route
From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Mark Anton Airport (2A0), Dayton, TN
Aircraft age
About 42 years (built 1974)
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 · flare/touchdown
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
Wildlife encounter (non-bird)
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 › Physical environment

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

According to the student pilot, the single-engine airplane was configured in a crab profile during the landing. After the flare, the airplane settled into ground effect and a deer then approached the airplane from the left and struck the left main landing gear. The pilot initiated a go-around, but the left wing struck the ground. The airplane landed hard on the nose landing gear, the nose landing gear collapsed, and the airplane slid to a stop after exiting the runway to the right. The firewall sustained substantial damage.

The airport facility directory stated that deer were present on and near the airport.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The student pilot’s inability to maintain pitch and bank control during the landing after the airplane was struck by a deer.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA17CA079
Event ID
20161128X25519
Case number
GAA17CA079
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: 69c84c7fd889bea203cdc826c069f400bf2d7209e0d8ae28de407c86ed422619; retrieved 2026-09-16T04:51:39.723Z.