Runway excursion Serious incident Gulfstream G200 N718QS,
ASN logo
ASN Wikibase Occurrence # 314564
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 22 November 2010
Time:09:29 LT
Type:Silhouette image of generic GALX model; specific model in this crash may look slightly different    
Gulfstream G200
Owner/operator:NetJets
Registration: N718QS
MSN: 136
Total airframe hrs:3511 hours
Engine model:P&W Canada PW306A
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: None
Category:Serious incident
Location:Jackson, Wyoming -   United States of America
Phase: Landing
Nature:Ferry/positioning
Departure airport:Bozeman Yellowstone International Airport, MT (BZN/KBZN)
Destination airport:Jackson Hole Airport, WY (JAC/KJAC)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR11IA055
Status: Investigation completed
Duration: 1 year and 4 months
Download report: Final report

Sources:

NTSB WPR11IA055

Location

Revision history:

Date/timeContributorUpdates
02-Jun-2023 18:38 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org