The U.S. aircraft register, updated daily
Accidents · NTSB ERA24LA140 · Final report

Cirrus Design CORP SR20 accident near Logan, West Virginia, March 15, 2024

On March 15, 2024 at about 8:27 pm local time, a 2012 Cirrus Design CORP SR20, registered N312DD, was substantially damaged in an accident during landing (landing roll) near Logan, West Virginia (Logan County airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 3 others were unhurt. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 15, 2024 · about 8:27 pm local time
Place
Logan, West Virginia · Logan County · map
Type
Accident
Injuries
1 person had minor injuries; 3 others were unhurt.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Cirrus Design CORP SR20, built 2012
Registration
N312DD · registry record · serial 2153
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during landing (landing roll) defining event
  2. Landing area overshoot during landing
  3. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)

The NTSB's findings

  • Personnel issues › Action/decision › Action › Delayed action › Pilot
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 714 hours in all; 565 in this make and model; 28 in the last 90 days; 16 in the last 30 days; 691 as pilot in command
  • Last flight review: February 1, 2024
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

Passenger

  • Seat: left
  • Injury: no injuries

Passenger

  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,217 hours
  • Last inspection: annual inspection, January 12, 2024; 24 hours since
  • Maximum gross weight: 3,150 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental IO-360-ES (piston); 3,217 hours total

The flight

  • Departed from: GMU Greenville SC at 6:56 pm
  • Destination: 6L4 Logan WV
  • Flight plan: IFR
  • Runway 06, 3,605 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 290° at 8 knots, gusting 14
  • Visibility: 1 statute miles
  • Sky: broken clouds at 800 ft; a few clouds at 300 ft
  • Temperature: 57°F (14°C), dew point 57°F (14°C)
  • Altimeter: 29.89 inHg
  • Observation at 4:35 pm from K6L4

Weather report (METAR): K6L4 152035Z AUTO 29008G14KT 220V320 1 3/4SM RA FEW003 BKN008 OVC014 14/14 A2989 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers3

Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on March 12, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download
2 Memorandum for the Record - FAA Inspector PDF, 1 page View Download
3 Weather Report PDF, 1 page View Download
4 Weather radar Depiction PDF, 1 page View Download
5 Excerpts from FAA Aircraft Accident Package - ATC Timeline PDF, 2 pages View Download
6 Google Earth File of ADS-B Plot map file Download
7 ADS-B Data spreadsheet Download
8 Investigation Photographs PDF, 4 pages · our copy View Download
9 Electronic Devices - Specialist's Factual Report PDF, 20 pages View Download
10 Electronic Devices - Specialist's Factual Report - ATTACHMENT1 - Rdm Tabular Data data file Download
11 Electronic Devices - Specialist's Factual Report - ATTACHMENT2 - G1000 Tabular Data data file Download
12 Wreckage Release and Evidence Control Forms PDF, 3 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.