# NTSB WPR14LA285: Bailey-Moyes Microlights Dragonfly B Model, N7008Z, Buckley, WA, July 8, 2014 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: July 7, 2014, 20:20 local (Jul 8, 2014, 03:20 UTC) - Place: Buckley, WA - Coordinates: 47.183887, -122.120002 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=47.1839&lon=-122.1200&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Defining event: [Maneuvering: Loss of control in flight](https://openairdocs.org/ntsb-events/240) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report November 5, 2015 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Adminitration - NTSB case key (mKey): 89621 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR14LA285 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89621/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89621 - Page: https://openairdocs.org/ntsb/WPR14LA285 ## Probable cause The pilot’s inability to maintain airplane control due to a loss of flight control effectiveness for reasons that could not be determined during postaccident examinations. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Moyes/Bailey Microlites Ptyltd DRAGONFLY B MODEL, 2 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05901X7), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters](https://openairdocs.org/ntsb-findings/01062000): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Moyes/Bailey Microlites Ptyltd DRAGONFLY B MODEL, 1 case](https://openairdocs.org/ntsb-findings/01062000/cases.md?model=05901X7), [All aircraft, 1,269 cases](https://openairdocs.org/ntsb-findings/01062000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Maneuvering: Loss of control in flight](https://openairdocs.org/ntsb-events/240) (defining event); cases with it: [Moyes/Bailey Microlites Ptyltd DRAGONFLY B MODEL, 2 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=05901X7), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) ## Analysis The pilot reported that, about 15 minutes after departure, he was maneuvering the experimental, light sport airplane to the destination airport. After he initiated a right turn, the airplane assumed a nose-low attitude with the right wing low. The pilot felt no feedback pressure on the control stick and determined that there was a flight control malfunction. The airplane continued to descend, so the pilot activated the onboard ballistic emergency parachute when the airplane was about 100 ft above the trees. The airplane subsequently collided with the trees and then came to rest inverted about 0.4 nautical mile from the airport. Three years previously, the airplane had been involved in an accident with a different pilot, and the probable cause of that accident was the pilot's improper recovery from a dive that led to a loss of in-flight control. Following the accident, that pilot reported that he was aware that the airplane had a tendency to pitch down and accelerate when not monitored and controlled continuously. He stated that, although the control stick would move freely during a maneuver, he was unable to correct the flightpath with the elevator, which was consistent with this accident pilot's statement. According to two other pilots who encountered delayed controllability while operating the accident make and model airplane, adding engine power corrected the problem. The airplane was disassembled for recovery purposes, which prevented investigators from determining its configuration before the accident. The examination of the disassembled flight control system revealed no evidence of any preimpact failures or malfunctions that would have affected normal operation of the flight controls. Further, because the pilot activated the parachute system, it could not be determined whether the flight control condition was temporary. ## Factual narrative On July 7, 2014, about 2020 Pacific daylight time, an experimental light-sport Bailey-Moyes Microlights Dragonfly B airplane, N7008Z, impacted trees after the pilot activated the onboard parachute near Flying H Ranch Airport, Buckley, Washington. Private individuals owned and operated the airplane under the provisions of 14 Code of Federal Regulations Part 91. The private pilot sustained minor injuries; the airplane was substantially damaged. Visual meteorological conditions prevailed and no flight plan was filed. The pilot departed Burnett Landing Airport, Wilkeson, Washington about 2000 for a local personal flight.The pilot reported that about 15 minutes after departure, he was maneuvering the airplane to the west of Flying H Ranch Airport. While maneuvering at an airspeed of about 33-34 mph, he initiated a right turn. The airplane then assumed a nose-low attitude with the right wing low. The pilot felt no feedback pressure on the control stick and determined that there was a flight control malfunction. The descent continued so he activated the onboard BRS emergency parachute when the airplane was about 100 feet above the trees. The airplane subsequently collided with the trees and came to rest inverted about .4 nautical miles from the airport. The airplane was involved in an accident in December 2010 (WPR11CA079), where the probable cause was attributed to the pilot's improper recovery from a dive that led to a loss of in-flight control; the pilot was not the accident pilot or current owner. Following the accident, that pilot reported that he was aware that the airplane had a tendency to pitch down and accelerate when not monitored and controlled continuously. He stated that during a maneuver, although the control stick would move freely, he was unable to correct the flight path with the elevator and deployed the BRS parachute system. According to two other Dragonfly pilots, they have been in similar situations of temporarily encountering a control delay, all of which were easily rectified by adding engine power to get more airflow over the elevator. The airplane was disassembled for recovery purposes which prohibited investigators from determining the configuration prior to the accident. The examination of the disassembled flight control system revealed no evidence of any pre impact failures or malfunctions which would have affected normal operation of the flight controls. According to maintenance records the airplane's most recent annual inspection was completed on June 30, 2014, or 6 days prior to the accident. At the time of the inspection, the airplane had accrued 449.7 total hours of operation and, according to that Hobbs meter, had acquired 5.4 hours since then. The pilot reported that he had amassed a total flight time of 700 hours, of which 5.8 hours were accrued in a Dragonfly. He had flown 1.1 hours in the last 30 days and all of the 5.8 hours were accumulated in the past 90 days. ## Aircraft - Registration: [N7008Z](https://openairdocs.org/aircraft/N7008Z), registered now, S/N 046, built 1998 (OpenAirDocs) - Reported make and model: BAILEY-MOYES MICROLIGHTS DRAGONFLY B MODEL - Registry model: [Moyes/Bailey Microlites Ptyltd DRAGONFLY B MODEL](https://openairdocs.org/model/moyes-bailey-microlites-ptyltd-dragonfly-b-model) (registry code 05901X7) (OpenAirDocs) - Registry engine: [Rotax 582UL DCDI](https://openairdocs.org/engine/rotax-582ul-dcdi) (registry code 55563, 2 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 046 - Year built: 1998 - Airframe hours: 449.7 - Engines: Rotax 582 65 hp reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental light sport (Special) - Last inspection: Condition, July 30, 2015, 5 hours before - Departed: WN15, Wilkeson, WA - Destination: WN15, Wilkeson, WA - Airport: WN42, Flying H Ranch Airport - Equipment: Airframe parachute ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 64; injuries: minor; private; airplane ratings: single-engine land; medical: sport pilot; last flight review February 10, 2013; seat: front; flight hours: 700 total, 5.8 in this make and model, 5.8 in the last 90 days, 1.1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F, dew point 63 °F - Altimeter: 30.04 inHg - Observed at: KPLU, 10 nm away ## Other investigations on N7008Z (2) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB WPR18LA204](https://openairdocs.org/ntsb/WPR18LA204), Jul 19, 2018: Microlites Ptyltd Dragonfly B (N7008Z), Buckley, WA, substantial damage. Probable cause: A total loss of engine power for reasons that could not be determined based on the available information. - [NTSB WPR11CA079](https://openairdocs.org/ntsb/WPR11CA079), Dec 22, 2010: Moyes Bailey Microlite (N7008Z), Newberg, OR, substantial damage. Probable cause: The pilot's improper recovery from a dive, which resulted in a loss of control. ## Docket (1 files) The files NTSB released with the investigation on September 29, 2015, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89621. 1.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40432214&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.