United Airlines Flight 232

United Airlines Flight 232

Photo of United Airlines Flight 232 from the NTSB report, with damage highlighted.
Accident summary
Date July 19, 1989 (1989-07-19)
Summary Uncontained engine failure due to faulty titanium alloy forging of fan disk leading to loss of flight controls due to ruptured hydraulic systems
Site Sioux Gateway Airport
Sioux City, Iowa, United States
Passengers 279[1]
Crew 17 [1]
Fatalities 111
Injuries (non-fatal) 172[1]
Survivors 185[1]
Aircraft type McDonnell Douglas DC-10-10
Operator United Airlines
Registration N1819U
Flight origin Stapleton International Airport, Denver, Colorado
Stopover O'Hare International Airport, Chicago, Illinois
Destination Philadelphia International Airport, Philadelphia, Pennsylvania

United Airlines Flight 232 was a DC-10, registered as N1819U, that crash-landed at Sioux City, Iowa in July 19, 1989 after suffering catastrophic failure of its tail-mounted engine, which led to the loss of all flight controls. The flight was en route from Stapleton International Airport in Denver, Colorado to O'Hare International Airport in Chicago. Of the 296 passengers and crew on board, 111 died in the accident and 185 survived in total.[note 1] Despite the deaths, the accident is considered a prime example of successful crew resource management due to the large number of survivors and the manner in which the flight crew handled the emergency and landed the airplane without conventional control.

Aircraft and crew

The accident airplane, a McDonnell Douglas DC-10-10 (registration N1819U), was delivered in 1973 and had been owned by UAL since then. Before departure on the flight from Denver on July 19, 1989, the airplane had been operated for a total of 43,401 hours and 16,997 cycles. The airplane was powered by General Electric Aircraft Engines (GEAE) CF6-6D high bypass ratio turbofan engines.[2]

Captain Alfred C. Haynes, 57, was hired by United Airlines in 1956. He had 30,000 hours of total flight time with United Airlines, of which 7,000 were in the DC-10.

First Officer William R. Records, 48, was hired by National Airlines in 1969. He subsequently worked for Pan American World Airways. He estimated that he had approximately 20,000 hours of total flight time. He had 665 hours as a DC-10 first officer.

Second Officer Dudley J. Dvorak, 51, was hired by United Airlines in 1986. He estimated that he had approximately 15,000 hours of total flying time. He had 1,900 hours as a second officer in the B-727 and 33 hours as a second officer in the DC-10.

Training Check Airman Captain Dennis E. Fitch, 46, was hired by United Airlines in 1968. He estimated that, prior to working for United, he had accrued at least 1,400 hours of flight time with the Air National Guard. His total DC-10 time with United was 3,000 hours, of which 2,000 hours were accrued as a second officer, 1000 hours as a first officer, and 79 hours as a captain.[2]

Events

Radar plot of the plane's flight path, from the NTSB report
Damage to the rear of the plane, from the NTSB report

Take off and failure

Flight 232 took off at 14:09 CDT from Stapleton International Airport, Denver, Colorado, bound for O'Hare International Airport in Chicago with continuing service to Philadelphia International Airport.[2]

At 15:16, while the plane was in a shallow right turn at 37,000 feet, the fan disk of its tail-mounted General Electric CF6-6 engine disintegrated. Debris penetrated the tail in numerous places, including the horizontal stabilizer, puncturing the lines of all three hydraulic systems.[3]

The pilots felt a jolt, and the autopilot disengaged. As Records took hold of his control column, Haynes focused on the tail engine, which instruments indicated was malfunctioning; he found its throttle and fuel supply controls jammed. At Dvorak's suggestion, a valve cutting fuel to the tail engine was shut off. This part of the emergency took 14 seconds.[3]

Attempts to control plane

Meanwhile, Records found that the plane did not respond to his control column.[1] Even with the control column turned all the way to the left, commanding maximum left aileron, and pulled all the way back, commanding maximum up elevator  inputs that would never be used together in normal flight, commanding a roll to the left and the aircraft's nose to rise  the aircraft was instead banking to the right with the nose dropping. Haynes attempted to level the aircraft with his own control column, then both Haynes and Records tried using their control columns together, but the aircraft still did not respond. Afraid the aircraft would roll into a completely inverted position (an unrecoverable situation), the crew reduced the left wingmounted engine to idle and applied maximum power to the right engine. This caused the airplane to slowly level out.[3]

