The U.S. aircraft register, updated daily
Accidents · NTSB CEN26LA100 · Preliminary: the investigation is not finished

Piper Aircraft INC PA 46-350P accident near Sioux City, Iowa, January 24, 2026

On January 24, 2026 at about 1:12 pm local time, a 2014 Piper Aircraft INC PA 46-350P, registered N91MK, was substantially damaged in an accident during takeoff near Sioux City, Iowa. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
January 24, 2026 · about 1:12 pm local time · cases in 2026
Place
Sioux City, Iowa · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper Aircraft INC PA 46-350P, built 2014
Registration
N91MK · registry record · serial 4636647
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On January 24, 2026, about 0712 central daylight time, a Piper PA-46-350P airplane, N91MK, was substantially damaged when it was involved in an accident near Sioux City, Iowa. The pilot and passenger were uninjured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that after the initial climb and immediately after leveling off at 2,500 ft mean sea level, he felt the airplane make two “thugs” and observed the manifold pressure fluctuate. He subsequently observed a drop in engine oil pressure. He stated that he told the Air Traffic Control tower controller that he was going to turn back toward the airport. Once the airplane was on a north heading, a loud “boom” was heard, and a subsequent loss of engine power occurred. The pilot executed a forced landing to a field. During the forced landing, the airplane’s engine and left wing impacted terrain and were separated. The forward fuselage and right wing sustained substantial damage. The pilot stated that on a previous flight, four days before the accident flight, a similar “thug” was observed, but it did not result in any other abnormal indications. The wreckage was retained for further examination.

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. Loss of engine power (partial) during takeoff defining event

The aircraft

  • Seats: 6
  • Landing gear: fixed
  • Operator: Mulaii LLC

Weather at the time

  • Light: night, dark
  • Wind: from 140° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: -6°F (-21°C), dew point -17°F (-27°C)
  • Altimeter: 30.61 inHg
  • Observation at 6:52 am from KSUX, 1 miles away

Weather report (METAR): METAR KSUX 241252Z 14003KT 10SM CLR M21/M27 A3061 RMK AO2 SLP398 T12061267=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Other NTSB records under N91MK the same tail number, which may have belonged to a different aircraft at the time

2009-04-24ERA09LA263 · accident near Demopolis, AL · substantial damage · fatal

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN26LA100.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.