CEN24LA357

NTSB accident investigation · Diamond DA42 · Mandan, ND · September 1, 2024

Accident · No injuriesClass 3 · LimitedFinal report
Date
September 1, 2024, 15:20 local (20:20 UTC)
Place
Mandan, ND
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N705JPDiamond DA42
Defining event
Landing-landing roll: Runway excursion
Weather
Visual (VMC) · Day
Status
Completed · report July 29, 2026
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Central Region
Parties
FAA - Fargo FSDO
FAA report
20240901012439A
Case key
195117

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 failure to perform a go-around following an unstable approach while landing with a tailwind, which resulted in the airplane touching down long on the runway with insufficient distance to stop. Contributing to the accident was the pilot’s selected flap setting which increased the airplane’s landing roll.

Findings · 4

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.

Wind: tailwindEnvironmental issues › Conditions/weather/phenomena · Effect on operationDiamond Aircraft Ind DA 42 NG: 1 caseAll aircraft: 594 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 estimated that he touched down about 100 ft past the numbers while landing. He attempted to decelerate, keeping constant pressure on the brakes. The pilot stated that the brakes were not working until he approached the end of the runway, at which point the brakes “slowly got responsive.” The pilot reported that a go-around was possible and that it was a “shock” that he couldn’t stop the airplane. He reported that the approach and landing was made with the flaps set to “APP.” The airplane exited the paved surface of the runway and impacted a runway end identifier light, resulting in substantial damage to the fuselage. A postaccident examination of the brake system revealed no anomalies that would have precluded normal operation, and a postaccident runway inspection by the airport manager revealed visible tire skid marks leading off the end of the runway. An aircraft performance study using ADS-B and engine control unit (ECU) data concluded that the airplane touched down at 92 kts calibrated airspeed (KCAS), 6 kts faster than the 86-kt VREF speed calculated from the airplane flight manual. The airplane’s weight on wheels sensors indicated that the airplane was not fully on the ground until 2,136 ft past the runway threshold. The airplane landed in a 6.3 kt tailwind that would have increased landing distance by 21%. Considering all factors, the study concluded that insufficient runway remained after the touchdown for the airplane to stop. Additionally, the study concluded that had the pilot used the LDG flap setting, there would have been sufficient runway remaining.

Factual narrative

On September 1, 2024, about 1520 central daylight time, a Diamond DA42 airplane, N705JP, sustained substantial damage when it was involved in an accident near Mandan, North Dakota. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he departed Bismark Municipal Airport (BIS) and requested vectors for the RNAV 31 approach at Mandan Regional Airport (Y19) from air traffic control. The pilot reported that his approach to Y19 was uneventful and estimated that he touched down about 100 ft past the numbers for runway 31. The pilot attempted to decelerate, keeping constant pressure on the brakes. The pilot stated that the brakes were not working until he approached the end of the runway, at which point the brakes “slowly got responsive.” The pilot stated that the pilot-rated passenger asked about conducting a go-around during the landing attempt, but the pilot was focused on stopping. The pilot reported that a go-around could have been possible and that it was a “shock” that he couldn’t stop the airplane. According to the pilot, he used a flap setting of 20°, or APP during the approach and landing. According to the pilot-rated passenger, the landing at Y19 was so smooth that he did not notice the airplane had touched down until the nose wheel shimmied. The passenger stated that the airplane appeared to touchdown within the first third of the 4399-ft runway and the landing roll seemed normal, but he did not feel as much deceleration as he expected. The airplane exited the paved surface of the runway and impacted a runway end identifier light, resulting in substantial damage to the fuselage. According to the airport manager, who examined the runway surface after the accident, there were visible tire skid marks leading off the end of the runway. A postaccident examination of the brake system revealed that the brakes appeared to function normally. There was no evidence of leaks at the hoses, calipers, or at the master cylinders attached to the rudder pedals. Brake application was firm and, with the brakes applied, would have prevented the movement of the airplane. The brake pads appeared to have adequate material left to not impede braking action. The right brake pads were worn more than the left, but not beyond the limit of function. An aircraft performance study using ADS-B and engine ECU data concluded that the airplane touched down at 92 kts calibrated airspeed, 6 kts faster than the 86-kt VREF speed calculated from the Airplane Flight Manual. The airplane’s weight on wheels (WOW) sensors indicated that the airplane was not fully on the ground until 2,136 ft past the runway threshold. The airplane was landed in a 6.3-kt tailwind that would have increased landing distance by 21%. Considering all factors, the study concluded that there was insufficient runway remaining after the touchdown for the airplane to stop. Additionally, the study concludedthat had the pilot used the LDG flap setting there would have been sufficient runway remaining. According to the AFM, ground roll distances for flaps LDG are about 73% of the ground roll distances for flaps APP/UP. If that ratio holds for the ground roll estimate above of 2,411 ft with flaps APP, the ground roll estimate for flaps LDG would be 1,760 ft. A ground roll of 1,760 ft would have allowed the airplane to stop on the runway.

Aircraft

Registration
N705JP
Reported as
Diamond DA42 (NG)
Category
Airplane
Serial number
42.N249
Built
2017
Airframe hours
500
Engines
Austro E4C, 153 horsepower, reciprocatingAustro E4C, 153 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · September 27, 2023
Departed
BIS · Bismark, ND
Destination
Y19 · Mandan, ND
Airport
Y19 · Mandan Rgnl/Lawler Fld, runway 13/31, 4,399 × 75 ft, concrete
Equipment
Electronic multifunction display, Auto-pilot, 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
78
Injuries
None
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Last flight review
November 17, 2023
Seat
Left
Restraint
3-point
Flight hours
1,153 total · 330 in this make and model · 996 as pilot in command · 12 in the last 90 days · 5 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
170° at 7 knots
Visibility
10 statute miles
Temperature
75 °F, dew point 48 °F
Altimeter
30.28 inHg
Observed at
KY19
METAR
KY19 012015Z AUTO 17007KT 10SM CLR 24/09 A3028 RMK AO2

Docket · 13

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