FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA304 · Cessna 120

10 Jun 2016 · Climax, NC, United States

Cessna 120 · Accident: wildlife encounter (non-bird) during landing

From Siler City Municipal Airport (SCR) to Greensboro Executive Airport (3A4)

Report a problem

Event

NTSB case
GAA16CA304
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 120

Aircraft type
Cessna 120
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
N77216
Operator
Unknown
Onboard fatalities
Unknown
Route
From Siler City Municipal Airport (SCR), Siler City, NCTo Greensboro Executive Airport (3A4), Climax, NC
Aircraft age
About 70 years (built 1946)
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
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

  • Environmental issues › Physical environment

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

NTSB narrative

The pilot reported that following a day visual meteorological condition flight, during the landing roll, two deer jumped onto the runway and he swerved the airplane to the right off of the runway, avoiding both deer. During the runway excursion, the right main landing gear became caught in tall grass and the airplane nosed over. The airplane sustained substantial damage to the fuselage, vertical stabilizer, and both wings.

The pilot did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.

During a postaccident interview with the airport manager, he reported that the airport does not a have a perimeter fence.

Probable cause

An evasive maneuver during the landing roll to avoid deer on the runway, which resulted in a runway excursion and a nose over. Contributing to the accident was the lack of an airport perimeter fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA304
Event ID
20160613X30919
Case number
GAA16CA304
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: 6146bacc95ea39de8ee7c6eefd7a916ef1de409b64ba67244259fb66a343a47f; retrieved 2026-09-16T03:30:03.297Z.