The IMPOSSIBLE Landing

On July 19, 1989, United Airlines Flight 232 lifted off from Denver with the ordinary confidence of a flight that had every reason to believe it would finish like thousands of others.

The sky over Iowa was bright and clear, the ride had been calm, and the aircraft, a DC-10, was cruising on autopilot toward Chicago as if the day itself had nothing unusual in store.

In the cockpit were three experienced professionals who had spent enough time in the air to know what normal looked like and what trouble felt like.

Captain Alfred Haynes was at the center of it all, surrounded by First Officer William Records and Flight Engineer Dudley Dvorak, each of them working in the measured rhythm that aviation demands.

Then, in a single explosive moment, the routine broke. The sound was sudden enough to be felt before it was understood.

A bang, hard and violent, tore through the rear of the aircraft. Dvorak, listening to the machine and reading the aircraft’s behavior the way an expert learns to do, quickly identified the tail engine as the problem.

Records took control of the flight path while Haynes immediately began the engine shutdown checklist, trying to respond to the failure in the same disciplined order that had gotten them through countless other problems.

One engine had failed, and that alone was serious, but not unprecedented. The DC-10 had three engines, and it was built to remain flyable even if one of them was loSt. That, at least, was the first relief.

But relief disappeared quickly. As the crew worked to stabilize the aircraft, Records noticed that the controls were not responding.

Haynes tried the control column himself and found the same thing. Nothing seemed to be working.

The plane could still move through the air, but the usual methods for telling it how to move were gone.

Dvorak then found the explanation that changed everything. The hydraulic fluid was gone. In an airliner like the DC-10, hydraulic pressure is the invisible force that makes the flight controls actually move.

When a pilot turns the control wheel or adjusts the yoke, that input does not directly bend metal and move giant surfaces by muscle alone.

It sends a command through pressurized fluid to the ailerons, rudder, elevators, and other control surfaces.

Without hydraulic pressure, the aircraft might still have engines, lift, and momentum, but it would lose the ability to respond in the normal way.

And that is exactly what happened here. The DC-10 had three hydraulic systems, designed so that if one failed the others could still function.

No standard emergency procedure existed for all three failing at once because the probability was thought to be nearly impossible.

But this flight had now reached that impossible state. The aircraft began banking to the right, and without a way to correct it, the danger became immediate.

If the roll continued, the plane could fully invert, and that would leave no meaningful chance of recovery.

Haynes realized they still had one limited form of control left: engine thruSt. By adjusting the throttles, especially the power on the left engine, he was able to counter some of the roll and bring the plane back toward level flight.

It was crude, awkward, and incredibly difficult, but it worked enough to keep the aircraft in the air.

The reason the hydraulics had failed was not yet known to the crew. All they knew was that they were essentially flying a damaged aircraft with no control surfaces and a rapidly worsening situation.

What later investigations would reveal was that the failure had a frighteningly specific cause. A fan disc in the rear engine had been manufactured with a defect in the metal.

Over time, microscopic cracking had formed and grown with each flight until the disc finally shattered.

The resulting explosion tore through the engine area, severed hydraulic lines, and sent fragments flying into the same region where the other hydraulic lines came close together.

In a matter of moments, all three systems were loSt. That is the kind of failure nobody expects because the overlap of events is too severe.

One broken part, one unlucky shrapnel path, and an entire aircraft becomes nearly ungovernable. When a flight attendant entered the cockpit to check on the situation, the expressions inside told her enough before the words did.

Haynes instructed her to prepare the cabin for an emergency landing. The message was direct and urgent.

She left to begin that process, aware now that something had happened far beyond the range of a simple engine malfunction.

Near the back of first class, a passenger noticed her urgency and stopped her. His name was Dennis Fitch, and unlike most passengers he was not just a traveler waiting helplessly for the outcome.

He was a pilot, and more than that, he was a DC-10 instructor familiar with the very aircraft they were flying in.

The flight attendant told him what had happened: the rear engine was gone, and the captain had reported losing all hydraulics.

Fitch immediately understood the implications. He also understood, with a sinking clarity that most passengers would never have had the background to recognize, that he was likely listening to the same catastrophe that had doomed another aircraft four years earlier.

That other flight was Japan Airlines Flight 123. On August 12, 1985, Japan Airlines Flight 123 had departed Tokyo bound for Osaka, carrying an astonishing number of people aboard a specially configured Boeing 747SR.

It was a domestic variation of the 747 built to maximize capacity for high-demand short routes.

