# NTSB ERA24LA140: Cirrus Design SR20, N312DD, Logan, WV, March 15, 2024 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Class 3 · Limited · Final report - Date: March 15, 2024, 16:27 local (20:27 UTC) - Place: Logan, WV · Off departure end of runway 6 - Coordinates: 37.855686, -81.915883 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.8557&lon=-81.9159&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: Minor injuries - Injuries: 1 minor, 3 uninjured - Status: Completed, report March 12, 2026 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 193948 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA24LA140 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/193948/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=193948 - Page: https://openairdocs.org/ntsb/ERA24LA140 ## Probable cause The pilot’s delayed decision to perform a go-around while attempting to land on a wet runway with a tailwind, which resulted in a runway overrun and collision with trees. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cirrus Design SR20, 15 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2130000), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [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 SR20, 6 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=2130000), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing: Landing area overshoot](https://openairdocs.org/ntsb-events/380); cases with it: [Cirrus Design SR20, 4 cases](https://openairdocs.org/ntsb-events/380/sequence.md?model=2130000), [All aircraft, 400 cases](https://openairdocs.org/ntsb-events/380/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cirrus Design SR20, 22 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2130000), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cirrus Design SR20, 39 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2130000), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot was attempting to land on a 3,605-ft-long, wet asphalt runway, with a left quartering tailwind at 4 to 8 knots. The airplane touched down long and fast, and the pilot believed the airplane was not slowing enough, so he applied heavier braking. The airplane then began to yaw left and was still not slowing enough. He believed that they were going to go off the departure end of the runway, so he attempted a go-around near the end of the runway. The airplane did not climb and traveled off the end of the runway, down a ravine, and struck trees before coming to rest upright. The pilot added that there were no preimpact mechanical malfunctions with the airplane and he likely encountered an adverse wind while landing. ## Factual narrative On March 15, 2024, about 1627 eastern daylight time, a Cirrus Design Corporation SR20 airplane, N312DD, was substantially damaged when it was involved in an accident near Logan, West Virginia. The pilot received minor injuries and the three passengers were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The flight had departed Greenville Downtown Airport (GMU), Greenville, South Carolina, about 1456, destined for Logan County Airport (6L4), Logan, West Virginia. According to the pilot, while landing at 6L4, he attempted to stop the airplane with normal braking. In his judgment, he believed the airplane was not slowing enough, so he applied significantly more braking. The airplane then began to yaw left and was still not slowing. He believed that they were going to go off the departure end of the runway, so he decided to abort the landing. He released the brakes, aligned the airplane with the runway, and applied full power. He estimated that he was near the runway numbers at the departure end when he applied power. As best as he could tell, the airplane never got above the runway elevation as it went off the runway into a ravine. The stall warning sounded, so he lowered the nose to prevent a stall/spin. The left wing then caught something, which threw them sideways; they then impacted another solid object, spinning them backward. The airplane came to rest facing in the opposite direction of travel. The engine came to rest about 50 feet away, further down the ravine. After ensuring everyone was in good condition, they called 911 and exited the aircraft. The pilot added that there were no preimpact mechanical malfunctions with the airplane and that he likely encountered an adverse wind while landing. 6L4 was located at an elevation of 1,664 feet. Information provided by an FAA inspector revealed skid marks in the grass area beyond the runway’s departure end that were consistent with the airplane touching down, leaving the paved surface of the runway, then traveling along the ground approximately 321 feet on its landing gear and dropping off the airport surface, which was about 36 feet above the surrounding terrain. It then traveled another 244 feet before clearing the airport perimeter fence, and shortly thereafter struck trees. Review of air traffic control data provided by the FAA indicated that, before landing at 6L4, the pilot had requested an area navigation (RNAV) approach for runway 24. The pilot then advised that he had received the local weather information. He then requested the RNAV approach for runway 6. The air traffic controller then pointed out areas of precipitation in the area, which the pilot acknowledged. He was later cleared for the approach. 6L4 was equipped with an automated weather observing system (AWOS), which reported the following conditions during the period surrounding the accident: At 1615, the 6L4 AWOS reported a wind from 270° at 4 knots, visibility of 8statute miles, scattered clouds at 900 feet above ground level (agl), ceiling broken at 1,500 feet agl, overcast clouds at 2,300 feet agl, temperature of 15°C, dew point temperature of 14°C, and an altimeter setting of 29.89 in Hg. At 1635, the 6L4 AWOS reported a wind from 290° at 8 knots with gusts to 14 knots, variable wind direction between 220° and 320°, visibility of 1 and 3/4 statute miles, moderate rain, few clouds at 300 feet agl, ceiling broken at 800 feet agl, overcast clouds at 1,400 feet agl, temperature of 14°C, dew point temperature of 14°C, altimeter setting of 29.89 in Hg. Review of meteorological radar data also indicated that about the time of the accident, 6L4, was under light to heavy precipitation. The radar data indicated that the area of precipitation had been approaching from the west-northwest. Review of data downloaded from the airplane’s remote data module (RDM) did not reveal evidence of any preimpact mechanical malfunctions The RDM data indicated that, at 1627:04, the airplane was about 500 feet beyond the approach threshold of runway 6, at 25 ft agl, at a groundspeed of 89 knots. It touched down about 5 seconds later, at a groundspeed of 85 knots. ## Aircraft - Registration: [N312DD](https://openairdocs.org/aircraft/N312DD), registered now, S/N 2153, built 2012 (OpenAirDocs) - Reported make and model: CIRRUS DESIGN CORP SR20 - Registry model: [Cirrus Design SR20](https://openairdocs.org/model/cirrus-design-sr20) (registry code 2130000) (OpenAirDocs) - Registry engine: [Continental IO-360-ES](https://openairdocs.org/engine/continental-io-360-es) (registry code 17160, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 2153 - Year built: 2012 - Airframe hours: 3217 - Engines: Continental IO-360-ES 200 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 12, 2024, 24 hours before - Departed: GMU, Greenville, SC - Destination: 6L4, Logan, WV - Flight plan: IFR - Airport: 6L4, Logan County, runway 06, 3,605 × 75 ft, asphalt - Equipment: Auto-pilot, Electronic multifunction display, Airframe parachute, ADS-B, Stall warning system, Onboard weather, Electronic primary flight display ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; injuries: minor; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, with waivers/limitations; last flight review February 1, 2024; seat: left; restraint: 4-point; flight hours: 714 total, 565 in this make and model, 691 as pilot in command, 28 in the last 90 days, 16 in the last 30 days ## Weather - Conditions: Instrument (IMC), Day - Wind: 290° at 8 knots, gusting 14 - Visibility: 1 statute miles - Lowest ceiling: 800 ft broken - Temperature: 57 °F, dew point 57 °F - Altimeter: 29.89 inHg - Observed at: K6L4 - METAR: K6L4 152035Z AUTO 29008G14KT 220V320 1 3/4SM RA FEW003 BKN008 OVC014 14/14 A2989 RMK AO2 ## 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 20240315002309A](https://openairdocs.org/incident/20240315002309A), Mar 15, 2024: Cirrus Design Corp SR20, Logan, WV, Substantial damage. The pilot requested the RNAV rwy 6 approach at 6L4 and did not recognize that there was a strong tailwind. He arrived at the initial fix 1200 feet above the… ## Docket (12 files) The files NTSB released with the investigation on March 12, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=193948. 18.4 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 11 pages, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19796618&FileExtension=pdf&FileName=6210_Redacted-Rel.pdf - Memorandum for the record - FAA inspector (item 2, PDF, 1 page, 72 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19798889&FileExtension=pdf&FileName=MFR-Rel.pdf - Weather report (item 3, PDF, 1 page, 119 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19798708&FileExtension=pdf&FileName=Metars-Rel.pdf - Weather radar depiction (item 4, PDF, 1 page, 360 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19798607&FileExtension=pdf&FileName=Weather%20Radar-Rel.pdf - Excerpts from FAA aircraft accident package - ATC timeline (item 5, PDF, 2 pages, 552 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19799088&FileExtension=pdf&FileName=FAA%20Accident%20Package%20Excerpt-Rel.pdf - Google earth file of ADS-B plot (item 6, KMZ, 352 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19798831&FileExtension=kmz&FileName=20240315_A34E8E_543474375-Rel.kmz - ADS-B data (item 7, XLSX, 9.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19798718&FileExtension=xlsx&FileName=20240315_A34E8E_543474375_ADSB-Rel.xlsx - Investigation photographs (item 8, PDF, 4 pages, 3 photos, 799 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19806161&FileExtension=pdf&FileName=Investigation%20Photographs-Rel.pdf - Electronic devices - specialist's factual report (item 9, PDF, 20 pages, 12 photos, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18124651&FileExtension=pdf&FileName=Electronic%20Devices%20-%20Specialist%27s%20Factual%20Report-Rel.pdf - Electronic devices - specialist's factual report - ATTACHMENT1 - rdm tabular data (item 10, CSV, 61 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18111114&FileExtension=csv&FileName=Electronic%20Devices%20-%20Specialist%27s%20Factual%20Report%20-%20Attachment1%20-%20RDM%20Tabular%20Data-Rel.csv - Electronic devices - specialist's factual report - ATTACHMENT2 - G1000 tabular data (item 11, CSV, 28 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18112319&FileExtension=csv&FileName=Electronic%20Devices%20-%20Specialist%27s%20Factual%20Report%20-%20Attachment2%20-%20G1000%20Tabular%20Data-Rel.csv - Wreckage release and evidence control forms (item 12, PDF, 3 pages, 928 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19796495&FileExtension=pdf&FileName=Wreckage%20And%20Evidence_Redacted-Rel.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.