Docket And Docket Items - National Transportation Safety Board:http://dms.ntsb.gov/pubdms
Aviation Accident Data Summary - National Transportation Safety Board:http://app.ntsb.gov/pdf
The National Transportation Safety Board did not travel to the scene of this accident.
Additional Participating Entity:
Federal Aviation Administration / Flight Standards District Office; Scottsdale, Arizona
Evolution Aircraft Inc:http://registry.faa.gov/N107SB
NTSB Identification: WPR16LA071
14 CFR Part 91: General Aviation
Accident occurred Tuesday, February 16, 2016 in Buckeye, AZ
Probable Cause Approval Date: 10/03/2016
Aircraft: Evolution Revo, registration: N107SB
Injuries: 1 Fatal.
NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
The commercial pilot, who had a total flight experience of about 4,500 hours in conventional airplanes, was learning to fly weight-shift-control (WSC) aircraft with the expressed intent of purchasing a high-performance WSC aircraft. The pilot obtained all of his 13.5 hours of WSC experience, including his WSC pilot and instructor certificates, in the 2 weeks before the accident in a docile, low performance WSC aircraft with dual seating. Despite being explicitly warned by his instructor that he was not “not qualified” to fly the specific model high performance WSC aircraft involved in the accident, the pilot convinced an owner of a high-performance WSC aircraft to allow him to fly it solo. The owner reported that the engine start, taxi out, and run-up appeared normal. The wind was light. Witnesses reported that, on takeoff, the aircraft climbed rapidly and entered a steep right bank/roll from which it did not recover. The flight lasted about 16 seconds, and the aircraft reached a maximum altitude of about 80 ft above the runway. Detailed examination of the wreckage did not reveal any mechanical deficiencies or failures that would have precluded normal operation, and data from an electronic engine control indicated that the engine operated normally throughout the flight. The pilot’s autopsy did not reveal the presence of any debilitating physical conditions or impairing drugs.
The pilot inputs for pitch and bank/roll control on a WSC aircraft are opposite those of conventional airplanes, and the pilot’s experience differential between the two aircraft types was substantial. In addition, the high performance WSC aircraft was a much more powerful and challenging aircraft due to its control sensitivity than the one flown by the pilot during his limited WSC training, which was all done with an instructor. The witnesses’ description of the sequence of events and the rapidity with which they occurred is consistent with excessive and contrary control inputs. Given the handling characteristics of the accident aircraft relative to the pilot’s flight experience, it is likely that the pilot over-controlled it during the initial rotation, which led to what witnesses reported to be a very steep takeoff attitude. The lack of familiarity with the aircraft, combined with potential threat of a stall or other loss of control, and possible reversion to habit patterns appropriate to his conventional airplane experience may then have led to the pilot’s reflexive and incorrect control inputs. Those inputs exacerbated the situation and ultimately resulted in a loss of aircraft control. The aircraft was equipped with a rocket-powered parachute, but the first responders worked on and around the wreckage for about 1 hour before they were advised by a Federal Aviation Administration inspector of the presence of the rocket and its potential hazard. Existing industry consensus standards only specify warning placards near the rocket egress point, which in this case, was on the aircraft’s left side. Because the aircraft came to rest on its left side, neither the rocket nor any placards would have been visible. ASTM International standards do not require that warning placards be placed on all sides of the aircraft.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The pilot's improper decision to operate the high-performance aircraft despite warnings from a flight instructor that he did not have the experience to operate the aircraft that had different and more sensitive handling characteristics than the low-performance weight-shift-control aircraft that he was used to flying, which led to his improper control inputs and resulted in his loss of aircraft control and ground impact immediately after takeoff.
HISTORY OF FLIGHT
On February 16, 2016, about 1452 Mountain standard time, an Evolution Revo special light sport weight-shift control "trike," N107SB, impacted terrain shortly after takeoff from Buckeye Municipal airport (BXK), Buckeye, Arizona. The pilot, who was the sole person on board, received fatal injuries, and the aircraft was substantially damaged. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no Federal Aviation Administration (FAA) flight plan was filed for the flight.
According to the owner of the aircraft, the pilot was referred to him by the Evolution president, because the pilot was interested in purchasing a Revo, and he was planning a trip to the Phoenix area. The pilot made contact with the owner, and appealed to him to be allowed to fly the aircraft. Based on the pilot's credentials, the owner eventually agreed to let the pilot fly the aircraft. The evening prior to the accident, the owner (acting as pilot in command) took the accident pilot (as a passenger) on an uneventful flight in the aircraft. On the day of the accident, both individuals conducted the preflight inspection, with no anomalies noted.
The pilot reportedly planned to conduct a solo flight, and then return for an unspecified passenger. According to the owner, the takeoff roll on runway 17 was normal, but shortly after breaking ground, the wing went to the "full flare" position, which he explained to mean that the wing was at the full wing leading edge up position. The wing remained in that position, and the aircraft climbed rapidly and steeply, but then appeared to stall, at an altitude estimated by witnesses to be less than about 100 above ground level. The aircraft then turned, rolled, to the right, and descended rapidly to the ground in a nose-down attitude. The aircraft was equipped with a Ballistic Recovery System brand rocket propelled parachute, but the device was not activated by the pilot.
The wreckage was examined on site by FAA inspectors, and was recovered to a secure location for subsequent examination.
PERSONNEL INFORMATION
Certificate Information
According to FAA records, the pilot held a commercial certificate with airplane single engine land, multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. He also held flight instructor certificate with airplane single- and multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. The pilot's most recent valid FAA medical certificate was obtained in 2004. On that medical certificate application, the pilot reported a total flight experience of 4,500 hours.
Weight Shift Control (WSC) Aircraft Experience
The pilot obtained all of his weight shift control (WSC) experience and instruction in the two weeks prior to the accident. According to the certified flight instructor (CFI) who provided nearly all that instruction, the pilot was referred to him by the owner of the accident aircraft. The pilot first met and flew with the CFI on February 6, 2016 at BXK; the CFI had flown his Northwing Navajo WSC aircraft to BXK for an airshow/exhibit there. The following week, the pilot traveled to Boulder City, Nevada to complete his training, and obtain his WSC pilot- and instructor- certificates.
The pilot accrued a total time of 9.5 hours with that CFI, and then 2 hours with another CFI, before taking his flight checks with the original CFI on February 12, 2016. At the completion of his WSC pilot and instructor flight checks, the pilot had accrued a total WSC aircraft flight experience time of 13.5 hours. All flights were conducted in the Navajo, and none of the flights were solo. Both CFIs were complementary regarding the pilot's skills.
Because the pilot was interested in purchasing a Revo, on multiple occasions he asked the CFI about the Revo. The CFI strongly discouraged the pilot from flying a Revo until he had more WSC aircraft experience, and then also obtained specific instruction in that aircraft. The CFI advised the pilot that he (the pilot) was "not qualified" to fly the Revo at this point in his experience/training level – his primary reason was that the Revo was a much more "sensitive" aircraft than the Navajo.
AIRCRAFT INFORMATION
FAA information indicated that the aircraft was manufactured in 2015, and was equipped with a Rotax 912-IS series engine. The aircraft was purchased new by the current owner in early 2015. He reported that the airframe and engine had each accumulated a total time in service of about 69 hours.
The two primary elements of the aircraft were the carriage and the wing. The carriage was a steel tube assembly with composite fairings. The instrument panel, tandem seats, landing gear and engine were all integral to the carriage. The primary pilot station was the front seat; the rear seat had no instruments and access to only a few controls. The primary flight controls consisted of horizontal, transversely-mounted control bar situated just ahead of the pilot, and attached to the wing. The pitch and roll/yaw control inputs were exactly the reverse of those of conventional airplanes; pushing the control bar forward would climb the WSC aircraft (and vice versa) while moving the control bar left would result in the WSC aircraft turning to the right (and vice versa).
The engine was situated behind the rear seat in a pusher-type arrangement. The engine was electronically controlled and fuel-injected. The installed electronic engine control unit (ECU) was equipped to record certain engine parameters during operation. The engine drove a 2 blade composite propeller, and its rated output was 100 hp.
The wing was a fabric-covered aluminum tube assembly which attached to the carriage by a mast. The mast attached behind the rear seat into a "pivot block" which allowed the wing to change its pitch orientation with regard to the carriage. On the ground, the wing was free to move through a range of pitch and roll attitudes, while the carriage remained in a stationary attitude. In flight, the carriage was suspended by the mast, and stabilized at an attitude determined by center of gravity and airloads. The wing attitude and angle of attack could be varied by the pilot's inputs on the control bar.
The aircraft was equipped with a pitch trim system which was used for cruise flight, in order to neutralize the forces required by the pilot on the control bar. There was no means to visually detect the trim setting, and there was no specific trim setting or range for takeoff or landing.
METEOROLOGICAL INFORMATION
The BXK 1455 automated weather observation included winds from 130 degrees at 8 knots, visibility 10 miles, clear skies, temperature 27 degrees C, dew point minus 2 degrees C, and an altimeter setting of 29.93 inches of mercury.
AIRPORT INFORMATION
BXK consisted of a single paved runway that measured 5,500 feet by 75 feet. The runway was designated as 17/35. The airport was located in the desert, and the unpaved areas consisted of hard-packed earth and sparse low vegetation. Airport elevation was listed as 1,032 feet above mean sea level. The airport ramp was situated about 3,200 feet from the runway 17 threshold, and about 750 feet from the runway centerline.
FLIGHT RECORDERS
EFIS SD Card
The aircraft was equipped with an MGL brand "Stratomaster Xtreme" electronic flight instrumentation system (EFIS), which had data recording capability. Recording of flight data, including parameters and time intervals, were user-defined. If and when the device was configured by the user to record flight data, the data would be stored on a compact SD card which inserted into the face of the device.
Post accident discussions with the aircraft owner indicated that he was unaware of the EFIS device's recording capabilities, and therefore had not modified any of the recording settings. The SD card was recovered intact. Separate readout efforts by the NTSB and MGL Avionics indicated that no flight data had been recorded.
Engine Control Unit (ECU)
The ECU was removed from the aircraft, and was observed to be physically intact. It was sent to the NTSB Recorders laboratory in Washington, DC for readout. The data from the accident flight was successfully downloaded.
The device recorded 18 engine-related parameters at a rate of 10 samples per second, and ambient pressure at a rate of 1 sample per second. The accident flight data began at engine start, and terminated with what appeared consistent with impact and engine stoppage. The data file extended from system time 102:30:21 (hhh:mm:ss) to 102:39:28. The engine operated in the idle range until about 102:36:54, when rpm increases and data dropouts (due to ECU channel-switching) consistent with an engine runup were observed.
About 102:39:12, the rpm increased and stabilized at its maximum value, consistent with the takeoff roll and climb. The data ended about 16 seconds later. The parameter values were all consistent with normal engine operation throughout the entire data file, and the engine remained at full rpm for the takeoff and flight, until about 0.2 seconds prior to the end of the data.
The ambient pressure values were utilized to derive aircraft altitude values. The data indicated that the aircraft climbed rapidly in the first few seconds, and reached a maximum height of about 80 feet above the runway.
WRECKAGE AND IMPACT INFORMATION
On-scene documentation provided by the Buckeye Police Department and the airport manager indicated that the aircraft left a series of near-continuous ground scars, first in the form of a tire skid mark on the runway, followed by earth-scoring and gouging, to the final location of the wreckage. The overall length of these ground scars was about 340 feet, and their track was oriented approximately 20 degrees divergent right (west) from the runway 17 alignment.
The first tire skid mark began about 25 feet west of the runway centerline, and terminated near the runway edge. Ground scars, at first consistent with the aircraft wingtips, and further along the path, consistent with other portions of the aircraft, continued to the main wreckage. The main wreckage came to rest in an unpaved region of level desert terrain, about 150 feet east of the runway centerline, and about 1,500 feet from the starting point of the takeoff roll. The wreckage was situated about 2,000 feet from the airport ramp where the witnesses were located. The carriage was found on its left side, oriented approximately north, but was significantly disrupted. The wing assembly was fracture-separated from, but adjacent to and partially covering, the carriage. The wing structure was also significantly disrupted.
Personnel from the FAA and NTSB examined the recovered airframe and engine on March 9, 2016 at the facilities of Air Transport in Phoenix, Arizona. The owner was in attendance for a portion of the period to provide additional information as requested.
The aircraft was in two major pieces (wing assembly and carriage), as well as about two dozen fracture-separated parts. Those parts included windscreen, carriage fairing, propeller and other component fragments. There was no evidence of fire, either pre- or post-impact. The carriage damage was consistent with a front and left-side ground impact, with some fore-aft scraping.
The instrument panel was dislodged from its mounts, and severely deformed, but all 3 instruments remained affixed in the panel. The rocket powered ballistic parachute was still in its case, and the extraction rocket had not been fired. The front restraint harness belts had been cut to extract the pilot.
The engine did not exhibit any signs of any pre-impact failures, and damage was limited to some minor muffler crush and displacement from impact. The four top spark plugs were pulled, and the engine rotated freely by hand; thumb compressions were observed on all four cylinders. The bodies and electrodes of the four spark plugs all were unremarkable. The ECU was removed and retained for data download. Both composite propeller blades were fracture-separated at their approximate 18 inch span locations, and propeller blade damage was consistent with engine power at impact.
The main mast tube of the wing assembly had fracture-separated from the carriage at its attach point to the mast mount block. The left front wing spar was fracture-separated at about its 2 foot span location, and the right front spar was fracture-separated about 5 feet inboard of the tip. The auxiliary/jury spar aft of the main spar was also fracture-separated, while the wing fabric was intact exclusive of impact damage
An unidentified/unassigned quick-release pin was found inside the left wing, but the investigation was unable to determine its origin. The aft actuating tube assembly of the pitch trim mechanism was fracture-separated from the travel block of the main housing jackscrew. On disassembly and inspection, it was revealed that the threads of the aluminum actuating tube had pulled aft over the jackscrew nylon travel block threads. The damage was not consistent with normal system capability, and was attributed to impact loads and structural deformation.
No evidence of any pre-impact mechanical malfunction was noted during the examination of the recovered airframe and engine.
MEDICAL AND PATHOLOGICAL INFORMATION
The pilot's most recent valid FAA medical certificate was obtained in 2004, and was expired by the time of the accident flight. In February 2005, the pilot was seriously injured in an accident where he was piloting a Cessna 177. That accident was attributed to a complete loss of power due to oil starvation/exhaustion. The pilot's girlfriend reported that the initial injuries and resulting debilitation had delayed the pilot's decision to apply for another FAA medical certificate and resume flying certificated airplanes, and that the pilot continued to suffer pain from some of those injuries. Therefore, at the time of his weight shift training and the accident, the pilot was operating in accordance the light sport rules, which do not require a valid FAA medical certificate.
The Maricopa County (Arizona) Office of the Medical Examiner autopsy report indicated that the cause of death was "multiple blunt force trauma," and that alcohol and drug test results were all negative.
Review of the pilot's previous medical history by an FAA Civil Aeromedical Institute (CAMI) physician indicated that the pilot reported no significant medical concerns, and that his FAA medical examiner did not identify any significant conditions during the pilot's 2004 physical examination. The CAMI physician's review also noted that the autopsy "revealed some moderately severe cardiovascular disease but no evidence of thromboemboli or a recent or previous heart attack," and that "there were no significant natural disease findings that could point towards a sudden incapacitating event."
CAMI conducted forensic toxicology examinations on specimens from the pilot, and reported that no carbon monoxide, cyanide, ethanol, or any screened drugs were detected.
ADDITIONAL INFORMATION
Revo Flight Characteristics
The manufacturer of the aircraft agreed with the two CFI assessments that the Revo and Navajo had dramatically different flight characteristics, and that the Revo performance characteristics were not well suited for beginner level WSC pilots.
The pilot's primary CFI noted that the Revo is a very high performance aircraft, and that a first flight in that aircraft, particularly a solo flight, would be very different from the pilot's prior dual experience in the lower-performance Navajo.
Learning Primacy
According to the Aviation Instructor Handbook (AIH, FAA-8083-9), the first information or behavior learned by a person "often creates a strong, almost unshakable, impression." This phenomenon is called "primacy," and the AIH states that such primacy of learning and behaviors "lay the foundation for all that is to follow." The AIH further stated that unlearning those first-learned behaviors is significantly more difficult than learning them in the first place. Persons will frequently revert to the first-learned behaviors in time of stress, distraction, or inattention.
The AIH also discussed how the "element of threat...adversely affects perception by
narrowing the perceptual field," which reduces the pilot's ability to adequately or accurately sense or process the inputs available. The imposition of a threat can result in an individual becoming overly task-focused on countering the threat, while concurrently ignoring relevant or critical information.
Rocket and Parachute System Information
According to the FAA inspector, until he arrived at the site about one and a half hours after the accident, the first responders who were working on the wreckage and pilot were unaware of the presence of the rocket, or the hazard that it posed. Review of the body camera footage and audio from one of the responding police officers revealed that one of the firefighters did raise the possibility of the presence of a rocket early in the emergency response, but the question did not receive a considered response, and the matter was apparently not discussed again by any of the first responders. When the FAA inspector arrived on scene, it was he who advised them of the rocket's presence. Once the personnel became aware of the system, they ceased all activity, and the NTSB was contacted for guidance to disarm the rocket. That was accomplished, and the recovery of the pilot and aircraft were completed without incident.
FAA regulations and ASTM standards required proper completion of certain FAA forms, and proper placarding of the aircraft with regard to the parachute recovery system. In this case, ASTM standard F2316 (Airframe Emergency Parachutes) is the applicable standard.
In part, the standard required that the "airframe manufacturer shall supply conspicuous placards or labels for placement in unobstructed view to anyone near the egress point (exterior). These placards are to be displayed such that they provide a visual warning to rescue or other personnel at the scene of an accident or incident." The standard also specified that the "airframe manufacturer shall permanently install the warning placards or labels in a manner defined by this specification and documented in the PIM [parachute installation manual]". The standard presented sample labels in an appendix.
Based on the installation configuration of the rocket and parachute inside the carriage/fuselage, the standard required that a placard be mounted adjacent to the fuselage exit point, which in the case of this aircraft, was on the left aft side. However, the aircraft came to rest on its left side, which obscured the rocket and parachute from view of the first responders. Any co-located, left-side placards would have been similarly obscured from view.
NTSB investigators coordinated with the FAA Light-Sport Aircraft Program Manager in an attempt to modify the ASTM standard, and require that warning placards be affixed to all sides of the aircraft, in order to minimize the potential for injury to first responders. On May 11, 2016, the proposal to alter the F2316 placarding standard was presented to and considered by the responsible ASTM committee; the committee rejected that proposed change. The formal substantiating rationale was that the existing standard is sufficient, and does not need to be revised, and that first responder training ensures adequate protections. Informal communications indicated that aircraft appearance (esthetics) was the primary reason for the rejection; the committee members prefer to minimize the number of placards on the aircraft exterior.
Although the ballistic airframe parachute recovery system was installed by the factory prior to delivery of the aircraft to the owner, the as-found condition of the aircraft revealed that none of the required rocket-related placards were present on the fuselage. Additional investigation revealed that the owner had the required, unused placards in his documentation package from the aircraft manufacturer. According to the aircraft manufacturer president, the required placards had been installed when the aircraft was originally constructed, but then subsequently removed for an unspecified "photo shoot." The aircraft was then delivered to the owner without the placards installed, but provided to him in a separate package. According to the owner, he was unaware that he was supposed to affix the placards to the aircraft, and they remained stored with his aircraft documentation files. The timing of the completion of aircraft construction, the photo shoot, and the delivery of the aircraft to the customer/owner was not determined. Insufficient time between the manufacture date of the aircraft and the accident date precluded the need for an annual condition inspection, which would have provided an opportunity to detect and rectify the absence of the proper placards.
Review of the FAA form 8130-15 for the accident aircraft, which was part of the airworthiness application that was completed by the airframe manufacture, revealed that, although required, the form did not cite ASTM F2316 as one of the "Consensus Standards" that the aircraft had been manufactured to. The reasons for this discrepancy could not be determined.
NTSB Identification: WPR16LA071
14 CFR Part 91: General Aviation
Accident occurred Tuesday, February 16, 2016 in Buckeye, AZ
Aircraft: Evolution Revo, registration: N107SB
Injuries: 1 Fatal.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On February 16, 2016, about 1452 mountain standard time, an Evolution Revo light sport weight-shift control "trike," N107SB, impacted terrain shortly after takeoff from Buckeye Municipal airport (BXK), Buckeye, Arizona. The pilot, who was the sole person on board, received fatal injuries, and the aircraft was substantially damaged. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no Federal Aviation Administration (FAA) flight plan was filed for the flight.
According to the owner of the aircraft, the pilot was a friend of a friend, and was visiting the area. The pilot had some free time, and urged the owner to be allowed to fly the aircraft. Based on the pilot's credentials and behavior, the owner eventually agreed to let the pilot fly the aircraft. The evening prior to the accident, the owner (acting as pilot-in-command) took the accident pilot (as a passenger) on an uneventful flight in the aircraft. On the day of the accident, both individuals conducted the preflight inspection, with no anomalies noted.
The pilot reportedly planned to conduct a solo flight, and then return for an unspecified passenger. According to the owner, the takeoff roll on runway 17 was normal, but shortly after breaking ground, the wing went to the "full flare" position, which he explained to mean that the wing was at the full wing leading edge up position. The wing remained in that position, and the aircraft climbed rapidly and steeply, but then appeared to stall, at an altitude the owner estimated to be about 100 to 150 feet above ground level. The aircraft then "rounded out," and descended rapidly to the ground in a nose-down attitude. The aircraft was equipped with a Ballistic Recovery System brand rocket propelled parachute, but the device was not activated by the pilot.
According to FAA records, the pilot held a commercial certificate with airplane single engine land, multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. He also held a flight instructor certificate with airplane single- and multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. The pilot's most recent valid FAA medical certificate was obtained in 2004, and had expired; he was operating under the conditions of the light sport medical requirements. On that 2004 medical certificate application, the pilot reported a total flight experience of 4,500 hours.
FAA information indicated that the aircraft was manufactured in 2015, and was equipped with a Rotax 912-IS series engine. The wreckage was examined on site by FAA inspectors, and was recovered to a secure location for possible subsequent examination.
The BXK 1455 automated weather observation included winds from 130 degrees at 8 knots, visibility 10 miles, clear skies, temperature 27 degrees C, dew point minus 2 degrees C, and an altimeter setting of 29.93 inches of mercury.
BUCKEYE, AZ (KPHO/KTVK) - One person was killed when a single-engine aircraft went down in the area of the Buckeye Airport Tuesday afternoon, according to Buckeye police.
The pilot has been identified as James George III, 55, of West Fargo, ND
A number of police and fire units were at the scene.
Pictures from our news helicopter showed the wreckage in scrub grass just off a paved roadway.
The aircraft involved was a single-engine Evolution REVO light sport aircraft, a powered hang glider, with one person aboard, according to Lynn Lunsford with the Federal Aviation Administration.
"The owners of the airplane were not involved," said Office Tamela Skaggs with the Buckeye Police Department. The glider is registered to a Buckeye resident.
"George, who was an experienced pilot, has flown aircrafts (sic) of this type before," Skaggs said in an email update. "George was taking off from the Buckeye Airport and it is unknown at this time what caused the aircraft to crash."
The runway at Buckeye Airport was closed during the investigation.
Story and video: http://www.tucsonnewsnow.com
Buckeye AZ Police Department
Plane Crash Press Release
On February 16, 2016 at about 1:52 pm, the Buckeye Police Department received several 911 calls about a plane crash at the Buckeye Municipal Airport located at 3000 S Palo Verde Rd, Buckeye Az.
Upon the arrival of Buckeye Police Officers they identified the scene as a single engine aircraft that crashed on the property of the Buckeye Airport with one occupant who was pronounced deceased at the scene.
The owners of the aircraft were not involved, and the occupant has not yet been identified.
At this time how the crash happened is unknown as the scene is now being investigated.
The Buckeye Police Department, FAA, and NTSB will be working together to investigate this incident.
One person was killed when a small aircraft crashed at Buckeye Municipal Airport Tuesday afternoon, police said.
Only the pilot had been aboard the single-engine Evolution REVO light sport aircraft when it went down, according to an Federal Aviation Administration official.
Buckeye Police Department received multiple 911 calls regarding a crash at the airport, 3000 S. Palo Verde Road, at about 1:52 p.m., a police spokesman said.
The owners of the aircraft were not involved with the crash and the occupant’s identity is still unknown, police said.
Authorities said that the police department, FAA and National Transportation Safety Board are working together in investigating the incident.
Source: http://www.azcentral.com
NTSB Identification: CHI05CA074
14 CFR Part 91: General Aviation
Accident occurred Saturday, February 26, 2005 in Fargo, ND
Probable Cause Approval Date: 06/08/2005
Aircraft: Cessna 177RG, registration: N1623H
Injuries: 2 Serious.
NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.
The aircraft experienced a total loss of engine power during initial climb after takeoff. The accident flight was the first flight after the oil filter had been replaced. The pilot reported that the engine began losing power about two miles south of the departure airport. He stated that the engine seized during a turn back toward the airport. He reported that the airplane did not have enough altitude remaining to glide to a runway and that he performed a downwind landing to a nearby road because there was "no place to go into the wind, even knowing I had a 29 [knot] tailwind." The pilot reported that the airplane impacted a street light and vehicle during the forced landing to a residential area. The pilot estimated that less than 30-seconds transpired between the loss of engine power and the impact with terrain. Post accident inspection of the engine revealed that the number four connecting rod had separated and protruded through the top of the engine case. An oil film covered the oil filter, the accessory case below the oil filter, and the bottom of the fuselage. The oil system was pressurized and a leak was noted around the base of the oil filter canister. Further inspection revealed that the oil filter canister bolt was not adequately torqued and its retaining safety-wire was incorrectly installed. Additionally, the canister base gasket was incorrectly installed which allowed oil to leak out from the canister base. No leaks were noted after the gasket was repositioned and the canister was reinstalled. The pilot reported that the oil-pressure was "in green" during an engine run-up check completed prior to takeoff. Several individuals reported there was an approximately 4-foot diameter oil spill in the ramp area used by the accident airplane for start-up and pre-takeoff operations.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The mechanic's improper installation of the oil filter canister base gasket, which resulted in an oil leak and the separation of the connecting rod due to oil starvation. Factors to the accident were the unsuitable terrain encountered during the forced landing, the tailwind condition, the light pole, and the vehicle.
On February 26, 2005, at 1403 central standard time, a Cessna 177RG, N1623H, piloted by a commercial pilot, was substantially damaged during a forced landing following a loss of engine power during initial climb from runway 18 (9,000 feet by 150 feet, grooved concrete) at Hector International Airport (FAR), Fargo, North Dakota. Visual meteorological conditions prevailed at the time of the accident. The airplane delivery flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot and passenger sustained serious injuries. The flight was destined for Festus Memorial Airport (FES), Festus, Missouri.
The airplane was recently sold and a pre-buy inspection of the airplane was completed on February 23, 2005, as a condition of the sale. During this inspection the engine oil filter was replaced. The accident flight was the first leg of a delivery flight from FAR to Charlotte, North Carolina. The airplane had accumulated 0.1 hours since the pre-buy inspection.
The pilot reported that the engine began losing power about two miles south of FAR. The pilot stated that he began a turn back toward FAR and informed air traffic control (ATC) of the loss of engine power. The pilot reported that the engine seized during the turn back to the airport and the airplane did not have enough altitude remaining to glide to a runway. The pilot performed a downwind landing to a nearby road because there was "no place to go into the wind, even knowing I had a 29 [knot] tailwind." The pilot reported that the airplane impacted a street light and vehicle during the forced landing to a residential area. The pilot estimated that less than 30-seconds transpired between the loss of engine power and the impact with terrain. The pilot reported that the oil-pressure was "in green" during an engine run-up check completed prior to takeoff. Several individuals reported there was an approximately 4-foot diameter oil spill on the ramp area used by the accident airplane for start-up and pre-takeoff operations.
Inspection of the engine revealed that the number four connecting rod had separated and protruded through the top of the engine case. An oil film covered the oil filter, the accessory case below the oil filter, and the bottom of the fuselage. The oil system was pressurized with nitrogen and a leak was noted around the base of the oil filter canister. The oil filter safety-wire was tensioned to the counter-clockwise (left) direction. A torque-wrench was used to measure the installation torque of the canister bolt. The bolt began tightening at 15 ft/lbs and the bolt had rotated 90-degrees at 25 ft/lbs. The recommended torque value for the canister bolt is 20 to 25 ft/lbs. The leak at the oil fileter canister base persisted after the canister bolt had been retorqued. The oil filter canister was removed and approximately 1/4 of the canister base gasket circumference was observed to be displaced (folded) to the inside of the canister sealing surface. No leaks were noted after the gasket was repositioned and the canister was reinstalled and torqued to 15 ft/lbs.
14 CFR Part 91: General Aviation
Accident occurred Tuesday, February 16, 2016 in Buckeye, AZ
Aircraft: Evolution Revo, registration: N107SB
Injuries: 1 Fatal.
This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed. NTSB investigators may not have traveled in support of this investigation and used data provided by various sources to prepare this aircraft accident report.
On February 16, 2016, about 1452 mountain standard time, an Evolution Revo light sport weight-shift control "trike," N107SB, impacted terrain shortly after takeoff from Buckeye Municipal airport (BXK), Buckeye, Arizona. The pilot, who was the sole person on board, received fatal injuries, and the aircraft was substantially damaged. The personal flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed, and no Federal Aviation Administration (FAA) flight plan was filed for the flight.
According to the owner of the aircraft, the pilot was a friend of a friend, and was visiting the area. The pilot had some free time, and urged the owner to be allowed to fly the aircraft. Based on the pilot's credentials and behavior, the owner eventually agreed to let the pilot fly the aircraft. The evening prior to the accident, the owner (acting as pilot-in-command) took the accident pilot (as a passenger) on an uneventful flight in the aircraft. On the day of the accident, both individuals conducted the preflight inspection, with no anomalies noted.
The pilot reportedly planned to conduct a solo flight, and then return for an unspecified passenger. According to the owner, the takeoff roll on runway 17 was normal, but shortly after breaking ground, the wing went to the "full flare" position, which he explained to mean that the wing was at the full wing leading edge up position. The wing remained in that position, and the aircraft climbed rapidly and steeply, but then appeared to stall, at an altitude the owner estimated to be about 100 to 150 feet above ground level. The aircraft then "rounded out," and descended rapidly to the ground in a nose-down attitude. The aircraft was equipped with a Ballistic Recovery System brand rocket propelled parachute, but the device was not activated by the pilot.
According to FAA records, the pilot held a commercial certificate with airplane single engine land, multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. He also held a flight instructor certificate with airplane single- and multi-engine land, and instrument airplane ratings, and "sport endorsements" for gyroplane and powered parachutes. The pilot's most recent valid FAA medical certificate was obtained in 2004, and had expired; he was operating under the conditions of the light sport medical requirements. On that 2004 medical certificate application, the pilot reported a total flight experience of 4,500 hours.
FAA information indicated that the aircraft was manufactured in 2015, and was equipped with a Rotax 912-IS series engine. The wreckage was examined on site by FAA inspectors, and was recovered to a secure location for possible subsequent examination.
The BXK 1455 automated weather observation included winds from 130 degrees at 8 knots, visibility 10 miles, clear skies, temperature 27 degrees C, dew point minus 2 degrees C, and an altimeter setting of 29.93 inches of mercury.
BUCKEYE, Ariz. – A West Fargo man died Tuesday when the motorized hang glider he was piloting crashed on takeoff from a municipal airport in Buckeye, which is about 40 miles from Phoenix, according to the Buckeye Police Department.
A report issued by the police department identified the pilot as James George III, 55.
The cause of the crash has not been determined, and the case has been turned over to the Federal Aviation Administration and the National Transportation and Safety Board.
The incident happened just before 2 p.m. Tuesday.
George was previously in a serious plane crash in February 2005, when the plane he was piloting crashed-landed in a north Fargo home’s front yard.
Both George and a passenger in the plane were seriously injured in the crash, which happened when the plane’s engine seized shortly after takeoff from Hector International Airport.
It was later determined that a mechanic had improperly installed an oil filter on the plane, according to Forum archives.
At the time of the crash, George operated Eagle 1 Aviation, a flight instruction, aircraft rental and sales business.
In the aftermath of the crash, fellow pilots credited George’s skills as a pilot for avoiding injuries to anyone on the ground.
Vic Gelking, who runs Vic’s Airfield in Fargo, a flight-training business, was a friend of George and knew him well as a fellow pilot.
“He did some flying for me recently,” Gelking said, adding that after the 2005 crash George became a “pretty cautious” pilot.
Gelking said in addition to doing some freelance pilot-training work, George operated a trucking business.
Gelking said he had heard about the crash in Arizona, but he wasn’t sure what type of aircraft George was flying, other than it may have been a type of ultralight aircraft.
Such aircraft are usually known to be fairly safe to fly, he said.
The police report on Tuesday’s incident stated George was an experienced pilot who in the past had flown the type of aircraft that crashed. The report identified the aircraft as a Revo weight-shift control trike, which resembles a three-wheeled motor bike with a V-shaped wing attached overhead.
Shawn Dobberstein, executive director of the Fargo airport, said he remembered George as someone who was always enthusiastic and excited about aviation.
Dobberstein also said that George did a great job of training other pilots, though he said George appeared to cut back on those activities after his crash landing in 2005.
Story and video: http://www.inforum.com
James George III
BUCKEYE, AZ - Authorities say a North Dakota man is dead after a powered hang glider crashed while taking off from an airport in the Phoenix area.
Buckeye police say the only person aboard the aircraft when it crashed Tuesday afternoon at Buckeye Municipal Airport was the pilot, 55-year-old James George III of West Fargo, North Dakota, who was killed.
Police say the cause of the crash isn't immediately known and that federal agencies are investigating.
Police say the hang glider belonged to a Buckeye resident.
Buckeye Airport Coordinator John McMahon had just talked to the victim two hours before he died.
"Just talked to him at lunch and just to hear about his experience and about what he'd done in the past, and then to realize later on that he had been in an accident, it was difficult to see, ok, what--how is his family going to feel," McMahon said.
His job is to manage the airport, so he comes in contact with people landing on the runway every day.
"I would say everybody was familiar with the aircraft, and knowing what happened is just a sobering thought, recognizing that could happen to any of us," McMahon said
George and a passenger were seriously injured in 2005 when a single-engine plane he was piloting crashed in Fargo, North Dakota, after it lost power shortly after takeoff.
Investigators determined that a mechanic had improperly installed an oil filter on the plane, causing a large oil leak.
Story and video: http://www.abc15.com
BUCKEYE, AZ (KPHO/KTVK) - One person was killed when a single-engine aircraft went down in the area of the Buckeye Airport Tuesday afternoon, according to Buckeye police.
The pilot has been identified as James George III, 55, of West Fargo, ND
A number of police and fire units were at the scene.
Pictures from our news helicopter showed the wreckage in scrub grass just off a paved roadway.
The aircraft involved was a single-engine Evolution REVO light sport aircraft, a powered hang glider, with one person aboard, according to Lynn Lunsford with the Federal Aviation Administration.
"The owners of the airplane were not involved," said Office Tamela Skaggs with the Buckeye Police Department. The glider is registered to a Buckeye resident.
"George, who was an experienced pilot, has flown aircrafts (sic) of this type before," Skaggs said in an email update. "George was taking off from the Buckeye Airport and it is unknown at this time what caused the aircraft to crash."
The runway at Buckeye Airport was closed during the investigation.
Story and video: http://www.tucsonnewsnow.com
Plane Crash Press Release
On February 16, 2016 at about 1:52 pm, the Buckeye Police Department received several 911 calls about a plane crash at the Buckeye Municipal Airport located at 3000 S Palo Verde Rd, Buckeye Az.
Upon the arrival of Buckeye Police Officers they identified the scene as a single engine aircraft that crashed on the property of the Buckeye Airport with one occupant who was pronounced deceased at the scene.
The owners of the aircraft were not involved, and the occupant has not yet been identified.
At this time how the crash happened is unknown as the scene is now being investigated.
The Buckeye Police Department, FAA, and NTSB will be working together to investigate this incident.
One person was killed when a small aircraft crashed at Buckeye Municipal Airport Tuesday afternoon, police said.
Only the pilot had been aboard the single-engine Evolution REVO light sport aircraft when it went down, according to an Federal Aviation Administration official.
Buckeye Police Department received multiple 911 calls regarding a crash at the airport, 3000 S. Palo Verde Road, at about 1:52 p.m., a police spokesman said.
The owners of the aircraft were not involved with the crash and the occupant’s identity is still unknown, police said.
Authorities said that the police department, FAA and National Transportation Safety Board are working together in investigating the incident.
Source: http://www.azcentral.com
NTSB Identification: CHI05CA074
14 CFR Part 91: General Aviation
Accident occurred Saturday, February 26, 2005 in Fargo, ND
Probable Cause Approval Date: 06/08/2005
Aircraft: Cessna 177RG, registration: N1623H
Injuries: 2 Serious.
NTSB investigators used data provided by various entities, including, but not limited to, the Federal Aviation Administration and/or the operator and did not travel in support of this investigation to prepare this aircraft accident report.
The aircraft experienced a total loss of engine power during initial climb after takeoff. The accident flight was the first flight after the oil filter had been replaced. The pilot reported that the engine began losing power about two miles south of the departure airport. He stated that the engine seized during a turn back toward the airport. He reported that the airplane did not have enough altitude remaining to glide to a runway and that he performed a downwind landing to a nearby road because there was "no place to go into the wind, even knowing I had a 29 [knot] tailwind." The pilot reported that the airplane impacted a street light and vehicle during the forced landing to a residential area. The pilot estimated that less than 30-seconds transpired between the loss of engine power and the impact with terrain. Post accident inspection of the engine revealed that the number four connecting rod had separated and protruded through the top of the engine case. An oil film covered the oil filter, the accessory case below the oil filter, and the bottom of the fuselage. The oil system was pressurized and a leak was noted around the base of the oil filter canister. Further inspection revealed that the oil filter canister bolt was not adequately torqued and its retaining safety-wire was incorrectly installed. Additionally, the canister base gasket was incorrectly installed which allowed oil to leak out from the canister base. No leaks were noted after the gasket was repositioned and the canister was reinstalled. The pilot reported that the oil-pressure was "in green" during an engine run-up check completed prior to takeoff. Several individuals reported there was an approximately 4-foot diameter oil spill in the ramp area used by the accident airplane for start-up and pre-takeoff operations.
The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The mechanic's improper installation of the oil filter canister base gasket, which resulted in an oil leak and the separation of the connecting rod due to oil starvation. Factors to the accident were the unsuitable terrain encountered during the forced landing, the tailwind condition, the light pole, and the vehicle.
On February 26, 2005, at 1403 central standard time, a Cessna 177RG, N1623H, piloted by a commercial pilot, was substantially damaged during a forced landing following a loss of engine power during initial climb from runway 18 (9,000 feet by 150 feet, grooved concrete) at Hector International Airport (FAR), Fargo, North Dakota. Visual meteorological conditions prevailed at the time of the accident. The airplane delivery flight was operating under the provisions of 14 CFR Part 91 without a flight plan. The pilot and passenger sustained serious injuries. The flight was destined for Festus Memorial Airport (FES), Festus, Missouri.
The airplane was recently sold and a pre-buy inspection of the airplane was completed on February 23, 2005, as a condition of the sale. During this inspection the engine oil filter was replaced. The accident flight was the first leg of a delivery flight from FAR to Charlotte, North Carolina. The airplane had accumulated 0.1 hours since the pre-buy inspection.
The pilot reported that the engine began losing power about two miles south of FAR. The pilot stated that he began a turn back toward FAR and informed air traffic control (ATC) of the loss of engine power. The pilot reported that the engine seized during the turn back to the airport and the airplane did not have enough altitude remaining to glide to a runway. The pilot performed a downwind landing to a nearby road because there was "no place to go into the wind, even knowing I had a 29 [knot] tailwind." The pilot reported that the airplane impacted a street light and vehicle during the forced landing to a residential area. The pilot estimated that less than 30-seconds transpired between the loss of engine power and the impact with terrain. The pilot reported that the oil-pressure was "in green" during an engine run-up check completed prior to takeoff. Several individuals reported there was an approximately 4-foot diameter oil spill on the ramp area used by the accident airplane for start-up and pre-takeoff operations.
Inspection of the engine revealed that the number four connecting rod had separated and protruded through the top of the engine case. An oil film covered the oil filter, the accessory case below the oil filter, and the bottom of the fuselage. The oil system was pressurized with nitrogen and a leak was noted around the base of the oil filter canister. The oil filter safety-wire was tensioned to the counter-clockwise (left) direction. A torque-wrench was used to measure the installation torque of the canister bolt. The bolt began tightening at 15 ft/lbs and the bolt had rotated 90-degrees at 25 ft/lbs. The recommended torque value for the canister bolt is 20 to 25 ft/lbs. The leak at the oil fileter canister base persisted after the canister bolt had been retorqued. The oil filter canister was removed and approximately 1/4 of the canister base gasket circumference was observed to be displaced (folded) to the inside of the canister sealing surface. No leaks were noted after the gasket was repositioned and the canister was reinstalled and torqued to 15 ft/lbs.
No comments:
Post a Comment