Because the aircraft was intended for frequent takeoffs and landings rather than long international flights, it carried less fuel and more seats.

As a result, it had an extraordinary passenger capacity. There were 524 people on board that evening.

Years earlier, that aircraft had suffered a tail strike during a hard landing. The damage required extensive repair, especially to the pressure bulkhead at the rear of the aircraft.

That bulkhead was one of the most important structures in the plane because it separated the pressurized cabin air from the unpressurized space at the back.

It functioned like a sealed wall that kept the cabin environment stable at altitude. During the repair, however, the lower section of the bulkhead was restored incorrectly.

The problem lay in the splice plate. In a proper repair, one continuous plate bridges the upper and lower parts of the pressure bulkhead so that the force of cabin pressure is distributed evenly across the rivets.

But in this case, the plate had been cut into two sections. That left the top row of rivets carrying a load they were not meant to handle.

The result was a hidden weakness. Each pressurization cycle stressed the repair further. Each flight pushed the crack a little farther along.

And each landing and takeoff nudged the structure closer to failure. For a while the plane remained serviceable.

Then, just twelve minutes into Flight 123, the bulkhead gave way in a sudden decompression event.

Air rushed violently into the unpressurized section behind it, tearing into the rear structure of the aircraft and ripping the vertical stabilizer off the tail.

That failure also severed the hydraulic lines, leaving the crew with no conventional way to control the plane.

Like Flight 232 later, Flight 123 became nearly impossible to steer. The crew was forced to use engine thrust to attempt course corrections, changing power on the four engines in the hope of coaxing the aircraft back toward Tokyo.

The plane entered phugoid motion, a dangerous oscillation where the aircraft climbs, slows, drops, accelerates, then climbs again in a repeating wave.

Without functioning controls, the pilots could only work against that motion by altering thrust in extremely precise ways.

For a while, they made progress. They turned the plane back toward Haneda. But then the Japanese Alps rose ahead.

The mountains turned the situation from desperate to nearly hopeless. The crew tried to steer around them with the few tools they had left, but without hydraulics and without the tail fin, they could not properly stabilize the aircraft.

In the end, Flight 123 struck a ridge near Mount Mikuni after nearly half an hour of uncontrolled flight.

The crash site was remote, and rescue was delayed. When rescuers finally reached the wreckage after daylight returned, they found signs of survival that made the loss of time even more heartbreaking.

Four people had made it through. The rest had not. It became, and remains, the deadliest single-aircraft accident in history.

That was the disaster Dennis Fitch remembered instantly on United 232, because he had studied it, understood it, and now recognized the same nightmare unfolding in real time.

He told the flight attendant what he knew, and then he asked to get to the cockpit.

Captain Haynes accepted the help without hesitation. He did not have the luxury of pride.

The aircraft was already too damaged for ego. Inside the cockpit, the crew explained the only control they still had: differential engine thruSt. By increasing power on one side and reducing it on the other, they could influence the plane’s direction at least partially.

It was nowhere near enough for normal flight, but it might be enough to survive long enough to find a place to land.

Fitch stepped into the middle seat area and began working the throttles while Haynes and Records called out commands and adjustments based on what they could see outside.

Even with all that effort, the crew realized they were too far from Chicago to make it.

They needed a closer destination, and air traffic control helped identify Sioux City, Iowa, as the nearest possible field they might reach.

The aircraft was enormous, damaged, and difficult to predict, but Sioux City offered the best chance.

Haynes advised the cabin crew to prepare passengers for a hard landing. He told them the brace command would be announced over the PA system and instructed them to get everyone ready.

Back in the cabin, the flight attendants began moving row by row, explaining how to brace and how to prepare for impact.

Then they noticed something that made the situation even harder. There were many children on board, including fifty-two minors, and several were traveling alone because of a promotion that had made the flight unusually crowded with young passengers.

Four children were too young to occupy seats on their own and had to be placed on the floor in front of their parents, surrounded by pillows in the standard emergency procedure for infants and toddlers.

Passengers helped one another. Adults made room for children who were traveling alone. Flight attendants moved with speed and calm despite the fear in the cabin.

Every action now had one purpose: survive the coming landing. In the cockpit, the team continued to wrestle the aircraft toward Sioux City.

The plane still wanted to turn right. It kept drifting, resisting, as if the invisible damage inside it had its own will.

Haynes, Records, and Fitch used every remaining trick they had. More and less power. Left and right.

Small corrections. Large corrections. Any movement that could keep the nose pointed in the right direction.

