# Incident 19981226044699I: Boeing 737300, Jackson, WY, December 26, 1998

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 26, 1998, 21:21 local time
- Place: Jackson, WY
- Airport: Jackson Hole
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: Air carrier (Part 121)
- Operator: UALA
- Location: 43.6073° N, 110.7377° W: Placed by OpenAirDocs at JACKSON HOLE (JAC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=43.6073&lon=-110.7377&mi=10
- Aircraft: N352UA, a cancelled registration (https://openairdocs.org/deregistered/N352UA-2005-05-16) (OpenAirDocs)
- Registry model: Boeing 737-322 (registry code 138447Y, https://openairdocs.org/model/boeing-737-322) (OpenAirDocs)
- Registry engine: CFM International CFM56 series (registry code 13802, https://openairdocs.org/engine/cfm-international-cfm56-series) (OpenAirDocs)
- Reported make and model: BOEING 737300
- People aboard: 131
- Fatal injuries: 0
- Pilot flight hours: 9,500 total, 1,737 in this make and model, 220 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19981226044699I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THIS IS A REPORT CONCERNING THE UNITED AIR LINES B-737-300 THAT WENT OFF THE RUNWAY AT JACKSON HOLE, WYOMING ON 12/26/98. UAL FLIGHT 1956 LAX/JAC WAS UNDER THE COMMAND OF CAPTAIN^PRIVACY DATA OMITTED^ AND WAS ASSISTED BY F/O^PRIVACY DATA OMITTED^          .BOTH PILOTS WERE EXPERIENCED ON THE B-737-300, BUT IT WAS THEIR FIRST ENTRY INTO JACKSON HOLE. CAPTAIN^PRIVACY DA^HAS 9500 TOTAL FLIGHT HOURS, WITH 1737 IN THE B-737 TYPE AIRCRAFT. F/O^PRIVAC^HAS 5500 TOTAL FLIGHT HOURS, WITH 2090 IN THE B-737 TYPE AIRCRAFT. UNITED AIR LINES' SOP'S INDICATE THAT LANDINGS AT JACKSON HOLE SHOULD BE MADE WITH MAX FLAP SETTING FOR THE WEIGHT AND RUNWAY CONDITIONS AND THAT AUTO BRAKES SHOULD BE AT LEVEL 3. THE APPROACH WAS INITIATED WITH FLAPS 40 AND A VREF OF APPROXIMATELY 132 KTS WITH A TARGET SPEED OF 152 KTS. THE WIND WAS 210/16 GUSTING TO 26. DURING THE APPROACH THE WIND GUSTS AND APPROACH SPEED CAUSED THE FLAPS TO BLOW UP TO THE 30 POSITION. THE CREW ELECTED TO LEAVE THE FLAPS AT 30 AND CONTINUE THE APPROACH BECAUSE OF THE EXISTING CONDITIONS. THE AUTO BRAKES WERE SELECTED TO LEVEL 3 AND THE AUTO SPEED BRAKE WAS ARMED AS PER SOP'S. CAPTAIN^PRIVACY DATA^REPORT INDICATES THAT THE                  BRAKING ACTION WAS FAIR AND IS VERIFIED BY THE JACKSON HOLE AIRPORT RUNWAY CONDITION FRICTION MEASUREMENT REPORT ( AVERAGE MU#=38.6). THERE WAS A STATEMENT MADE IN THE AIR CARRIER INCIDENT REPORT THAT THE PILOT WAS INFORMED THE BRAKING ACTION WAS FAIR TO POOR AND THAT WAS VERFIED BY THE ATC TAPE. BUT THE JACKSON HOLE AIRPORT SUPPLEMENTARY INCIDENT REPORT INDICATED THE CAPTAIN REPORTED TOUCHIN DOWN WITHIN 1000 TO 2000 FT OF THE LANDING ZONE. THE AIRCRAFT WAS IN GOOD WORKING CONDITION WITH NO INOPERATIVE COMPONENTS THAT WOULD IMPAIR THE THE AIRCRAFT'S PERFORMANCE. JACKSON HOLE AIRPORT HAS NO OPERATING CONTROL TOWER THAT COULD GIVE THE FLIGHT CREWS UP-TO-DATE INFORMATION CONCERNING THE BRAKING ACTION OR ANY OTHER USEFUL INFORMATION. THE RUNWAY LENGTH IS A FACTOR IN THIS INCIDENT BECAUSE ITS LENGTH IT ONLY 6305 FT WITH AN ELEVATION OF 6445 ABOVE SEA LEVEL. ^PRIVACY DATA OMITTED^ . THERE WERE APPARENTLY NO SOFT WARE PROBLEM AREAS. THE FLIGHT CREW DID NOT HAVE AT THEIR DISPOSAL ALL THE TOOLS THAT COULD HAVE MADE FOR A BETTER DECISION, I.E.A CURRENT BRAKING ACTION REPORT, A CHECK AIRMAN EXPERIENCED IN TH                                                                                      E AREA AND IN PARTICULAR THAT AIRPORT OR HIGH ALTITUDE AIRPORT OPERATIONS, TRAINING IN HIGH ALTITUDE OR SPECIAL AIRPORT (FAR 121.445) OPERATIONS, AND DISPATCH UNABLE TO CONTACT THE FLIGHT CREW VIA ACARS IN A TIMELY MANNER. THE DENVER FSDO SUBMITTED A SAFETY RECOMMENDATION CONCERNING THE JACKSON HOLE AIRPORT ON AUGUST 4, 1998 OUTLINING MANY OF THESE ELEMENTS AS POTENTIAL PROBLEM AREAS. ^PRIVACY DATA OMITTED^

## Other reports on N352UA (1)

Matched to the same aircraft by N-number and date.

- [Incident 19980610024089I](https://openairdocs.org/incident/19980610024089I), Jun 10, 1998: Boeing 737322 (N352UA), Nashville, TN. Diverted to bna due to inoperative horizontal stabilizer trim system.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
