Accident Details
Probable Cause and Findings
THE PILOT/OPERATOR'S OPERATION OF THE HELICOPTER WITH A DISCONNECTED THROTTLE ON THE RIGHT COLLECTIVE; THE FAA INSPECTOR'S INADEQUATE PREFLIGHT/PRETAKEOFF CHECKS OF THE FLIGHT CONTROL/THROTTLE SYSTEMS; AND THE PILOT/OPERATOR'S FAILURE TO ADEQUATELY INFORM THE INSPECTOR OF THE DISCONNECTED RIGHT THROTTLE, WHICH RESULTED IN AN INADEQUATE POWER RECOVERY FROM AN INSPECTOR INITIATED AUTOROTATION.
Aircraft Information
Registered Owner (Historical)
Analysis
History of the Flight
On September 22, 1994, at 1145 hours Pacific daylight time, a Hughes (McDonnell Douglas) 369D helicopter, N58352, collided with the terrain at Genoa, Nevada. The pilots were conducting a local area visual flight rules pilot recurrency check and a Title 14 CFR 135.293 pilot proficiency flight check. The helicopter, operated by Skydance Helicopters, Inc., El Cajon, California, sustained substantial damage. The certificated commercial pilot (first pilot) and the certificated airline transport pilot, a Federal Aviation Administration (FAA) operations inspector, sustained minor injuries. Visual meteorological conditions prevailed. The flight originated at Douglas County Airport, Minden, Nevada, at 1000 hours.
National Transportation Safety Board investigators interviewed the FAA inspector (herein called the examining inspector) at the Reno Flight Standards District Office on September 26, 1994. In addition, the examining inspector provided the Safety Board with a written statement. Safety Board investigators also conducted two other telephone interviews on September 22 and September 23, 1994, respectively.
The examining inspector said that the accident flight was a dual purpose flight. Initially he was going to become recurrent in the accident helicopter make and model; he had not flown one in over a year. Secondly, he was going to provide the pilot with a Title 14 CFR Part 135.293 pilot proficiency check as required by the regulations.
The examining inspector arrived at the operator's facility at 0900 hours. The pilot/operator (the pilot) then provided the examining inspector with some changes in the helicopter operations and ground checks. The inspector continued the preflight inspection and also asked the pilot some questions to satisfy the oral portion of the pilot's pilot proficiency check.
During the preflight inspection, the inspector did not check the right seat flight controls, including the throttle continuity. (The flight manual does not specifically require this action.) The inspector and operator discussed in depth the starting procedure while the examining inspector was in the left front seat; the seat normally used by the flying pilot.
The examining inspector helped the pilot in removing the helicopter from the hangar. The inspector sat in the left seat when the helicopter was on the ramp. The pilot operator stood to the left of the inspector during the start. The inspector thought that the pilot was doing fire guard duties. After the inspector initiated the engine start, the pilot returned to the helicopter and occupied the right front seat.
The examining inspector did a hovering maneuver and made some pedal turns to assure that the helicopter was operating normally before he departed on the accident flight. The flight departed the airport and flew to a lower mountain range east of the airport. He also did several maneuvers including a power off autorotation to a power on recovery.
While in this area, the examining inspector asked the pilot to do some maneuvers to satisfy the pilot's required items under the 14 CFR 135.293; the inspector reasoned that by having the pilot do these maneuvers, the flight would not have to return to the area. The maneuvers included a pinnacle approach, a confined area approach, and a slope landing. The pilot satisfactorily executed these maneuvers.
The examining inspector reassumed the controls and flew to a higher mountainous area about 4 miles west of the airport and about 1 mile east of the accident site. Upon arrival over the mountainous area, the inspector did several maneuvers including those he asked the pilot to do. During this time, the pilot also demonstrated a few slope landing techniques. Afterwards, the examining inspector flew toward the airport.
After passing over the mountainous area, the examining inspector reduced the power and asked the pilot to do a power off autorotation to a designated landing area. The pilot entered the autorotation and began to fly toward the designated landing area. The examining inspector said the pilot's technique during the autorotation flight pattern was "textbook"; the pilot's airspeed control and glide path were perfect.
During the final approach, about 300 feet above the ground, the examining inspector said he saw the N2 (the turbine power indicator) and the main rotor rpm needles come together. When the helicopter approached the landing area, the examining inspector did not feel any heavy collective movement; he did feel some cyclic movement. The helicopter then sustained a hard landing.
On touchdown, the helicopter began to violently "rock back and forth." The main rotor blades severed the tailboom assembly and the engine continued to run. When the helicopter was rocking back and forth, the examining inspector attempted to reach for the fuel control shut off valve located on the lower section of the instrument panel, but was unable to do so. He shut off the engine by placing the left collective throttle to the cut-off position.
Before exiting the helicopter, the examining inspector reported that he observed the right collective on the floor and either one or two of the pedals lying on the front of the helicopter. After both pilots exited the helicopter, the inspector saw the pilot place the collective and one or two of the pedals on the right front seat.
Safety Board investigators interviewed the pilot/operator on September 26, 1994, at his maintenance facility, Douglas County Airport. The pilot said that his son prearranged the accident flight. He concurred the scheduled flight was a dual purpose flight as stated by the examining inspector. He said that the examining inspector arrived at his facility at 0930 hours.
He then observed the examining inspector preflight the helicopter. During the preflight inspection, he informed the examining inspector of certain changes in the helicopter. He told Safety Board investigators that he considered the initial flight was a dual instructional flight to help the examining inspector in becoming current in the helicopter make and model. The pilot also confirmed the examining inspector's statement that he explained the start procedure in depth. He said after he and the examining inspector moved the helicopter out of the hangar he stood by the examining inspector while he started the engine. He said this was the only time he told the examining inspector that the right seat throttle was inoperative; he did not go into a detailed explanation. He stood at the door next to the examining inspector during the start so he could shut off the engine in case of a hot start.
The pilot concurred with the examining inspector's statement regarding the route of the flight. He said, however, that the examining inspector did all of the flying except during the accident rotation. He concurred that the examining inspector told him to do a simulated emergency landing (autorotation) to a designated area. The pilot said that he always does autorotations with full power and that he normally "flys out at the bottom of the autorotation."
He said that he was not aware that the examining inspector had retarded the throttle to idle before he began the autorotation. Both he and the examining inspector were talking via the "hot mike" during the maneuver. When the helicopter was between 8 and 10 feet above the ground, he applied up collective.
During the collective application, the pilot realized that engine power was not available and then knew a hard landing was imminent. He said that after the accident, his foot was jammed between the antitorque pedals. He removed the pedals to release his foot, but he did not recall removing the collective. He said he could have, but did not have a clear recollection of doing so.
The pilot also said that the examining inspector emphasized that he was the pilot-in-command (PIC), but that if a real emergency existed the pilot would assume control of the helicopter. The examining inspector said that whoever was flying the helicopter was the PIC. He did say that if a real emergency occurred he would have transferred control to the pilot because of his, the examining inspector's, lack of familiarity of the helicopter.
Crew Information
First Pilot (Pilot/Operator)
The pilot held a commercial pilot certificate with a rotorcraft - helicopter rating. He also held a second- class medical certificate with a "Must have available glasses for near vision" endorsement. The pilot provided the Safety Board with the flight hours reflected on page 3 from memory. He did not have his flight hours logbook in his possession.
The pilot said that he had accrued more than 15,000 flight hours of which more than 6,000 hours were flown in the accident helicopter make and model. The pilot satisfactorily completed the last Title 14 CFR 135.293 pilot proficiency check flight administered by an FAA inspector on August 1, 1993. The proficiency flight check was flown in the accident helicopter make and model.
Second Pilot (FAA Examining Inspector)
The examining inspector holds an airline transport pilot certificate with airplane single-engine land, multiengine land, rotorcraft - helicopter, instrument - airplane and helicopter, and DC-9, B-727, CE-650, BH-204, and DH-206 type ratings. He also holds a flight instructor certificate with airplane single-engine, airplane multiengine, rotorcraft - helicopter, and instrument - airplane and helicopter ratings.
The flight hours reflected on Supplement E of this report were provided by the pilot in the Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1/2. Safety Board investigators did not review the inspector's flight hours logbook. The inspector also showed that he had satisfactorily completed a biennial flight review (BFR) on July 14, 1994; the BFR was flown in a DC...
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# LAX94FA372