Disasters · Sioux City, Iowa · 1989

The Airliner They Steered With Its Engines

The remaining engines worked, but the familiar controls no longer did.

1. A Failure at Cruise Altitude

On 19 July 1989, United Airlines Flight 232 was travelling from Denver towards Chicago when its tail-mounted engine suffered a catastrophic failure. Pieces escaped the engine and damaged the DC-10’s hydraulic systems. What began as an engine emergency became a much rarer situation: the crew lost the normal means of controlling the aircraft.

The remaining engines worked, but the familiar controls no longer did.

2. Three Systems, One Event

The aircraft had three hydraulic systems to provide redundancy. The engine debris compromised them through the same accident, defeating the separation intended to protect the flight controls. Captain Al Haynes and his crew faced a machine still producing lift and forward thrust, but no longer responding to the usual movements of its control surfaces.

Backup systems could not help when the same damage reached them all.

3. Help From the Cabin

Dennis Fitch, a United training pilot travelling as a passenger, joined the cockpit crew. They shared tasks and used the remaining engines’ thrust to influence direction and descent. Adjusting power was far less precise than normal control, but coordinated work gave them a limited way to guide the aircraft towards an emergency landing rather than surrendering every decision to its motion.

The engines had become an improvised steering system.

4. Sioux City Prepares

Air traffic controllers directed the aircraft towards Sioux City while emergency services prepared on the ground. The crew struggled with oscillations, turns and an unusually difficult approach. Their conversations and decisions later became important examples of crew resource management, not because they found a perfect solution, but because they cooperated under conditions no standard landing technique could resolve.

A runway was available. Reaching it safely remained another problem.

5. The Landing Breaks Apart

Flight 232 struck the ground and broke up during its landing attempt. Fire and wreckage spread across the airport, and rescuers began working among the survivors and victims. The event was both a catastrophic accident and a remarkable survival story; treating either description as the whole account would erase the other part of what happened.

Survival and loss occupied the same wreckage.

6. Counting the Outcome Carefully

Of the 296 people aboard, the NTSB’s formal accident count recorded 111 fatalities and 185 survivors. One seriously injured passenger died after the thirty-day reporting window, leading later histories to use 112 deaths and 184 survivors. The differing numbers reflect that definition and later death, rather than two different groups of people aboard the flight.

Even the familiar totals have a timeline behind them.

7. The Crack Before the Crisis

Investigators traced the engine failure to a fatigue crack that inspection procedures had not detected. Their findings addressed maintenance and human factors as well as the unusual damage to the hydraulic systems. The crew’s response became celebrated, but it did not erase the preventable chain that had placed them in a cockpit with almost no conventional control.

The last minutes showed teamwork. The first cause lay years earlier.