ERA22FA387 · SEA & SKY Inc KRUCKER CYGNET
SEA & SKY Inc KRUCKER CYGNET · Accident: collision with terrain/object (non-CFIT) during initial climb
Event
- NTSB case
- ERA22FA387
- 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
- Completed
- 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
SEA & SKY Inc KRUCKER CYGNET
- Aircraft type
- Sea SKY KRUCKER CYGNET
- Category
- Weight-Shift
- 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
- N505DB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 12 years (built 2010)
- 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
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft propeller/rotor
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22FA387
- Event ID
- 20220829105807
- Case number
- ERA22FA387
- 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, cause areas. 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: b26bc02ca9faef498f66977a8a25567d4c0a0b607ae34bf6cbbdd4b775ce396b; retrieved 2026-09-15T07:49:52.605Z.