United Two Thirty-Two, Al Haynes, and the Sioux City Landing Flown With Nothing but Two Throttles

On July 19, 1989, United Airlines Flight 232, a McDonnell Douglas DC-10 carrying 296 people, suffered a catastrophic failure that severed all three of its independent hydraulic systems, leaving the crew with no working flight controls. Using only the throttles of the two wing-mounted engines to steer, Captain Al Haynes and his crew guided the crippled jet to a crash landing at Sioux City, Iowa - and 185 of the 296 aboard survived an accident that every simulation said should have killed everyone. The reason it’s still taught today isn’t luck. It’s a masterclass in flying the airplane you have, working the problem calmly, and using every resource available.

What Happened to United Flight 232?

Flight 232 departed Denver bound for Chicago, with a continuing leg to Philadelphia. In the cockpit were Captain Al Haynes, with more than 30 years and nearly 30,000 flight hours; First Officer Bill Records; and Flight Engineer Dudley Dvorak.

About an hour into the flight, at 37,000 feet, the number two engine - the one buried in the tail at the base of the vertical fin - came apart. Its titanium fan disk had a fatigue crack that had been growing invisibly for years, born from a tiny flaw in the metal the day it was cast.

When that disk let go, it didn’t simply stop. Hundreds of pounds of metal spinning at thousands of RPM turned into shrapnel and sprayed outward through the tail. Engineers call this an uncontained failure: the engine case cannot hold the debris in.

Why Did the DC-10 Lose All Flight Controls?

On a jet the size of a DC-10, there are no cables or pushrods a human arm can move. The pilot moves the yoke, and hydraulic pressure moves the ailerons, elevator, rudder, flaps, and slats.

The DC-10 had three completely independent hydraulic systems, specifically so that losing one still left two, and losing two still left one. The odds of losing all three at once were considered so remote they rounded down to never.

But all three systems ran lines through the tail, past the number two engine. When the disk exploded, the shrapnel cut every one of them. Within seconds, pressure on all three systems bled to zero. The crew had a fully functioning airframe, two good engines still running on the wings - and no way whatsoever to control where the airplane pointed.

How Do You Fly an Airplane With No Flight Controls?

The crew’s first act wasn’t clever - it was the oldest rule in aviation: aviate, navigate, communicate, in that order. You do not troubleshoot while the airplane flies itself into the ground. You fly first. This crew, with almost nothing to fly with, still put flying first.

They worked out in real time - with no procedure, because none existed - that they had exactly two things left that could change the airplane’s path: throttle number one on the left wing and throttle number three on the right.

• Push the left throttle up, and the airplane yaws and rolls right.
• Push the right throttle up, and it goes left.
• Push both up together, and the nose eventually rises.
• Pull both back, and it sinks.

They were steering a 200-ton airplane like paddling a canoe with one oar - pushing harder on one side than the other. It was neither precise nor fast.

Adding power on an under-wing-mounted engine makes the nose climb, overshoot, sink, and climb again - a slow porpoising oscillation pilots call a phugoid, taking nearly a minute to swing through one cycle. The crew rode that wave the whole way down, trying to time touchdown to the exact moment the nose was coming back up.

What Is Crew Resource Management, and Why Did It Matter Here?

There was a fourth pilot aboard: Denny Fitch, an off-duty United training check airman whose entire job was teaching pilots to fly the DC-10. He was riding in back as a passenger.

When word reached him that something was badly wrong, Fitch went forward and offered to help. Captain Haynes did the thing that ego and pride so often prevent - he said yes.

Haynes put Fitch on the cockpit floor between the seats, one hand on each throttle. Working those two throttles took a full-time human being, freeing the captain and first officer to concentrate on everything else. Four brains, four sets of hands, nobody guarding their turf.

That’s Crew Resource Management (CRM): using every resource you have - the people in the cockpit, the people on the ground, and the passenger who happens to know something you don’t.

CRM is not just an airline concept. Alone in a Cessna 172, you have resources too:

• Air Traffic Control, who can give you a heading to the nearest runway, report the winds, and roll the trucks before you arrive.
• Flight Service.
• The passenger beside you, who can hold a chart, read a checklist aloud, or simply stay quiet when you need to work.
• The airplane’s own automation.

