FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA235 · Cessna 182P

14 May 2016 · Williamsburg, VA, United States

Cessna 182P · Accident: loss of control in flight during landing

From Williamsburg Jamestown Airport (JGG) to New Kent County Airport (W96)

Report a problem

Event

NTSB case
GAA16CA235
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 182P

Aircraft type
Cessna 182
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
N58625
Operator
Unknown
Onboard fatalities
Unknown
Route
From Williamsburg Jamestown Airport (JGG), Williamsburg, VATo New Kent County Airport (W96), QUINTON, 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
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
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

According to the pilot, shortly after he climbed above the tree tops during the takeoff initial climb, he determined that he was uncomfortable flying in the gusting wind conditions. He reported that he completed one traffic pattern and made an approach to runway 31. He recalled that during the landing flare, the airplane encountered a wind gust and was blown to the right, and off of the runway. The pilot reported that the airplane touched down in the safety area on the right side of the runway and the airplane impacted a drainage culvert where it came to rest. The airplane sustained substantial damage to the firewall and the right wing spar.

The pilot reported that there were not any pre-accident mechanical failures or anomalies with the airplane that would have precluded normal operation prior to the accident.

The meteorological aerodrome report at the accident airport reported: KJGG 141915Z AUTO 28013G18KT 220V300 10SM CLR 28/12 A2972 RMK AO1

Probable cause

The pilot's failure to maintain directional control during the landing in variable direction and gusting wind conditions, resulting in a landing off the side of the runway and impact with a drainage culvert.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA235
Event ID
20160517X15930
Case number
GAA16CA235
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: 3df2953fba70de809b9e49a7b01ccfd8c9f0d55dff13d840ea246e4eaffc2a94; retrieved 2026-09-16T03:23:49.477Z.