ERA10CA343 · Cirrus Design Corp SR22
XT Applications Cirrus Design Corp SR22 · Accident: landing area undershoot
From Washington Manassas Harry P. Davis Field (KHEF) to Mountain Air Airport (2NC0)
Event
- NTSB case
- ERA10CA343
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cirrus Design Corp SR22
- Aircraft type
- Cirrus SR22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N220WJ
- Operator
- XT Applications
- Onboard fatalities
- Unknown
- Route
- From Washington Manassas Harry P. Davis Field (KHEF), Manassas, VATo Mountain Air Airport (2NC0), Burnsville, NC
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Landing area undershoot
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
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.
Probable cause
The pilot's failure to maintain a proper visual glideslope during final approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA343
- Event ID
- 20100702X94829
- Case number
- ERA10CA343
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 67b83d0cd8f8799b4646835dfa8c12d30c72e928a8310ba36715279c993080ea; retrieved 2026-09-15T14:35:56.425Z.