# NTSB ERA10CA343: Cirrus Design SR22, N220WJ, Burnsville, NC, July 2, 2010 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: July 2, 2010, 13:10 local (17:10 UTC) - Place: Burnsville, NC - Coordinates: 35.86861, -82.341667 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.8686&lon=-82.3417&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-flare/touchdown: Landing area undershoot](https://openairdocs.org/ntsb-events/370) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report December 20, 2010 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO, Cirrus Aircraft - NTSB case key (mKey): 76513 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10CA343 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76513/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76513 - Page: https://openairdocs.org/ntsb/ERA10CA343 ## Probable cause The pilot's failure to maintain a proper visual glideslope during final approach. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cirrus Design SR22, 14 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2130001), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Wind: tailwind](https://openairdocs.org/ntsb-findings/03034015): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cirrus Design SR22, 9 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md?model=2130001), [All aircraft, 594 cases](https://openairdocs.org/ntsb-findings/03034015/cases.md) - [Temp/humidity/pressure: high density altitude](https://openairdocs.org/ntsb-findings/03031020): Environmental issues › Conditions/weather/phenomena · Effect on operation; cases with it: [Cirrus Design SR22, 3 cases](https://openairdocs.org/ntsb-findings/03031020/cases.md?model=2130001), [All aircraft, 278 cases](https://openairdocs.org/ntsb-findings/03031020/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cirrus Design SR22, 13 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=2130001), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Landing area undershoot](https://openairdocs.org/ntsb-events/370) (defining event); cases with it: [Cirrus Design SR22, 4 cases](https://openairdocs.org/ntsb-events/370/sequence.md?model=2130001), [All aircraft, 201 cases](https://openairdocs.org/ntsb-events/370/sequence.md) - [Landing-flare/touchdown: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cirrus Design SR22, 113 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2130001), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## 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](https://openairdocs.org/deregistered/N220WJ-2013-09-20), registration cancelled 2013-09-20, S/N 0823, built 2004 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR22 - Registry model: [Cirrus Design SR22](https://openairdocs.org/model/cirrus-design-sr22) (registry code 2130001) (OpenAirDocs) - Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 0823 - Airframe hours: 794 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; 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 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20100702046369A](https://openairdocs.org/incident/20100702046369A), Jul 2, 2010: Cirrus Desi SR22, Burnsville, NC, Substantial damage. Aircraft was landing rwy 23 at Mountain Air, 2NC0. Impacted terrain with landing gear approximately three feet short of the pavement. The point of impact was… ## Docket (8 files) The files NTSB released with the investigation on August 23, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76513. 2.0 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 151 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333076&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Memorandum for Record - Phone Interview with Pilot (item 2, .PDF, 76 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333454&FileExtension=.PDF&FileName=Memorandum%20for%20Record%20-%20Phone%20Interview%20with%20Pilot-Redacted.PDF - Landing Performance Data and Calculations (item 3, .PDF, 702 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333696&FileExtension=.PDF&FileName=Landing%20Performance%20Data%20and%20Calculations-Master.PDF - Excerpts from Pilot's Operating Handbook (item 4, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333305&FileExtension=.PDF&FileName=Excerpts%20from%20Pilot%27s%20Operating%20Handbook-Master.PDF - Mountain Air Country Club Pilot's Manual (item 5, .PDF, 607 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333608&FileExtension=.PDF&FileName=Mountain%20Air%20Country%20Club%20Pilot%27s%20Manual-Redacted.PDF - Statement of Party Representatives to NTSB Investigation (item 6, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333094&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Photo 1: Airplane At Rest (Photo courtesy of FAA) (item 7, .PDF, 208 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333078&FileExtension=.PDF&FileName=Photo%201%3A%20Airplane%20At%20Rest%20(Photo%20courtesy%20of%20FAA)-Master.PDF - Photo 2: Initial Impact Point (Photo courtesy of Pilot) (item 8, .PDF, 117 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333077&FileExtension=.PDF&FileName=Photo%202%3A%20Initial%20Impact%20Point%20(Photo%20courtesy%20of%20Pilot)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.