PROFILPELAJAR.COM

United Airlines Flight 863
	Boeing 747-400s of United Airlines at San Francisco International Airport; San Bruno Mountain rises to a peak of 1,319 feet (402 m) in the background, excluding radio towers.
Occurrence
Date	June 28, 1998
Summary	Near-CFIT
Site	San Bruno Mountain, after takeoff from San Francisco International Airport
Aircraft
Aircraft type	Boeing 747-422
Operator	United Airlines
IATA flight No.	UA863
ICAO flight No.	UAL863
Call sign	UNITED 863
Registration	N???UA
Flight origin	San Francisco International Airport, San Mateo County, California
Destination	Sydney Airport, Sydney, New South Wales, Australia
Occupants	307
Passengers	288
Crew	19
Fatalities	0
Injuries	0
Survivors	307

On June 28, 1998, United Airlines Flight 863, a Boeing 747-400 flying United's regularly scheduled transpacific service from San Francisco International Airport to Sydney Airport was forced to shut down one of its right-wing engines and nearly collided with San Bruno Mountain while recovering from the engine failure. The aircraft was able to dump fuel over the Pacific Ocean and return to San Francisco for an overweight landing, but the occurrence prompted United Airlines to change pilot training requirements.

Flight

Flight 863 to Sydney departed from San Francisco International Airport at 10:39 pm PST on Sunday June 28, 1998 (UTC: 5:39 am, 29 June).^[1] As it took off, the Boeing 747-400 entered fog at the end of runway 28R.^[2] After lifting off, the crew experienced a "loud thumping noise" accompanied by vibration just after the aircraft's landing gear had retracted.^[2] The first officer was handling the takeoff under the captain's supervision, and since the noise occurred just after the landing gear had been retracted, at approximately 300 feet (90 m) above ground level, the first officer initially believed one of the tires had failed.^[2] At the same time, the exhaust gas temperature of the #3 engine (the inboard engine on the starboard wing) rose to 750 °C (1,380 °F), exceeding the takeoff limit of 650 °C (1,202 °F).^[2] With the first officer still flying, the captain retarded the #3 engine throttle to idle, which stopped the temperature rise and aircraft vibration.^[2]

There were two non-flying relief pilots in the cockpit during takeoff; both noticed the aircraft had lost approximately 40 knots indicated airspeed after the problems with #3 engine and shouted 'airspeed' to the first officer to alert him to the potential stall danger.^[2] At that point, the stick shaker system activated and the captain took over control of the aircraft.^[2] The captain later stated he held the aircraft level to gain airspeed and avoid a stall,^[2] but it had drifted to the right due to the imbalanced thrust and narrowly missed colliding with San Bruno Mountain, which rises to a height of 1,319 feet (402 m) above sea level, excluding the television and radio towers on its summit.

According to the cockpit voice and flight data recordings, rather than using the rudder, the first officer had tried to compensate for the right drift by turning the aircraft to the left using ailerons, which control the aircraft's longitudinal "roll" axis rather than the vertical "yaw" axis which would have been the correct response to compensate for an asymmetrical thrust condition. The use of ailerons also deployed spoilers on the "down" wing, which increased the aircraft's net drag and decreased its net lift. A second activation of the stick shaker stall warning resulted.^[1]^[3] The relief pilots urged the flight crew to enter a shallow dive to gain airspeed and avoid a stall,^[1]^[3] but this soon brought the aircraft close to San Bruno Mountain. The ground proximity warning system then alerted the captain, who had since taken over flying the aircraft, to pull up to avoid striking the hill.^[3]

By later accounts, the plane narrowly cleared San Bruno Mountain by only 100 feet (30 m).^[1] The aircraft had approached San Bruno Mountain so closely that air traffic control radars briefly stopped detecting the aircraft. An air traffic controller in the San Francisco tower was conversing with one of her colleagues and said, "... Is United 863 still ... oh there he is, he scared me, we lost radar, I didn't want to give you another airplane if we had a problem."^[1]^[4] In total, the aircraft had disappeared from radar for approximately 15 seconds.^[5] Residents in houses along the flight path, in South San Francisco, Daly City, and San Francisco, called into the airport to complain about the noise and voice their fears the aircraft was about to crash.^[1]

After the near-collision, UA863 was vectored out to sea to dump fuel to reduce weight and return to San Francisco for an overweight landing.^[2] During the initial climbout, the first officer stated he had noted the aircraft was handling sluggishly and was slow to climb, which he instinctively responded to by "[pulling] the nose up just a bit more to climb away from the ground."^[2] The first officer had limited experience, having made only one takeoff and landing in a 747 during the year preceding the occurrence.^[3]

Aftermath

United Airlines revised its training protocols after the incident by implementing much more rigorous standards, which ultimately became industry-wide standards. All 9,500 of United's pilots were shown a recreation of the occurrence, filmed in one of United's simulators.^[3] As a compromise, pilots were required to make at least three takeoffs and landings in a 90-day period, of which at least one had to be in an actual aircraft.^[1]^[3] Aviation media consultant Barry Schiff noted the incident in an article decrying the lack of basic stick-and-rudder skills, especially among pilots who had never flown a light aircraft.^[6]

United still uses Flight 863 for its transpacific service from San Francisco to Sydney, but now using a Boeing 777-300ER.^[7]

References

^ ^a ^b ^c ^d ^e ^f ^g Carley, William M. (19 March 1999). "United 747's Near Miss Initiates A Widespread Review of Pilot Skills". The Wall Street Journal. ISSN 0099-9660. Archived from the original on 8 January 2015. Retrieved 13 January 2017.
^ ^a ^b ^c ^d ^e ^f ^g ^h ⁱ ^j Flight Crew, UA863 (June 1998). "ACN 406810". Aviation Safety Reporting System. Retrieved 13 January 2017.{{cite web}}: CS1 maint: numeric names: authors list (link) Search for Report Number (ACN) 406810.
^ ^a ^b ^c ^d ^e ^f Johnson, Glen (20 March 1999). "United pilot inexperienced in landings nearly crashed 747". Pittsburgh Post-Gazette. Associated Press. Archived from the original on 17 December 2015. Retrieved 13 January 2017.
^ Orr, Bob (15 April 1999). "A High-Flying Brush With Death". CBS News. Archived from the original on 25 August 2014. Retrieved 13 January 2017.
^ "747 Just Missed San Bruno Mountain in June". San Francisco Chronicle. March 19, 1999. Retrieved 22 August 2019.
^ Schiff, Barry (5 June 1999). "Proficient pilot: Lazy-rudder syndrome". Aircraft Owners and Pilots Association. Retrieved 13 January 2017.
^ "UA863 (UAL863) United Flight Tracking and History - FlightAware". Retrieved 29 September 2021.

External links

Arnold, Robert (2015). Role of pilot lack of manual control proficiency in air transport aircraft accidents. 6th International Conference on Applied Human Factors and Ergonomics. doi:10.1016/j.promfg.2015.07.862.
Atkinson, James F. (11 July 2013). "OPINION: Do pilots have adequate flying skills?". San Francisco Chronicle. Retrieved 13 January 2017.