The U.S. aircraft register, updated daily
Accidents · NTSB ERA10CA343 · Final report

Cirrus Design CORP SR22 accident near Burnsville, North Carolina, July 2, 2010

On July 2, 2010 at about 5:10 pm local time, a Cirrus Design CORP SR22, registered N220WJ, was substantially damaged in an accident during landing (flare/touchdown) near Burnsville, North Carolina (Mountain Air Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to maintain a proper visual glideslope during final approach.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 2, 2010 · about 5:10 pm local time
Place
Burnsville, North Carolina · Mountain Air Airport · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22
Registration
N220WJ · no longer on the register · serial 0823
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area undershoot during landing (flare/touchdown) defining event
  2. Collision with terrain or object (not controlled flight into terrain) during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • Environmental issues › Conditions/weather/phenomena › Wind › Tailwind › Effect on operation
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Effect on operation
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 393 hours in all; 207 in this make and model; 17 in the last 90 days; 12 in the last 30 days; 330 as pilot in command
  • Last flight review: February 27, 2010
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 794 hours
  • Last inspection: annual inspection, July 1, 2010
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550 SERIES (piston); 0 hours total
  • Operator: Xt Applications LLC

The flight

  • Departed from: KHEF Manassas VA at 3:23 pm
  • Destination: 2NC0 Burnsville NC
  • Flight plan: IFR
  • Runway 32, 2,900 ft by 50 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: broken clouds at 4,000 ft
  • Temperature: 72°F (22°C), dew point 54°F (12°C)
  • Altimeter: 30.30 inHg
  • Observation at 4:54 pm from KAVL, 28 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.