Portland-Hillsboro Airport
Aircraft Accident/Incident Report

Portland, Oregon 97124
Wednesday, November 17, 2010 15:53 PST

NTSB Narrative Summary Released at Completion of Accident

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.

NTSB Probable Cause Narrative

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.

Event Information

Type of Event Accident
Event Date 11/17/2010
Event Day of the Week Wednesday
Time of Event 1553
Event Time Zone Pacific Standard Time
Event City Portland
Event State OREGON
Event Country --
Zipcode of the event site 97124
Event Date Year 2010
Event Date Month 11
MidAir Collision Indicator No
On Ground Collision occurred ? No
Event Location Latitude 453304N
Event Location Longitude 1225739W
Event Location Airport Portland-Hillsboro
Event Location Nearest Airport ID HIO
Indicates whether the acc/inc occurred off or on an airport On Airport
Distance from airport in statute miles 1
Degrees magnetic from airport --
Airport Elevation 208
Weather Briefing Completeness --
Investigator's weather source Weather Observation Facility
Time of the weather observation 1553 Pacific Standard Time
Direction of event from weather observation facility (degrees) --
Weather Observation Facility ID HIO
Elevation of weather observation facility 208
Distance of event from weather observation facility (units?) 0
Time Zone of the weather observation PST
Lighting Conditions Day
Lowest Ceiling Height 1300
Lowest Non-Ceiling Height --
Sky/Lowest/Cloud Conditions --
Sky Condition for Lowest Ceiling Overcast
Visibility Runway Visual Range (Feet) --
Visibility Runway Visual Value (Statute Miles) --
Visibility (Statute Miles) 2
Air Temperature at event time (in degrees celsius) 9
Dew Point at event time (in degress fahrenheit) 8
Wind Direction (degrees magnetic) 190
Variable Wind Indicator Wind direction could be determined
Wind Speed (knots) 8
Wind Velocity Indicator --
Wind Gust Indicator Not Gusting
Wind Gust (knots) --
Altimeter Setting at event time (in. Hg) 29.76
Density Altitude (feet) --
Intensity of Precipitation --
METAR weather report METAR KHIO 172353Z 19008KT 2SM RA BR OVC013 09/08
Event Highest Injury None
On Ground, Fatal Injuries --
On Ground, Minor Injuries --
On Ground, Serious Injuries --
Injury Total Fatal --
Injury Total Minor --
Injury Total None 2
Injury Total Serious --
Injury Total All --
Investigating Agency NTSB
NTSB Docket Number (internal use) 30850
NTSB Notification Source NM ROC
NTSB Notification Date --
NTSB Notification Time --
Fiche Number and/or location -used to find docket information --
Date of most recent change to record Mar 26 2013 10:25AM
User who most recently changed record stam
Basic weather conditions Instrument Meteorological Cond
FAA District Office --

Aircraft Involved

Aircraft #1

Aircraft Registration Number N25PJ
NTSB Number WPR11FA052
Missing Aircraft Indicator --
Federal Aviation Reg. Part Part 91: General Aviation
Type of Flight Plan filed IFR
Flight plan Was Activated? Yes
Damage Substantial
Aircraft Fire None
Aircraft Explosion None
Aircraft Manufacturer's Full Name GATES LEAR JET
Aircraft Model 25B
Aircraft Series Identifier --
Aircraft Serial Number 111
Certified Max Gross Weight 15000
Aircraft Category Airplane
Aircraft Registration Class --
Aircraft is a homebuilt? No
Flight Crew Seats 2
Cabin Crew Seats --
Passenger Seats 5
Total number of seats on the aircraft 7
Number of Engines 2
Fixed gear or retractable gear Fixed
Aircraft, Type of Last Inspection AAIP
Date of Last Inspection Jul 29 2010 12:00AM
Airframe hours since last inspection --
Airframe Hours 8453
ELT Installed Yes
ELT Activated Yes
ELT Aided Location of Event Site No
ELT Type --
Aircraft Owner Name PREMIER JETS INC
Aircraft Owner Street Address --
Aircraft Owner City HILLSBORO
Aircraft Owner State OR
Aircraft Owner Country USA
Aircraft Owner Zipcode 97124-5962
Operator is an individual? No
Operator Name PREMIER JETS INC
Operator Same as Owner? Yes
Operator Is Doing Business As --
Operator Address Same as Owner? Yes
Operator Street Address --
Operator City HILLSBORO
Operator State OR
Operator Country USA
Operator Zip code 97124-5962
Operator Code CMWA
Owner has at least one certificate Yes - certificate holder
Other Operator of large aircraft? No
Certified for Part 133 or 137 Operation --
Operator Certificate Number --
Indicates whether an air carrier operation was scheduled or not --
Indicates Domestic or International Flight --
Operator carrying Pax/Cargo/Mail --
Type of Flying (Per_Bus / Primary) Positioning
Second Pilot on Board Yes
Departure Point Same as Event No
Departure Airport Code BOI
Departure City Boise
Departure State ID
Departure Country USA
Departure Time 1545
Departure Time Zone MST
Destination Same as Local Flt crash at destination city
Destination Airport Code HIO
Destination City Portland
Destination State OR
Destination Country USA
Specific Phase of Flight --
Report sent to ICAO? --
Evacuation occurred --
Date of most recent change to record Dec 15 2012 12:18PM
User who most recently changed record stam
Since inspection or accident Time of Accident
Event Location Runway Number and Location 30
Runway Length 6600
Runway Width 150
Sight Seeing flight No
Air Medical Flight No
Medical Flight --