NTSB Factual Report

HISTORY OF FLIGHT

On November 17, 2010, about 1553 Pacific standard time, a Gates Lear Jet, 25B, N25PJ, experienced separation of its nose gear assembly upon impacting terrain during a landing overrun accident at the Portland-Hillsboro Airport (HIO), Portland, Oregon. The airplane was owned and operated by Premier Jets, Inc., Hillsboro, Oregon, and it was substantially damaged. Neither the airline transport certificated pilot-in-command (PIC) nor the commercial licensed second-in-command (SIC) was injured. Instrument meteorological conditions prevailed at the time of the positioning flight that was performed under the provisions of 14 Code of Federal Regulations Part 91. An instrument flight rules (IFR) flight plan was filed. The flight originated from Boise, Idaho, about 1545 mountain standard time (68 minutes before the accident).

The pilots reported to the National Transportation Safety Board investigator that the accident occurred on the return leg of a round-trip flight from HIO to Boise. No evidence of any mechanical malfunction or system anomaly was noted with the airplane on the outbound flight.

The PIC, who was the flying pilot during both the outbound and inbound legs, reported that on the return leg the air traffic controller cleared him to perform the VOR/DME-C instrument approach procedure (IAP) to HIO. He flew this approach and elected to circle to land on runway 30, rather than circle to land on runway 12. [There is no straight-in landing option on this IAP.] The PIC said that on short final approach the airplane was flown at the prescribed airspeed (Vref), with the wing flaps fully extended. According to the PIC, in all respects the approach and landing were normal.

The PIC further reported that he extended the wings' spoilers immediately after touchdown. He tested the brakes and normal brake pedal pressure was noted. However, during rollout he noted a lack of deceleration and more brake pressure was applied, with no discernable deceleration. The airplane's optional thrust reversers were not used; they had been previously rendered non-operational by company maintenance personnel and were therefore not functional.

According to the PIC, although the indicated brake pressure remained normal, within a few seconds both he and the second pilot recognized that the airplane was not appropriately decelerating. The PIC stated that he directed the SIC try applying his brakes. The SIC reported to the Safety Board investigator that he complied with the PIC's directions. However, the airplane did not appropriately decelerate.

The PIC stated that he thought about performing a go around, but believed that insufficient runway remained to ensure a safe takeoff. While trying to stop, he did not activate the emergency brakes. He stated that there was insufficient time, and he was preoccupied with maintaining control of the airplane. According to the PIC, he continued applying brake pedal pressure, and when the airplane was about 2,000 feet from the runway's end, it was still traveling about 100 knots. As the airplane rolled off the departure end on runway 30, which was wet, both pilots estimated that it was still travelling between 85 and 90 knots. (Activation of the emergency brakes is accomplished by applying downward pressure to an activation handle located adjacent to the center console. Activation of emergency brakes bypasses the antiskid system.)

The PIC further reported to the Safety Board investigator that he had no indication on any cockpit annunciator light of a system failure or malfunction. As the airplane was traversing the soft, wet field, its wheels partially sank into the ground. The nose gear sheared off in an aft direction when the airplane impacted and traversed the drainage ditch. Thereafter, the airplane slid on its nose until coming to a stop in the rain water-soaked field. While decelerating, soil impacted the landing gear wheels and struts where wiring to the antiskid brake system was located.

The PIC stated that after the airplane came to a stop he observed that the annunciator light associated with the antiskid system for the #2 wheel was illuminated (indicating a system failure). The other three annunciator lights (one for each wheel) were not illuminated.

During a subsequent conversation with the Safety Board investigator, the PIC initially opined that the brake and/or antiskid system appeared to have malfunctioned. The pilot stated that although the runway was wet, he did not believe the airplane hydroplaned. The pilot further stated that he opted to continue trying to decelerate rather than attempting to go-around because by the time he realized there was a deceleration problem, insufficient runway existed to ensure that a departure could be successfully performed from the remaining runway.

On duty Federal Aviation Administration (FAA) air traffic control tower (ATCT) personnel reported that the airplane appeared to have touched down abeam the ATCT at the intersection of taxiway A6 and runway 30. This intersection is located about 1,900 feet from runway 30's approach end, and about 4,700 feet from the runway's departure end.

The HIO ATCT's front line manager reported that while in the control tower, he observed the airplane approach the airport on the VOR/DME-C approach. The local controller offered the pilot any runway of his choice to use for landing, and he issued the pilot a wind check which indicated that the wind was from 180 degrees at 10 knots, with 16 knot gusts. The pilot requested and was cleared to land on runway 30. The airplane touched down in front of the ATCT, near the intersection of taxiway A6 and runway 30.

