NTSB CAROL · Event
Event GAA16CA449
Aircraft involved
Probable cause & findings
The flight instructor's failure to go-around and the subsequent long landing and his failure to maintain directional control, which resulted in a runway excursion.
Factual narrative
The flight instructor reported that during a Civil Air Patrol evaluation flight, he decided to demonstrate a power off landing to the pilot being evaluated. The flight instructor further reported that the airplane touched down within the first 400 feet of the 2,160-foot runway and reported that the brakes were ineffective during the landing roll. The pilot witness who observed the landing from the left seat reported that he observed heavy braking, some swerving, a loss of control, and the airplane exited the left side of the runway near the departure end of the runway. During the runway excursion, the airplane nosed over and sustained substantial damage to the fuselage, empennage, and the right wing lift strut. In a Civil Air Patrol online system, the pilot witness reported that over the runway threshold the airspeed was 84 knots, the altitude was 20 feet, and the airplane touchdown zone was 1/2 to 2/3 down the runway, with 1000 feet of runway remaining. The local flight school provided video surveillance of the landing. The video showed the airplane still airborne while in the camera frame, which was about 700 feet past the runway threshold. The airplane subsequently moved out of camera view and was still airborne. The video did not show the airplane touch down on the runway. In a post-accident examination four days after the accident by the Federal Aviation Administration (FAA), both brakes were found to be functional. In a post-accident inspection almost two weeks after the accident by the repair mechanic, it was revealed that the left brake was working, but the right brake was "full of air." The mechanic reported that when the airplane was upside down air can enter into the hydraulic system, so "all bets are off". The mechanic further reported that there were no flat or bald spots on the tires. The flight instructor reported that during a Civil Air Patrol evaluation flight, he decided to demonstrate a power off landing to the pilot being evaluated. The flight instructor further reported that the airplane touched down within the first 400 feet of the 2,160-foot runway and reported that the brakes were ineffective during the landing roll. The pilot witness who observed the landing from the left seat reported that he observed heavy braking, some swerving, a loss of control, and the airplane exited the left side of the runway near the departure end of the runway. During the runway excursion, the airplane nosed over and sustained substantial damage to the fuselage, empennage, and the right wing lift strut. In a Civil Air Patrol online system, the pilot witness reported that over the runway threshold the airspeed was 84 knots, the altitude was 20 feet, and the airplane touchdown zone was 1/2 to 2/3 down the runway, with 1000 feet of runway remaining. The local flight school provided video surveillance of the landing. The video showed the airplane still airborne while in the camera frame, which was about 700 feet past the runway threshold. The airplane subsequently moved out of camera view and was still airborne. The video did not show the airplane touch down on the runway. In a post-accident examination four days after the accident by the Federal Aviation Administration (FAA), both brakes were found to be functional. In a post-accident inspection almost two weeks after the accident by the repair mechanic, it was revealed that the left brake was working, but the right brake was "full of air." The mechanic reported that when the airplane was upside down air can enter into the hydraulic system, so "all bets are off". The mechanic further reported that there were no flat or bald spots on the tires. 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 Personnel issues-Task performance-Use of equip/info-Aircraft control-Instructor/check pilot - C
- C Personnel issues-Action/decision-Action-Lack of action-Instructor/check pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained - C
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Capability exceeded
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA16CA449.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 (loss of control, runway excursion, go-around). 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.
- Embry-Riddle Scholarly Commons 2017 · Conference paper
Energy Safety Management: Mitigating Loss of Control Inflight
Under the new Airman Certification Standards (ACS), the Federal Aviation Administration (FAA) has mandated for the first time that private and commercial pilot candidates demonstrate understanding of …
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- 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…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
Browse the full corpus — academia portal ↗