GAA17CA055
2016-10-30 · Bristow, Virginia, United States · Minor · 1 aircraft · Status: Completed
Airport HEF
N781MA has since been reassigned. It is now registered to a different aircraft (BOEING CO C-135FR), which was not involved in this event.
Aircraft involved
Probable cause & findings
The pilot’s loss of directional control during a landing attempt at night, which resulted in a delayed go-around procedure and subsequent impact with terrain. Contributing to the accident was the pilot’s lack of recent flight experience.
Factual narrative
According to the pilot, after multiple previous landings that night to runway 34L, he reported that the airplane was thrown "off course" after it encountered a crosswind. The pilot pulled the power off briefly during the landing and the airplane touched down. However, he reported that he made a late decision to go-around and reapplied the power in hopes of establishing a climb. The airplane was "off course" at a low airspeed, and he applied full power; but he panicked and reduced his right rudder application and the airplane veered to the left. The airplane stalled and impacted the ground, the nose landing gear became imbedded in the mud and the airplane nosed over and came to rest inverted. The airplane sustained substantial damage to the left wing root, and empennage. According to the airport security camera video, the airplane descended over runway 34L, and made an immediate sharp left turn 270° to the left of the runway heading, and rapidly ascended. After the sharp left turn, the airplane was airborne for about 534 ft. before impacting the ground and nosing over. White paint transfer markings observed on the runway surface, and damage to the airplane's left wing indicated that the airplane had impacted the runway surface during the accident sequence. About 25 minutes prior to the accident, the published METAR for the accident airport reported that the wind was out of 320° true at 6 knots. There were no reported wind gusts at the time of the accident, and there were no published wind gusts at the airport for the remainder of the day. The pilot reported that he has 99 hours of total flight time, 78 hours in the accident airplane make and model, and a total of 4 hours of flight time within the last 90 days prior to the accident. The pilot reported that there were no pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation. According to the pilot, after multiple previous landings that night to runway 34L, the airplane was thrown "off course" after it encountered a crosswind. The pilot pulled the power off briefly during the landing, and the airplane touched down. However, he reported that he made a late decision to go around and reapplied the power to establish a climb. He added that the airplane was "off course" at a low airspeed and that he applied full power, but he panicked and reduced his right rudder application, and the airplane veered to the left. The airplane stalled and impacted the ground, the nose landing gear became embedded in the mud, and the airplane nosed over and came to rest inverted. The airplane sustained substantial damage to the left wing root and empennage. According to the airport security camera video, the airplane descended over runway 34L and made an immediate sharp left 270° turn to the left of the runway heading and rapidly ascended. After the sharp left turn, the airplane was airborne for about 534 ft before impacting the ground and nosing over. White paint transfer markings observed on the runway surface and damage to the airplane's left wing indicated that the airplane had impacted the runway surface during the accident sequence. About 25 minutes before the accident, the published METAR for the accident airport reported that the wind was from 320° at 6 knots. There were no reported wind gusts at the time of the accident, and there were no published wind gusts at the airport for the remainder of the day. The pilot reported that he had 99 hours of total flight time, 78 hours of which were in the accident airplane make and model, and 4 hours of which were within the 90 days before the accident. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- C Environmental issues-Conditions/weather/phenomena-Light condition-Dark-Effect on personnel - C
- C Personnel issues-Action/decision-Action-Delayed action-Pilot - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- F Personnel issues-Experience/knowledge-Experience/qualifications-Recent experience-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA17CA055.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (stall, go-around). All research papers
- NASA NTRS 2026 · Conference Paper Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- arXiv 2023 · arXiv preprint Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…