United Airlines Flight 266

United Airlines Flight 266 was a scheduled flight from Los Angeles International Airport, California, to General Mitchell International Airport, Milwaukee, Wisconsin via Stapleton International Airport, Denver, Colorado with 38 on board. On January 18, 1969 at approximately 18:21 PST it crashed into Santa Monica Bay, Pacific Ocean, about 11.5 miles west of Los Angeles International Airport, four minutes after takeoff.

United Airlines Flight 266

A United Airlines Boeing 727 similar to the accident aircraft
Accident
Date	January 18, 1969
Summary	Mechanical failure leading to loss of electrical power
Site	Santa Monica Bay, California, United States
Aircraft
Aircraft type	Boeing 727-22C
Operator	United Airlines
Registration	N7434U
Occupants	38
Passengers	32
Crew	6
Fatalities	38
Survivors	0

Rescuers (at the time) speculated that an explosion occurred aboard the plane, a Boeing 727. Three and a half hours after the crash three bodies had been found in the ocean along with parts of fuselage and a United States mail bag carrying letters with that day's postmark. Hope was dim for survivors because the aircraft was configured for domestic flights and did not carry liferafts or lifejackets. A Coast Guard spokesman said it looked "very doubtful that there could be anybody alive."[1]

Up until 2013, United used "Flight 266" designation on its San Francisco-Chicago (O'Hare) route.

Flight crew

The crew of Flight 266 was Captain Leonard Leverson, 49, a veteran pilot who had been with United Airlines for 22 years and had almost 13,700 flying hours to his credit. His first officer was Walter Schlemmer, 33, who had approximately 7,500 hours, and the flight engineer was Keith Ostrander, 29, who had 634 hours. Between them the crew had more than 4,300 hours of flight time on the Boeing 727.[2]

Accident

The Boeing 727-22C aircraft, registration N7434U,[3] was almost new and had been delivered to United Airlines only four months earlier. It had less than 1100 hours of operating time. The aircraft had had a nonfunctional #3 generator for the past several days leading up to the accident. Per standard procedure, the crew placed masking tape over the switches and warning lights for the generator. Approximately two minutes after takeoff, the crew reported a fire warning on engine #1 and shut it off. The crew radioed to departure control that they only had one functioning generator and needed to come back to the airport, but it turned out to be their last communication, with subsequent attempts to contact Flight 266 proving unsuccessful. Shortly after engine #1 shut down, the #2 generator also ceased operating for reasons unknown.[2] The NTSB was unable to determine why the #2 generator had failed after it had become the plane's sole power source, nor why the "standby electrical system either was not activated or failed to function."[2]

Several witnesses saw Flight 266 take off and reported seeing sparks emanating from either engine #1 or the rear of the fuselage, while others claimed an engine was on fire. Salvage operations were conducted to recover the wreckage of the aircraft, but not much useful information was gleaned as the cockpit instruments were not recovered. The wreckage was in approximately 930 feet (280 meters) of water and had been severely fragmented, however the relatively small area in which it was spread indicated an extremely steep, nose-down angle at impact. There was little in the way of identifiable human remains at the wreckage site, only two passengers were identified and only one intact body was found. The #2 and #3 engines suffered severe rotational damage from high RPM speeds at impact, but the #1 engine had almost no damage because it had been powered off. No evidence of any fire or heat damage was found on the engines, thus disproving the witnesses' claims. The small portion of the electrical system that was recovered did not provide any relevant information. The CVR took four weeks to locate and recover. NTSB investigators could not explain the sparking seen by witnesses on the ground and theorized that it might have been caused by debris being sucked into the engine, a transient compressor stall or an electrical system problem that led to the eventual power failure. They also were unable to explain the engine #1 fire warning in the absence of a fire, but this may have resulted from electrical system problems or a cracked duct that allowed hot engine air to set off the temperature sensors. The sensors from the #1 and #2 engines were recovered and exhibited no signs of malfunction. Some tests indicated that it was indeed possible for the #2 generator to fail from an overload condition as a result of the operating load being suddenly shifted onto it following the #1 generator's shutdown, and this was maintained as a possible cause of the failure.

N7434U had recently been fitted with a generator control panel that had been passed around several different UAL aircraft because of several malfunctions. After being installed in N7434U the month prior to the ill-fated flight, generator #3 once again caused operating problems was swapped with a different unit. Since that generator was subsequently tested and found to have no mechanical issues, the control panel was identified as the problem after it caused further malfunctions with the replacement generator. Busy operating schedules and limited aircraft availability meant that repair work on N7434U was put on hold, with nothing that could be done in the meantime except to disable the #3 generator. The NTSB investigators believed that the inoperative #3 generator probably was not responsible for the #2 generator's in-flight failure since it was assumed to be isolated from the rest of the electrical system.

With the loss of all power to the lights and flight attitude instruments, flying at night in instrument conditions, the pilots quickly became spatially disorientated and unable to know which inputs to the flight controls were necessary to keep the plane flying normally. Consequently, the crew lost control of the aircraft and crashed into the ocean in a steep nose-down angle, killing everyone on board. The flight control system would not have been affected by the loss of electrical power, since it relied on hydraulic and mechanical lines, so it was concluded that loss of control was the result of the crew's inability to see around the cockpit. It was theorized that the backup electrical system had not been activated because the crew could not locate the switch for it in darkness. The CVR and FDR both lost power just after the crew informed ATC of the fire warning on engine #1. At an unknown later point, both resumed operation for a short period of time. The FDR came back online for 15 seconds, the CVR nine seconds during which time it recorded the crew discussing their inability to see where the plane was. No sounds of the plane impacting the water could be heard when this second portion of the recording ceased.[2]

At the time, a battery-powered backup source for critical flight instruments was not required on commercial aircraft. The accident prompted the Federal Aviation Administration to require all transport-category aircraft to carry backup instrumentation, powered by a source independent of the generators.

Probable cause

The NTSB's "probable cause" stated:

"The Board determines that the probable cause of this accident was loss of altitude orientation during a night, instrument departure in which the altitude instruments were disabled by loss of electrical power. The Board has been unable to determine (a) why all generator power was lost or (b) why the standby electrical power system either was not activated or failed to function."[2]

On January 13, 1969, just five days before the crash of United Flight 266, a Scandinavian Airlines DC-8 on final approach to Los Angeles International also crashed into Santa Monica Bay. The jet broke in half on impact, killing 15. Thirty people survived in a portion of the fuselage that remained afloat.[4][5]

References

1. "Airliner crashes in Pacific with 37", The New York Times, January 19, 1969
2. "NTSB UAL 266 Report" (PDF). NTSB.
3. "FAA Registry (N7434U)". Federal Aviation Administration.
4. Southern California's Worst Air Crashes, LATimes.com
5. NTSB/AAR-70/14 SAS 933 Report

External links

• Accident description at the Aviation Safety Network
• NTSB Aircraft Accident Report (Alternate)