Aviation Crash Map

Beechcraft F33A N8032X

25 April 2026 · Minneapolis, Minnesota, United States · Fatal

Summary

On 25 April 2026 at about 16:51 local time, a Beechcraft F33A registered N8032X was involved in an accident near Minneapolis, Minnesota, United States. 2 people were on board and 2 died. The aircraft was destroyed. No probable cause has been published yet; this accident is still under investigation.

The record

Date
at 16:51
Classification
Accident
Location
Minneapolis, Minnesota, United States
Nearest airport
Crystal Airport (KMIC)
Coordinates
45.0667, -93.3618
Aircraft
Beechcraft F33A
Registration
N8032X
Category
Airplane
Year built
1991
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Aircraft damage
Destroyed
Weather
VMC
Light
Day
NTSB number
CEN26FA172

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

Probable cause

The NTSB has not published a probable cause for this record. The investigation is still open; a final report usually follows one to two years after the accident.

Nothing about the cause is stated here that is not in the source record.

Read the full NTSB narrative

On April 25, 2026, about 1151 central daylight time, a Beechcraft F33A airplane, N8032X was destroyed when it was involved in an accident near Minneapolis, Minnesota. The pilot and passenger were fatally injured. The airplane was operated under Title 14 Code of Federal Regulations Part 91 as a personal flight. The day before the accident, the pilot flew the airplane from Park Rapids Municipal Airport-Konshok Field (PKD) Park Rapids, Minnesota, to Crystal Airport (MIC) Minneapolis, Minnesota. The pilot filled the airplane with 18.7 gallons of 100 LL aviation fuel after landing at MIC. According to the pilot’s son, the pilot and his passenger were flying back to PKD when the accident occurred. Air traffic control (ATC) cleared the pilot to depart runway 32 at MIC and climb out on runway heading. The pilot correctly read back the instructions, and the airplane departed runway 32. A recording of ATC communications revealed that, shortly after the airplane departed runway 32, the pilot said, “abort, abort, 32X.” Air traffic control told the pilot that he was cleared to land on any runway. Airport video surveillance captured the airplane turn left before it descended behind trees. Shortly after, a large plume of black smoke appeared from behind the tree line. The airplane impacted a park within a residential community about 900 ft northwest of the departure end of runway 32. A postimpact fire ensued. Four video cameras at and around the airport captured audio and video of the airplane. The first video camera mounted on the side of a hangar on the north side of MIC captured the airplane take off and climb out. The airplane’s wings were level as it climbed out. A video camera on a residential structure across the street from the park captured the impact sequence. The airplane’s engine is heard before the airplane comes into frame. The engine sound gets louder the closer the airplane gets to the camera. The airplane comes into the frame then impacts trees and then the ground at a near vertical nose down attitude. A video camera on the other side of the same property captured the airplane bank to the left before it impacted the trees. A fourth video camera from a residential structure on the departure end of runway 32 captured the airplane fly over the property and then turn left before it disappeared from the frame. In all four videos, the engine sound can be heard. Two witnesses who were at the airport on the day of the accident said they saw the airplane at the time it departed. The first witness was on the north side of the airport when he noticed the airplane. He said it was about 150 ft in the air, and he thought it was unusual that the landing gear was still down when the airplane was that high on the departure. Then he saw the airplane make a left turn. He thought that the airplane was returning to the airport, but then he saw the airplane lose altitude. He lost sight of the airplane but could still hear the airplane’s engine. Then he heard an explosion. The second witness had just landed his airplane and was taxiing his airplane to the fuel pump when he saw the accident airplane takeoff. He reported that the takeoff did not seem abnormal; however, he thought the airplane looked low and was not climbing. Control cable continuity for the elevator and the ailerons were traced back to the control column. Both elevator trim tab actuators measured about 1.7 in, which equated to 15° trailing edge down (nose up position.) Only the right flap track was observed, and both flap rollers were in the retracted position. Rudder control cable continuity was established from the rudder to the left cockpit bellcrank. Control cable continuity was established for the autopilot cables and bridal attach points. One of the videos that captured the airplane just before impact showed that the landing gear was down. The postaccident examination of the airplane confirmed that the landing gear was down upon impact. The nosewheel detached in the accident sequence and was found about 40 ft away from the main wreckage. The left and right main landing gear were still attached to the fuselage and were thermally damaged. All fuel lines were damaged, but the fuel selector was on the right tank. When the engine was being lifted for transport, oil, gold in color, leaked from the engine. The engine driven fuel pump was removed, and the drive coupling was intact. All b-nut fittings on the flexible fuel hoses were tight. The spark plugs were removed and appeared to be unremarkable. Crankshaft continuity was established using the thumb compression method. All cylinders were borescoped and were unremarkable. The fuel metering valve and throttle assembly were thermally damaged. The fuel injector nozzles were unremarkable. The fuel manifold was disassembled and the liquid inside was consistent in smell with 100 LL aviation gas. The screen was free of debris. Both magnetos supplied a spark to all terminals when rotated. The 3-bladed constant speed propeller separated from the crankshaft flange, and all blades exhibited polishing and chordwise scratches. Two of the blades were bent and/or twisted. The airplane was retained for further examination.

Quoted verbatim from the NTSB record.

Other Beechcraft F33A accidents

Date Aircraft Location Operator Outcome Died
24 Apr 2026 Beechcraft F33A
N85WM
Sanford, North Carolina, United States - No injuries -
20 Jul 2026 Beechcraft F33A
N933A
Janesville, Wisconsin, United States - No injuries -
16 May 2025 Beechcraft F33A
N6376S
Houston, Texas, United States - No injuries -
30 Jul 2024 Beechcraft F33A
N8121N
Lincoln, Nebraska, United States - No injuries -
6 May 2023 Beechcraft F33A
N2294L
Tahlequah, Oklahoma, United States - Serious injuries -
6 Feb 2023 Beechcraft F33A
N1074W
Hilbert, Wisconsin, United States - No injuries -

All 147 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
23 Feb 2026 Piper PA-28RT-201
N279SR
Glencoe, Minnesota, United States Metro Aircraft Co No injuries -
26 Jun 2026 Airborne Windsports EDGE XT-912-L
N912CV
Winona, Minnesota, United States - Fatal 1
30 Jun 2026 Beechcraft A36
N8095F
Paynesville, Minnesota, United States Brown DR JAY No injuries -
4 Jul 2026 Piper PA-25-235
N386AB
Forest Lake, Minnesota, United States Plane and Simple Leasing LLC No injuries -
9 Jul 2026 Garza Charles Frank GLASAIR I RG
N141CG
Utica, Minnesota, United States
no coordinates
- Serious injuries -
1 Jun 2026 Piper PA-28-235
N15291
Montevideo, Minnesota, United States - Minor injuries -

All 170,864 records in United States