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

Amateur-built Habercraft accident near Pelican Rapids, Minnesota, September 27, 2026

On September 27, 2026 at about 10:20 pm local time, a 1981 amateur-built Habercraft, registered N10516, was substantially damaged in an accident during approach (VFR pattern base) near Pelican Rapids, Minnesota (Pelican Rapids Municipal Airpo 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

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
September 27, 2026 · about 10:20 pm local time · cases in 2026
Place
Pelican Rapids, Minnesota · Pelican Rapids Municipal Airpo · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Habercraft, built 1981
Registration
N10516 · registry record · serial 1
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On September 27, 2026, about 1720 central daylight time, a Haberman Habercraft airplane, N10516, was substantially damaged during an accident near Pelican Rapids, Minnesota. The pilot sustained a minor injury. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that before the flight the 12-gallon fuselage fuel tank contained about 8.5 gallons of fuel and that the cork-and-wire fuel indicator gauge installed in the fuel tank cap was about 5.5 inches above an empty indication. The pilot noted that the airplane’s Continental C85 engine consumed 4.5 to 5 gallons per hour at a cruise power setting. The pilot reported that at 1602 the local flight departed Pelican Rapids Municipal Airport (47Y), Pelican Rapids, Minnesota. The pilot flew a meandering route over the lakes in the Pelican Rapids area, then over Highway 34 west to Barnesville, Minnesota, then to the south before turning back toward 47Y. The pilot reported that about 1 hour and 15 minutes had elapsed since departure when the airplane was on the left downwind for runway 33 at 47Y. The pilot acknowledged that the flight was 10 to 15 minutes longer than he had planned for, but the cork-and-wire fuel indicator gauge was about an inch above the empty indication. The pilot considered flying a circle-to-short final because there were no other aircraft in the traffic pattern; however, ultimately, he decided to fly a normal traffic pattern to runway 33. The pilot reported he reduced engine throttle and the airplane entered a descent during the turn from downwind to base leg. The airplane’s altitude and airspeed were reportedly lower-than-normal after the turn to base leg. The pilot increased the engine throttle but there was no response from the engine. The pilot reported that the engine continued to operate at a near idle power setting and at no point sputtered or quit. The airplane continued to descend rapidly toward trees. The pilot does not recall the final sequence of events that led to the impact with terrain. The airplane sustained substantial damage to the forward fuselage during the nose-low impact into a soybean field.

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 approach (VFR pattern base) defining event
  2. Loss of control in flight during approach (VFR pattern base)
  3. Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern base)

The aircraft

  • Airframe total time: 221.7 hours
  • Last inspection: condition inspection, June 2, 2026
  • Maximum gross weight: 1,000 lb
  • Seats: 2
  • Landing gear: fixed

The flight

  • Departed from: 47Y Pelican Rapids MN at 9:02 pm
  • Destination: 47Y Pelican Rapids MN
  • Flight plan: none
  • Runway 33, 3,260 ft by 140 ft

Weather at the time

  • Light: daylight
  • Wind: from 280° at 3 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 11,000 ft
  • Temperature: 68°F (20°C), dew point 43°F (6°C)
  • Altimeter: 30.11 inHg
  • Observation at 5:15 pm from KDTL, 15 miles away

Weather report (METAR): METAR KDTL 272215Z AUTO 28003KT 10SM BKN110 20/06 A3011 RMK AO2 T02050065

Injuries

FatalSeriousMinorNone
Flight crew1

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN26LA327.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.