Aviation Accident Summaries

Aviation Accident Summary WPR15TA002

Grass Valley, CA, USA

Aircraft #1

N700PQ

ROCKWELL INTERNATIONAL 690B

Analysis

The airline transport pilot reported that, after returning from a fire mission, the airplane floated over the runway and landed long (about 1,500 to 1,800 ft down the runway, which left a maximum of about 2,850 ft of runway remaining). He reduced the power setting to flight idle and then adjusted the thrust levers to (beta) reverse. As the landing roll continued, the pilot adjusted the levers for less reverse thrust. Aware that the ground speed was too fast to make the normal exit turnoff, he applied full reverse thrust again. The airplane then swerved left, departed the runway, impacted some boulders, and came to rest upright in a drainage area. A postaccident examination of the brake system and engines revealed no evidence of mechanical failures or malfunctions that would have precluded normal operation. If the pilot had initiated a go-around when he realized the airplane was going to land long, he would not have had to modulate the reverse thrust multiple times to make the turnoff.

Factual Information

HISTORY OF FLIGHT On October 4, 2014, at 1343 Pacific daylight time, a Rockwell International 690B airplane, N700PQ, departed the runway surface and impacted medium sized boulders, and came to rest in a drainage area at the Nevada County Air Park (GOO), Grass Valley, California. The airplane was registered to Rogers Helicopters, Inc. and operated under an exclusive use contract to the United States Forest Service (USFS) as a public aircraft. The pilot and two USFS passengers were not injured. The airplane sustained substantial damage to the fuselage undercarriage. The local area flight departed GOO at 0953 in support of the King Fire. Visual meteorological conditions prevailed, and a company flight plan had been filed. The flight was designated as an Air Attack flight for the King Fire; a pilot and two Air Attack Group Supervisors (ATGS) were onboard. The mission flight was uneventful, and after transition with another crew and aircraft, the accident airplane returned to base. Upon landing, the pilot reported that the airplane floated and landed slightly long. He reduced the power setting to flight idle, and then moved the thrust levers to beta (reverse). On the landing roll out, the pilot adjusted levers for less reverse thrust, and indicated that he would not be able to make his normal exit turnoff. He knew he needed to slow down in order to make the next turnoff. He applied full reverse again; the airplane made a 'violent swerve' to the left, and departed the runway. The pilot stated that it was not even 5 seconds between the first time he pulled full reverse to the second time he pulled full reverse. The pilot applied right rudder and brake to return the airplane to the runway; however, the airplane continued to exit the runway surface into the infield where it impacted several medium-sized boulders, and came to rest upright in a drainage area. The front-seated passenger had flown with the pilot on five previous missions. On the accident flight, the mission was briefed. The first part of the flight, he was seated in the back so he could watch the other passenger function as ATGS. A switch was then made so that he could complete some GPS proficiency training. During the return to the airport, he was seated in the front. During the approach, he noted that the temperature was in the upper 80's, and the gauges were normal; no lights were illuminated, and no audible warnings sounded. The pilot made the same approach that the passenger had witnessed on the previous five missions. The airplane landed on the centerline of the runway; the pilot reversed the throttle, and it felt like they were being pulled to the left. The pilot tried to keep the airplane on the runway. The airplane came to a stop off the edge of the runway. The rear-seated passenger had flown with the pilot for the past 3 years. The mission was briefed, and they departed shortly thereafter. For the first part of the flight, he was seated in the front, so that the rear-seated passenger could observe his actions. Following the aerial supervision transition with another aircraft, they flew toward the north, which allowed him to change seats with the rear-seated passenger. Garmin GPS training was completed and they returned to Grass Valley. The approach and landing were consistent with previous missions that he had flown on with the pilot. About 3-4 seconds after landing, the airplane began to drift to the left of the runway. He watched the pilot attempt to make corrections to the airplane to remain on the runway. The passenger stated that he recalled seeing the sloped, uneven terrain, and structures approaching the left side of the airplane. The airplane came to a stop in the dirt, the pilot shut down the airplane, and they exited the airplane. PERSONNEL INFORMATION The 73-year old pilot held an Airline Transport Pilot certificate with ratings for airplane single-engine land and sea, multiengine land, and instrument airplane. The pilot was issued a class 2 medical certificate on April 13, 2014, with the limitation that he must have available glasses for near vision. His last flight review was conducted on May 20, 2014. The pilot reported his total flight time as 26,520 hours with 550 hours in the accident make and model. AIRCRAFT INFORMATION The airplane was a Rockwell International; N700PQ, manufactured in 1977. It was powered by two Garrett TPE-331-5-251 turbo prop engines. The engines were equipped with Hartzell propellers. According to the operator, the airplane was maintained under an Approved Inspection Program (AAIP). The last inspection was signed off and the airplane was returned to service on October 3, 2014, with an airframe total time of 8,625.1 hours. Both engines were manufactured in 1977. Engine number 1, serial number P-06769 had a recorded total time of 8,338.6 hours, with 1,050.4 hours since the last inspection and 2,932.8 hours since overhaul. Engine number 2, serial number P-06923 had a total time of 8,338.4 hours, with 1,050.4 hours since the last inspection, and 292.8 hours since overhaul. AIRPORT INFORMATION The Airport Facility Directory, Southwest, for GOO, indicated that runway 07 was 4,351 feet long by 75 feet wide. The runway surface was asphalt. The airport elevation was 3,154 feet. METEOROLOGICAL INFORMATION Recorded weather at 1340 for GOO indicated clear weather conditions with visibility 10 miles; temperature 84 degrees Fahrenheit; altimeter 30.15 inches of mercury, relative humidity at 15 percent; wind from the west-southwest at 08 knots, and a density altitude calculated as 5,269 feet. TEST AND RESEARCH The airplane was inspected with structural damage identified to the undercarriage. According to a representative from Honeywell, there should have been no reasons that reverse could not have been selected multiple times; unless the governor was not adjusted properly. Upon landing with speed levers at high rpm, there should not have been a lag in the engine when placed into reverse again. The representative stated that in the engine maintenance manual were procedures that pertained to governor checks and adjustment procedures, and that the governor settings had to be checked before they were removed to verify their setting. The USFS representative reported that the governor settings were normal; however, they did find a loose fuel control rod end for the left engine. The USFS representative reported that normal touchdown for runway 07 is 1,000 feet down the runway. According to USFS calculations, the accident airplane landed between 1,500-1,800 feet from the threshold, which left a maximum of 2,850 feet of runway remaining with 302 feet of stop-way useable for the landing rollout. An examination of the airframe, engine, and related systems revealed no anomalies that would have precluded normal operation.

Probable Cause and Findings

The pilot’s unstabilized approach and failure to go around and his subsequent failure to maintain directional control during the landing roll.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports