Understanding the Causes of the Uruguayan Plane Incident

The 1972 Andes Plane Crash: What Brought Down the Uruguayan Air Force Flight

The 1972 Andes crash discussions have gotten complicated with all the “how could experienced pilots miscalculate their position so badly over the Andes” debates, the aviation safety lessons learned versus the survival story comparisons, and “what specifically went wrong technically and procedurally that caused a military flight crew to begin descending while still in the mountains” conversations flying around. As someone who has spent years studying aviation accident investigations and the specific combination of human factors, navigation limitations, and decision-making errors that turn routine flights into tragedies, I learned everything there is to know about the 1972 Fairchild FH-227 crash in the Andes. Today, I will share it all with you.

But what caused the Uruguayan plane crash, really? In essence, it was a compounding sequence of navigation error, inadequate weather planning, overconfidence in dead-reckoning position estimates, and the descent into mountainous terrain that resulted from the crew incorrectly believing they had cleared the Andes — a chain of decisions and circumstances that aviation safety professionals have studied for decades because it contains lessons about crew resource management and mountain flying that remain relevant to every generation of pilots operating in terrain. But it’s much more than pilot error. For aviation safety analysts, the 1972 crash illustrates how the navigation technology of the era created specific vulnerabilities that modern GPS and terrain awareness systems have largely — but not completely — eliminated.

The Flight and Route Context

Uruguayan Air Force Flight 571 departed Mendoza, Argentina on October 13, 1972, carrying 45 people including the Old Christians Club rugby team from Montevideo, traveling to Santiago, Chile. The route required crossing the Andes through a pass, a crossing that the crew planned using visual navigation and dead reckoning — estimating position by calculating time elapsed and speed since a known reference point. Weather had already forced the flight to divert and overnight in Mendoza; the departure the following day carried forward optimism about weather and position that the actual conditions didn’t support.

The Navigation Error: How the Crew Lost Position

The crew’s fatal error was misjudging their position relative to the Curicó waypoint on the Chilean side of the Andes. Using dead reckoning in a region where strong winds can dramatically affect groundspeed versus airspeed, the crew calculated they had cleared the mountains and began descending while still over the high terrain. Don’t make my mistake of treating this as simple incompetence — at least if you’re studying the accident from an aviation safety perspective, because the navigation limitations of 1972 meant that crews crossing the Andes had limited independent position verification capability, and a position error of even a few minutes of flying time in that terrain could place an aircraft over peaks rather than passes.

Aircraft Systems and Weather Factors

The Fairchild FH-227D was properly maintained and mechanically airworthy. The crash was not a mechanical failure — it was a controlled aircraft flown into terrain. The weather conditions, while challenging, were not beyond the aircraft’s capabilities. What the weather contributed was reduced visibility and the psychological pressure that deteriorating conditions create on crews who want to complete the crossing and reach their destination. That’s what makes the 1972 Andes accident endearing to human factors researchers studying controlled flight into terrain — the chain of pressure, position uncertainty, and commitment to the descent decision illustrates how confirmation bias and schedule pressure interact to produce decisions that seem reasonable to the crew and catastrophic in retrospect.

The Crash and Immediate Aftermath

The aircraft struck the mountain at approximately 11,800 feet elevation, with the impact shearing off the wings and tail section before the fuselage continued as a toboggan down the snow slope. Twelve people died during the crash itself; others died in the subsequent days from injuries and exposure. The 27 survivors faced conditions at high altitude in the Andes with minimal equipment, no radio contact, and no immediate prospect of rescue — the search had been suspended after eight days without finding the wreckage, which was essentially invisible against the snow-covered mountains from the air.

Impact on Mountain Flying Safety

The 1972 crash contributed directly to improved emphasis on mountain flying training and the limitations of dead-reckoning navigation in terrain. First, you should understand how completely GPS and terrain awareness systems have changed the risk profile of mountain flying since 1972 — at least if you’re evaluating the relevance of the accident’s lessons to modern operations, because a GPWS (Ground Proximity Warning System) or TAWS (Terrain Awareness and Warning System) would almost certainly have provided the crew warning before terrain impact, and GPS would have provided independent position confirmation that the dead-reckoning calculation was wrong. The accident’s primary modern relevance is as a human factors case study in the dangers of commitment bias and schedule pressure overriding appropriate caution.

The Survival Story and its Aviation Legacy

The 16 survivors who were rescued after 72 days in the Andes owe their lives to the decision of two survivors to make a 10-day trek across the mountains to find help — a decision that proved correct when official search operations had been abandoned as unsuccessful. The crash has generated extensive coverage in books and films because the survival elements are genuinely extraordinary. For aviation safety professionals, however, the crash is primarily a navigational accident that illustrates the consequences of position uncertainty in mountainous terrain — a lesson that remains relevant even as navigation technology has dramatically reduced the specific vulnerability that the 1972 crew faced.

Marcus Chen

Marcus Chen

Author & Expert

Marcus is a defense and aerospace journalist covering military aviation, fighter aircraft, and defense technology. Former defense industry analyst with expertise in tactical aviation systems and next-generation aircraft programs.

369 Articles
View All Posts