CIRRUS DESIGN CORP SR22 near Burnsville, NC — 2010-07-02
- Date
- 2010-07-02
- Location
- Burnsville, NC, USA
- Airport
- 2NC0
- Aircraft
- CIRRUS DESIGN CORP SR22
- Registration
- N220WJ
- Category
- Airplane
- Highest injury
- None
- Fatalities
- 0
- Phase of flight
- Approach
Probable cause
The pilot's failure to maintain a proper visual glideslope during final approach.
NTSB 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.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Pilot could have diverted instead of attempting to land with tailwind.
NTSB coding
Evidence available
- Photos
- 8 docket documents
Docket documents8
- Landing Performance Data and Calculationsform
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Memorandum for Record - Phone Interview with Pilotinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Excerpts from Pilot's Operating Handbookother
- Mountain Air Country Club Pilot's Manualother
- Photo 1: Airplane At Rest (Photo courtesy of FAA)photos
- Photo 2: Initial Impact Point (Photo courtesy of Pilot)photos
Related mishaps
- SHOEMAKER RONALD R PAZMANY PL-2
2025-05-06 · Reading, PA
- CESSNA 150
2023-08-23 · Pink Hill, NC
- PIPER PA-32-260
2023-02-11 · Tok, AK
- TEXTRON AVIATION INC 172
2022-11-22 · Newnan, GA
- AIRBUS HELICOPTERS MBB-BK 117 C-2
2022-03-07 · Abingdon, VA
- CESSNA 120
2021-06-05 · Warwick, NY