ISRAEL AIRCRAFT INDUSTRIES GULFSTREAM 200 near Jackson, WY — 2010-11-22
- Date
- 2010-11-22
- Location
- Jackson, WY, USA
- Airport
- JAC
- Aircraft
- ISRAEL AIRCRAFT INDUSTRIES GULFSTREAM 200
- Registration
- N718QS
- Category
- Airplane
- Highest injury
- None
- Fatalities
- 0
- Phase of flight
- Landing
Probable cause
The flight crew's inability to stop the airplane during landing roll on a snow- and ice-contaminated runway. Contributing to the runway overrun were the deteriorating runway conditions.
Contributing factors
Contributing to the runway overrun were the deteriorating runway conditions.
NTSB narrative
The flight crew reported that, prior to the flight, they were initially delayed due to weather and low runway friction values (MU) at their intended destination. (MU values range from 0 and 100, where 0 is the lowest friction value and 100 is the maximum friction value. A MU value of 40 or less is the level at which aircraft braking performance starts to deteriorate and directional control begins to be less responsive.) Dispatch personnel later reported that the conditions had improved and that the crew was released for the flight. While en route, the crew monitored weather and runway conditions at the destination airport and calculated the required landing distances, which they found to be within acceptable limits for the reported MU values of 41, 37, and 36. About 10 minutes before landing, MU values were reported as 40, 42, and 40, with patchy thin snow over patchy thin packed snow and ice on the runway surface. The flight crew received these MU values, continued their approach to the airport, and landed. During the landing roll, thrust reversers were deployed, and the crew noted that all of the ground and air slat indication lights were green and that the anti-skid system began to pulse; however, the airplane was not slowing down. Despite the application of maximum thrust reverse, there was no effect on slowing the airplane, and it exited the departure end of the 6,300-foot runway and came to rest just beyond the blast pad. The flight crew reported no mechanical malfunctions or failures with the airplane that would have precluded normal operation. About 7 minutes after the runway overrun, MU values were recorded as 34, 33, and 23. As indicated by the MU values reported just prior to landing, and the lower values reported shortly after landing, the landing was made at a time when the runway conditions were deteriorating, and the braking performance was becoming less effective.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Flight crew should have reassessed landing conditions before landing.
NTSB coding
- Runway excursion · Landing-landing roll
Evidence available
- CVR
- 9 docket documents
Docket documents9
- Cockpit Voice Recorder 12 - Specialist's Factual Reportcvr
- Excerpt of the Federal Aviation Administration Aeronautical Information Manual, Chapter 4, Section 3.form
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Statement of Party Representatives to NTSB Investigation - Net Jetsinterview
- Statement of Party Representatives to NTSB Investigation - Net Jets Association of Shared Aircraft Pilot'sinterview
- Survival Factors Specialist's Factual Report - Attachment 1: Pilot Statementsinterview
- Airport Saab 9-5 SFT Runway Friction Test Logs and Printoutother
- Survival Factors Specialist's Factual Reportreport
- Survival Factors Specialist's Factual Report - Attachment 2: Letter of Agreementreport
Related mishaps
- JEREMY PRICE SMITH SUPER CUB
2026-07-19 · Allisonia, VA
- CESSNA 172S
2026-06-17 · DEATH VALLEY, CA
- PIPER PA 31P 350
2026-04-17 · Ardmore, OK
- CESSNA 180K
2026-03-27 · Beloit, KS
- CESSNA T210
2026-03-11 · Upland, CA
- FRANKEWICH WALTER S-21 OUTBOUND
2026-01-19 · Madisonville, TN