The various gauges for all three hydraulic systems were registering zero.[3] The three hydraulic systems were separate, so that failure of any one of them would leave the crew with full control, but lines for all three systems shared the same narrow passage through the tail where the engine debris had penetrated, and thus control surfaces were inoperative.[1] The crew contacted United maintenance personnel via radio, but were told that, as a total loss of hydraulics on the DC-10 was considered "virtually impossible", there were no established procedures for such an event.[1]

The plane was tending to pull right, and slowly oscillated vertically in a phugoid cycle  characteristic of planes in which control surface command is lost. With each iteration of the cycle, the aircraft lost approximately 1,500 feet (460 m) of altitude. Dennis E. Fitch, an off-duty United Airlines DC-10 flight instructor, was among the passengers and offered his assistance.[3]

Haynes asked Fitch to observe the ailerons through the passenger cabin windows to see if control inputs were having any effect.[3] Fitch reported back that the ailerons were not moving at all. Nonetheless, the crew continued to manipulate their control columns for the remainder of the flight, hoping for at least some effect. Haynes then asked Fitch to take over control of the throttles so that Haynes could concentrate on his control column. With one throttle in each hand, Fitch was able to mitigate the phugoid cycle and make rough steering adjustments.

Air traffic control (ATC) was contacted and an emergency landing at nearby Sioux Gateway Airport was organized. Haynes kept his sense of humor during the emergency, as recorded on the plane's cockpit voice recorder (CVR):

Fitch: "I'll tell you what, we'll have a beer when this is all done."[4]
Haynes: "Well I don't drink, but I'll sure as shit have one."[5][6]

and later:

Sioux City Approach: "United Two Thirty-Two Heavy, the wind's currently three six zero at one one; three sixty at eleven. You're cleared to land on any runway."[4]
Haynes: "[laughter] Roger. [laughter] You want to be particular and make it a runway, huh?"[4]

A more serious remark often quoted from Haynes was made when ATC asked the crew to make a left turn to keep them clear of the city:

Haynes: "Whatever you do, keep us away from the city."[7]

Haynes later noted that "We were too busy [to be scared]. You must maintain your composure in the airplane, or you will die. You learn that from your first day flying."[8]

Crash landing

As the crew began to prepare for arrival at Sioux City, they questioned whether they should deploy the landing gear or belly-land the aircraft with the gear retracted. They decided that having the landing gear down would provide some shock absorption on impact.[9] The complete hydraulic failure left the landing gear lowering mechanism inoperative. Two options were available to the flight crew. The DC-10 is designed such that if hydraulic pressure to the landing gear is lost, the gear will fall down slightly and rest on the landing gear doors. Placing the regular landing gear handle in the down position will unlock the doors mechanically, and the doors and landing gear will then fall down into place and lock due to gravity.[9] An alternative system is also available using a lever in the cockpit floor to cause the landing gear to fall into position.[10] This lever has the added benefit of unlocking the outboard ailerons, which are not used in high-speed flight and are locked in a neutral position.[9] The crew hoped that there might be some trapped hydraulic fluid in the outboard ailerons and that they might regain some use of flight controls by unlocking them. They elected to extend the gear with the alternative system.[9] Although the gear deployed successfully, there was no change in the controllability of the aircraft.[1]

Landing was originally planned on the 9,000-foot (2,700 m) Runway 31. Difficulties in controlling the aircraft made lining up almost impossible. While dumping some of the excess fuel, the plane executed a series of mostly right-hand turns (it was easier to turn the plane in this direction) with the intention of lining up with Runway 31. When they came out they were instead lined up with the shorter (6,888 ft) and closed Runway 22, and had little capacity to maneuver.[1] Fire trucks had been placed on Runway 22,[3] anticipating a landing on nearby Runway 31, so all the vehicles were quickly moved out of the way before the plane touched down. Runway 22 had been permanently closed a year earlier in 1988.[1]

ATC also advised that I-29 ran North and South just East of the airport they could land on if they didn't think they could make the runway. The pilot opted to try for the runway instead.[11][12]

The plane landed askew, causing the explosion and fire seen in this still from local news station video.

