CEN24LA357 · Diamond DA42 NG
Diamond DA42 NG · Accident: runway excursion during landing
From Bismarck Municipal Airport (BIS) to Mandan Municipal Airport (Y19)
Event
- NTSB case
- CEN24LA357
- 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
- Event fatalities
- Unknown
- 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
Diamond DA42 NG
- Aircraft type
- Diamond DA42
- 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
- N705JP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bismarck Municipal Airport (BIS), Bismarck, NDTo Mandan Municipal Airport (Y19), Mandan, ND
- Aircraft age
- About 7 years (built 2017)
- 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 · landing roll
- 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
- Runway excursion
- 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
- Environmental issues › Conditions/weather/phenomena
- 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 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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN24LA357
- Event ID
- 20240913195117
- Case number
- CEN24LA357
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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, cause areas. 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: 3877347066c48cc7d1a8f5cd8eff199a816202691132349412de940b5c95aa44; retrieved 2026-09-16T19:16:07.162Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: departure. Misspelled city; BIS is Bismarck Municipal Airport, Bismarck, ND.