The U.S. aircraft register, updated daily
Accidents · NTSB WPR11FA052 · Final report

Gates Lear Jet 25B accident near Portland, Oregon, November 17, 2010

On November 17, 2010 at about 11:53 pm local time, a Gates Lear Jet 25B, registered N25PJ, was substantially damaged in an accident during landing (flare/touchdown) near Portland, Oregon (Portland-Hillsboro airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 17, 2010 · about 11:53 pm local time
Place
Portland, Oregon · Portland-Hillsboro · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Gates Lear Jet 25B · all 25Bs on the register
Registration
N25PJ · registry record · serial 111
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The airplane was flying a VOR/DME-C approach that was on an oblique course about 40 degrees to the runway 30 centerline; the wind conditions produced an 8-knot tailwind for landing on runway 30. Despite the tailwind, the captain elected to land on the 6,600-foot-long runway instead of circling to land with a headwind. Moderate to heavy rain had been falling for the past hour, and the runway was wet. The crew said that the airplane was flown at the prescribed airspeed (Vref) for its weight with the wing flaps fully extended on final approach, and that they touched down just beyond the touchdown zone. The captain said that he extended the wings' spoilers immediately after touchdown. He tested the brakes and noted normal brake pedal pressure. However, during rollout, he noted a lack of deceleration and applied more brake pressure, with no discernible deceleration. The airplane's optional thrust reversers had been previously rendered non-operational by company maintenance personnel and were therefore not functional. The captain 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 (which would have bypassed the anti-skid system) because he thought that there was insufficient time, and he was preoccupied with maintaining control of the airplane. He asked the first officer to apply braking with him, and together the crew continued applying brake pedal pressure; however, 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 the airplane was still travelling between 85 and 90 knots. The airplane traveled 618 feet through a rain-soaked grassy runway safety area before encountering a drainage swale that collapsed the nose gear. As the airplane was traversing the soft, wet field, its wheels partially sank into the ground. While decelerating, soil impacted the landing gear wheels and struts where wiring to the antiskid brake system was located. The crew said that there were no indications on any cockpit annunciator light of a system failure or malfunction; however, after the airplane came to a stop they observed that the annunciator light associated with the antiskid system for the No. 2 wheel was illuminated (indicating a system failure). The other three annunciator lights (one for each wheel) were not illuminated. During the approach, the first officer had completed the landing data card by using a company-developed quick reference card. The quick reference card’s chart, which contained some data consistent with the landing charts in the Airplane Flight Manual (AFM), did not have correction factors for tailwind conditions, whereas the charts in the AFM do contain corrective factors for tailwind conditions. The landing data prepared by the first officer indicated that 3,240 feet was required to stop the airplane on a dry runway in zero wind conditions, with a wet correction factor increasing stopping distance to 4,538 feet. The Vref speed was listed as 127 knots for their landing weight of 11,000 pounds, and the first officer’s verbal and written statements noted that they crossed the runway threshold at 125 knots. During the investigation, Bombardier Lear calculated the wet stopping distances with an 8-knot tailwind as 5,110 feet. The touchdown zone for runway 30 is 1,000 feet from the approach end. The crew’s estimate of their touchdown location on the runway is about 1,200 feet from the approach end, yielding a remaining runway of 5,400 feet. On-duty controllers in the tower watched the landing and said that the airplane touched down in front of the tower at a taxiway intersection that is 1,881 feet from the approach end, which would leave about 4,520 feet of runway to stop the airplane. The controllers observed water spraying off the airplane’s main landing gear just after touchdown. Postaccident testing indicated that the brake system, including the brake wear, was within limits, with no anomalies found. No evidence of tire failure was noted. The antiskid system was removed from the airplane for functional tests. The control box and the left and right control valves tested within specifications. The four wheel speed sensors met the electrical resistance specification. For units 1, 2 and 3, the output voltages exceeded the minimum specified voltages for each of the listed frequencies. Unit 4 was frozen and could not be rotated and thus could not be tested. Sensors 1 and 2 exceeded the specified 15% maximum to minimum voltage variation limit. Sensor 3 was within the limit and 4 could not be tested. Based on all the evidence, it is likely that the airplane touched down on the water-contaminated runway beyond the touchdown zone, at a point with about 600 feet less remaining runway than the performance charts indicated that the airplane required for the wet conditions. Since a reverted rubber hydroplaning condition typically follows an encounter with dynamic hydroplaning, the reverted rubber signatures on the No. 2 tire indicate that the airplane encountered dynamic hydroplaning shortly after touchdown, and the left main gear wheel speed sensor anomalies allowed the left tires to progress to reverted rubber hydroplaning. This, along with postaccident testing, indicates that the anti-skid system was not performing optimally and, in concert with the hydroplaning conditions, significantly contributed to the lack of deceleration during the braking attempts.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Landing area overshoot during landing (flare/touchdown) defining event
  2. Runway excursion during landing (landing roll)
  3. Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
  4. Landing gear collapse during landing (landing roll)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Aircraft capability › Landing distance › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Organizational issues › Management › Resources › Adequacy of documents/info › Operator
  • Environmental issues › Physical environment › Runway/land/takeoff/taxi surfa › Wet › Contributed to outcome
  • cause Aircraft › Aircraft systems › Landing gear system › Anti › skid section › Not specified

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
  • Flight time: 6,000 hours in all; 23 in the last 90 days; 18 in the last 30 days
  • Last flight review: September 19, 2010
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 652 hours in all; 10 in this make and model; 10 in the last 90 days; 10 in the last 30 days; 220 as pilot in command
  • Last flight review: May 7, 2010
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 8,453 hours
  • Last inspection: approved inspection programme, July 29, 2010
  • Maximum gross weight: 15,000 lb
  • Seats: 7
  • Landing gear: fixed
  • Engine 1: Ge CJ610-6 (turbojet); 0 hours total
  • Engine 2: Ge CJ610-SER (turbojet); 0 hours total
  • Operator: Premier Jets INC

The flight

  • Departed from: BOI Boise ID at 10:45 pm
  • Destination: HIO Portland OR
  • Flight plan: IFR
  • Runway 30, 6,600 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 190° at 8 knots
  • Visibility: 2 statute miles
  • Sky: overcast at 1,300 ft
  • Temperature: 48°F (9°C), dew point 46°F (8°C)
  • Altimeter: 29.76 inHg
  • Observation at 11:53 pm from HIO

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.