Another HIO air traffic controller reported that it was raining when the airplane landed, and the runway was wet. The controller stated that he observed water spraying off the airplane's main gear as the airplane passed in front of the control tower at the intersection of taxiway A-6 and runway 30.

According to the SIC's statements and a review of the airplane's radar derived flight track as it approached the airport revealed that the airplane was tracking on a northeasterly course and approached the airport from the southwest. As the airplane approached the airport, the pilot maneuvered its flight path into the base leg for runway 30. Thereafter, the pilot made a left turn, entered onto the final approach course, and landed. The second pilot stated that he recalled the approach was stabilized at Vref when on the final approach leg. Also, the airplane was initially above the visual glide path, but when on short final approach the airplane was on the visual glide path.

PERSONNEL INFORMATION

Pilot

The pilot, age 56, held an Airline Transport Pilot certificate with a multi-engine land rating, and type ratings in the Lear Jet series, Cessna 500, and the Swearingin SA-227. He also held commercial privileges for airplanes single engine land and sea. The pilot’s most recent Federal Aviation Administration FAA 14 CFR 135.293 and 135.299 checkrides were accomplished on September 19, 2010, in the Lear 25B. The pilot held a first class medical certificate that was issued September 1, 2010, with the limitation that correcting lenses be worn. The pilot reported a total of 6,000 flight hours, with his recent flight experience in the 90 and 30 days prior to the accident estimated at 23 and 18 respectively, with 5 hours accrued in the Lear 25B.

Co-pilot

The Second in Command (SIC), age 34, held a commercial pilot certificate with ratings for airplanes single and multi-engine land and instruments. He also held a first class medical certificate issued July 20, 2010, with the limitation that correcting lenses be worn. The pilot reported a total flight time of 652 hours, with 10 hours accrued in the Lear 25B. The pilot said that in the preceding 90 days to the accident he had flown 10 hours. The pilot’s most recent FAA 14 CFR 135.293 and 135.299 checkrides were accomplished on May 7, 2010, in a Lear 35. FAA inspectors examined the pilot’s records and determined that he met the qualifications to act as a Second in Command in Learjets as specified in 14 CFR 61.55(f)(2).

The PIC was the owner of Premier Jets. He employed the second-in-command, who worked on a full time basis as his office manager, and also served as an on-demand air taxi pilot for the company.

AIRPLANE INFORMATION

Records review disclosed that the Lear 25B, serial number 25-111, was manufactured in 1973 and had accrued a total time in service of 8,453 hours at the time of the accident. The most recent maintenance check under the company’s approved inspection program was accomplished on July 29, 2010. The airplane was equipped with 2 GE CJ610-6 engines that had accrued total times in service of 8,561 hours for the left engine and 8,632 for the right.

The crew reported the airplanes landing weight as 10,800 pounds, and they used sea level altitude and an outside air temperature of 50 degrees F in calculating the required landing distance.

The crew used a company developed quick reference chart to determine the landing distance and Vref speed. Review of the quick reference chart and the ones from the Airplane Flight Manual disclosed they produced similar numbers. Reference of both charts for the stated conditions, found that 3,240 feet were required to stop the airplane on a dry runway in zero wind conditions. The wet runway correction factor was listed as 1.4 times the dry distance, yielding a wet runway stopping distance of 4,538 feet. The Vref speed was listed as 127 knots for 11,000 pounds. The SIC’s verbal and written statements noted that they crossed the runway threshold at 125 knots.

The quick reference chart used by the crew did not have correction factors for tailwind conditions. Bombardier Lear calculated the dry and wet stopping distance incorporating an 8 knot tailwind and reported stopping distances of 3,640 feet and 5,110 feet respectively.

METEOROLOGICAL INFORMATION

At 1553, the Automatic Terminal Information Service (ATIS) broadcast the airport's weather as, in part, wind from 180 degrees at 8 knots. There was an overcast ceiling at 1,300 feet above ground level, and the visibility was 2 miles in moderate intensity rain and mist. During the landing radio exchange between the local controller and the airplane’s crew, the controller told the crew that the winds were from 180 degrees at 10 knots, with gusts to 16 knots.

AIDS TO NAVIGATION

According to FAA records of facility operations, all electronic aids to navigation pertinent to the aircraft's route of flight were functional on the day of the accident.

AIRPORT INFORMATION

Runways.

Runway 12/30 is 6,600 feet long by 150 feet wide. It has an asphalt non-grooved surface. Airport management reported that its surface condition was "good."

Runway 12's threshold elevation is 199.9 feet mean sea level (msl). Runway 30's threshold elevation is 198.0 feet msl. Landing on runway 30 provides a 0.2 percent uphill gradient. The magnetic course of runway 30 is 307.1 degrees.