Fitch continued to control the aircraft's descent by adjusting engine thrust. With the loss of all hydraulics, the crew were unable to control airspeed independent from sink rate. On final descent, the aircraft was going 220 knots and sinking at 1,850 feet per minute (approximately 407 km/h forward and 34 km/h downward speed), while a safe landing would require 140 knots and 300 feet per minute (approximately 260 km/h and 5 km/h respectively). Fitch needed a seat for landing; Dvorak offered up his own, as it could be moved to a position behind the throttles.[1] Dvorak sat in the cockpit's jump seat for landing. Fitch noticed the high sink rate and that the plane started to yaw right again, and fire-walled the throttles attempting to mitigate the high sink rate and level the plane. There wasn't enough time for the flight crew to react. The tip of the right wing hit the runway first, spilling fuel, which ignited immediately. The tail section broke off from the force of the impact, and the rest of the aircraft bounced several times, shedding the landing gear and engine nacelles and breaking the fuselage into several main pieces. On the final impact, the right wing was shorn off and the main part of the aircraft skidded sideways, rolled over onto its back, and slid to a stop upside-down in a corn field to the right of Runway 22. Witnesses reported that the aircraft "cartwheeled" end-over-end, but the investigation did not confirm this.[1] The reports were due to misinterpretation of the video of the crash that showed the flaming right wing tumbling end-over-end and the intact left wing, still attached to the fuselage, rolling up and over as the fuselage flipped over.

Injuries

Locations of passengers indicated by lack of injury, severity of injury, and reason of death from the NTSB report

Of the 296 people on board, 111 died in the crash. Most were killed by injuries sustained in the multiple impacts, but 35 people in the middle fuselage section directly above the fuel tanks died from smoke inhalation in the post-crash fire. Of those, 24 had no traumatic blunt-force injuries. The majority of the 185 survivors were seated behind first class and ahead of the wings.[7] Many passengers were able to walk out through the ruptures to the structure.

Of all of the passengers:[1]

The passengers who died for reasons other than smoke inhalation were seated in rows 1–4, 24–25 and 28–38. Passengers who died due to smoke inhalation were seated in rows 14, 16 and 22–30. The person assigned to 20H moved to an unknown seat and died of smoke inhalation.

One crash survivor died 31 days after the accident; he was classified according to NTSB regulations as a survivor with serious injuries.[1]

Fifty-two children, including four "lap children" without their own seats, were on board the flight due to the United Airlines "Children's Day" promotion. Eleven children, including one lap child, died.[13] Many of the children had traveled alone.[14]

It was not until 35 minutes after the crash that rescuers identified the debris that was the remains of the cockpit, with the four pilots alive inside. All four recovered from their injuries and eventually returned.[3]

Investigation

The rear engine's fan disk and blade assembly  approximately 8 feet (2.4 m) across  could not be located at the accident scene[1] despite an extensive search. The engine's manufacturer, General Electric, offered rewards of $50,000 for the disk and $1,000 for each fan blade.[15] Three months after the crash a farmer discovered most of the fan disk, with several blades still attached, in her cornfield.[15] The rest of the fan disk and most of the additional blades were later found nearby.

The Board determined that the probable cause of this accident was the inadequate consideration given to human factors limitations in the inspection and quality control procedures used by United Airlines' engine overhaul facility. These resulted in the failure to detect a fatigue crack originating from a previously undetected metallurgical defect located in a critical area of the titanium-alloy stage 1 fan disk that was manufactured by General Electric Aircraft Engines. The uncontained manner in which the engine failed resulted in high-speed metal fragments being hurled from the engine; these fragments penetrated the hydraulic lines of all three independent hydraulic systems on board the aircraft, which rapidly lost their hydraulic fluid. The subsequent catastrophic disintegration of the disk resulted in the liberation of debris in a pattern of distribution and with energy levels that exceeded the level of protection provided by design features of the hydraulic systems that operate the DC-10's flight controls; the flight crew lost its ability to operate nearly all of them. Despite these losses, the crew was able to attain and then maintain limited control by using the throttles to adjust thrust to the remaining wing-mounted engines. By using each engine independently, the crew made rough steering adjustments, and by using the engines together they were able to roughly adjust altitude. The crew guided the crippled jet to Sioux Gateway Airport and lined it up for landing on one of the runways. Without the use of flaps and slats, they were unable to slow down for landing, and were forced to attempt landing at a very high ground speed. The aircraft also landed at an extremely high rate of descent due to the inability to flare (reduce the rate of descent before touchdown by increasing pitch). As a result, upon touchdown the aircraft broke apart, rolled over and caught fire. The largest section came to rest in a cornfield next to the runway. Despite the ferocity of the accident, 185 (62.5%) passengers and crew survived owing to a variety of factors including the relatively controlled manner of the crash and the early notification of emergency services.[2]