Using all of it is not weakness. On Flight 232, it was the whole ballgame.

How Did the Landing Unfold?

The crew turned toward Sioux Gateway Airport in Sioux City, Iowa. On the ground, emergency crews staged and ready, and the controller stayed calm - feeding headings, never cluttering the frequency with anything that didn’t matter.

At one point the controller cleared them to land on any runway. Haynes, wrestling an airplane he could not steer, laughed and replied that they’d “like to be particular and make it a runway.” He wasn’t joking because it was funny - he was choosing calm on purpose, because a calm brain works and a panicked brain does not.

They came down toward runway 22, far too fast - more than 200 knots, because without flaps and slats you cannot slow a jet - and sinking faster than any airplane is meant to touch down. Right at the end, the phugoid caught them. The right wing dropped as the right engine spooled, and there was no aileron to pick it back up.

The right wingtip struck first. The airplane cartwheeled, broke apart, and caught fire in the corn beside the runway. And yet 185 of the 296 people aboard walked away.

After the accident, investigators put DC-10 crews in simulators and programmed the exact same total hydraulic failure. Time after time, crews who knew it was coming could not get the airplane down in one piece. What Haynes, Records, Dvorak, and Fitch did that day, most pilots could not repeat even knowing the ending in advance.

What Can a General Aviation Pilot Actually Learn From This?

You’re probably flying singles and light twins, not wide-bodies. Here’s the practical part you can use on your next flight.

1. Fly the airplane you have, not the one you wish you had. When something breaks, your job isn’t to restore the airplane to perfect - it’s to find what still works and use it to reach the ground under control. Trim still works with a jammed yoke. One good mag still makes power. Partial flaps beat no flaps. Find what you’ve got and fly it.

2. Aviate, navigate, communicate - never let the order slip. When the engine coughs, the instinct is to grab the radio or stare at a gauge. Don’t. Pitch for best glide first, pick your spot, then talk. The airplane doesn’t care about your emergency until you make it care by flying it.

3. Use everyone and everything. Declare the emergency early. The word is “Mayday,” said three times, and it costs you nothing but a little pride and some paperwork you’ll happily fill out from the ground. In return you get a controller who clears the airspace, points you at a runway, and has help waiting. That’s a resource - use it.

4. Train the four things you can control. Haynes spent the rest of his life giving a talk about that day, and he credited the outcome to five things: luck, communication, preparation, execution, and cooperation. He admitted luck was part of it. But the other four you can train. You can prepare before the failure. You can execute the memory items cold. You can cooperate instead of freezing or going it alone.

This is exactly what the Airman Certification Standards target in the emergency operations tasks. When an examiner pulls your power abeam the numbers, they aren’t testing whether you memorized a checklist - they’re testing whether you’ll fly the airplane first, work the problem calmly, and use what you’ve got. They want a pilot who stays ahead of the airplane instead of chasing it.

Emergency training can feel like your instructor is only trying to scare you. That’s not it. The point is to build the version of you that - on the worst day of your flying life - reaches for the throttle, the trim, and the radio instead of the panic. That version is built now, in the practice area, on the days when nothing is actually wrong.

The details here come from the National Transportation Safety Board’s accident report on Flight 232 and from Captain Al Haynes himself, who spent years telling the story so the rest of us could learn from it without living it.

Key Takeaways

• United Flight 232 (July 19, 1989) lost all three hydraulic systems when its tail-mounted engine suffered an uncontained fan-disk failure, leaving the DC-10 with no working flight controls.
• The crew steered using only the two wing-engine throttles, fighting a slow phugoid oscillation all the way to the ground.
• 185 of 296 aboard survived a scenario simulators showed was virtually unsurvivable - thanks to skill and teamwork, not luck alone.
• Crew Resource Management was decisive: Captain Haynes accepted help from off-duty check airman Denny Fitch, turning four people into one coordinated crew.
• For any pilot: fly the airplane you have, hold the order aviate–navigate–communicate, declare emergencies early, and train the four things you can control - communication, preparation, execution, and cooperation.