The last surface rubber removal project was performed on 2003. Airport management reported that within a few months before or following the accident, it has not received complaints regarding poor or marginal stopping ability due to inadequate runway surface friction.

On February 11, 2011, the airport tested the surface friction (Mu) for runway 30. The runway's friction was found average between 0.670 and 0.701.

FLIGHT RECORDERS

The flight recorders were not obtained or read-out.

WRECKAGE AND IMPACT INFORMATION

Initially, the departure end of runway 30, adjacent safety area (RSA), and the runway protection zone (RPZ), were examined by HIO management staff and the FAA coordinator who responded to the accident site. Subsequently, the area was examined by the Safety Board investigator. Global positioning satellite measurements and area survey data were provided by the airplane operator and airport management personnel.

Based upon estimated 3- to 6-inch deep depressions in the soil that are consistent in appearance with the airplane's landing gear, the airplane impacted and severed a runway end light before overrunning the 203-foot- long RSA. The airplane then rolled downslope (estimated between 5 and 9 degrees) until impacting a rain water flooded drainage swale, which was located 470 feet from the runway's end. The airplane's separated nose gear strut, with attached wheel assembly, was found near the swale in the RPZ, where the ground was near level. The airplane traversed the swale with its nose on the ground. The airplane came to rest on a northwesterly heading in an upright and nose low pitch attitude in the soft, rain-soaked, near level open field. The approximate distance between the runway's end and the airplane was 618 feet.

A portion of the airplane's belly was found punctured aft of where the nose gear had been attached, and belly skin panels were torn open. A portion of the forward pressure bulkhead was bent, and the bottom of the pressure vessel was punctured. There was no evidence of fire.

All of the airplane's flight control systems and engines were intact. No evidence of fuel leakage was found. The flight crew reported that the emergency locator transmitter (ELT) activated. Neither of the flight crew seats were damaged.

The left inboard wheel speed transducer wires were noted to be chaffed near the transducer connecter.

TESTS AND RESEARCH

Touchdown Location and Runway Distance Calculation

The SIC opined that the airplane touched down prior to the location where runway 20 intersects runway 30. [This intersection is about 1,337 feet from runway 30's threshold.]

Two on duty HIO air traffic controllers reported observing the airplane arrive. One of the controllers indicated that the airplane touched down in front of the tower on runway 30 near the intersection of taxiway A-6. The second controller reported observing water spraying off the airplane's main landing gear when it passed the tower by taxiway A-6. This controller also stated that the airplane appeared to be travelling a little faster than usual. [The intersection of runway 30 and taxiway A-6 is located about 1,881 feet from runway 30's threshold.]

Based upon these reported touchdown locations, the maximum and minimum runway length available for the airplane to decelerate was about 5,900 and 4,649 feet, respectively.

Tire Examination

The tires were examined by a representative from Goodyear Tire. The tires are numbered as follows: #1, left outboard wheel; #2 left inboard wheel; #3 right inboard wheel; and #4 right outboard wheel.

No evidence of tire failure was noted. All of the tires were found inflated. The tread depth in all tires was measured, and in no case was the depth less than about 1/32-inch. No evidence of bulging or chord was showing on any tire.

Tire # 1, 3 and 4 had the least tread depth, ranging between 1/32- to 3/32-inches. Tire # 2 had the most tread depth, ranging from 2/32- to 4/32 inches.

Tire #2 exhibited two areas of reverberated rubber hydroplaning. No such evidence was observed on any other tire.

Tire Air Pressure

The tires' air pressure was not ascertained until February 2, 2011. On this date the nose tire was found inflated to 100 pounds/square inch (psi). The main tires were found at 119, zero, 119, and 50 psi, respectively (left outboard, left inboard, right inboard, and right outboard). Mechanics reported that tires of this design may lose 10 psi/month.

Landing Gear Squat Switches

The antiskid system is precluded from activating unless the squat switch indicates that the airplane has weight on its wheels and the gear strut is compressed to a prescribed level. Additional activation components relate to the positioning of the switch on the gear strut.

An examination of the squat switch was accomplished and the switch was found internally functional. In addition, no anomalies were found regarding its positioning on the gear strut.

Brake System, Normal

The brakes and hydraulic brake activation system was examined. The brakes were found within limits and no anomalies were found. The brake wear measurements were found to be 0.200, 0.200, 0.280

NTSB Probable Cause

The failure of the flight crew to stop the airplane on the runway due to the flying pilot’s failure to attain the proper touchdown point. Contributing to the accident was an anti-skid system that was not performing optimally, which allowed the airplane to encounter reverted rubber hydroplaning, and the company-developed quick reference landing distance chart that did not provide correction factors related to tailwind conditions.