- Date
- July 2, 2010, 13:10 local (17:10 UTC)
- Place
- Burnsville, NC
- Injuries
- 3 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N220WJCirrus Design SR22
- Defining event
- Landing-flare/touchdown: Landing area undershoot
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO, Cirrus Aircraft
- FAA report
- 20100702046369A
- Case key
- 76513
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The pilot's failure to maintain a proper visual glideslope during final approach.
Findings · 4
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
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.
Factual 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.
Aircraft
- Registration
- N220WJ
- Reported as
- Cirrus Design SR22
- Category
- Airplane
- Serial number
- 0823
- Airframe hours
- 794
- Engine
- Cont Motor IO-550 SERIES, 300 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Operator
- Xt Applications LLC
- Registered owner
- Xt Applications LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · July 1, 2010
- Departed
- KHEF · Manassas, VA
- Destination
- 2NC0 · Burnsville, NC
- Flight plan
- IFR
- Airport
- 2NC0 · Mountain Air Airport, runway 32, 2,900 × 50 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 55
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- February 27, 2010
- Seat
- Left
- Flight hours
- 393 total · 207 in this make and model · 330 as pilot in command · 17 in the last 90 days · 12 in the last 30 days · 3 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Visibility
- 10 statute miles
- Lowest ceiling
- 4,000 ft broken
- Temperature
- 72 °F, dew point 54 °F
- Altimeter
- 30.30 inHg
- Observed at
- KAVL, 28 nm away
Docket · 8
The files NTSB released with the investigation on August 23, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.0 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.