# NTSB WPR10LA040: Hallbauer Dragonfly Mark II, N555RX, Las Vegas, NV, October 30, 2009 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: October 30, 2009, 16:50 local (23:50 UTC) - Place: Las Vegas, NV - Coordinates: 36.210556, -115.194442 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=36.2106&lon=-115.1944&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor - Status: Completed, report May 6, 2010 - Report: Approved by Office Director - NTSB office: Western Pacific Region - Parties: Federal Aviation Administration - NTSB case key (mKey): 74988 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA040 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/74988/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=74988 - Page: https://openairdocs.org/ntsb/WPR10LA040 ## Probable cause The CFI's failure to maintain directional control of the airplane during takeoff. ## 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 · Instructor/check pilot (probable cause); cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=05644TZ), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Object/animal/substance: runway/taxi/approach light](https://openairdocs.org/ntsb-findings/03022012): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-findings/03022012/cases.md?model=05644TZ), [All aircraft, 106 cases](https://openairdocs.org/ntsb-findings/03022012/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=05644TZ), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-events/230/sequence.md?model=05644TZ), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=05644TZ), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Hallbauer Kenneth R DRAFONFLY MARK II, 1 case](https://openairdocs.org/ntsb-events/300/sequence.md?model=05644TZ), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The certified flight instructor (CFI) requested to remain in the traffic pattern and received a clearance for takeoff. During the takeoff roll, the airplane veered off the runway into a dirt area adjacent to the pavement and collided with a runway light, sheering a portion of its canard. The airplane bounced down the surface, eventually becoming airborne, and reaching about 200 feet above ground level. The Air Traffic Controller advised the airplane to climb, as it was approaching power lines. The CFI configured the airplane in a right bank and it collided with a utility pole. This was the CFI's first experience in the accident make and model airplane and the CFI did not hold a current medical certificate. In a written statement, the student pilot who owned the airplane reported that there were no preimpact mechanical malfunctions or failures with the airframe or engine. ## Factual narrative On October 30, 2009, at 1650 Pacific daylight time, a Hallbauer Dragonfly Mark II, N555RX, collided with a runway light during takeoff from the North Las Vegas Airport, Las Vegas, Nevada, and subsequently crashed into an automobile. The student pilot sustained minor injuries and the certified flight instructor (CFI) was seriously injured. The airplane, owned by the student pilot, sustained substantial damage during the crash sequence. The airplane was operated under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the local instructional flight, and a flight plan had not been filed. During a telephone interview with a Safety Board investigator, the student pilot reported that the CFI was flying the airplane while he monitored the cockpit gauges. After departing, and during the initial climb, the CFI maneuvered the airplane in a right turn. The airplane was not able to climb and the airplane crashed near a street. He recalled that the engine instruments appeared normal and there was no audible detection of a malfunction. In a written statement, the student pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine. According to a Federal Aviation Administration (FAA) inspector, who responded to the accident, the CFI requested to remain in the traffic pattern and received a clearance for takeoff about 1645. While on the departure roll, the airplane veered off the runway surface into an adjacent dirt area and collided with a runway light. The pilot continued the takeoff and the airplane lifted off about 1,500 feet down the runway. The Air Traffic Controller on the radio with the pilot warned that the airplane needed to start climbing, due to power lines directly ahead. He then issued a clearance to land on any runway, based on the observations of abnormal maneuvering. The airplane banked to the right (south) and struck a utility pole, sheering the left wing from the airframe. The airplane subsequently impacted the roof of a vehicle and skidded across six lanes of traffic before coming to rest near a parking lot. In an interview with the FAA inspector, the CFI reported that he was at the controls during the entire flight and that this was his first experience in the accident make and model airplane. He stated that he thought that there was a malfunction with the rudder, which prohibited him from maintaining the runway centerline; he additionally, stated that he could not reduce the throttle input because the controls were stuck. The CFI did not hold a current medical, as his application was denied in June 2003. Several witnesses observed the airplane on the departure roll from runway 12R. They reported that the airplane collided with a runway light and bounced down the surface, eventually becoming airborne. The airplane reached about 200 feet above ground level (agl) and rolled/banked right. They did not observe the impact sequence. According to the FAAinspector who visited the airport following the accident, an approximate 10-inch portion of the airplane's canard was found in the vicinity of a broken runway light. The FAA inspector stated that skid marks were observed on the runway leading up to the broken light. A post accident examination by an aircraft mechanic revealed no evidence of preimpact mechanical malfunction or failure. He established flight control continuity on all three axes. ## Aircraft - Registration: [N555RX](https://openairdocs.org/deregistered/N555RX-2019-07-26), registration cancelled 2019-07-26, S/N 516 (OpenAirDocs) - Reported make and model: Hallbauer Dragonfly Mark II - Registry model: [Hallbauer Kenneth R DRAFONFLY MARK II](https://openairdocs.org/model/hallbauer-kenneth-r-drafonfly-mark-ii) (registry code 05644TZ) (OpenAirDocs) - Registry engine: [Amateur-built UNKNOWN ENG](https://openairdocs.org/engine/amateur-built-unknown-eng) (registry code 99999) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 516 - Airframe hours: 183 - Engines: Rotax UNKN reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Annual, October 30, 2009 - Departed: VGT, Las Vegas, NV - Destination: VGT, Las Vegas, NV - Airport: VGT, North Las Vegas Airport, runway 12R, 5,000 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Flight instructor; age 75; injuries: serious; flight instructor, commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; seat: left; flight hours: 6,800 total - Student pilot; age 37; injuries: minor; student; medical: class 3, with waivers/limitations; seat: right; flight hours: 30 total ## Weather - Conditions: Visual (VMC), Day - Wind: 160° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 25 °F - Altimeter: 30.12 inHg - Observed at: VGT ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20091030022389A](https://openairdocs.org/incident/20091030022389A), Oct 30, 2009: Amtr DRAGONFLYMAR, Las Vegas, NV, Substantial damage. N555RX crashed after takeoff from the North Las Vegas Airport. The aircraft struck a utility pole cable and a sports utility vehicle prior to impact with the… ## Docket (6 files) The files NTSB released with the investigation on February 10, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=74988. 3.4 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 469 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40321693&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Record of Conversation: Pilot (item 2, .PDF, 65 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40325281&FileExtension=.PDF&FileName=Record%20of%20Conversation%3A%20Pilot-Master.PDF - Witness Statement and FAA Air Traffic Controllers' Statements (item 3, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40325280&FileExtension=.PDF&FileName=Witness%20Statement%20and%20FAA%20Air%20Traffic%20Controllers%27%20Statements-Redacted.PDF - Federal Aviation Administrator (FAA) Inspector's Comments (item 4, .PDF, 1.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40325277&FileExtension=.PDF&FileName=Federal%20Aviation%20Administrator%20(FAA)%20Inspector%27s%20Comments-Redacted.PDF - Clark County Department of Aviation Report (item 5, .PDF, 184 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40325278&FileExtension=.PDF&FileName=Clark%20County%20Department%20of%20Aviation%20Report-Master.PDF - Mechanic's Statement (item 6, .PDF, 108 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40325279&FileExtension=.PDF&FileName=Mechanic%27s%20Statement-Redacted.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.