# NTSB ERA26FA178: Mooney M20J, N205MK, Ironton, OH, April 17, 2026 - Type: NTSB accident investigation - Classification: Accident · Fatal · Class 3 · Field · Preliminary report - Date: April 17, 2026, 14:14 local (18:14 UTC) - Place: Ironton, OH - Coordinates: 38.572461, -82.808467 - Nearby events: https://openairdocs.org/map.md?lat=38.5725&lon=-82.8085&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Fatal - Injuries: 1 fatal - Status: Investigation ongoing - Investigation class: Class 3 - NTSB office: Eastern Region Aviation - Parties: Textron Lycoming, FAA/FSDO - NTSB case key (mKey): 202840 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA26FA178 - NTSB preliminary report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/202840/pdf - Page: https://openairdocs.org/ntsb/ERA26FA178 ## Preliminary report On April 17, 2026, about 1414 eastern daylight time, a Mooney M20J, N205MK, was destroyed when it was involved in an accident near Ironton, Ohio. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Airport security video captured a portion of the takeoff roll from runway 28 at Ashland Regional Airport (DWU), Ashland, Kentucky, followed by rotation about 3,218 ft before the departure end of the runway. A pilot-rated witness who was sitting on a bench outside the door of a fixed-base operator reported that after the airplane rotated it flew in ground effect with the landing gear retracted. He added that the airplane was, “not really climbing”, which he thought was odd, but the flight “did climb some” when it reached the departure end of the runway, but not as much as he expected. He then lost sight of the airplane. After takeoff, the flight proceeded in a westerly direction flying over the Ohio River. A security camera installed at a business on the north side of the Ohio river about 2 nautical miles from the departure end of runway 28, or about .3 nautical mile east of electrical powerlines that spanned the Ohio river captured the airplane flying for about 5 seconds at a low altitude with the landing gear retracted. DWU Virtower ADS-B data revealed that the airplane was flying at an altitude of about 600 ft mean sea level (msl), 130 knots ground speed, and descending at 300 ft per minute, immediately before the location of electrical transmission lines that crossed the Ohio River. Immediately after the electrical transmission lines, or at 1413:32, the airplane was flying at an altitude of about 700 ft msl, 110 knots ground speed, and climbing at 3,200 ft per minute. Further review of the Virtower ADS-B data revealed that after passing the electrical transmission lines, the airplane changed heading to the right, slowed initially and descended slightly, then proceeded in a northwesterly direction with the airplane’s ground speed gradually decreasing while maintaining altitude. The last data point at 1414:03, showed the airplane at an altitude of 500 ft msl, 70 knots ground speed and descending at a rate of 700 ft per minute. One witness near the accident site reported seeing the airplane pitch up before impacting an open field behind houses. Another witness reported hearing a loud engine noise, followed by the sounds of impact and a subsequent fireball and explosion. The initial ground contact was located about 450 ft from the last Virtower ADS-B target. The wreckage came to rest upright near a tree line, about 3 nautical miles from the departure end of runway 28 at DWU. The cockpit, cabin, and inboard sections of both wings exhibited extensive postcrash fire damage. Further examination of the wreckage revealed the upper section of the vertical stabilizer and the upper portion of the rudder from the middle hinge up including the rudder counterweight were separated and notrecovered. ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Low altitude operation/event](https://openairdocs.org/ntsb-events/220); cases with it: [Mooney M20J, 1 case](https://openairdocs.org/ntsb-events/220/sequence.md?model=5870219), [All aircraft, 780 cases](https://openairdocs.org/ntsb-events/220/sequence.md) - [Initial climb: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Mooney M20J, 4 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=5870219), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) - [Initial climb: Part(s) separation from AC](https://openairdocs.org/ntsb-events/338); cases with it: [Mooney M20J, 1 case](https://openairdocs.org/ntsb-events/338/sequence.md?model=5870219), [All aircraft, 563 cases](https://openairdocs.org/ntsb-events/338/sequence.md) - [Emergency descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20J, 41 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870219), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-flare/touchdown: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Mooney M20J, 8 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=5870219), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing-landing roll: Dragged wing/rotor/float/other](https://openairdocs.org/ntsb-events/093); cases with it: [Mooney M20J, 3 cases](https://openairdocs.org/ntsb-events/093/sequence.md?model=5870219), [All aircraft, 319 cases](https://openairdocs.org/ntsb-events/093/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Mooney M20J, 41 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=5870219), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Post-impact: Fire/smoke (post-impact)](https://openairdocs.org/ntsb-events/170); cases with it: [Mooney M20J, 1 case](https://openairdocs.org/ntsb-events/170/sequence.md?model=5870219), [All aircraft, 354 cases](https://openairdocs.org/ntsb-events/170/sequence.md) - [Post-impact: Explosion (post-impact)](https://openairdocs.org/ntsb-events/180); cases with it: [Mooney M20J, 1 case](https://openairdocs.org/ntsb-events/180/sequence.md?model=5870219), [All aircraft, 47 cases](https://openairdocs.org/ntsb-events/180/sequence.md) ## Aircraft - Registration: [N205MK](https://openairdocs.org/aircraft/N205MK), registered now, S/N 24-3029, built 1987 (OpenAirDocs) - Reported make and model: MOONEY M20J (NO SERIES EXISTS) - Registry model: [Mooney M20J](https://openairdocs.org/model/mooney-m20j) (registry code 5870219) (OpenAirDocs) - Registry engine: [Lycoming I0360 SER A&C](https://openairdocs.org/engine/lycoming-i0360-ser-a-c) (registry code 41511, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 24-3029 - Year built: 1987 - Damage: Substantial damage - Fire: On-Ground - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Airport: DWU, Ashland Regional Airport - Equipment: Stall warning system, ADS-B ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Temperature: 81 °F, dew point 52 °F - Altimeter: 30.03 inHg - Observed at: KDWU, 3 nm away - METAR: METAR KDWU 171756Z AUTO VRB03KT 10SM FEW070 27/11 A3003 RMK AO2 SLP165 T02670106 10272 20128 58014 $ ## 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 20260417008029A](https://openairdocs.org/incident/20260417008029A), Apr 17, 2026: Mooney M20J, Ironton, OH, Destroyed, 1 fatal. On April 17, 2026, [privacy data omitted] Mooney M20J departed under VFR conditions from ashland, KY (kdwu) enroute to salina, KS (ksal) from runway 28. Video… 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.