NTSB CAROL · Event
Event ERA16LA322
Aircraft involved
Probable cause & findings
An uncommanded flap retraction for reasons that could not be determined, as a postaccident examination of the flap system did not reveal evidence of any preaccident anomalies.
Factual narrative
On September 23, 2016, at 1215 eastern daylight time, an Aero Vodochody L39, N139AJ, was substantially damaged after it impacted trees during a runway excursion while landing at Hampton Roads Executive Airport (PVG), Norfolk, Virginia. The private pilot was not injured. Visual meteorological conditions prevailed, and no flight plan had been filed for the personal flight that was operated under the provisions of 14 Code of Federal Regulations Part 91.According to the pilot, the airplane was on final approach to runway 28, about 100 ft above ground level and 60 ft from the runway threshold, when there was an "uncommanded" retraction of the flaps. He adjusted the pitch of the airplane and advanced the throttle in order to compensate for the flap retraction. The airplane touched down on the paved surface of the runway, the pilot applied the brakes, and then he applied the emergency brake. As the airplane began to veer toward the side of the runway, the pilot released the emergency brake, and continued to apply the brakes utilizing the brake pedals. The pilot stated that the "normal" braking action was insufficient to keep the airplane from over-running the runway. The airplane continued off the departure end of the runway, struck trees, and came to rest about 1,050 feet from the end of runway 28, which was a 5,350-ft-long runway. An examination of the runway revealed that skid marks from the airplane began around 1,000 ft prior to the departure end of the runway and continued into the area where the airplane came to rest. According to Federal Aviation Administration (FAA) records, the airplane was issued an experimental exhibition airworthiness certificate on December 12, 2007. It was powered by a Ivchenko, AI-25TL engine. According to the pilot, the most recent condition inspection was performed on September 1, 2016, at an airframe total time of 3,016.9 total hours. According to the emergency checklist located in the airplane, it was equipped with an emergency flap extension system. The pilot did not mention using the emergency flap extension system during the accident sequence. An examination of the flap system, under the oversight of an FAA inspector, revealed that there were no disconnects or abnormalities in the flap mechanical actuation system besides the impact damage, which prevented a test of the flap system. The flap actuator was intact and no evidence of hydraulic leakage was noted. The emergency flap extension handle located to the right of the pilot's seat was moved without anomaly. A review of the accident airplane's flight manual revealed, under the conditions that existed at the time of the accident, that the landing ground roll distance was approximately 2,000 feet, and was based on the circumstances of idle engine power, full flaps, and the speedbrakes retracted. According to the private pilot of the jet trainer airplane, the airplane was on final approach for landing about 100 ft above ground level and 60 ft from the runway threshold, when there was an "uncommanded" retraction of the flaps. He adjusted the airplane's pitch and advanced the throttle in order to compensate for the flap retraction, increasing the airspeed from 90 knots to 130 knots. The airplane touched down on the runway and the pilot applied the brake pedals, followed by the emergency brake. As the airplane began to veer toward the side of the runway, the pilot released the emergency brake and continued to apply brakes using the brake pedals. The airplane continued off the departure end of the runway, struck trees, and came to rest about 1,050 ft from the end of the 5,350ft-long runway. While impact-related damage prevented a functional test of the airplane's normal and emergency flap extension systems, an examination of the flap system components revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. It is likely that the airplane's increased speed at the time of touchdown resulted in the runway excursion. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Aircraft-Aircraft structures-Wing structure-Trailing edge flaps-Malfunction - C
Verbatim from NTSB's published report. Source file
NTSB_2016_ERA16LA322.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (runway excursion). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Runway Excursion — SKYbrary Knowledge Base
SKYbrary runway excursion review — RE-OE (overruns) + RE-LO (lateral). Risk drivers: long landing, high approach speed, contaminated surface, tailwind, mis-set autobrakes.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- NASA NTRS 2025 · Presentation
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- NASA NTRS 2025 · Conference Paper
Uncovering Resilient Behavior in the Aviation Safety Reporting System Using Large Language Models
Resiliency is present in everyday life, both in system design and exhibited by the operators that function within these systems.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Runway Safety Initiative Final Report (RSI)
Foundation Runway Safety Initiative final report — comprehensive analysis of runway excursion + incursion risk drivers worldwide.
- Semantic Scholar 2020 · Article
Towards online prediction of safety-critical landing metrics in aviation using supervised machine learning
Abstract In recent years, due to the increased availability of data and improvements in computing power, application of machine learning techniques to various aviation safety problems for identifying,…
Browse the full corpus — academia portal ↗