20000727039819A

Accident · Substantial damage

FAA accident report · Robsin R22 BETA · Phoenix, AZ · July 27, 2000

Date
July 27, 2000 · 09:00 local
Place
Phoenix, AZ
Phase of flight
Other Ground Ops
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N888KB
NTSB investigation
NTSBLAX00LA279
Reported as
Robsin R22BETA
Reported engine
Lycoming O360*
People aboard
1
Fatal injuries
0

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23)During solo cross country flight student pilot landed in a desert area used as a practice landing site. After touchdown the aircraft remained on the ground for about a minute at idle. After applying power for takeoff the aircraft began to shake uncontrollably and the pilot shut down the aircraft. Inspection of the helicopter revealed a damage tail rotor and gear box, one tail rotor blade had separated and was found several yards away. The damage parts were sent to the manufacturer for evaluation. (.4) on July 27, 2000, at 0900 hours mountain standard time, a Robinson R-22 beta, N888KB, experienced a tail rotor failure while standing with the engine and rotors idling in a field near Phoenix, Arizona. The aircraft sustained substantial damage; however, the student pilot, the sole occupant, was not injured. The aircraft was being operated as an instructional flight by universal helicopters, inc., under 14 CFR part 91 when the accident occurred. The flight originated in wickenburg, Arizona, earlier that morning. Visual meteorological conditions prevailed at the time and no flight plan was filed. The pilot reported that he intended to land in a field used by the o perator as a practice area in order to make some entries in his navigational log. He initiated his approach to the center of a field, terminating at a 5-foot hover. He then hovered forward about 150 feet looking for a smooth, level surface on which to touch down. After selecting his touchdown point, he performed a 360-degree pedal turn to determine wind direction and make certain he would be landing into the wind. He performed a smooth touchdown, reduced the throttle to idle, turned the governor off, and set the control frictions. He was at idle for about a minute, entering his flight time on his cross-country log and determining the heading for the final leg back to scottsdale airport. In preparation for departure, the pilot released the control frictions and began to increase the throttle. As the power approached 95 percent, but before engaging the governor, the aircraft began to shake uncontrollably and the antitorque pedals began to move under his feet. He immediately reduced the throttle to idle, took out the checklist, and shutdown the aircraft per the instructions. After shutdown, the pilot exited the aircraft and inspected it for damage. He noted visible damage to the tail rotor and vertical stabilizer. He then notified the operator by cell phone and stayed with the aircraft until help arrived.

As the FAA filed it

(-23)DURING SOLO CROSS COUNTRY FLIGHT STUDENT PILOT LANDED IN A DESERT AREA USED AS A PRACTICE LANDING SITE. AFTER TOUCHDOWN THE AIRCRAFT REMAINED ON THE GROUND FOR ABOUT A MINUTE AT IDLE. AFTER APPLYING POWER FOR TAKEOFF THE AIRCRAFT BEGAN TO SHAKE UNCONTROLLABLY AND THE PILOT SHUT DOWN THE AIRCRAFT. INSPECTION OF THE HELICOPTER REVEALED A DAMAGE TAIL ROTOR AND GEAR BOX, ONE TAIL ROTOR BLADE HAD SEPARATED AND WAS FOUND SEVERAL YARDS AWAY. THE DAMAGE PARTS WERE SENT TO THE MANUFACTURER FOR EVALUATION. (.4) ON JULY 27, 2000, AT 0900 HOURS MOUNTAIN STANDARD TIME, A ROBINSON R-22 BETA, N888KB, EXPERIENCED A TAIL ROTOR FAILURE WHILE STANDING WITH THE ENGINE AND ROTORS IDLING IN A FIELD NEAR PHOENIX, ARIZONA. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE; HOWEVER, THE STUDENT PILOT, THE SOLE OCCUPANT, WAS NOT INJURED. THE AIRCRAFT WAS BEING OPERATED AS AN INSTRUCTIONAL FLIGHT BY UNIVERSAL HELICOPTERS, INC., UNDER 14 CFR PART 91 WHEN THE ACCIDENT OCCURRED. THE FLIGHT ORIGINATED IN WICKENBURG, ARIZONA, EARLIER THAT MORNING. VISUAL METEOROLOGICAL CONDITIONS PREVAILED AT THE TIME AND NO FLIGHT PLAN WAS FILED. THE PILOT REPORTED THAT HE INTENDED TO LAND IN A FIELD USED BY THE O PERATOR AS A PRACTICE AREA IN ORDER TO MAKE SOME ENTRIES IN HIS NAVIGATIONAL LOG. HE INITIATED HIS APPROACH TO THE CENTER OF A FIELD, TERMINATING AT A 5-FOOT HOVER. HE THEN HOVERED FORWARD ABOUT 150 FEET LOOKING FOR A SMOOTH, LEVEL SURFACE ON WHICH TO TOUCH DOWN. AFTER SELECTING HIS TOUCHDOWN POINT, HE PERFORMED A 360-DEGREE PEDAL TURN TO DETERMINE WIND DIRECTION AND MAKE CERTAIN HE WOULD BE LANDING INTO THE WIND. HE PERFORMED A SMOOTH TOUCHDOWN, REDUCED THE THROTTLE TO IDLE, TURNED THE GOVERNOR OFF, AND SET THE CONTROL FRICTIONS. HE WAS AT IDLE FOR ABOUT A MINUTE, ENTERING HIS FLIGHT TIME ON HIS CROSS-COUNTRY LOG AND DETERMINING THE HEADING FOR THE FINAL LEG BACK TO SCOTTSDALE AIRPORT. IN PREPARATION FOR DEPARTURE, THE PILOT RELEASED THE CONTROL FRICTIONS AND BEGAN TO INCREASE THE THROTTLE. AS THE POWER APPROACHED 95 PERCENT, BUT BEFORE ENGAGING THE GOVERNOR, THE AIRCRAFT BEGAN TO SHAKE UNCONTROLLABLY AND THE ANTITORQUE PEDALS BEGAN TO MOVE UNDER HIS FEET. HE IMMEDIATELY REDUCED THE THROTTLE TO IDLE, TOOK OUT THE CHECKLIST, AND SHUTDOWN THE AIRCRAFT PER THE INSTRUCTIONS. AFTER SHUTDOWN, THE PILOT EXITED THE AIRCRAFT AND INSPECTED IT FOR DAMAGE. HE NOTED VISIBLE DAMAGE TO THE TAIL ROTOR AND VERTICAL STABILIZER. HE THEN NOTIFIED THE OPERATOR BY CELL PHONE AND STAYED WITH THE AIRCRAFT UNTIL HELP ARRIVED.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N888KB · 1

Matched to the same aircraft by N-number and date.