NTSB CAROL · Event
Event ERA15CA302
Registry · N206DZ
FAA Aircraft Registry record.
Make / Model
CESSNA 206
Engine
CONT MOTOR IO 520 SERIES (285 hp)
Seats / Engines
6 seats · 1 engine
Last airworthiness date
19800514
ADS-B equipped
Yes — Mode-S A1A8B0
Registrant of record
EVANS DAVID J
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's landing with a tailwind at an excessive speed, which resulted in a runway excursion, and collision with a ditch.
Factual narrative
The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch.An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight. The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident. The pilot stated that he was conducting a skydiver "jump run", and prior to letting the skydivers out the radio squelch interrupter failed causing a constant static noise. After letting the skydivers out over the airport the pilot set up the descent based on the winds acquired for the previous landing on runway 22. As he circled for landing the manifold pressure indication "dropped off" to zero. The pilot was unsure if he had a partial power loss or a gauge failure. He could not hear or feel the engine indications because of the static noise on the radio squelch and descent profile, so he committed to a power off glide path for his approach. The pilot stated that the airplanes approach speed was about 100 knots prior to the threshold for landing. The airplane touched down beyond the threshold and as the pilot applied full braking the airplane "ballooned" back into the air. The pilot attempted to stop the airplane but was unsuccessful and exited the runway, coming to rest after colliding with a ditch. An examination of the airplane revealed that the empennage and firewall was buckled during the landing sequence. The airplane was equipped with a JPI engine monitor and review of the data did not reveal a loss in engine power during the flight. The wind reported from a nearby weather station revealed that winds were 010 degrees at 6 knots at the time of the accident. 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 oper/perf/capability-Performance/control parameters-Airspeed-Incorrect use/operation - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
- — Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2015_ERA15CA302.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 ↗