NTSB CAROL · Event
Event GAA16CA445
Registry · N91025
FAA Aircraft Registry record.
Make / Model
CESSNA T207
Year of manufacture
1969 · 47 years old at event
Engine
CONT MOTOR TSIO-520 SER (300 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
20110909
ADS-B equipped
Yes — Mode-S AC9967
Registrant of record
ARCTIC AVIATION LEASING LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s unstabilized approach and a subsequent runway overrun while landing on a short runway in variable wind conditions.
Factual narrative
The pilot reported that during landing the wind sock at the airport indicated that the wind was variable, about 5 knots, and predominately favored runway 1. According to the FAA airport facility directory, runway 01/19 was 1,850 feet long, and soft gravel. However, 1,000 feet of northern portion of the runway was closed indefinitely. The pilot recalled that about 500 feet down the 1850 foot runway, and just before touchdown the airplane encountered, "a pretty rapid shift in the winds in both direction and velocity." He reported that the airplane touched down momentary, and then went airborne again. After the second touchdown, the speed did not decline as expected, and although the airplane did start to slow as it got a better grip on the gravel (which was wet from rain that had occurred earlier), he ran out of runway. He reported that the airplane overran the runway at a groundspeed of about 10 knots, went down a small embankment, had a propeller strike and the airplane sustained substantial damage when the left wing struck a post. The pilot reported that there were no mechanical malfunctions or anomalies during the flight that would have prevented normal flight operations. The pilot reported that he considered going around, but due to the wind and terrain rejected the idea. The pilot reported that during landing the wind sock at the airport indicated that the wind was variable, about 5 knots, and predominately favored runway 1. According to the FAA airport facility directory, runway 01/19 was 1,850 feet long, and soft gravel. However, 1,000 feet of northern portion of the runway was closed indefinitely. The pilot recalled that about 500 feet down the 1,850 foot runway, and just before touchdown the airplane encountered, "a pretty rapid shift in the winds in both direction and velocity." He reported that the airplane touched down momentarily, and then went airborne again. After the second touchdown, the speed did not decline as expected, and although the airplane did start to slow as it got a better grip on the gravel (which was wet from rain that had occurred earlier), he ran out of runway. He reported that the airplane overran the runway at a groundspeed of about 10 knots, went down a small embankment, had a propeller strike and the airplane sustained substantial damage when the left wing struck a post. The pilot reported that there were no mechanical malfunctions or anomalies during the flight that would have prevented normal flight operations. The pilot reported that he considered going around, but due to the wind and terrain rejected the idea. 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-Pilot - C
- C Aircraft-Aircraft oper/perf/capability-Aircraft capability-Landing distance-Not attained/maintained - C
- C Environmental issues-Conditions/weather/phenomena-Wind-Variable wind-Effect on equipment - C
- — Environmental issues-Physical environment-Object/animal/substance-Pole-Contributed to outcome
- — Environmental issues-Physical environment-Runway/land/takeoff/taxi surface-Wet surface-Effect on operation
Verbatim from NTSB's published report. Source file
NTSB_2016_GAA16CA445.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 (unstabilized approach). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
Utilizing Deep Learning to Predict Unstabilized Approaches for General Aviation Aircraft
Unstabilized approaches pose a major hazard for general aviation aircraft. In the period from 2009 to 2019, 3,257 general aviation accidents occurred during the landing phase of flight in which loss o…
- NTSB Aircraft Accident Reports 2014 · Accident report
Crash during a Nighttime Nonprecision Instrument Approach — UPS 1354
UPS Flight 1354 (A300-600F) Birmingham AL, August 14, 2013. Investigation of UPS 1354 crash short of runway 18 at Birmingham.
Browse the full corpus — academia portal ↗