Beechcraft F33A accident near Minneapolis, Minnesota, April 25, 2026
On April 25, 2026 at about 4:51 pm local time, a 1991 Beechcraft F33A, registered N8032X, was destroyed in an accident during initial climb near Minneapolis, Minnesota (Crystal Airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. 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
- April 25, 2026 · about 4:51 pm local time · cases in 2026
- Place
- Minneapolis, Minnesota · Crystal Airport · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Beechcraft F33A, built 1991 · all F33As on the register
- Registration
- N8032X · registry record · serial CE-1551
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
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.
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
- Loss of control in flight during initial climb defining event
The aircraft
- Maximum gross weight: 3,400 lb
- Seats: 5
- Landing gear: retractable
- Fire on the ground
The flight
- Flight plan: VFR
- Runway 32, 3,751 ft by 75 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: broken clouds at 11,000 ft
- Temperature: 55°F (13°C), dew point 28°F (-2°C)
- Altimeter: 30.01 inHg
- Observation at 12:00 pm from KMIC, 1 miles away
Weather report (METAR): METAR KMIC 251653Z 00000KT 10SM BKN110 13/M02 A3001 RMK AO2 SLP167 T01281022
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
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.
Connections how this case links to the rest of the register
- N8032X on the register today · the tail number may have moved to another aircraft since
- Beechcraft F33 Bonanza 1,008 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Crystal Airport · nearest airport
- Accidents and incidents in Minnesota 1,544 since 1982 · 209 in the last ten years
- Minnesota 6,969 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN26FA172.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.
