Plane crash map Locate crash sites, wreckage and more

N178UA accident description

California map... California list
Crash location 37.618889°N, 122.391389°W
Reported location is a long distance from the NTSB's reported nearest city. This often means that the location has a typo, or is incorrect.
Nearest city San Francisco, CA
37.774929°N, 122.419415°W
10.9 miles away
Tail number N178UA
Accident date 14 Nov 2003
Aircraft type Boeing 747-422
Additional details: None

NTSB Factual Report

On November 14, 2003, about 1250 Pacific standard time, United Airlines Flight 805, a Boeing 747-422, N178UA, experienced a tail strike on rotation at San Francisco, California. United Airlines, Inc., was operating the airplane as a scheduled international passenger flight under the provisions of 14 CFR Part 121. The airline transport pilot licensed captain, 3 aircrew members, 17 flight attendants, and 335 passengers were not injured. The airplane sustained substantial damage. The flight was en route as a non-stop to Hong Kong, China. Visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan had been filed.

The operator submitted a written report. The first officer was the Pilot Flying (PF), and the airplane departed on runway 10L. The winds were 180 at 16, gusting to 22 knots. The takeoff roll was normal, and the PF utilized control wheel input to correct for the crosswind. A few seconds after rotation, the PF noted the stick shaker annunciate, and responded by gently easing back pressure off the control yoke. The captain and a relief pilot felt a nose wheel vibration following the takeoff.

The air traffic control tower contacted the flight crew alerting them of a possible tail strike after observing smoke from the airplane at rotation. The crew returned to land at San Francisco. Evaluation of the damage resulted in structural repair to two structural members.

A National Transportation Safety Board specialist examined the solid state flight data recorder (FDR) and prepared a factual report. It included graphical plots of pertinent data. Boeing also evaluated the FDR data.

The data indicated that the takeoff occurred during variable wind conditions. The wind shifted resulting in a decreasing headwind, and an increasing crosswind, to an average 8-knot tailwind during rotation. During the takeoff roll, the data showed right control wheel inputs and left rudder pedal, suggesting that the winds had a crosswind component from the right. The maximum pitch rate was slightly higher than average, but within the normal expected variation. Boeing felt that this was a minor contributor to the tail strike. The PF used significant wheel input (35 degrees right wheel); this resulted in the right spoiler raising 12 degrees. Boeing pointed out that there was a loss of lift due to the use of spoilers. They also pointed out that rotating at a lower airspeed requires a higher angle of attack, and therefore, a higher pitch attitude to achieve liftoff. The combination of the tailwind gust and spoiler movement resulted in the airplane's pitch attitude exceeding 12.6 degrees, while the gear was still on the ground. This resulted in the aft body contact with the runway.

Boeing discussed a typical takeoff in gusty or strong crosswind conditions. They recommended maximum takeoff thrust, and to avoid rotation during a gust. Slightly delaying rotation would allow the airplane additional time to accelerate through the gust, and the greater airspeed would improve the tail clearance margin.

The FDR-recorded longitudinal control system parameters suggested a properly functioning system. The airplane motion was consistent with the control inputs and power settings.

NTSB Probable Cause

a tail strike due to a combination of the wind shifting from a headwind to a tailwind during rotation, and the pilot's control inputs for the crosswind condition.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.