Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

July 2, 2010 · Cirrus Design SR22 · N220WJ

Burnsville, NC

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
July 2, 2010
Injury Outcomes
No injuries (3 uninjured)
Location
Burnsville, NC
Aircraft
Cirrus Design SR22
Tail Number
N220WJ
Operator
Xt Applications
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA10CA343

The pilot reported that he was low on the final approach to runway 32 at the mountaintop airport, but thought he could "make the numbers." The airplane encountered a downdraft, and the pilot wasn't able to compensate for it. The airplane impacted terrain about 3 feet short of the runway, bounced, then veered off the right side of the runway and struck an embankment, resulting in substantial damage to the right wing and fuselage. The pilot also stated that there was a 7-knot tailwind "from the right," and that the density altitude was about 6,300 feet at the time of the accident. The flight was the pilot’s seventh arrival into the airport, and his first time landing there with a tailwind. There were no preaccident mechanical anomalies noted with the airplane, which "was performing great." According to the airport's pilot manual, runway 32 was the preferred landing runway due to its upslope and fewer obstructions at the arrival end. There was no displaced threshold, and the terrain rose sharply to the approach end of the runway. A visual glideslope indicator was located to the left of the runway. The pilot's manual also advised, "consider flying a steeper approach to compensate for the 'burble' downdraft typically present at the end of the runway," and noted that the hills on either side and the runway's upslope "will combine to produce the optical illusion of being too steep an approach path." The manual further stated, "consider carefully the effects of density altitude on the performance of your aircraft," as well as, "many pilots will not consider landing with SSE winds, and will simply divert" to another airport.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C

Full Narrative

The pilot reported that he was low on the final approach to runway 32 at the mountaintop airport, but thought he could "make the numbers." The airplane encountered a downdraft, and the pilot wasn't able to compensate for it. The airplane impacted terrain about 3 feet short of the runway, bounced, then veered off the right side of the runway and struck an embankment, resulting in substantial damage to the right wing and fuselage. The pilot also stated that there was a 7-knot tailwind "from the right," and that the density altitude was about 6,300 feet at the time of the accident. The flight was the pilot’s seventh arrival into the airport, and his first time landing there with a tailwind. There were no preaccident mechanical anomalies noted with the airplane, which "was performing great." According to the airport's pilot manual, runway 32 was the preferred landing runway due to its upslope and fewer obstructions at the arrival end. There was no displaced threshold, and the terrain rose sharply to the approach end of the runway. A visual glideslope indicator was located to the left of the runway. The pilot's manual also advised, "consider flying a steeper approach to compensate for the 'burble' downdraft typically present at the end of the runway," and noted that the hills on either side and the runway's upslope "will combine to produce the optical illusion of being too steep an approach path." The manual further stated, "consider carefully the effects of density altitude on the performance of your aircraft," as well as, "many pilots will not consider landing with SSE winds, and will simply divert" to another airport.

Flight

Event TypeAccident
Event Time13:10 EDT
Nearest AirportMountain Air Airport (0nm)
Runway32
Runway Length2900 ft
Runway Width50 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCirrus Design SR22
Tail NumberN220WJ
Aircraft CategoryAir
DamageSubstantial
OperatorXt Applications
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · IO-550 SERIES · Reciprocating · 300
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 55 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingBroken clouds 4000 ft
Temperature / Dew Point54
Altimeter30.30 inHg
Observation Time16:54
Weather SourceWFAC

Appendix: Source Data