Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 4, 2019 · Alisport Silent 2 Electro · N66911

Danbury, CT

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 4, 2019
Injury Outcomes
1 injury (1 minor injury)
Location
Danbury, CT
Aircraft
Alisport Silent 2 Electro (2016)
Tail Number
N66911
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA19LA186

The pilot was conducting a personal flight in an electrically-powered, self-launching motor glider. He stated that, while returning to the departure airport at the conclusion of the flight, the glider encountered sink and he turned on the electric motor, but it produced “no thrust.” The glider continued to descend and impacted a house about 2 miles from the airport, resulting in substantial damage. The pilot reported that there were no mechanical failures or malfunctions with the glider that would have prevented normal operation before the accident and that the accident might have been prevented with “better management of power and understanding of battery power source.” Data from the engine control unit indicated that the motor was used for about 13 minutes during the taxi, takeoff, and climb. The motor was used again about 5 hours into the flight for about 19 minutes, and again about 5:49 hours elapsed flight time, for about 32 minutes. The final activation of the motor occurred at 6:21 elapsed flight time; the accident occurred at an elapsed flight time of about 6:22. According to the glider manufacturer, the battery supplied power for takeoff and an additional 40 minutes of use thereafter. During the accident flight, the motor was used for a total of over 1 hour. Given this information, it is likely that the pilot had exhausted the available battery power and that the motor was no longer able to provide sufficient thrust to sustain flight.

NTSB Probable Cause

The pilot’s inadequate inflight management of the motor glider’s available battery power, which resulted in the inability of the electric motor to provide sufficient thrust to sustain flight in an environment where no atmospheric lift was available.

Full Narrative

On June 4, 2019, about 1700 eastern daylight time, an experimental Alisport SRL Silent 2 Electro glider, N66911, was substantially damaged when it was involved in an accident near Danbury Municipal Airport (DXR), Danbury, Connecticut. The pilot sustained minor injuries. The glider was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he performed a preflight inspection of the glider and the self-launching electric motor. He stated the glider’s battery was fully charged before the flight. He utilized the glider’s electric motor to take off from DXR and proceeded northbound using thermals and ridge lift. He flew for about 2 hours before turning southbound near the Massachusetts/Vermont border to return to DXR. He stated high overcast conditions pushed him west toward the New York/Connecticut border and that he needed to use the electric motor to maintain a safe altitude due to low thermal activity. His last calculation of remaining battery energy was about 20 minutes from DXR, when he noted about 20% battery life remaining. About 8 miles from DXR, the pilot contacted the tower controller and was cleared to land, but the glider encountered sink and the pilot turned on the electric motor. The pilot reported that the motor produced “no thrust,” and the glider continued to lose altitude until it impacted trees and a house 2.4 miles northeast of DXR. The impact with the house resulted in substantial damage to the glider’s foldable fixed-pitch propeller, nose cowling, cockpit canopy, both wings, and the tail boom. After the accident, the pilot reported that there were no mechanical malfunctions or failures of the glider that would have prevented normal operation prior to the accident. According to the glider manufacturer’s website, a typical self-launch can be expected to consume about 20% of the available battery capacity, leaving about 40 minutes of power available for use as a sustainer. The glider was equipped with a front electric-self launch (FES) control unit that contained nonvolatile memory on an SD card. The glider was also equipped with an LX9050 GPS navigation system, from which data for the flight were extracted and correlated with data from the FES. The contents of the FES SD card contained about 6 1/2 hours of data associated with the accident flight and indicated that the FES motor was used five times during the accident flight for a total duration of 1:09:16. The FES control unit also recorded battery annunciations and provided system warnings. A yellow warning message was provided when the battery power dropped below 95 volts and a red warning message and red light were provided when the battery dropped below 90 volts. The yellow warning required a reduction in power, while the red warning was a critical voltage warning and required the pilot to stop using the FES motor. The data from the accident flight showed that pilot received three yellow warning messages and two red warning messages during the flight. The yellow warning messages were displayed at 05:06:32 (elapsed flight time), about 41 nautical miles (nm) from DXR; at 06:08:46 about 12 nm from DXR; and 06:21:51, just 1 minute before impact and at an approximate distance of 2.4 nm from DXR. The red warning messages were displayed at 06:18:12 and 06:18:31. The pilot reported that the accident might have been prevented with “better management of power and understanding of battery power source.”

Flight

Event TypeAccident
Event Time17:00 EDT
Nearest AirportDanbury Muni (2nm NNE)
Runway26
Runway Length4422 ft
Runway Width150 ft
Flight Plan FiledVFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftAlisport Silent 2 Electro
Tail NumberN66911
Aircraft CategoryGli
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeElectric
Engine DetailsLz Design · FES · Electric · 29
Seats1

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 63 · Sprt · Minor

Conditions

ConditionsVMC
LightDaylight
Wind240° @ 11 kt, gusting 16 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point68 F / 39 C
Altimeter30.01 inHg
Observation Time20:53
Weather SourceWFAC

Appendix: Source Data