Piper PA-28-235 accident near Montevideo, Minnesota, June 1, 2026
On June 1, 2026, a 1972 Piper PA-28-235, registered N15291, was substantially damaged in an accident during approach (VFR pattern final) near Montevideo, Minnesota (Montevideo-Chippewa County airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power on approach due to carburetor icing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 1, 2026 · cases in 2026
- Place
- Montevideo, Minnesota · Montevideo-Chippewa County · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-235, built 1972 · all PA-28-235s on the register
- Registration
- N15291 · registry record · serial 28-7310031
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, while on final approach to the runway, the engine rpm began to run rough. The pilot applied carburetor heat, and the engine lost all power. The pilot attempted to restart the engine but was unsuccessful and prepared for a forced landing. The airplane touched down at the edge of a corn field and came to rest upright against a grass embankment. The airplane sustained substantial damage to the right wing and fuselage. Following the accident, the pilot stated that the loss of engine power was likely the result of carburetor icing. According to the airplane handbook, during approach and landing, carburetor heat should be off unless icing conditions exist. The weather conditions at the time of the accident were conducive to the formation of serious icing at glide engine power settings.
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 engine power (total) during approach (VFR pattern final) defining event
- Off-field or emergency landing during approach (VFR pattern final)
- Landing gear collapse during landing (flare/touchdown)
- Fuel related during approach (VFR pattern final)
The NTSB's findings
- Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to carburetor icing › Effect on equipment
- Personnel issues › Action/decision › Action › Lack of action › Pilot
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel control/carburetor › Not used/operated other cases naming the engine
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 453 hours in all; 48 in this make and model; 5.9 in the last 90 days; 1.6 in the last 30 days; 327 as pilot in command
- Last flight review: March 8, 2026
- Medical certificate: BasicMed
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 1,617 hours
- Last inspection: annual inspection, March 1, 2026
- Maximum gross weight: 3,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-540 (piston); 1,612 hours total
The flight
- Flight plan: none
- Runway 14/3, 3,999 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 140° at 12 knots
- Visibility: 10 statute miles
- Sky: scat at 11,000 ft
- Temperature: 64°F (18°C), dew point 61°F (16°C)
- Altimeter: 29.95 inHg
- Observation at 7:35 pm from KMVE
Weather report (METAR): METAR KMVE 010035Z AUTO 14012KT 10SM SCT110 18/16 A2995 RMK AO2
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them
The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on September 17, 2026. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Investigation Photographs | PDF, 3 pages · our copy | View Download |
| 3 | Memorandum for Record A�� Telephone Interview, Pilot | PDF, 1 page | View Download |
| 4 | POH Excerpt | PDF, 2 pages | View Download |
| 5 | Carburetor Icing Probability Graph | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N15291 on the register today · the tail number may have moved to another aircraft since
- Piper PA-28 Cherokee, Warrior, Archer and Arrow 18,620 registered today · the model family and its accident history
- Piper 44,843 aircraft on the register
- Engine: Lycoming O-540 5,245 aircraft carry this series today · as the NTSB recorded it
- Montevideo-Chippewa County · 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/CEN26LA211.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.


