ERA21LA283 · Bailey N Moyes DRAGONFLY
KHK Morningside Bailey N Moyes DRAGONFLY · Accident: collision with terrain/object (non-CFIT) on approach
Event
- NTSB case
- ERA21LA283
- 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
- 1 · 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
Bailey N Moyes DRAGONFLY
- Aircraft type
- Bailey N Moyes DRAGONFLY
- Category
- Airplane
- 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
- N346FL
- Operator
- KHK Morningside
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 24 years (built 1997)
- 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
- Approach · VFR pattern base
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
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 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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA283
- Event ID
- 20210710103451
- Case number
- ERA21LA283
- 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: 18823a1fbd98f71f4da63192a4f8a13430ff8d308eaccb9c189aa8d497e77764; retrieved 2026-09-15T07:31:17.726Z.