Captain Al Haynes, United Flight Two Thirty-Two, and the Forty-Five Minutes Over Iowa When a DC-Ten Flew Without Hydraulics

On July 19, 1989, United Airlines Flight 232 lost all three of its independent hydraulic systems simultaneously when a fan disk in its tail-mounted engine shattered over Iowa. With no elevator, no rudder, no ailerons, and no flaps, Captain Al Haynes and his crew flew a Douglas DC-10 carrying 296 people using only differential engine thrust - a technique that had never been trained, never been simulated, and had no place in any checklist. 185 people survived. The accident redefined how the aviation industry thinks about cockpit communication and crew coordination.

What Caused United Flight 232 to Lose All Hydraulic Control?

Flight 232 departed Denver, Colorado bound for Chicago, Illinois on a clear summer afternoon. The crew - Captain Al Haynes, First Officer William Records, and Second Officer Dudley Dvorak - was cruising at 37,000 feet when, at 12:59 PM, the number two engine failed.

The DC-10’s number two engine sits in the tail, at the base of the vertical stabilizer. When its titanium fan disk fractured, it didn’t simply stop turning. It disintegrated into high-velocity fragments that ripped through the tail section, severing every hydraulic line routed through that area.

The critical detail: the DC-10 had three completely separate hydraulic systems, each fully independent by design. Engineers had modeled failure scenarios extensively. Losing all three simultaneously was considered so statistically improbable that aircraft certification standards treated it as a practical impossibility.

The fatigue crack in that fan disk had been developing for years, invisible to every inspection. When it finally failed, it proved that “practically impossible” is not the same as impossible.

How Did the Crew Fly a DC-10 With No Flight Controls?

Records reached for his controls and found nothing - the yoke moved freely, connected to nothing. Haynes tried his own. The same. They ran every checklist. The result was unchanged.

No elevator. No rudder. No ailerons. No flaps. No spoilers.

What they discovered almost immediately was that differential thrust could influence the aircraft’s heading. More power on the right engine, less on the left, and the DC-10 would enter a slow, wallowing turn to the right. They could not hold altitude. The aircraft kept wanting to spiral downward, and the crew kept fighting it back with throttle inputs, reading the instruments moment to moment.

Haynes contacted Sioux City Approach Control, where controller Kevin Bachman - who had never worked anything remotely like this scenario - kept his transmissions steady and began vectoring the flight toward Sioux Gateway Airport, which had a runway long enough to handle a DC-10.

Who Was Captain Al Haynes?

Al Haynes had 33 years with United Airlines and had come up through the industry the way pilots of his generation did - starting on propeller aircraft, transitioning to jets as the industry modernized, accumulating tens of thousands of hours across aircraft types. He knew the DC-10 well.

What stands out about those 45 minutes over Iowa is not only the flying itself, but how Haynes managed the human side of an unprecedented emergency. He kept his voice level on the radio. He kept his crew informed. He contacted United Airlines maintenance in San Francisco, where engineers pulled up schematics in real time. Those conversations confirmed what the crew already suspected: there was no solution in the manual. The checklist had simply run out of pages.

Who Was Dennis Fitch, and Why Did It Matter That He Was on Board?

A United Airlines DC-10 instructor and check airman named Dennis Fitch was traveling as a passenger that day, deadheading in coach after completing a check ride. When the aircraft shuddered and the crew’s responses became perceptible even to those who couldn’t see the instruments, Fitch sent a note forward.

Haynes let him come to the cockpit.

Fitch knelt between the two pilot seats and took over the throttle levers directly. His years teaching DC-10 handling characteristics meant he understood intuitively how the aircraft wanted to move. With Fitch managing the throttles, Haynes and Records were freed to focus on instruments and decision-making.

Four people were now flying an airplane that technically couldn’t be flown: Haynes in the left seat, Records in the right, Dvorak at the engineer panel, and Fitch on his knees between them, running the power levers with both hands for the final approach into Sioux City.

What Happened When Flight 232 Touched Down at Sioux City?

The word had moved through the system quickly. By the time Flight 232 descended toward Runway 31 at Sioux Gateway, hundreds of emergency responders - National Guard medical units, city fire equipment, ambulances - were staged and waiting.

The crew knew this was not going to be a landing in any conventional sense. Their goal was not to stop the aircraft on the runway. Their goal was to get it onto the ground in a configuration that gave the people in the back the best possible chance of surviving the impact.

Touchdown speed was approximately 240 knots - roughly double a normal DC-10 approach speed. They had no flaps. They could not hold a stable glidepath. The aircraft was still rolling slowly to the right as it crossed the threshold.

The right wing touched first. The gear collapsed. Sections of the fuselage broke apart and tumbled across the runway and into a cornfield alongside the airport.

112 people died. 185 walked out of that cornfield.

How United Flight 232 Changed Aviation Training Forever

The National Transportation Safety Board’s analysis of the cockpit voice recorder, the flight data recorder, and every second of those 45 minutes produced a finding that remains significant today: there was no prior training for this emergency. No simulator scenario had covered complete hydraulic failure on a DC-10. The crew had constructed a technique from first principles, under pressure, in the air - and had executed it well enough that the majority of people on board survived what every model said was unsurvivable.

The NTSB called it “a testament to extraordinary crew coordination.”

That report, and the accident that prompted it, became the foundational case study for what the industry now formalizes as crew resource management (CRM). The principles drawn directly from Flight 232 are now embedded in training worldwide: the captain uses every available resource regardless of where it comes from; rank does not insulate you from being wrong; the first officer’s observations matter; the person in the back of the airplane with relevant knowledge gets called forward; the controller gets told what you actually know. Open, honest communication as the mechanism that keeps people alive when the procedures have been exhausted.

Al Haynes gave talks about Flight 232 for the rest of his life. He was consistent in what he said: he didn’t save anyone. Haynes, Records, Dvorak, and Fitch together - and Bachman at Sioux City Approach, and the emergency responders who were ready and waiting - those people saved 185 lives. He was not being modest. He believed it, and the record supports him.

Haynes passed away in August 2019, 30 years after the accident at Sioux City.

The techniques that crew discovered that afternoon - using differential thrust to maintain directional control on an aircraft with no conventional authority - now live in simulator programs. Crews have practiced them. The knowledge created in a DC-10 cockpit on July 19, 1989 exists in a form that could help someone someday.

But beyond the technique is the posture. The willingness to say out loud: I don’t know - what do you see? The willingness to call the person with relevant knowledge forward. The willingness to tell approach control exactly how bad it is and ask for everything they have.

That posture is available to every pilot who flies.

Key Takeaways

On July 19, 1989, United Flight 232 lost all three independent hydraulic systems after a titanium fan disk fatigue fracture in the tail engine destroyed every hydraulic line in the aircraft’s tail section.
With no conventional flight controls, Captain Al Haynes and his crew - joined by off-duty instructor Dennis Fitch - flew the aircraft to Sioux City using differential engine thrust alone, a technique with no prior training or simulator precedent.
185 of 296 people aboard survived an impact the NTSB characterized as theoretically unsurvivable under those conditions.
The NTSB credited extraordinary crew coordination - the crew’s use of every available resource, their open communication with ATC, and their willingness to seek outside expertise - as central to the survival rate.
The accident became the foundational case study for crew resource management (CRM) training and permanently changed how the aviation industry teaches cockpit communication and decision-making under pressure.