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

Bailey N Moyes DRAGONFLY accident near Charlestown, New Hampshire, July 10, 2021

On July 10, 2021 at about 9:30 pm local time, a 1997 Bailey N Moyes DRAGONFLY, registered N346FL, was substantially damaged in an accident during approach (VFR pattern base) near Charlestown, New Hampshire (Morningside Flight Park airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The passenger’s decision to continue an unstable approach while at low altitude and in proximity to a known obstacle, which resulted in a collision with power lines.

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

What the record shows

Date
July 10, 2021 · about 9:30 pm local time
Place
Charlestown, New Hampshire · Morningside Flight Park · map
Type
Accident
Injuries
1 person was killed and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Bailey N Moyes DRAGONFLY, built 1997 · all DRAGONFLYs on the register
Registration
N346FL · registry record · serial 034
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was in the airport’s traffic pattern receiving mentoring and airplane familiarization from the passenger in the rear seat, who had been a private pilot but had his airmen and medical certificates revoked about 4 years before the accident. The pilot reported that, during the third landing, the airplane was too high while on final approach and the passenger told the pilot to perform a go-around. A witness who saw the airplane on the subsequent downwind described the airplane as being “slower and lower” than normal. Near the end of the downwind leg, at an estimated altitude of 400 ft above ground level, the passenger yelled “something about power” according to the pilot and assumed control of the airplane. When abeam the runway threshold, with an engine speed about 3,200 rpm which was about 300 rpm below normal cruise speed, the passenger turned onto the base leg. The pilot later reported that although the airplane’s altitude was “low,” it seemed sufficient to clear the power lines located several hundred feet to the west of and nearly parallel to the runway. The pilot reported that a partial loss of engine power occurred about the same time the passenger turned the airplane onto the base leg. The airplane banked “hard” to the left, pitched nose down, and descended into one of the power lines. After the airplane impacted the ground, the engine continued to operate until the pilot shut it down. Because the previous pattern circuit was too high on final approach and resulted in a go-around maneuver, the pilot may have overcompensated and flown the accident pattern at too low of an altitude given the power line obstruction on the base leg. The passenger was likely concerned about the approach when he took over the controls. His subsequent turn to the base leg suggests that he intended to continue in the normal traffic pattern over the power lines. Given the low altitude at the time, this decision involved significantly greater risk than extending the downwind and correcting whatever condition(s) that caused the passenger to take control. The pilot described a partial loss of engine power about the same time the passenger made the turn to base leg, which was followed by a sharp turn to the left and a nose-down attitude just before impact with the power lines. The investigation could not determine if the reduction in engine power was due to a failure or malfunction or was intentionally commanded by the passenger in an attempt to avoid the power lines. Postaccident examination of the engine did not reveal any anomalies that would have resulted in a partial loss of engine power. Toxicology testing for the passenger, who was flying the airplane at the time of the collision with the power line, was positive for tetrahydrocannabinol (THC), the primary psychoactive chemical in cannabis and hashish and its metabolites. The levels detected may have been sufficient to cause significant impairing effects; however, they do not indicate the severity of THC-related impairment or whether such impairment contributed to the accident. Therefore, whether impairing effects of the passenger’s THC use contributed to the accident could not be determined.

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

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Passenger
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Passenger
  • Personnel issues › Physical › Impairment/incapacitation › Illicit drug › Passenger
  • Aircraft › Aircraft power plant › (general) › (general) › Unknown/Not determined

Pilot-Rated Passenger

  • Flight time: 3,600 hours in all
  • Medical certificate: None
  • Seat: rear
  • Injury: fatal

Pilot

  • Ratings: multi-engine land; single-engine land; instrument: airplane; rotorcraft: glider
  • Flight time: 234 hours in all; 13 in this make and model; 21 in the last 90 days; 13 in the last 30 days
  • Last flight review: May 19, 2021
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: frt
  • Injury: minor injuries

The aircraft

  • Airframe total time: 2,587 hours
  • Last inspection: 100-hour inspection, June 5, 2020
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912ULS (piston); 0 hours total
  • Operator: Khk Morningside LLC

The flight

  • Flight plan: none
  • Runway 36, 2,300 ft by 50 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 340° at 3 knots
  • Visibility: 10 statute miles
  • Sky: scat at 6,500 ft
  • Temperature: 73°F (23°C), dew point 61°F (16°C)
  • Altimeter: 30.00 inHg
  • Observation at 5:54 pm from VSF, 7 miles away

Weather report (METAR): METAR KVSF 102154Z AUTO 34003KT 10SM SCT065 23/16 A3000 RMK AO2 SLP158 T02330156 $=

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number ERA21LA283.