ERA24LA140

NTSB accident investigation · Cirrus Design SR20 · Logan, WV · March 15, 2024

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
March 15, 2024, 16:27 local (20:27 UTC)
Place
Logan, WV · Off departure end of runway 6
Injuries
1 minor, 3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N312DDCirrus Design SR20
Defining event
Landing-landing roll: Runway excursion
Weather
Instrument (IMC) · Day
Status
Completed · report March 12, 2026
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20240315002309A
Case key
193948

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 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 · 2

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.

Action: delayed actionPersonnel issues › Action/decision · PilotCirrus Design SR20: 15 casesAll aircraft: 894 casesProbable cause
Performance/control parameters: descent/approach/glide pathAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR20: 6 casesAll aircraft: 809 casesProbable cause

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 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
Reported as
Cirrus Design SR20
Category
Airplane
Serial number
2153
Built
2012
Airframe hours
3,217
Engine
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

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
59
Injuries
Minor
Certificate
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

Docket · 12

The files NTSB released with the investigation on March 12, 2026, on NTSB’s docket system: statements, records, photos and specialists’ reports. 18.4 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.