The U.S. aircraft register, updated daily
Accidents · NTSB ERA22FA387 · Final report

Sea & Sky INC KRUCKER CYGNET accident near Emily, Minnesota, August 28, 2022

On August 28, 2022 at about 10:34 pm local time, a 2010 Sea & Sky INC KRUCKER CYGNET (weight-shift aircraft), registered N505DB, was substantially damaged in an accident during initial climb near Emily, Minnesota. 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 pilot’s operation of the weight-shift control aircraft over its design gross weight and his decision to take off with the engine operating at less than the specified takeoff rpm, which resulted in degraded takeoff and climb performance. Contributing to the accident was the increased density altitude conditions, which further decreased the aircraft’s climb capability.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
August 28, 2022 · about 10:34 pm local time
Place
Emily, Minnesota · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Sea & Sky INC KRUCKER CYGNET NO SERIES, built 2010
Registration
N505DB · no longer on the register · serial H20056
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot and one passenger were departing from a lake for a local flight in the weight-shift-control aircraft. The pilot’s wife reported that the aircraft did not become airborne at the usual location. Video captured by an onboard camera revealed that, after becoming airborne with the engine operating about 300 rpm below the takeoff rpm setting, the aircraft began a slow climb while flying toward the south edge of the lake. Near the south end of the lake, with the engine operating at the same rpm, the climb stopped and the pilot abruptly manipulated the controls, likely to avoid trees ahead and prevent an aerodynamic stall. Around this time, the pilot’s wife heard a “pop” sound. The aircraft then entered a left descending spiral, impacting the tree canopy then the ground. Examination of the flight controls revealed no evidence of preimpact failure or malfunction. Damage signatures observed on one propeller blade indicated that the pop sound heard by the witness was likely the sound of the propeller blade impacting a control cable during the impact sequence. Examination and postaccident operational testing of the engine and propeller revealed that the propeller blade angle was set higher than optimal for the propeller/engine combination, preventing the engine from attaining the published takeoff power setting of 5,800 rpm. Additionally, calculations of the engine rpm during both the accident flight and one previous takeoff recorded by the onboard camera revealed the rpm to be consistent with the engine operating at or near its published maximum continuous power setting (5,500 rpm), rather than the takeoff power setting (5,800 rpm). Given the weights of the occupants and the fuel found onboard after the accident, the aircraft was a minimum of 29 lbs over design gross weight at the time of the accident, but could have been as much as 62 lbs, or about 5.8%, over the design gross weight at the start of the flight. The density altitude at the time of the accident was about 2,950 ft mean sea level. It is likely that the combined effects of the pilot’s operation of the aircraft in an overweight condition, the engine operating at less than the specified takeoff rpm throughout the flight, and the increased density altitude reduced the aircraft’s climb performance, resulting in impact with trees and terrain.

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. Collision with terrain or object (not controlled flight into terrain) during initial climb defining event
  2. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Aircraft propeller/rotor › Propeller system › Propeller blade section › Incorrect use/operation
  • Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › High density altitude › Decision related to condition
  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Climb rate › Not attained/maintained
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › Maximum weight › Capability exceeded

Pilot

  • Certificate: private, sport pilot
  • Ratings: single-engine land; instructor: sport pilot
  • Flight time: 592 hours in all; 161 in this make and model; 25 in the last 90 days; 6 in the last 30 days
  • Medical certificate: Sport Pilot
  • Seat: frt
  • Injury: fatal

The aircraft

  • Airframe total time: 422 hours
  • Last inspection: annual inspection, June 28, 2022
  • Maximum gross weight: 1,060 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912UL (piston); 422 hours total

The flight

  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 160° at 10 knots
  • Visibility: 10 statute miles
  • Sky: scat at 1,900 ft
  • Temperature: 75°F (24°C), dew point 68°F (20°C)
  • Altimeter: 29.61 inHg
  • Observation at 5:15 pm from KPWC, 15 miles away

Weather report (METAR): KPWC 282215Z AUTO 16010KT 10SM SCT019 24/20 A2961 RMK AO2

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

18 documents, released by the NTSB on May 16, 2024. 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.

#DocumentWhat it is
1 Record of NTSB Conversations PDF, 23 pages · our copy View Download
2 Memorandum for Record - Correspondence with Mechanic PDF, 2 pages · our copy View Download
3 Maintenance Record Entries PDF, 1 page · our copy View Download
4 Weight and Loading Document PDF, 1 page · our copy View Download
5 Excerpts from Aircraft Operating Instructions PDF, 4 pages · our copy View Download
6 Excerpts from Engine Operators Manual PDF, 2 pages · our copy View Download
7 Excerpts from Engine Operators Manual-engine Performance PDF, 4 pages · our copy View Download
8 Density Altitude Calculation PDF, 1 page · our copy View Download
9 Wreckage Examination Summary PDF, 12 pages · our copy View Download
10 Memorandum for Record - Engine Run and Propeller Blade Angle Inspection Results PDF, 2 pages · our copy View Download
11 Memorandum for Record - Propeller Blade Angle vs Engine Rpm PDF, 3 pages · our copy View Download
12 Toxicological Report - Pilot PDF, 1 page · our copy View Download
13 Autopsy Memorandum for Record and Weight - Pilot PDF, 1 page · our copy View Download
14 Autopsy Memorandum for Record and Weight - Passenger PDF, 1 page · our copy View Download
15 Onboard Image Recorder - Specialist's Factual Report PDF, 10 pages · our copy View Download
16 Onboard Image Recorder - Attachment 1 (Csv GPS Data for Accident Flight) data file · our copy Download
17 Release of Aircraft Wreckage, NTSB Form 6120.15, and NTSB Evidence Control Form for Engine Assembly PDF, 2 pages · our copy View Download
18 NTSB Evidence Control Form for Go-pro Camera PDF, 2 pages · our copy View Download

The same docket at the NTSB.

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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.