As they approached the airport, they began dumping fuel to reduce weight. Every pound mattered.

They needed the aircraft to come down as lightly as possible, even though the plane had no effective flaps and could not slow the way it should have.

That meant the landing would be much faster than normal, far faster than the runway and the aircraft ideally wanted.

Sioux City Airport had three runways, though one had been permanently closed by then. The crew tried to line up with runway 31.

Emergency responders positioned themselves near the closed runway 22, preparing for the worst and hoping they would not need to use it.

But with only minutes left, Haynes realized they were not aligned correctly for the active runway at all.

The aircraft had slipped off course. Yet in a twist of luck that felt almost impossible in the moment, they were nearly lined up with the closed runway.

Air traffic control cleared them to land on any runway available. There was a brief, strained exchange in the cockpit as the crew realized that the closed runway might actually be the best available option.

Emergency personnel rushed to clear it as best they could. The airport offered a long stretch of pavement ending in open field, which at least removed one obstacle if the landing went poorly.

Then came the final moments. Haynes called for the brace. The passengers held tight. The aircraft came in too fast, too high, too difficult to correct at the end.

The right wing dropped. The plane struck the ground, broke apart, and erupted into fire as it skidded across the runway and out toward nearby fields.

Emergency crews ran toward the wreckage expecting the worSt. What they found was chaos, but not total loss.

Passengers were climbing or crawling out of the torn fuselage. Some helped one another out.

Others were already assisting the injured before the responders reached them. One passenger, after escaping the burning wreckage, heard a baby crying from inside the plane and ran back into the wreckage to retrieve the child.

The baby had somehow ended up trapped in an overhead bin during impact. He brought the infant out and reunited her with her mother.

In another part of the wreckage, Flight Engineer Dudley Dvorak was found waving his arms from the broken cockpit section, helping rescuers locate the crew.

Captain Haynes, First Officer Records, Flight Engineer Dvorak, and Dennis Fitch all survived, though critically hurt.

They were extracted and rushed to medical care along with other survivors. By the time the rescue was complete, 113 people had been lost and 183 had survived.

Eleven children were among those who did not make it. The numbers were staggering, but what stood out even more was that more than half of the aircraft’s occupants had managed to survive a crash that should have seemed impossible to live through.

The skill of the crew, the coordination inside the cabin, the improvisation of emergency responders, and an extraordinary amount of luck all combined to create one of the most remarkable survival stories in aviation history.

In the broader history of flight, both United 232 and Japan Airlines 123 became milestones for a reason that has less to do with the aircraft themselves than with the people flying them.

Both planes lost all hydraulic control. Both crews had to use engine thrust as a substitute for lost systems.

Both events showed how close aviation can come to complete catastrophe when a hidden defect or repair failure tears away the basic tools of flight.

But the most important legacy of United 232 was not simply that it survived. It became a defining example of crew resource management, the idea that cockpit authority must be paired with open communication, shared problem solving, and the willingness to use every available mind in the cockpit rather than relying on rank alone.

Haynes, Records, Dvorak, and Fitch had to work as a team. They had to speak constantly, hear one another, and adjust quickly.

The flight did not become survivable because one person was brilliant. It became survivable because several people were allowed to contribute everything they had, exactly when it mattered.

That lesson did not emerge in a vacuum. Aviation had to learn it through far worse experiences, including the Tenerife disaster in 1977, where two 747s collided on the runway after a catastrophic breakdown in communication.

From those earlier failures, aviation culture changed. Procedures changed. Cockpit interaction changed. The industry learned, painfully, that clear speaking and shared authority can matter as much as technical skill.

That is why Flight 232 is remembered not only as a crash, but as a case study in what teamwork can do when technology fails.

The aircraft lost the systems everyone expects to rely on. The crew lost the ability to do things the normal way.

Yet they still found a path that brought many passengers home. And that is what makes the story linger.

Two flights, separated by four years, different countries, different aircraft, different terrain, and different outcomes, all tied together by the same terrifying reality: if every hydraulic system fails, the plane may still fly for a while, but flying and controlling are not the same thing.

One crew faced mountains. One crew faced a flat field. One aircraft lost its tail.

One did not. One ended in nearly total loss. The other became one of the most extraordinary survivals in aviation.

What they share is not just tragedy or heroism, but the reminder that modern flight depends on hidden systems most passengers never see, and that when those systems fail, the difference between disaster and survival can rest on a few people talking clearly, thinking fast, and refusing to give up even when the aircraft itself has almost nothing left to give.