Failed component

The fracture is clearly visible in the recovered fan disk from the center engine of UAL 232.

The investigation, while praising the actions of the flight crew for saving lives, would later identify the cause of the accident as a failure by United Airlines maintenance processes and personnel to detect an existing fatigue crack.[1] The Probable Cause in the report by the NTSB read as follows:

The National Transportation Safety Board determines that the probable cause of this accident was the inadequate consideration given to human factors limitations in the inspection and quality control procedures used by United Airlines' engine overhaul facility which resulted in the failure to detect a fatigue crack originating from a previously undetected metallurgical defect located in a critical area of the stage 1 fan disk that was manufactured by General Electric Aircraft Engines. The subsequent catastrophic disintegration of the disk resulted in the liberation of debris in a pattern of distribution and with energy levels that exceeded the level of protection provided by design features of the hydraulic systems that operate the DC-10's flight controls.[1]

Post-crash analysis of the crack surfaces showed the presence of a penetrating fluorescent dye used to detect cracks during maintenance. The presence of the dye indicated that the crack was present and should have been detected at a prior inspection. The detection failure arose from poor attention to human factors in United Airlines' specification of maintenance processes.[1]

Investigators discovered an impurity and fatigue crack in the disk. Titanium reacts with air when melted, which creates impurities which can initiate fatigue cracks like that found in the crash disk. To prevent this, the ingot that would become the fan disk was formed using a "double vacuum" process: the raw materials were melted together in a vacuum, allowed to cool and solidify, then melted in a vacuum once more. After the double vacuum process, the ingot was shaped into a billet, a sausage-like form about 16 inches in diameter, and tested using ultrasound to look for defects. Defects were located and the ingot was further processed to remove them, but some contamination remained. (GE later changed to an improved triple-vacuum process because of their investigation into failing rotating titanium engine parts.)[1]

The contamination caused what is known as a hard alpha inclusion, a brittle part of the metal, which cracked during forging and then fell out during final machining. This formed a cavity with microscopic cracks at the edges. For the next 18 years, the crack grew slightly each time the engine was powered up and brought to operating temperature. Eventually the crack grew large enough to cause structural failure of the disk.[1]

The origins of the crash disk are uncertain because of significant irregularities and gaps, noted in the NTSB report, in the manufacturing records of GE Aircraft Engines (GEAE) and its suppliers.[1] Records found after the accident indicated that two rough-machined forgings having the serial number of the crash disk had been routed through GEAE manufacturing. Records indicated that Alcoa supplied GE with TIMET titanium forgings for one disk with the serial number of the crash disk. Some records show that this disk “was rejected for an unsatisfactory ultrasonic indication”, that an outside lab performed an ultrasound inspection of this disk, that this disk was subsequently returned to GE, and that this disk should have been scrapped. The FAA report stated “There is no record of warranty claim by GEAE for defective material and no record of any credit for GEAE processed by Alcoa or TIMET”.[1]

GE records of the second disk having the serial number of the crash disk indicate that it was made with an RMI titanium billet supplied by Alcoa. Research of GE records showed no other titanium parts were manufactured at GE from this RMI titanium billet during the period of 1969 to 1990. GE records indicate that final finishing and inspection of the crash disk were completed on December 11, 1971. Alcoa records indicate that this RMI titanium billet was first cut in 1972 and that all forgings made from this material were for airframe parts.[1] If the Alcoa records were accurate, the RMI titanium could not have been used to manufacture the crash disk, indicating that the initially rejected TIMET disk with “an unsatisfactory ultrasonic indication” was the crash disk.

