FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26FA172 · Beechcraft F33A

25 Apr 2026 · Minneapolis, MN, United States

Beechcraft F33A · Accident: loss of control in flight during initial climb

Report a problem

Event

NTSB case
CEN26FA172
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
Ongoing
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
0
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

Beechcraft F33A

Aircraft type
Beechcraft 33
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
N8032X
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 35 years (built 1991)
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
Initial climb
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN26FA172
Event ID
20260425202884
Case number
CEN26FA172
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • 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. 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: c4daa4eae20f76e1fe2ff6790669655f07aadf14dddb2e499114f7aca88c7ae7; retrieved 2026-09-15T09:15:21.493Z.