FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA396 · Cessna 150 L

27 Jul 2016 · Williamsburg, VA, United States

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

From Williamsburg Jamestown Airport (JGG) to Williamsburg Jamestown Airport (JGG)

Report a problem

Event

NTSB case
GAA16CA396
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 150 L

Aircraft type
Cessna 150
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
N18228
Operator
Unknown
Onboard fatalities
Unknown
Route
From Williamsburg Jamestown Airport (JGG), Williamsburg, VATo Williamsburg Jamestown Airport (JGG), Williamsburg, VA
Aircraft age
About 43 years (built 1973)
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)
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

  • Environmental issues › Physical environment

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

NTSB narrative

The solo student pilot reported that during a day visual meteorological condition flight, in the landing flare he saw a deer where he intended to touch down. He further reported that he banked to the right and applied power to go-around, but during the turn to the right he was unable to clear a line of trees in his flight path. The student pilot reported that the landing gear "scraped" one line of trees, and in order to avoid a thicker line of trees ahead, he forced the airplane down into a marsh area.

The fuselage and both wings sustained substantial damage.

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

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

The Federal Aviation Administration Chart Supplement airport page for the accident airport in part states: "Deer and birds on and invof [in the vicinity of] arpt."

Probable cause

An evasive maneuver during the landing flare to avoid deer on the runway, which resulted in a collision with trees and terrain during a go-around. 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 GAA16CA396
Event ID
20160728X85058
Case number
GAA16CA396
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: aadae94775055061342046c057ac1efc5cb6d5eca7af15d25363b06683c1ae0c; retrieved 2026-09-16T03:43:00.422Z.