CF6 engines like that containing the crash disk were used to power many civilian and military aircraft at the time of the crash. Due to concerns that the accident could recur, a large number of disks that were in service were examined by ultrasound for indications of defects. At least two “sister disks” were found to have defects like that of the crash disk. Prioritization and efficiency of inspections of the many engines under suspicion would have been aided by determination of the titanium source of the crash disk. Chemical analyses of the crash disk intended to determine its source were inconclusive. The NTSB report stated that if examined disks were not from the same source, “the records on a large number of GEAE disks are suspect. It also means that any AD (Airworthiness Directive) action that is based on the serial number of a disk could fail to have its intended effect because suspect disks could remain in service.” [1] The FAA report did not explicitly address the impact of these uncertainties on operations of military aircraft that might have contained a suspect disk.

Influence on the industry

Damage to N1819U's three hydraulic systems

The National Transportation Safety Board (NTSB) investigation, after subsequent reconstructions of the accident in flight simulators, deemed that training for such an event involved too many factors to be practical. While some level of control was possible, no precision could be achieved, and a landing under these conditions was stated to be "a highly random event".[1] The NTSB further noted that "under the circumstances the UAL[note 2] flight crew performance was highly commendable and greatly exceeded reasonable expectations."[1]

The manufacturing process for titanium was changed in order to eliminate the type of gaseous anomaly that served as the starting point for the crack. Newer batches of titanium use much higher melting temperatures and a "triple vacuum" process in an attempt to eliminate such impurities.[16]

Because this type of aircraft control (with loss of control surfaces) is difficult for humans to achieve, some researchers have attempted to integrate this control ability into the computers of fly-by-wire aircraft. Early attempts to add the ability to real airplanes were not very successful; the software was based on experiments conducted in flight simulators where jet engines are usually modeled as "perfect" devices with exactly the same thrust on each engine, a linear relationship between throttle setting and thrust, and instantaneous response to input. Later, computer models were updated to account for these factors, and planes have been successfully flown with this software installed.[17]

Newer aircraft designs such as the McDonnell Douglas MD-11 have incorporated hydraulic fuses to isolate a punctured section and prevent a total loss of hydraulic fluid. Following the UAL 232 accident, such fuses were installed in the number 3 hydraulic system in the area below the number 2 engine on all DC-10 aircraft to ensure sufficient control capability remained if all three hydraulic system lines should be damaged in the tail area.[7] Although elevator and rudder control would be lost, the aircrew would still be able to control the aircraft's pitch (up and down) with stabilizer trim, and would be able to control roll (left and right) with some of the aircraft's ailerons and spoilers. Although not an ideal situation, the system provides a greater measure of control than was available to the crew of United 232.

It is still possible to lose all three hydraulic systems if serious damage occurs elsewhere, as nearly happened to a cargo airliner in 2002 during takeoff when a main gear tire exploded in the wheel well area. The damage in the left wing area caused total fluid loss from the number 1 and the number 2 hydraulic systems. The number 3 system was dented but not penetrated. DC-10s still have no fuse protection for any of the three hydraulic systems in the event of an exploding main gear tire.[18]

Of the four children deemed too young to require seats of their own ("lap children"), one died from smoke inhalation.[1] The NTSB added a safety recommendation to the FAA on its "List of Most Wanted Safety Improvements" in May 1999 suggesting a requirement for children under 2 to be safely restrained, which was removed in November 2006.[19][20] The accident sparked a campaign led by United Flight 232's senior flight attendant, Jan Brown Lohr, for all children to have seats on aircraft.[21] Though it is no longer on the "most wanted" list, aircraft restraints for children under 2 is still recommended practice by the NTSB and FAA, though it is not required by the FAA as of May 2016.[22][23] The NTSB asked the International Civil Aviation Organization to make this a requirement in September 2013.[24]

The accident has since become a prime example of successful crew resource management.[25] For much of aviation's history, the captain was considered the final authority, and crews were to respect the captain's expertise and not question him. This began to change in the 1970s, especially after the Tenerife airport disaster. Crew Resource Management, while still considering the captain the final authority, instructs crewmembers to speak up when they detect a problem, and instructs captains to listen to their concerns. United Airlines instituted a Crew Resource Management class in the early 1980s. The NTSB would later credit this training as valuable toward the success of United 232's crew in handling their emergency.[1] The FAA made Crew Resource Training mandatory in the aftermath of the accident.

Factors contributing to survival rate

