United Airlines Flight 863

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 summary
Date 28 June 1998
Summary Near-CFIT
Site after takeoff from San Francisco International Airport
Passengers 288
Crew 19
Fatalities 0
Injuries (non-fatal) 0
Survivors 307 (all)
Aircraft type Boeing 747-400
Operator United Airlines
Flight origin San Francisco International Airport
Destination Sydney Airport

On June 28, 1998 a United Airlines Boeing 747-400 flying United's regularly scheduled transpacific service from San Francisco 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 to change pilot training requirements.

Flight

Flight 863 to Sydney departed from San Francisco International Airport on the evening of 28 June 1998. As it took off, the Boeing 747-400 entered fog at the end of runway 28R.[1] After lifting off, the crew experienced a "loud thumping noise" accompanied by vibration just after the aircraft's landing gear had retracted.[1] 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 (91 m) above ground level, the first officer initially believed one of the tires had failed.[1] At the same time, the exhaust gas temperature of the #3 engine (the inboard engine on the starboard wing) rose to 750°C, exceeding the takeoff limit of 650°C.[1] With the first officer still flying, the captain retarded the #3 engine throttle to idle, which stopped the temperature rise and aircraft vibration.[1]

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.[1] At that point, the stick shaker system activated and the captain took over control of the aircraft.[1] The captain later stated he held the aircraft level to gain airspeed and avoid a stall,[1] 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.

This photograph, taken from a blimp over Burlingame, California (foreground), shows the runways at San Francisco airport (in the middle of the picture) and their proximity to San Bruno Mountain (in the background).

According to the cockpit voice and flight data recordings, rather than using the rudders, the first officer had tried to compensate for the right drift by turning the aircraft to the left. Turning the aircraft involved the use of ailerons and spoilers on the wing, which increased the aircraft's drag and activated the stick shaker stall warning again.[2][3] The relief pilots urged the first officer to enter a shallow dive to gain airspeed and avoid a stall,[2][3] but this soon brought the aircraft close to San Bruno Mountain, and the ground proximity warning alerted the relief pilots and first officer to pull up to avoid striking the hill.[3] By later accounts, the aircraft narrowly cleared San Bruno Mountain by only 100 feet (30 m).[2] 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 [...]"[2][4] 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.[2]

After the near-miss, UA863 was vectored out to sea to dump fuel to reduce weight and return to San Francisco for an overweight landing.[1] During the 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."[1] 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 instituted mandatory pilot training and rules, including mandating the use of the rudder in the event of an engine failure upon takeoff.[2] 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.[2][3] Aviation media consultant Barry Schiff noted the incident, in an article descrying the lack of basic stick-and-rudder skills, especially among pilots who had never flown a light aircraft.[5]

References

  1. 1 2 3 4 5 6 7 8 9 10 Flight Crew, UA863 (June 1998). "ACN 406810". Aviation Safety Reporting System. Retrieved 13 January 2017. Search for Report Number (ACN) 406810.
  2. 1 2 3 4 5 6 7 Carley, William M. (19 March 1999). "United 747's Near Miss Initiates A Widespread Review of Pilot Skills". The Wall Street Journal. Archived from the original on 8 January 2015. Retrieved 13 January 2017. (subscription required)
  3. 1 2 3 4 5 6 Johnson, Glen (20 March 1999). "United pilot inexperienced in landings nearly crashed 747". Pittsburgh Post-Gazette. Associated Press. Retrieved 13 January 2017.
  4. 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.
  5. Schiff, Barry (5 June 1999). "Proficient pilot: Lazy-rudder syndrome". Aircraft Owners and Pilots Association. Retrieved 13 January 2017.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.