FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR11IA055 · Israel Aircraft Industries GULFSTREAM 200

22 Nov 2010 · Jackson, WY, United States

Netjets Sales Israel Aircraft Industries GULFSTREAM 200 · Incident: runway excursion during landing

From Bozeman Yellowstone International Airport (BZN) to Jackson Hole Airport (JAC)

Report a problem

Event

NTSB case
WPR11IA055
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Incident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Israel Aircraft Industries GULFSTREAM 200

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N718QS
Onboard fatalities
Unknown
Route
From Bozeman Yellowstone International Airport (BZN), Bozeman, MTTo Jackson Hole Airport (JAC), Jackson, WY
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft oper/perf/capability

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

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.

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR11IA055
Event ID
20101122X80707
Case number
WPR11IA055
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 55bb3318b5397b62e62f04965a326f878de67fc367e2e6746f483eec163fdf62; retrieved 2026-09-15T15:34:44.184Z.