Of the 296 people aboard, 111 were killed in the crash, while 185 survived.[note 1] Haynes later told of three contributing factors regarding the time of day that allowed for a greater number of passengers surviving:

  1. The accident occurred during daylight hours in good weather;
  2. The accident occurred as a shift change was occurring at both a regional trauma center and a regional burn center in Sioux City, allowing for more medical personnel to treat the injured;
  3. The accident occurred when the Iowa Air National Guard was on duty at Sioux Gateway Airport, allowing for 285 trained personnel to assist with triage and evacuation of the injured.

"Had any of those things not been there," Haynes said, "I'm sure the fatality rate would have been a lot higher."[26]

Haynes also credited Crew Resource Management as being one of the factors that saved his own life, and many others.

…the preparation that paid off for the crew was something … called Cockpit Resource Management… Up until 1980, we kind of worked on the concept that the captain was THE authority on the aircraft. What he said, goes. And we lost a few airplanes because of that. Sometimes the captain isn't as smart as we thought he was. And we would listen to him, and do what he said, and we wouldn't know what he's talking about. And we had 103 years of flying experience there in the cockpit, trying to get that airplane on the ground, not one minute of which we had actually practised, any one of us. So why would I know more about getting that airplane on the ground under those conditions than the other three. So if I hadn't used CRM, if we had not let everybody put their input in, it's a cinch we wouldn't have made it.[27]

As with the Eastern Air Lines Flight 401 crash of a similarly-sized Lockheed L-1011 in 1972, the relatively shallow angle[note 3] of descent likely played a large part in the relatively high survival rate. The National Transportation Safety Board concluded that under the circumstances, "a safe landing was virtually impossible."[1]

Notable survivors

Depictions

Survivor accounts

Similar accidents

The odds against all three hydraulic systems failing simultaneously had previously been calculated as high as a billion to one.[37] Yet such calculations assume that multiple failures must have independent causes, an unrealistic assumption, and similar flight control failures have indeed occurred:

The disintegration of a turbine disc, leading to loss of control, was a direct cause of two major aircraft disasters in Poland:

See also

Notes

  1. 1 2 One passenger died 31 days after the accident; in accordance with NTSB regulations, he is classified as a survivor with "serious" injuries.
  2. UAL is the three-letter designator code for United Airlines.
  3. Angle of descent and Rate of descent are two different things. The aircraft approached at a high rate of descent but a shallow angle.

References

  1. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 "NTSB/AAR-90/06" (PDF). NTSB. Archived from the original (PDF) on January 4, 2011. Retrieved 2011-03-15.
  2. 1 2 3 4 "NTSB-AAR90-06" (PDF). Air Disaster.com. Archived from the original (PDF) on January 4, 2011.
  3. 1 2 3 4 5 6 7 8 Haynes, Al. "Special report". Airdisaster.com. Retrieved 2006-09-15.
  4. 1 2 3 "Aviation Safety Network CVR/FDR: United Airlines DC-10-10 – 19 JUL 1989" (PDF). Aviation Safety Network. Retrieved 25 March 2011.
  5. Playback of original CVR recording on “A Wing and a Prayer” episode of TV series Black Box, 1996.
  6. last cockpit voice recording of United Flight 232 at 0:18 Retrieved January 10, 2013.
  7. 1 2 3 Macarthur Job (1996). Air Disaster Volume 2, Aerospace Publications, ISBN 1-875671-19-6: pp.186–202
  8. Gates, Dominic (2009-07-19). "20 years ago, pilot's heroic efforts saved 185 people as plane crashed". Seattle Times. Retrieved 2009-07-19.
  9. 1 2 3 4 Haynes, Al. "The Crash of United Flight 232". Retrieved 16 March 2011.
  10. "DC-10 Flight Crew Operating Manual". Retrieved 16 March 2011.
  11. Haynes, Capt. Al. "The Crash of United Flight 232" 15:59
  12. Sioux City Journal "Flight 232 Radio Transcript" 3:57 p.m.
  13. United Airlines Flight 232 episode, Seconds From Disaster
  14. "The Crash of United Flight 232 by Capt. Al Haynes". Clear-prop.org. Retrieved 2011-03-15.
  15. 1 2 "Key Piece of Doomed DC-10 Found in Field". Los Angeles Times. 1989-10-12. Retrieved 2011-03-15.
  16. Thomas, Malcolm. "Titanium in Aero Engines, Trends & Developments" (PDF). Rolls Royce. Retrieved April 10, 2011.
  17. "Active Home Page". Past Research Projects. NASA. Retrieved 2006-06-01.
  18. "NTSB/Safety Recommendation to FAA". NTSB, August 21, 2003.
  19. "Aviation Issues". 2006-08-13. Archived from the original on August 13, 2006. Retrieved 2011-03-15.
  20. "Modifications to NTSB Most Wanted List: List of Transportation Safety Improvements after September 1990" (PDF). NTSB. Archived from the original (PDF) on 2008-12-30.
  21. Newman, TB (2003). "The power of stories over statistics". BMJ. British Medical Journal. 327: 1424–7. PMC 300791Freely accessible. PMID 14684635. doi:10.1136/bmj.327.7429.1424.
  22. http://www.ntsb.gov/safety/Pages/Children.aspx
  23. http://www.ntsb.gov/safety/safety-alerts/Documents/SA_015.pdf
  24. https://app.ntsb.gov/safety/mwl2014/10_MWL_OccupantProtection.pdf
  25. How Swift Starting Action Teams Get off the Ground: What United Flight 232 and Airline Flight Crews Can Tell Us About Team Communication Management Communication Quarterly, Vol. 19, No. 2, November 2005
  26. Nicholas Faith (1996, 1998). Black Box, Boxtree, ISBN 0-7522-2118-3: pp.158–165
  27. Capt. Al Haynes (May 24, 1991). "The Crash of United Flight 232". Archived from the original on October 26, 2013. Retrieved 2013-06-04. Presentation to NASA Dryden Flight Research Facility staff.
  28. Noguchi Museum The; Magazine, Surface; Surface Magazine; The New York Times; Businessweek, Bloomberg; Journalism, Columbia University-Graduate School of. "Spencer Bailey | LinkedIn". Retrieved 2016-05-27.
  29. Schemmel, Jerry; Simpson, Kevin (1996). Chosen to Live: The Inspiring Story of a Flight 232 Survivor. Victory Publishing. ISBN 0-9652086-5-6.
  30. Wallechinsky, David and Loucky, Jaime (2008). "Equestrian: Jumping (Prix des Nations), Team". In The Complete Book of the Olympics: 2008 Edition. London: Aurum Pres Limited. pp. 582, 584–5.
  31. Lyrics to Pete Wernick's "A Day in '89 (You Never Know)" from drbanjo.com (Wernick's official site).
  32. "Crash Landing: The Rescue of Flight 232". IMDB. Retrieved 2006-09-15.
  33. Ihejirika, Maudlyne (April 16, 2016). "Surviving crew of doomed United Flight 232 reunites for play". Chicago Sun-Times. Retrieved February 15, 2016.
  34. Jones, Chris (October 17, 2016). "'Dreamgirls' and 'Tempest' win at 2016 Equity Jeff Awards". Chicago Tribune. Retrieved February 15, 2016.
  35. "Errol Morris’ First Person Episode 10". Archived from the original on April 8, 2011. Retrieved 2011-03-15.
  36. Morning Edition (2008-01-11). "After Disaster, a Survivor Sheds Her Regrets". NPR. Retrieved 2011-03-15.
  37. "Eyewitness Report:United 232". AirDisaster.Com. Archived from the original on June 18, 2008. Retrieved 2008-06-04.
  38. "Aircraft Accident Report Pan American World Airways Inc Boeing 747, N747PA Flight 845" (PDF). NTSB. Retrieved 11 April 2011.
  39. "Aircraft Accident Report Eastern Airlines Flight 935" (PDF). NTSB. Retrieved 11 April 2011.
  40. "Japan Airlines Flight 123, Boeing 747-SR100, JA8119". FAA. Retrieved 11 April 2011.
  41. "Aviation Safety Network Accident Description". Aviation Safety Network. Retrieved 11 April 2011.
  42. "Aviation Safety Network Criminal Occurrence Description". Aviation Safety Network. Retrieved 11 April 2011.
  43. "Aviation Safety Network Accident Description". Aviation Safety Network. Retrieved 11 April 2011.
  44. "Aviation Safety Network Accident Description". Aviation Safety Network. Retrieved 11 April 2011.

Coordinates: 42°24′29″N 96°23′02″W / 42.40806°N 96.38389°W / 42.40806; -96.38389

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.